Consensus system

Use this lens when value may exist but adoption, approval, payment, or relationship does not follow.

Locate the disagreement

• Perception: the same feature may be must-have, performance, attractive, indifferent, or reverse for different users.
• Identity: the user profile describes current context; the user persona also describes who the user wants to become or be seen as.
• Scene: specify person, event, task, place, time, frequency, and perceived intensity.
• Interest: map user, beneficiary, payer, decision-maker, implementer, compliance owner, blocker, and affected party.

For each stakeholder record influence, benefit, cost, risk, veto power, and the minimum agreement required. Do not average conflicting roles into a generic “user.”

From message to action

Treat positioning and communication as testable translations of proven value. Define which evidence, wording, scene, and messenger should cause which next action. Attention without qualified action is not consensus.

Relationship can progress through need, liking, identification, and belonging. Deeper labels imply resource sharing and responsibility; do not claim a community or partnership that the product does not support.

Source boundary: synthesized from True Demand, Part Two. Use source material critically; persuasion must not conceal harm or replace informed choice.