Most meeting invitations tell people where to be and what will be discussed. Very few tell them what conversation they are there to have. That gap—small, invisible, easy to overlook—is where an enormous amount of project time quietly disappears.
Purpose closes it.
Purpose Is Not the Agenda, and It Isn’t the Outcome
Purpose gives direction to action. In a meeting, it defines the conversation the meeting exists to have.
That makes purpose the bridge between two things leaders are usually more comfortable with. Context is the why: the larger commitment the meeting serves. Purpose is the work of the conversation. Outcomes are the what-must-exist: the specific, measurable results with a who, a what, and a by-when.
It is worth being clear about what purpose is not. It is not context. Not an outcome or a result. Not a goal, a strategy, a role, or a task. Not a problem to solve. Not “general discussion.”
The moment a purpose statement starts collecting words like check in, review, or discuss, or begins listing topics, it has drifted into agenda territory.
Agenda organizes the conversation. Purpose defines it.
Three Questions That Produce a Powerful Purpose
1. What conversation are we here to have?
This identifies the conversation. Every meeting has one primary conversation, even when other kinds show up inside it: strategic, alignment, decision-making, coordination, planning, problem-solving, escalation, or status.
Naming the primary one is what allows a leader to stay focused and lead the meeting intentionally rather than reactively.
2. What work is this conversation intended to move forward?
This reveals the immediate work—decide, coordinate, create, resolve, align, prioritize, escalate, integrate.
These are verbs, not topics.
A useful test: finish the sentence “This conversation is intended to…” and see whether what follows describes work or merely subject matter.
3. What is this conversation in support of in the overall project?
Every conversation produces an immediate result, and that result contributes to something larger. This question names the larger commitment:
- Delivering the next phase on schedule
- Reliable execution across teams
- Keeping our agreements
- Strengthening trust across the project
- Removing barriers to project success
A Format Worth Stealing
Those three answers assemble into a single sentence:
To have the (conversation type) conversation that (does the work of the conversation) in support of (what the work is intended to advance).
Watch what it does to a real meeting purpose.
The original read:
To review all items related to elevator construction and prioritize action items to support the project schedule.
Rewritten:
To have the coordination conversation that identifies, evaluates, and prioritizes elevator construction issues in support of maintaining the project schedule.
The subject matter didn’t change. What changed is that everyone now knows what conversation they’re in, what work it is doing, and why that work matters.
That is a different meeting.
Purpose Is a Leadership Practice, Not an Opening Statement
Writing the purpose is the design work. Leading from it is where the value shows up.
Send the purpose with the agenda the day before. State it at the start of the meeting—and again halfway through, especially when someone new joins, or any time the conversation has gone astray. Topic leaders should create a purpose for their own section rather than assuming the meeting’s purpose covers it.
Then keep it alive. Use it as a decision filter: Which option best supports what we’re here to create? When discussion drifts, reconnect people to the conversation they agreed to have. A useful follow-up question for any meeting leader is the inverse: What conversation does not belong in this meeting?
Close by relating to the purpose and connecting it to the context.
Every participant carries a version of this too. Before speaking, the question is:
Is what I’m about to say forwarding the purpose?
The Takeaway
Without context, people may not care. Without purpose, people may not know what to do. You need both.
Context creates alignment around why. Purpose creates alignment around the work that needs to happen.
And alignment, it turns out, isn’t created by agreement. It’s the natural outcome when people are committed to a shared purpose and a clear direction.
Don’t organize meetings around information. Organize them around the work that information makes possible.
