Mountain Stone.

The Decision Architecture.

The Playbook / System 03 · Structure

The documented matrix of who decides what across the growth function.

System
03/10
Class
Structure
Governs
Growth decisions
Principle
Rules before data
The Playbook
THE PROBLEM

Too many decisions start after the number moves.

A result changes and the team decides what it means in the moment. The action may be perfectly reasonable, but if the rule only appears after the data does, the same situation can produce a different answer next time.

Over time, decisions become harder to explain, delegate and learn from.

WHEN THE RULE COMES FIRST

Decision Architecture writes the rule before the situation arrives. When the condition is met, the team already knows what it means, what happens next and who has the authority to act.

Judgment still matters. It just stops being reinvented every time.

The principle

Decisions move faster when the rule is already there.

Decision Architecture writes the basis for recurring decisions in advance, so the answer doesn’t change depending on who is looking at the data.

The system

The Architecture has two working parts.

The Decision Matrix sets who can act. The Standing Rules Registry sets the rule they act against. Routine decisions can move without another round of interpretation, while anything that still needs judgment stays with the strategist.

WHERE THE RULES COME FROM

We build them from decisions the account is already making. When the same judgment call keeps coming up, it becomes a candidate for a standing rule. If the answer still depends on context, it stays a judgment call.

The goal isn’t to turn every decision into a rule. It’s to stop solving the same ones from scratch.

In operation

Four columns.
Every decision routed.

The matrix makes clear who owns which decisions, so it doesn’t have to be worked out in the moment.

The founder
Brand voice
Product roadmap
Capital
Hiring
Executive direction
The growth operator
Scaling within ceilings
Kill decisions on margin
Creative direction
Bid strategy & audiences
Cross-channel coordination
The internal team
Execution within scope
Flow tweaks
Daily operational work
The calls they have the data for
Joint · On cadence
New market launches
New product lines
Brand pivots
Strategic partnerships
The team surface · Ownership

Each part of the team has decisions it can make without waiting for approval.

The boundaries are written down before the work starts.

The brand surface · Escalation

When a decision falls outside those boundaries, the route is already clear.

It goes to the person with the authority to make it, rather than becoming a debate about who should.

The test

Three questions.

Answer them honestly.

01The last time a campaign changed, could the team point to the rule that triggered the decision?
02If the same numbers showed up tomorrow, would the same decision be made?
03Does the team know which decisions it can make against a standing rule and which still require judgment?

If the answer depends on who happens to be looking at the numbers, the Architecture isn’t doing its job yet.

What speed actually looks like

When the rules are clear, routine decisions move without another meeting. The founder stays on the decisions that actually need founder judgment, and the same question doesn’t have to be solved twice.

The Decision Architecture
The fastest decisions are the ones the business has already learned how to make.