The space your team builds within.

A name, a priority, a timeframe, a status. The “why” — why this, why now, what changes if you win. The beliefs this bet rests on, so the argument stays legible when the evidence shifts. The signals that will tell you it’s working, and the ones that will tell you it isn’t.

Then the operational half: the direction to build in, the boundaries that can’t be crossed, and a handful of concrete anti-patterns — “a bad solution would look like this” — so nobody has to infer what you meant.

A builder reading the area knows what to build, how to build it, and what not to build. Without a meeting. Without waiting.

Three to five areas. That’s it. That’s the entire strategic surface for the quarter — and it’s also everything a well-run team needs to operate coherently.

Defining an area is a morning’s work. You write the why, link the beliefs it rests on, define what success looks like, set direction, draw boundaries, and name the anti-patterns. The principles catalogue and your existing thinking do most of the heavy lifting — most of what you’re doing is externalising what’s already in your head.

Once the areas exist, every build, every agent call, every stakeholder question resolves against them. The areas stop being a document and start being the operating surface.

Before. A BA asks “should we prefill the address field?” You answer. A week later a different BA asks the same thing in a different channel. You answer again, slightly differently. Six months later the product has seven small inconsistencies you can trace to the fact that you were the cache.

After. The Activation Flow area says “direction: pre-fill from existing data, cut setup to one screen” and “anti-pattern: don’t complete steps on behalf of the user.” Both BAs read the same thing. Both agents read the same thing. The answer is the same in April and October.

Active, paused, completed, abandoned. When you pause an area, the guidance pauses with it — compliance checks stop enforcing boundaries on a bet you’re no longer making. When you abandon one, the history stays in the Direction log. Next quarter you’ll know why you stopped, not just that you did.