The Uncomfortable Work of Explicitness

The reason many professionals resist outcome-first direction is that it requires making your implicit standards explicit. You have to think about what good looks like and say it out loud, to someone else, before you see the work. This is uncomfortable. Your standards might be inconsistent. They might change depending on context in ways you haven't fully articulated. Writing them down reveals the gaps.

This is also the whole point. The discipline of writing a real outcome brief forces you to clarify your own thinking. You discover what you actually care about, as opposed to what you think you should care about. You learn where you've been rationalizing low standards, and where you've been optimizing for the wrong thing. The exercise itself develops your director's eye.

Moreover, writing outcome briefs changes how you work with executors — human or AI. Instead of a cycle of vague instruction, plausible-but-wrong output, frustration, and rewriting, you get a cycle of clear outcome definition, evaluated output, and real feedback. The executor knows what you wanted. You can evaluate whether they understood. You can iterate on the standard itself, not just the output.

The transition from process-first to outcome-first feels slower at first. You spend more time upfront in clarity and less time correcting at the end. But that slowness is a feature, not a bug. It's the slowness of doing the cognitive work upfront instead of distributing it across multiple iterations of correction and rework.