By Sherrell Hendrix, Chief of Staff

When an executive director, board chair, or public agency lead calls us about facilitation, we ask one question early: what do you need people to be able to do when they leave the room? The most common answer is “We need to get everyone on the same page.” It is a real answer, and it usually points to a problem a single meeting cannot solve.

The request tends to arrive at a predictable moment. The annual retreat is six weeks out. A new initiative launches next quarter, and staff or partners will have to carry it. A project that had strong support in January has not moved since March. In each case, the hope is that the right conversation will produce shared direction. Many leaders have seen what happens when a meeting carries that weight alone: the session generates energy and goodwill, and within a few weeks the old gaps reappear. People describe the goal differently, deadlines slip, and the work drifts back to the two or three people who cared most about it to begin with.

That pattern shapes how we respond to a facilitation request. When the goal is alignment, we design the meeting as one part of a larger process, with preparation beforehand and follow-through afterward. This article walks through how Key Strategic Group approaches that work, from the first conversation through the months after the session, and closes with the questions we would encourage any leader to answer before putting the next meeting on the calendar.

Name What “The Same Page” Means

“The same page” covers several different goals, and each one calls for a different process. In our first conversation, we work out which one the client actually needs. With clients we have worked with before, that usually takes a couple of questions. With new clients, it takes more digging.

Goal	What the client needs	What the session has to produce
Inform	People understand a decision leadership has already made.	Clear understanding of the decision, the reasons behind it, and what changes as a result.
Reflect and connect	Time to look back on the year, strengthen relationships, or reset as a team.	A shared view of where the team has been and early thinking about what comes next.
Gather input	Perspectives that will shape a decision leadership has not yet made.	A clear picture of concerns, ideas, and tradeoffs, with a plan for how input will be used.
Align	The people carrying out the work share an understanding of the goal, success measures, roles, decision rights, accountability expectations, milestones, and resources.	A starting point. Alignment also requires preparation before the session and follow-through after it.

 

Most of these goals can be met with a well-designed session, supported by the tools and resources we bring to the work. A retreat meant to reflect on the year and reconnect the team needs good design and a skilled facilitator. It does not need three weeks of interviews. Alignment is different. When a client tells us that is the goal, we share that it will take more: time with participants before the meeting, decisions from leadership about what is and is not open, and a structure for what happens afterward. We push on this because the alternative, a strong meeting with no follow-through, costs the client time and credibility with the people they convened.

To be clear, we do not believe that every initiative needs that investment. A policy change leadership has already decided needs clear communication and direct delegation. A task shared by two departments needs coordination. Treating every initiative as an alignment effort wastes staff time building shared ownership where it is not required. The opposite mistake is more common and more expensive: an initiative that depends on many people or organizations owning it gets launched through assignments alone, and it stalls.

Define Alignment Precisely

When we say a group is aligned, we mean the people doing the work share an understanding of seven things:

• The goal: what the work is meant to achieve.
• Success measures: how everyone will know the goal has been reached.
• Roles: who is responsible for each part of the work.
• Decision rights: who can make which decisions, and who makes the final call.
• Accountability expectations: what each person will be held to, and how progress will be reviewed.
• Milestones: what needs to happen, and by when.
• Resources: the time, staff, budget, and information available to do the work.

A quick test is to ask people individually what the goal is, how the organization will know it has been reached, what their role is, what they are accountable for, and what happens next. While they likely will not use the same words, we are listening to see whether their answers point in the same direction.

Consensus is a separate question. A program director can disagree with a decision and still be aligned on it, meaning she understands what was decided, why, and what she is responsible for delivering by when. Some disagreement is healthy. Significant change should generate questions, and people need room to test assumptions, raise barriers, and work out what a new priority means for their workload.

Attendance is easier to mistake for alignment because it is visible. Every department sent someone, every partner organization was represented, and the sign-in sheet is full. But being in the room does not mean someone left with a clear understanding of their role, or with the authority to act on it. A partner organization may send a staff member who cannot commit resources without their director’s approval. A department head may attend, agree, and never brief the team that will do the work. The meeting looks well attended, and the people responsible for follow-through were never fully part of the conversation.

That is also why we treat silence as a signal. When leadership introduces a major initiative, and nobody asks a question, we do not read that as agreement. More often, people have not yet worked out what the initiative means for them, or they do not believe their questions will change anything. That quiet acceptance can show up later as missed deadlines and existing work taking priority.

In Managing Transitions, William Bridges draws a distinction between change and transition that helps explain why. The change is the event: the new strategy, the reorganization, the announcement at the all-staff meeting. The transition is what each person goes through to let go of the old way of working and take on the new one. A meeting can announce a change. People move through the transition on their own timeline and through continued conversation, which is one reason alignment rarely happens in a single room.

Listen Before Designing the Session

Once we know the goal is alignment, we talk with the people involved before we design anything. On a small team, we talk with everyone. On a larger effort, we talk with a stratified sample across roles, levels, and partner organizations, and we aim for demographic representation across gender, race and ethnicity, and age. When the timeline is tight, or the group is large, we add a survey, but conversation is our default because it lets us follow up on what we hear.

