Reader resources for The Systems-Building LeaderFind your starting point ↗
Reader resources for The Systems-Building LeaderFind your starting point ↗
Use the book
One guide for each chapter: the idea in brief, what the chapter covers, its Field Guide Tool, questions for your team, and where to read further.
Part OneChapters 1 to 6
Part One makes the case that trust is an engineering problem. Not a personality trait, not a relational achievement, but a designed condition that either exists in the structure of how the organization operates or does not exist at all.
01
The team liked her. That was never the question.
Tool #1: The Trust Diagnostic
Read the guide →
02
Busyness is not the same thing as value.
Tool #2: The Stewardship Audit
Read the guide →
03
Micromanagement is rarely a control problem. It is almost always a clarity failure.
Tool #3: The Accountability Design Worksheet
Read the guide →
04
What you say matters far less than what you do after you say it.
Tool #4: The Leader Voice Audit
Read the guide →
05
Don’t mistake smooth meetings as evidence of alignment. They are sometimes evidence of the opposite.
Tool #5: The Safety Diagnostic
Read the guide →
06
Change fatigue is more about the instability of meaning than the volume of change
Tool #6: The Change Cadence Planner
Read the guide →
Part TwoChapters 7 to 12
Part Two makes the case that expertise is not synonymous with intelligence. The intelligent leader who hasn’t built the structural disciplines of systems thinking, metrics governance, uncertainty judgment, operating cadence, and executive calibration is producing results that depend on their personal cognitive engagement with every significant problem. When they step back, the results degrade. When they scale, the intelligence doesn’t replicate. When they leave, the capability leaves with them.
07
Being the smartest person in the room is not the same as being the most effective.
Tool #7: The Expertise Self-Assessment
Read the guide →
08
Why almost every recurring problem is a system problem in disguise
Tool #8: The Root Cause Worksheet
Read the guide →
09
A metric that never triggers a decision is a ritual, not a metric.
Tool #9: The Metrics Governance Audit
Read the guide →
10
Waiting for certainty is a decision that is rarely the right one.
Tool #10: The Decision Quality Checklist
Read the guide →
11
Organizations do not improve because people try harder. They improve because someone built a system for turning experience into learning.
Tool #11: The Learning Loop Design Template
Read the guide →
12
Strategy is not what you choose to do. It is what you choose not to do, and whether you are honest about it.
Tool #12: The Strategic Tradeoff Framework
Read the guide →
Part ThreeChapters 13 to 18
Part Three makes the case that delegating is not empowerment. The leader who announces empowerment without building the structural conditions for it produces a formal change in authority that produces no change in behavior, because behavior is shaped by structure and not by announcements.
13
Granting permission is not a structure. Having good intention is not a system. Empowerment begins with design.
Tool #13: The Empowerment Readiness Assessment
Read the guide →
14
If the organization stops working when you leave, you have not built an organization. You have built a dependency.
Tool #14: The Escalation Audit
Read the guide →
15
Consistency is a virtue in values. In management style, it is often a failure of diagnosis.
Tool #15: The Leadership Response Diagnostic
Read the guide →
16
The best development happens when someone designs for it.
Tool #16: The Capability Builder Conversation Guide
Read the guide →
17
Change does not fail at the launch. It fails in the months that follow, when nobody is watching closely anymore.
Tool #17: The Change Reinforcement Diagnostic
Read the guide →
18
Empowerment is proven when ownership holds, not when it rises.
Tool #18: The Sustainability Audit
Read the guide →