A leadership team alignment workshop should end with a shared operating priority, explicit trade-offs and commitments that have owners. It is not a meeting to make every leader agree about everything. The useful test is whether people can make compatible decisions after they leave the room.
This illustrative 90-minute agenda focuses on one recurring situation: a cross-functional priority that keeps being reopened. Adjust the timing to the complexity of the work. It is a discussion format, not a promise that an entrenched disagreement can be solved in one session. The broader reason for doing it is described in Alignment Drives Speed.
Before the workshop: choose the decision, not just the theme
The sponsor identifies a decision the group needs to support and who holds the authority to make it. 'Improve alignment' is too broad. 'Agree which customer work takes priority when two departments need the same capacity' gives the discussion a practical boundary. Bring current approved information about the work, not a slide deck of opinions about personalities.
Ask each participant to prepare a short statement of the outcome they believe matters, the constraint they see and one recent example. Make relevant facts available beforehand. If the necessary decision-maker cannot attend, define which recommendations the group can make and which decision must wait. Avoid inviting a team to negotiate authority it does not possess.
Minutes 0–15: define the outcome and constraints
The facilitator states the decision and asks each leader to describe the desired outcome in plain language. Capture the differences before trying to resolve them. A team can use the same word, such as 'urgent,' while meaning different conditions. Agree the customer or operating outcome, the time horizon and the limits that existing policy places on the decision.
Write a working statement: For this situation, the priority is [outcome]. We must protect [required boundaries]. We are deciding [specific choice]. We are not deciding [out-of-scope issue]. Ask participants to correct the statement while its meaning is still negotiable. Do not call silence a shared understanding.
Minutes 15–35: surface trade-offs and conflicting assumptions
Use one concrete example to examine where decisions diverge. What did each function optimize? What information did it have? Which other team's work did its choice affect? Distinguish a disagreement over facts from a disagreement over priorities. Assign missing evidence to an owner instead of filling the gap with the loudest interpretation.
The facilitator gives each participant room to explain a constraint and a consequence. Record a trade-off as a choice: 'Prioritizing this work delays that work,' not 'Operations never cooperates.' The aim is a decision the business can own, rather than a compromise that leaves every function interpreting it differently.
Minutes 35–60: agree the decision rule and authority
The authorized owner decides or states what must happen before a decision is possible. Capture the rule that will guide the next comparable situation, the person who can decide and the condition that requires escalation. A workshop may produce a recommendation rather than approval; label that distinction clearly.
Test the proposed rule against a second example. Can leaders explain what they would do and why? If their answers differ, examine the ambiguity now. A rule that works only for the example on the whiteboard may be too narrow. A rule that says 'use good judgment' without boundaries may be too broad.
Minutes 60–80: convert agreement into commitments
Each affected leader states the next action, owner, needed input and checkpoint. Identify what stops or changes as well as what starts. Without that step, a new priority can be added to an already full workload without resolving the original conflict. Record dependencies between commitments rather than leaving teams to discover them later.
An illustrative commitment is: The designated leader will update the approved priority record, confirm the interpretation with both receiving teams and bring one real decision to the next review. It identifies evidence of implementation rather than treating distribution of workshop notes as completion.
Minutes 80–90: close with a review, not a victory claim
Have the group summarize the priority, the decision rule, unresolved evidence and individual commitments. Set a review point after people have had a genuine opportunity to apply the agreement. The review asks what decision was made, where the rule helped and what still required clarification. Adjust the rule using the work, not a satisfaction score alone.
How should the team maintain its agreement after the workshop?
Carry the approved decision into a working agreement with an owner, an exception route and a condition for review. The leadership-team charter helps describe how peers will make commitments and address disagreement; it does not replace the decision owner's actual authority. Test the agreement with a later work example so circulation of the notes is not mistaken for shared understanding.
If the choice is repeatedly reopened, ask what changed: the facts, the business priority or the authority boundary. The cross-functional conflict guide separates those questions before another negotiation begins. An illustrative review might reveal that one department never received the approved priority change. Repair that communication and examine the next decision rather than declaring the workshop unsuccessful—or automatically adding another session.
For the follow-through discipline, read Execution Is a Leadership Discipline. If the same disagreement repeatedly returns because leadership priorities or authority remain unresolved, discuss the wider operating situation rather than adding another workshop to the calendar.
About this resource: Prepared with AI-assisted drafting. The agenda and examples are illustrative, not a validated facilitation protocol or a description of a contracted service. Cover illustration: AI-generated.