These conversations do two things. They give people an early look at what the client hopes to accomplish, so no one walks into the session cold. They also show us where understanding diverges. We listen for different definitions of success, uncertainty about what has already been decided, concerns people have not raised with leadership, and resource gaps that will surface later if no one names them now.

We then share a synthesis of what we heard. Leadership sees it before the session. Depending on the engagement, other participants see it in advance or at the opening of the session. Either way, the group starts from a shared picture of the range of perspectives, so the time together goes to working through differences instead of discovering them.

Settle What Is Decided and What Is Open

The leader championing the work has to be clear about the intended outcome and honest about which parts are still open. Before the session, we ask leaders to name what is fixed, what is flexible, where they genuinely want input, and who will make the final call.

When that clarity is missing, engagement becomes performative. Staff are invited to weigh in without knowing whether they are shaping the decision, advising on implementation, or hearing about a direction leadership already chose. Leadership walks away believing it created room for participation. Staff walk away believing their input should have changed something. Both are frustrated, and trust in the next convening drops.

Clear boundaries make pushback useful. When the operations manager says the timeline assumes a hire that has not been approved, or a partner points out a dependency on data they do not control, that is exactly the information the plan needs. These conversations bring tension to the table early enough to improve the work.

Build the Structure That Carries the Work

Most leaders will recognize this pattern. The session ends with a RACI chart, named owners, and deadlines. Everyone leaves knowing who owns what. Six weeks later, the deliverable has not moved, and the conversation turns to why the owner did not get it done.

Charts and project plans are useful, and we use them. They also have limits. A RACI chart can name a task owner without showing whether that person can make the decisions the task requires. A project plan can set a deadline without accounting for an owner who is already at capacity. A meeting summary can record a decision without confirming that anyone knows what changed because of it.

So when we help clients assign ownership, we check the conditions that make ownership real: a defined outcome, milestones, access to the necessary information, decision rights that match the responsibility, and enough time, staff, and budget. A program lead who owns a launch but needs executive approval for every $500 expense has responsibility without authority. Over time, that gap pushes work back up to leadership or to the most capable person on the team, and the organization becomes dependent on a few people and exposed when one of them leaves.

This also changes how accountability works. When something stalls, we look first at whether the process held up. Were milestones set? Were resources allocated? Were decision rights clear? Did leadership keep reinforcing the priority once other demands competed with it? Individual accountability still matters, and it becomes fair and far easier to act on once the organization has done its part.

Alignment in Action

On one recent initiative, the client’s project team discovered at kickoff that they had different ideas of what success would look like at the end of the project. We stopped and worked through it on the spot: what does success look like, and what are we going to do to get there? It resolved quickly because the team was small, already trusted one another, and had its decision-maker on the call. Most of the alignment was already there. The team needed the differences named and a decision maker to settle them so everyone could move forward.

The harder work came later. While preparing for a larger workshop on the same initiative, we met with participants in advance to share what we hoped to accomplish and hear their perspectives. Those conversations surfaced the real tensions, including people’s concerns and fears about the effort. The workshop was productive, and people still did not leave it on the same page. Getting there took continued relationship-building and conversation over the following months. Nine months later, potential partners who had not been aligned at the start were supporting the initiative.

Stay With the Work After the Session

For alignment efforts, our role continues after the facilitated session. We stay engaged as clients track progress against milestones, keep the priority visible when competing demands show up, work through barriers that were not visible at the start, and revisit decisions as conditions change. The session is where people commit. The weeks that follow determine whether that commitment turns into action. Much of what happens in those weeks is set before anyone walks into the room, which is why the planning questions below matter as much as the session itself.

Before You Put the Next Meeting on the Calendar

Whether or not you bring in a facilitator, answer these questions first. They will tell you what kind of gathering you need and, if the answer is alignment, what has to be in place for it to hold. A companion worksheet walks through each one.

1. What are we trying to accomplish? Describe what will be different when the work succeeds.

2. What kind of gathering do we need? Decide whether people need to be informed, reconnected, consulted, or aligned.

3. How will we measure success? Identify the evidence and milestones that will show progress, and by when.

4. Where do people stand right now? Consider whose perspectives you have heard, whose you have not, and where definitions of success may differ.

5. What has already been decided? Be explicit about what is fixed, what is open, and who makes the final call.

6. Who owns the work? Confirm each owner has the decision rights to carry it out and knows what they will be held accountable for.

7. What will people need to succeed? Think through information, time, staff, budget, and relationships.

8. How will we sustain it after the meeting? Decide how we will track, share, and revisit progress.

If your answers to these questions point to a need for alignment, budget the time for it: the conversations before the session, the decisions leadership has to make, and the follow-through afterward. That work determines whether people leave the room ready to act.

Source: William Bridges and Susan Bridges, Managing Transitions: Making the Most of Change, 4th ed. (Da Capo Lifelong Books, 2017).