The plan is made by whoever is in the room. The Five What-Ifs makes sure the system is also in the room.
What it is
The Alignment Ceremony℠ is the collaborative decision surface where the team comes together to review what changed, commit to what’s next, and surface disagreements explicitly rather than letting them become implicit blockers. It is intentionally not an authoring tool — it’s a review-and-decide surface that composes data from every other tool and presents it as a structured agenda.
The Since Last Session view is the ceremony’s opening frame: confidence score movements, service tier changes, objective state transitions, and metric movement on pursuing objectives. The team isn’t starting from a blank slide deck. They’re starting from a diff of what the system learned since the last time they met.
Why this matters
Most planning meetings start from whoever prepared the most slides. The Alignment Ceremony starts from the data. The confidence frontier — services organized by where objectives are failing or advancing — determines the agenda, not the most vocal stakeholder in the room.
What you can do with it
- Review what changed across the full system since the last session, organized by urgency
- Make and record decisions that write back to objective states immediately
- Park disagreements explicitly rather than leaving them as unspoken blockers
- Close sessions as immutable meeting minutes that power the next session’s diff
Who it's for
Cross-functional teams running sprint reviews, quarterly planning, or any structured checkpoint. Anyone who wants meeting outcomes that are traceable, not just summarized.
In the system
The Alignment Ceremony is where the team drives the one state transition the framework reserves for human judgment: Modeled → Pursuing. Individual tools can advance objectives to Modeled; committing to pursue them requires the team forum. This is intentional — it keeps the highest-stakes decisions collaborative.
Six tools. One coherent practice.
Seven tiers of user confidence.
Periphery-to-core service mapping.
User-voice objectives with leading and lagging indicators.
Causal system modeling — root cause backward, projected effect forward.
Strategy → executable plan, mechanical traceability.