Distinctions · Conceptual Precision

Most confusion is a naming problem.

Two things are treated as the same when they are not. Decisions that should differ are made identically. Distinctions are the tool that separates them — precisely enough to act on the difference.

A distinction is not a definition. It is a separation — precise enough to change a decision.

Effort Value

Effort is what you put in. Value is what changes for someone else. They are not correlated. The hardest work can create no value. The simplest insight can create enormous value. Rewarding effort rather than value is how organisations optimise the wrong thing.

Importance Scarcity

Something can be critical to survival and command almost no premium if everyone can provide it. Markets reward scarcity, not importance. Oxygen is essential. Oxygen is abundant. The premium is near zero. Strategy built on importance without scarcity is charity, not business.

Visible value Dark matter

Visible value is what happened — the product shipped, the cost reduced, the breach detected. Dark matter is what didn't happen — the crisis prevented, the reputation maintained, the optionality preserved. Enormous mass, zero emission. The measurement system cannot register it. Its loss is catastrophic.

Current value Future value

What commands a premium today is not what will command a premium tomorrow. The basis of competition shifts as scarcity shifts. Optimising current value while ignoring future value is how market leaders become case studies in disruption.

Execution Differentiation

Execution earns the right to stay in the conversation. Differentiation earns the premium. When execution becomes abundant — through technology, commoditisation, or internal capability — it stops differentiating. Competing harder on execution when execution is no longer scarce is a strategic error, not a capability gap.

Trust Influence

Trust earns access. Influence earns a seat before decisions are made. A firm can be deeply trusted and still receive every strategic brief after it has already been written. Trust is not influence. Confusing them is where most mature service relationships stall.

Participation Ownership

Participation shares the upside. Ownership shares the obligation — including the downside. Decision rights do not follow contribution or trust. They follow obligation. The firm that is expected to carry accountability when outcomes fail is the firm the client eventually gives the keys to.

Position Direction

Position is where you are. Direction is where you are pointed. A dashboard tells you position — utilisation, revenue, satisfaction scores. Almost nothing on the standard dashboard tells you whether you are still pointed at the customer. Organisations mistake healthy position for healthy direction and are surprised when customers leave.

Operational health Strategic health

An organisation can be operationally excellent — delivering consistently, hitting every target — while moving strategically in the wrong direction. Operational metrics measure whether you are doing the thing right. Strategic health measures whether you are doing the right thing. Both can be true or false independently.

Product roadmap Customer roadmap

A product roadmap describes what you plan to build. A customer roadmap describes where your customer is trying to go. They are not the same document, and organisations that confuse them build increasingly sophisticated products that solve increasingly irrelevant problems.

Observation Interpretation

An observation is what can be verified. An interpretation is what it might mean. Most meetings skip directly from observation to decision, treating the interpretation as obvious. It never is. The fastest path to the wrong conclusion is a confident interpretation that was never made explicit.

The stated problem The actual problem

The stated problem is what the client says they need. The actual problem is the constraint that is generating it. Solving the stated problem often makes the actual problem worse. Discovery is the discipline of finding the constraint before proposing the solution.

Symptom Constraint

A symptom is what you see. A constraint is what is binding the system. Treating symptoms relieves discomfort but does not improve performance. Removing the constraint changes what is possible. Most organisational problem-solving is symptom management disguised as strategy.

A useful distinction should help you see something that was previously invisible — and change a decision you would have made identically before.