James CookTechnology Strategist & Architect
All insights

Leadership

Design the decision rights before designing the solution.

Teams make better products when they establish who provides evidence, names constraints, recommends, decides, and owns the result before reviewing concepts.

An architectural plan with a pencil and measurement tools.
Field note 37 · Leadership · Photo by Soham Banerjee on Unsplash

A team should know how a decision will be made before it has something beautiful to argue about.

01

Design reviews expose governance

The first concept review often reveals that nobody agreed who could decide. Marketing owns the message, sales claims the customer, technology owns feasibility, brand owns expression, and executives own the ability to overrule everyone.

Without a decision model, the solution becomes the battlefield where organizational ambiguity is resolved badly.

02

Give each role a purpose

Identify who supplies evidence, who defines constraints, who recommends a direction, who makes the decision, and who owns the result. These roles can be collaborative without being interchangeable.

The accountable decision maker should have enough context to choose and enough authority to remain responsible when the evidence later changes.

When decision rights are improvised during review, hierarchy replaces evidence.
03

Set escalation before conflict

Teams need a clear path when legal, commercial, technical, and customer needs collide. Decide which principles govern the tradeoff and who resolves it before the urgent meeting.

This prevents escalation from becoming a contest of access to the most senior executive. It also lets specialists contribute forcefully without pretending every constraint is absolute.

04

Govern the decision, then design

Decision rights do not make judgment automatic. They make judgment legible. People know how input becomes action and where accountability remains.

Design the decision rights before designing the solution. The quality of the work will improve because the team can focus on evidence instead of authority.

About the author

James Cook

James is a technology strategist and architect who helps organizations build, modernize, and manage websites, applications, and the systems behind them.

More about James

Continue reading

01

Strategy

The smallest decisive intervention is often the most strategic.

Read the essay
02

Leadership

Alignment is not accountability.

Read the essay
03

Operating capability

The team should survive the launch.

Read the essay

What comes next

What are you trying to build, fix, or change?

Bring the context. We will make the next step clear.

Schedule a consultation

An honest conversation makes the next step clear.

Tell me what you are trying to build, fix, or change. We will use 30 minutes to understand the need, clarify how I can help, and agree on what comes next.

Free 30-minute initial consultation · Remote nationwide