The Argument Is Not About the Work

Three people leave the same strategy review. One believes the plan is feasible. One thinks it needs major revision. One is certain it will be ignored.

None of them is looking at different evidence. They are holding different attitudes toward the same object.

Most friction in strategy, design, and architecture work follows this pattern. A developer says "we cannot do this." That is not a fact about the work. It is a stance — possibly epistemic (known to be technically impossible), possibly deontic (known to be prohibited), possibly intentional (not something they will pursue). Each stance requires a different response. Treating them as interchangeable is how governance arguments run for months without resolution.

The confusion compounds in larger groups. When a team declares consensus on a plan, three distinct conditions must hold: each party must believe they have agreed, believe that the other party has agreed, and believe the other party understands the commitment they have made. These are not the same condition. Most agreement failures trace not to disagreement on substance, but to one of these conditions being absent from the conversation.

Attitudes take several forms. What an agent believes about the work — epistemic attitudes: known, unknown, known unknown, unknown unknown. What they communicate — from informative through guided and recommended to directed and required. What they intend for it. And how they characterise its current status across the full lifecycle: considered, desired, intended, realised, sensed, interpreted.

None of this is theoretical. The practitioner who can name the attitude in play, rather than arguing about the object the attitude is directed at, resolves disagreements faster and with less collateral damage. The confusion in most strategic debates is not about the work itself. It is about differing attitudes toward the work, held without anyone recognising the distinction.

The vocabulary for naming attitudes precisely is developed in the full article: Beyond Blueprints: How Agents Relate to Strategy, Design, Architecture, and Interweave.