Companion working session
Leadership Architecture Workshop
The guide section “Rebuild the Leadership Architecture the Second Curve Requires,” condensed into a facilitated agenda. Seven blocks, timed, each one leaving the room with a named output rather than a discussion.
3 hours 45 minutes · 7 blocks · Decision rights, cadence, development path
Who is in the room
The owner or CEO plus the full executive team — every person who holds or wants a decision domain. Six to ten people is the working range; above twelve, split the architecture blocks into two sessions.
Pre-work
- Each participant lists the five decisions they most often escalate, and the five they most often absorb from below.
- The owner or CEO lists every recurring decision they alone can make today.
- Pull the last eight weeks of standing meetings: purpose, attendees, and the output each one actually produced.
- Each leader writes one sentence on the capability they believe their next role requires.
- Run the Governance Readiness Diagnostic individually — bring the Executive Report to the session.
Materials
- Printed decision inventory from pre-work, one page per participant
- Wall space for the decision-rights grid (decide / consult / inform / escalate)
- Blank operating cadence calendar — governance, executive, functional, team
- One development-path card per leader
- Individual Governance Readiness Executive Reports
01
20 min · The Principle
Dependency is designed, not chosen
Establish that upward decision drift is a structural output, not a character flaw — so the session can work on design rather than on people.
Prompts in the room
- Name a decision that consistently comes to this table that should not. Who could hold it?
- The last time someone made that call without asking — what happened next?
- Where is the owner currently the bottleneck for judgment that needs to happen in parallel?
Output
A shared statement of the dependency the group is trying to design out, in one sentence.
Facilitator note
Stop the room the first time a name is offered as the cause. Redirect to the structure: where was the authority placed, and was it defended when tested?
02
25 min · The Philosophy
Capability compounds; dependency does not
Agree that building leaders is the work, and define what this team means by a leadership system rather than a set of strong individuals.
Prompts in the room
- What would be true about this team if the owner were unreachable for six weeks?
- Where do we disagree after meetings instead of inside them, and what makes the room unsafe for it?
- Which decisions are we currently protecting people from making?
Output
Four agreed attributes of the leadership system: decision rights, shared outcomes, closing cadence, and disagreement in the room.
Facilitator note
Keep this at the level of the system. If it becomes a performance conversation about an individual, park it for a one-to-one and return to design.
03
55 min · The Architecture
Build the decision-rights grid
Place every recurring decision: who decides, who is consulted, who is informed, and what threshold escalates.
Prompts in the room
- Read the decision aloud. Who decides — one name, not a committee?
- What is the dollar, risk, or reputational threshold that moves this up a level?
- Who is genuinely consulted before, and who only needs to know after?
Output
A written decision-rights grid covering every recurring decision from the pre-work inventory, with escalation thresholds.
Facilitator note
Force single owners. 'The leadership team decides' is the sound of the old architecture. Write the grid where everyone can see it, and read the contested rows twice.
04
40 min · The Architecture
Set the operating cadence
Design the rhythm that converts strategy into closed commitments: governance, executive, functional, and team reviews.
Prompts in the room
- For each standing meeting: what is its purpose, and what output must exist when it ends?
- Which meeting closes commitments, and which one only reports?
- What gets deleted today because nothing it produces is used?
Output
A one-page cadence calendar with a purpose and a required output for every recurring meeting.
Facilitator note
Any meeting with no named output is a candidate for deletion. Protect the governance layer — it is the one most often collapsed into the executive meeting.
05
35 min · The Architecture
Name the development path
Give every leader one real decision domain they own outright and one next capability attached to a live assignment.
Prompts in the room
- Which decision domain do you own outright as of today — no confirmation required?
- What is your one next capability, and which live assignment will require it?
- How will that capability be assessed, and in which review?
Output
One development card per leader: owned domain, next capability, live assignment, review point.
Facilitator note
Capability targets must land in the same rhythm as financial ones. If the assignment is hypothetical, the capability will not develop — insist on live work.
06
25 min · The Outcome
Define the signals of a working design
Agree the observable evidence that the new leadership architecture is holding, and when it will be reviewed.
Prompts in the room
- How much shorter should the executive meeting be in ninety days?
- How many levels lower should the decisions on our grid be made?
- What percentage of the owner's calendar moves from operating to architecting?
Output
Three to five measurable signals with a ninety-day review date on the cadence calendar.
Facilitator note
Push for numbers and dates. Signals without a review date become intentions again — exactly the failure the cadence exists to prevent.
07
25 min · The Action
Commit, defend, and schedule
Close the session with named owners, dates, and an explicit agreement on how the grid is defended the first time it is tested.
Prompts in the room
- Which row of the grid will be tested first, and how will we respond?
- Who publishes the grid and the cadence, and by when?
- What is the first decision each of us will make this week without asking?
Output
A published commitment sheet: owner and date for the grid, the cadence, and each development card, plus the agreed defence of the first test.
Facilitator note
The first test sets the real rule. Have the group rehearse it out loud before they leave the room.
Within 5 days
Publish the decision-rights grid and cadence calendar to everyone affected, not just attendees.
Week 2
Run the first cadence cycle exactly as designed, including the governance layer.
Day 30
Review escalations: any decision that came up a level tells you which row needs defending or replacing.
Day 90
Re-run the Governance Readiness Diagnostic and compare against the signals agreed in Block 06.
Architecture determines performance. When the leadership system is designed, the second curve stops being a plan and starts being a capability.