How we work.

The dominant failure mode in strategy work is not that the answers are wrong. It's that the work doesn't carry its own uncertainty. Claims arrive without sources. Caveats live in a separate notes section. Hedging language stands in for verification. The deliverable looks confident; the reasoning underneath is brittle.

The result is work that survives the meeting it was made for and fails the test of being re-read six months later. The recommendations get acted on or quietly shelved without ever being examined.

Our discipline exists to prevent that. Three written playbooks — for inquiry, for writing, for design — applied to every artifact we produce.

A response procedure that prioritizes thoroughness, honesty about gaps, and explicit use of available evidence over fluent confidence. The discipline closes the failure modes that hedging-language and performed-thoroughness create.

The plan is shown before the work, and executed

Every substantive engagement begins with a written plan — what will be examined, what sources will be used, what the deliverable will contain. Deviations from the plan are surfaced, not absorbed.

Verification has granularity

"I saw it on a page" is not the same as "I confirmed it at the precision the deliverable implies." Both technically count as verified. Only one is honest. The work distinguishes them.

Alternative reads, named explicitly

For every positioning claim, archetype determination, or strategic interpretation, the alternative read considered is named — along with the counter-evidence that ruled it out. This is the structural defense against the most common analytical failure: locking onto the first plausible reading.

Iterative improvement is not optional

Before delivery, every deliverable gets a structured second pass with named checks. The pass catches what the first draft missed, and the checks are recorded so the methodology improves over time.

A final-polish pass on every document we produce — so the client receives prose that is already clean, rather than prose they have to clean up afterward. The discipline runs four passes in order, each with a named focus.

Set the register

The intended formality of the document is decided before the writing starts — formal, professional, neutral, informal, casual. The decision shapes every subsequent pass and prevents the most common writing failure: a document that doesn't know what voice it's speaking in.

Correctness pass

Grammar, punctuation, mechanical errors. Quiet fixes — typos, capitalization, the punctuation that changes meaning. Nothing that shifts the substance of a claim is changed without flagging it.

Clarity pass

Wordy phrasing tightened, weak-passive constructions activated, uneven sentence structure smoothed. The pass that turns competent writing into precise writing.

Engagement pass

Word choice and verb energy strengthened in a way that fits the chosen register. The discipline cares about how the document reads, not only what it says.

The judgment a senior design director applies to every interface and every printed artifact. Not style, not decoration — the systems that produce work people remember, use effortlessly, and trust.

Direction before decoration

Every artifact starts with a direction: the aesthetic commitment the piece is making. Without it, work decays into decorated noise.

Tokens before screens

Color, type, spacing, and motion are defined as a token system before the first surface is laid out. Coherence at scale comes from this discipline — and the lack of it is the signature flaw in most AI-generated UI work.

States before screens

Every component is designed in its full set of states — default, hover, focus, active, disabled, loading, empty, error — before any of them is treated as finished. Skipped states are the cracks production work falls through.

Review with named checks

Like rigorous inquiry, design closes with a structured pass — accessibility, contrast, hierarchy, type discipline, motion appropriateness. Each check is named, each is verified, none is presumed.