ALIGN
Week 3–4
Assessment without alignment is just a report that gathers dust. The Align phase takes everything you learned in Assess and designs the operating system your company needs — the cadences, the frameworks, the decision rights, and the communication architecture.
Key Deliverable
A complete Operating System Blueprint: cadence design, KPI framework, decision rights matrix, and communication protocol — ready to implement.
Modules
The building blocks of the align phase.
Operating Cadence Design
Weekly rhythms, monthly reviews, quarterly planning.
Design the heartbeat of your organization. Daily standups, weekly team meetings, monthly business reviews, quarterly planning sessions — each with a clear purpose, agenda, participants, and output.
Common Mistake
Making meetings the cadence instead of the work. The cadence is the rhythm of decisions and accountability. Meetings are just one mechanism.
What Good Looks Like
A healthy operating cadence means every person knows: what happens daily, weekly, monthly, and quarterly — and what's expected of them in each cycle.
OKR/KPI Framework
What matters, measured how, reviewed when.
Build a measurement framework that connects company objectives to team-level key results to individual metrics. Not 47 KPIs — the 5-8 that actually drive the business.
Common Mistake
Setting OKRs once per quarter and never looking at them again. OKRs aren't a planning exercise. They're an operating tool.
What Good Looks Like
Every team should have no more than 3-5 metrics they own. If you can't fit your KPIs on a single page, you have too many.
Decision Rights Architecture
RACI, escalation paths, autonomy boundaries.
Define who decides what, at every level. Build RACI matrices for recurring decisions, design escalation paths for exceptions, and establish clear autonomy boundaries so people know when they can act without asking.
Common Mistake
Creating a RACI matrix and filing it away. Decision rights only work if people know them, use them, and are held accountable to them.
What Good Looks Like
The test: Can a mid-level manager make a $10K decision without asking their boss? If not, your decision rights are too centralized.
Communication Protocol
Who talks to whom, through what channels, how often.
Design intentional communication architecture. What information flows where, through which channels, at what frequency. Eliminate the 'I didn't know' problem without creating information overload.
Common Mistake
Defaulting to Slack for everything. Not every communication needs real-time delivery. Some things need a document. Some need a meeting. Some need a decision log.
What Good Looks Like
Every recurring communication should have a defined channel, frequency, audience, and purpose. If it doesn't, it's noise.
Cross-Functional Alignment
Breaking silos without creating bureaucracy.
Design the interfaces between teams. Shared objectives, joint reviews, cross-functional projects, and information-sharing protocols that keep teams aligned without creating committee culture.
Common Mistake
Solving silos by adding more meetings. The fix is shared metrics and shared accountability, not shared calendars.
What Good Looks Like
Cross-functional projects should have a single accountable owner, not a committee. If three people are accountable, nobody is.
From the Field
“For a $1.4B distribution company with 7 subsidiaries, the Align phase created a unified operating cadence that replaced 47 different meeting rhythms across the portfolio with one coherent system — without reducing autonomy at the subsidiary level.”
Download the Align Phase Checklist
A step-by-step checklist to guide you through the align phase. Includes templates, frameworks, and evaluation criteria.
Related Reading
Articles from the playbook that connect to this phase.