Every Meeting Is Already Three Meetings
The first moment is preparation. It happens before anyone enters the room or conversation. It is the quality of preparation each participant brings: the intent they have clarified, the context they have gathered, the capacity they have honestly assessed, and the communication they have thought through in advance. This meeting shapes everything that follows, whether or not it is consciously designed.
The second meeting is the one most leaders recognise. Meetings happen, conversations happen, offers are made, requests are put forward, agreements are reached, and commitments are confirmed and recorded. This is where coordination is designed.
The third part begins the moment the conversation ends. It is the domain of execution: scheduling the work, managing the commitments, tracking fulfilment, surfacing risk early, and closing each promise with the rigour it deserves.
Keep it simple: Prep. Promise. Perform.
These three phases already exist inside every successful meeting cycle. The developmental question is not whether to introduce them. It is whether to design them intentionally, or leave them to chance.
When all three are consciously architected, something qualitatively different becomes available. Meetings become shorter and more focused. They know where they are going. Commitments become more reliable. They are clear and explicit. Execution accelerates. Expectations and resources can be assigned when things are clear. Trust, which is ultimately a function of consistent follow-through rather than goodwill alone, compounds across the organisation over time.
This article defines each phase precisely, and describes what becomes possible when leaders begin to treat the full meeting cycle as a single, designed system of coordinated action.
Stage One: Prep
Come ready. Intent, context, information, and how to communicate it.
Preparation is not administration. It is the act of creating the conditions from which reliable commitments can be made.
In the early stages of organisational life, informal preparation is sufficient. Teams are small, relationships are close, context is shared, and a degree of improvisation inside meetings works well enough. As organisations grow in complexity and interdependence, what sustained a small team begins to create friction at scale. The preparation that once happened naturally through proximity now needs to be designed deliberately.
There are four things a leader brings to a meeting that is fully prepared.
Intent: know what you are there to achieve.
Before entering any meeting, a leader clarifies their purpose. Not the agenda item, which is a topic, but the outcome they are responsible for producing. What decision needs to be made? What commitment needs to be negotiated? What information needs to be shared, and to what end? Intent is the difference between attending a meeting and leading within one. Without it, participation is reactive. With it, coordination becomes possible from the first exchange.
Context: know what is actually happening.
Preparation means arriving with the relevant information already in hand. This includes the current state of the work or project under discussion, the constraints and dependencies that will affect any commitments made, the risks that are already visible, and any external conditions that will shape what is genuinely achievable. Context shared before a meeting is foundation. Context shared inside a meeting is recovery time. Leaders who bring full context create the conditions for fast, precise coordination. Leaders who surface it reactively consume the meeting establishing what should already have been known.
Information: know what others need in order to decide and commit.
Preparation includes identifying what each participant will need in order to engage productively, make informed decisions, and accept realistic commitments. This might mean circulating data, sharing a pre-read, providing a brief on recent developments, or simply framing the key question clearly enough that people arrive already thinking about it. When relevant information reaches participants before the meeting, the conversation inside the meeting can move immediately into coordination rather than orientation.
How to communicate it: know how to make your contribution land.
This is the dimension of preparation most frequently overlooked. It is not enough to hold good information or clear intent. A leader who has not considered how to communicate their position, request, or offer will find that the meeting generates discussion without generating agreement. Preparation includes thinking through the language of the commitments to be proposed, the specific requests to be made, and the outcomes to be offered. It includes anticipating the legitimate concerns of others and preparing to engage with them honestly. It includes, at its most disciplined, conducting the 4T Assessment before the meeting begins.
The Promises Protocol’s 4T Assessment asks four questions of any commitment being considered: is there sufficient Time to deliver it? Is the Talent available to do it well? Are the Tools and resources in place? Is any Training or qualification required? When a leader completes this assessment in preparation, they arrive at the meeting already knowing what they can authentically offer and what would require renegotiation. This is what makes a promise made in the meeting a promise that will hold outside it.
The research on decision quality consistently demonstrates that the conditions under which decisions are made matter as much as the decisions themselves. Daniel Kahneman’s work on cognitive bias (Thinking, Fast and Slow, 2011) shows that time pressure, incomplete information, and social expectation predictably degrade the quality of judgement. Deliberate preparation does not eliminate these pressures entirely. It reduces them sufficiently for clearer thinking and more realistic commitment-making to occur.
Leaders who invest consistently in preparation often find that their meetings shorten, their commitments hold more reliably, and the energy previously spent recovering from misalignment is released for productive work. The apparent efficiency of arriving unprepared tends, on closer examination, to be borrowed time repaid with interest in the aftermath.
Stage Two: Promise
In meetings and conversations: make offers and requests, confirm agreements, and record and manage the promises made.
The meeting is where coordination is designed. The question is how precisely that design is executed.
Most meetings produce some combination of discussion, direction, and intention. In small, close-knit teams operating in relatively stable conditions, this is often sufficient. Relationships are strong, goodwill is abundant, and informal alignment bridges the gap between what was said and what gets done. This is a genuine and functional form of coordination, and it deserves recognition as such.
As organisations scale and interdependence deepens, a more explicitly structured approach to agreement-making becomes increasingly valuable. Not because informal alignment is inadequate as a quality of relationship, but because it cannot be tracked, renegotiated, or reliably transferred across a complex system. What holds a small team together through trust and proximity needs a different instrument when the team is large, distributed, or operating under significant pressure.
The instrument is the promise.
Speech Act Theory, developed by J. L. Austin (How to Do Things with Words, 1962) and extended by John Searle (Speech Acts, 1969), establishes that certain utterances do not merely describe reality. They constitute it. A promise is a performative speech act: it does not report on a future state but brings a new social reality into being. When this is understood operationally, the language of meetings becomes more than communication. It becomes the primary mechanism through which coordinated action is generated.
The promise phase has three distinct disciplines: making offers and requests, confirming agreement explicitly, and recording and managing what is committed.
Making offers and requests.
Every commitment in a meeting begins as either a request or an offer. A request asks another person to deliver a specific outcome. An offer proposes to deliver one. Both are legitimate moves in the design of coordination. What matters is that they are made explicitly and structured precisely.
The Promises Protocol’s WWWBW formula provides that structure: Who is doing What, as a specific outcome, for Whom, by When, stated as an absolute date and time. This structure makes a commitment trackable, adjustable, and verifiable. It also makes the quality of the commitment visible in the moment it is made.
Two versions of the same intent illustrate the difference. “I’ll try to get you the report by end of week” carries genuine goodwill and real intent. It also leaves the outcome undefined, the deadline open to interpretation, and the customer unspecified. “I will deliver the revised pricing PDF to you by Thursday, 6 March at 17:00” is the same intent expressed as a workable promise. The outcome is named. The deadline is precise. The customer is identified. The commitment can be tracked, adjusted where necessary, and verified on completion.
This structural difference compounds across an organisation. When commitments are made with WWWBW precision, execution becomes visible, renegotiation becomes possible, and the energy spent pursuing unclear agreements is released for productive work.
Confirming agreement explicitly.
A promise requires acceptance. This is one of the more countercultural propositions in the Promises Protocol, because most organisational cultures treat a nod, a silence, or a casual “sure” as sufficient confirmation. In practice, assumed agreement and genuine agreement produce very different outcomes.
Explicit acceptance means hearing a clear “yes” to a specific offer or request before the commitment is recorded. It means the performer has considered the 4T Assessment and confirmed that the promise is authentic rather than optimistic. And it means the customer has confirmed the terms, so that both parties share the same understanding of what done looks like.
There are three legitimate responses to any offer or request: accept, decline, or counter-offer. High-performing teams learn to treat all three as equally valid contributions to reliable coordination. An honest decline, paired with a counter-offer that proposes what is genuinely deliverable, keeps the system realistic and protects the reliability of the whole network of commitments. The courage to counter-offer is not a lesser form of responsiveness. It is its more mature and more trustworthy expression.
Recording and managing the promises made.
A commitment that is not recorded is dependent on memory, and memory is an unreliable coordination instrument. The Promises Log is the operational record of every promise in the system: who made it, to whom, for what outcome, by when, and what its current status is. This record makes the network of commitments visible, shared, and manageable.
The log is not a task list. It is a commitment register. The distinction matters because it orients the conversation differently. A task list asks what needs doing. A Promises Log asks whether the commitments made are still realistic, and if not, what needs to happen now.
Maintaining the log as a live and shared record is itself a leadership act. It signals that agreements are taken seriously, that the organisation operates at the level of commitment rather than intention, and that accountability is a structural feature of how coordination works here, not a cultural value applied inconsistently.
Kegan and Lahey’s work on transformational language (How the Way We Talk Can Change the Way We Work, 2001) demonstrates that the language structures inside an organisation are not merely reflective of its culture. They are constitutive of it. The shift from a language of good intentions to a language of explicit, structured commitment is a developmental shift in the operating architecture of the organisation, and in the identity of those leading within it.
Stage Three: Perform
Schedule the work, manage the commitments, and steward every promise through to verified fulfilment.
A promise made is a system created. What happens next determines whether it becomes an asset or a liability.
The perform phase is the disciplined execution and stewardship of every commitment from creation through to verified completion. It is the stage most organisations address with genuine effort and the least deliberate design. Task lists are maintained, project software is updated, status is reported. These instruments are valuable. The developmental step beyond them is using them in active service of promise stewardship: keeping the underlying commitment visible, tracking not only what is being done but whether the original promise is still intact, and managing the conditions for fulfilment as actively as the work itself.
Schedule the work.
A promise without a scheduled plan is an intention dressed as a commitment. The first act of the perform phase is translating each promise into a concrete work plan: the actions required, the sequence in which they need to happen, the time allocated in the calendar, and the dependencies that need to be managed. This is the bridge between the commitment made in the meeting and the reality of execution. Where this bridge is not built explicitly, the promise floats in operational space, supported only by the memory and motivation of the performer.
Scheduling is therefore not a logistical detail. It is the act of making a promise real.
Manage the commitments.
Promises exist in relationship to each other. A commitment made by one person frequently depends on commitments made by others. The perform phase requires active management of this interdependence: tracking the status of each promise in the log, identifying where dependencies are at risk, and surfacing emerging constraints early enough for intelligent adaptation to occur.
The Promises Log provides the instrument for this. Status moves through defined states: Open, meaning the promise has been made and work has not yet begun; In Progress, meaning execution is underway; Completed, meaning the customer has verified fulfilment; and Broken, meaning the terms were not met and restoration is required.
The Promises Log is reviewed at a regular cadence. Daily standups, weekly team reviews, or project milestone conversations all provide the opportunity to surface risk proactively rather than reactively. What is reviewed is managed. What is managed is more likely to be fulfilled.
Breakdown, when it occurs, is a normal condition of complex work rather than evidence of failure. Conditions shift. New information surfaces. Constraints emerge that were not visible at the time the promise was made. The perform phase is not designed to prevent all breakdown. It is designed to make breakdown visible early enough for renegotiation to happen cleanly, before the cost of the breakdown compounds through the system.
When a promise cannot be kept, integrity is maintained through immediate, honest communication: acknowledging the breakdown clearly, renegotiating the terms with the customer, and making a new, specific promise using the WWWBW formula. This restoration process is not a failure of the system. It is evidence that the system is working as designed, because the breakdown is visible and being managed rather than hidden and accumulating.
Steward every promise through to verified fulfilment.
A promise is not complete when the performer believes they are done. It is complete when the customer verifies fulfilment against the agreed outcome. This distinction is where much organisational friction quietly lives. Closing it requires a simple but deliberate habit: always close the loop explicitly. Inform the customer. Invite their assessment. Confirm that the outcome meets the standard agreed.
This final act of the perform phase is completion, and it deserves more attention than most organisations give it. Completion is the mechanism through which the reliability of commitments becomes visible across the organisation. When completions are acknowledged, trust accumulates. When they are assumed and move past without recognition, the culture loses one of its primary opportunities to reinforce that commitments matter and that fulfilling them well is worth noting.
A culture of explicit completion is a culture in which the word “yes” carries compounding weight.
The Full Architecture
Prep. Promise. Perform. is not a set of meeting tips. It is a complete coordination architecture applied to the full cycle of organisational commitment.
Organisations are networks of agreements. Every team, project, client relationship, and strategic initiative is held together by a web of commitments made between people. The quality of those commitments, and the architecture within which they are made and managed, determines the quality of what the organisation is capable of producing.
Where agreements are sustained by goodwill, proximity, and personal initiative, a great deal still gets done. Relationships hold. Effort is genuine. This is the honest account of how most organisations function, and it deserves recognition.
The structural layer that becomes available at a further stage of maturity is one in which preparation is deliberate, commitments are explicitly designed and recorded, and execution is actively stewarded through to verified completion. Not instead of goodwill, but in addition to it. The two are not in competition. Structural rigour in promise-making does not diminish the quality of relationships. In most cases it deepens them, because the burden of ambiguity, assumption, and silent expectation is removed.
Preparation creates the conditions for realistic commitment. The promise phase converts intention into structured, trackable agreements. The perform phase stewards those agreements through to verified completion. Together, the three phases constitute a complete coordination cycle: a designed system in which what is agreed and what is delivered are the same thing.
Language does not merely describe what an organisation does. In the domain of leadership and commitment, it helps create it. Every meeting is an opportunity to design that creation deliberately, with the precision and care that the people inside the system deserve.
This article is a supplementary resource to The Promises Protocol by Alan Froggatt. The Promises Protocol provides the foundational framework for promise-making, the WWWBW formula, the 4T Assessment, and the Promises Log referenced throughout.