Team Agreements That Get Kept
Why Execution Breaks Down Before the Work Begins
Agreements: The Infrastructure Behind Execution
Every organization runs on agreements. Who committed to what. By when. What completion means. How the work connects to other work. What happens when a commitment cannot be kept.
Most organizations do not manage any of these explicitly.
A meeting ends. People leave believing they understood. Someone committed to a deliverable, or everyone assumed someone did. The deadline arrives, and the result is not what was expected, or it does not arrive at all. The conversation that follows focuses on who was at fault.
The problem was not the execution. The problem was that no specific agreement existed to execute against.
YOUR TEAM CANNOT KEEP AN AGREEMENT THAT WAS NEVER SPECIFIC.
This is not a communication problem. It is not solved by telling people to communicate better. It is a structural problem in how organizations coordinate action. DorWay’s Network of Agreements addresses it as a practice, not a process improvement.
The Anatomy of a Broken Agreement
Examine most execution breakdowns in organizations and the same pattern appears. Not failure of effort. Not failure of talent. Failure of specificity.
Someone says “I will get that to you.” Neither person specified what “that” includes, what format it takes, when it will arrive, what constitutes completion, or how to handle a change in scope or timeline.
A team leaves a meeting with “action items.” The items are vague enough that each person can construct a different understanding of what they committed to. Three weeks later, the project is off track and every person believes they did what was asked.
A leader commits to a strategic initiative. The commitment is a direction, not a set of specific agreements. The team begins work based on their interpretation of what the leader meant. The leader’s interpretation was different. The gap between the two becomes visible only when the results arrive.
In each case, the agreement was never specific enough to keep. What existed was an assumption dressed as a commitment.
What an Agreement Actually Requires
An agreement, in the sense that produces coordination and execution, is not a general understanding. It has specific components:
Who. One person owns the commitment. Shared ownership is no ownership.
What. The deliverable is described with enough specificity that both parties would recognize completion. “Update the report” is not an agreement. “Add the Q3 revenue figures to the executive summary by section, formatted to match the existing tables, with a one-paragraph narrative for each variance greater than 10%” is an agreement.
By when. A specific date and time. “Soon,” “ASAP,” “when you get a chance” are not commitments. They are invitations to interpret.
What completion means. The conditions that both parties would point to and say “this is done.” Without this, the person delivering does not know when to stop and the person receiving does not know what to expect.
What happens when it changes. Because it will change. Circumstances shift. Information arrives. Priorities move. The practice is not keeping every agreement regardless of changed circumstances. The practice is managing the agreement, renegotiating before the deadline, going to the person affected and creating a new commitment before the gap becomes their problem.
Why "Communicate Better" Does Not Fix This
The standard response to agreement breakdowns is some version of “we need to communicate better.” That statement is about as useful as telling a person with a broken transmission to “drive better.”
Telling people to communicate better without specifying what that means in practice produces nothing. What does “better” mean? Say more words? Send more emails? Have more meetings?
The practice is specific. It means: make agreements explicit. Define who, what, by when, and what completion means. When you cannot keep a commitment, address it before the deadline. Track what was agreed to. Follow through. When something is unclear, ask. When a commitment was not specific, make it specific before proceeding.
These are practices. They can be developed, examined, and embedded into how a team operates. “Communicate better” is a wish. Managing agreements is a practice.
Agreements as Infrastructure
DorWay treats agreements not as individual commitments but as a network. An organization’s execution runs through that network the way a city’s transportation runs through its roads.
When the network is explicit, visible, and managed, people know what they committed to, what others committed to them, and how the commitments connect. Coordination is possible because the infrastructure supports it.
When the network is implicit, assumed, and unmanaged, people operate on interpretation. They do their best based on what they think was agreed to. The result is that individual effort is high and organizational execution is inconsistent.
The difference between these two states is not talent, motivation, or strategy. It is whether the agreements that connect people’s work are specific enough to keep and managed enough to stay current.
The Five Breakdowns
Most agreement breakdowns fall into one of five categories:
Never made. The agreement was assumed, not stated. Both parties believed something was understood. Neither checked. No specific commitment existed.
Not specific enough. The agreement was stated but left important dimensions undefined. “Handle the client situation” is not specific enough to execute. What does “handle” mean? By when? What outcome constitutes handling it?
Not managed. The agreement was specific when made. Circumstances changed. The person who made the commitment did not renegotiate. They either delivered late, delivered something different, or did not deliver. The gap became visible only at the deadline.
Not tracked. The agreement was made and forgotten. No one tracked it. No one followed up. It dissolved into the stream of daily activity and resurfaced only when the consequence arrived.
Not completed. The agreement was tracked but completion was never confirmed. The work was done, but the person who requested it never received confirmation, never reviewed the result, and never closed the loop. The agreement exists in a state between done and open, consuming attention and trust.
Each of these is addressable through practice. None of them is solved by effort or good intentions alone.
How Agreement Management Connects to [Accountability](/accountability/)
Accountability without agreements is arbitrary. Holding someone accountable for a result they never specifically committed to is not accountability. It is after-the-fact judgment.
Genuine accountability requires agreements specific enough to evaluate against. Did the person deliver what they committed to, in the form they committed to, by the time they committed to? If not, did they manage the agreement before the deadline?
When agreements are specific and managed, accountability becomes straightforward. The commitment either happened or it did not. If it did not, the conversation is about what happened and what will happen next. If it did, the commitment is complete.
When agreements are vague, accountability becomes a battle of interpretations. “I thought you meant…” “That is not what I understood…” “I was waiting for…” Each person has a defensible position because the agreement was never specific enough to rule any interpretation out.
This is why DorWay develops Managing Agreements and Being Accountable together as two of the Eight Practices of the Leaders Edge Path. Each makes the other operational.
How Agreement Management Connects to [Conflict Resolution](/leadership-development/conflict-resolution-training-options/best-conflict-resolution-programs/)
Most organizational conflict traces back to unmanaged agreements. Two people have different understandings of what was committed to. Each believes the other failed to deliver. Each is operating from their interpretation of an agreement that was never specific enough for either of them to be definitively right or wrong.
The conflict is not between the people. It is between their interpretations of a commitment that was never explicit. Resolving the conflict requires making the agreement explicit, which should have happened before the work began.
Organizations that develop the practice of managing agreements explicitly reduce conflict not by avoiding disagreement but by removing the ambiguity that produces unnecessary disagreement. When commitments are specific, visible, and managed, the conversations that remain are about substance, not about whose interpretation was correct.
What the Practice Looks Like
In practice, managing agreements means developing specific behaviors:
Before leaving a conversation where work was discussed, confirm what was agreed to. State it. “Here is what I am committing to. Here is what I understand you are committing to. Here is the timeline. Here is what completion means. Is that accurate?”
When circumstances change, go to the person or people affected before the deadline. “I committed to delivering X by Friday. That is not going to happen. Here is why. Here is what I propose instead. Is that workable?”
Track commitments. Not in a project management tool that no one checks. In whatever system the team actually uses. The mechanism matters less than the practice of making commitments visible and following up.
When a commitment is complete, close the loop. “The deliverable I committed to is done. Here it is. Let me know if this meets the conditions we agreed to.”
These are not complex processes. They are specific practices. What makes them difficult is not the practice itself but the consistency required to sustain it, which is why DorWay develops agreement management as part of an integrated system rather than as a standalone process improvement.
Why Process Improvement Is Not Enough
Organizations frequently address agreement breakdowns by adding process: more templates, more tracking tools, more status meetings, more review gates. Process is useful. It is not sufficient.
A tool that tracks agreements does not produce the practice of making agreements specific. A meeting cadence that reviews commitments does not produce the practice of renegotiating early when a commitment cannot be kept. A template that captures who, what, and by when does not produce the practice of actually filling it out with the specificity required.
The practice is what makes the process work. Without the practice, the process becomes another layer of administration that people comply with but do not use.
DorWay develops the practice. The Human Performance Infrastructure that supports it includes coaching, evaluation, D3X (DorWay’s AI Leadership Intelligence available through the DorWay Leadership Hub), and the Organizational Practice System for embedding practices across teams.
Evidence
When DorWay’s Network of Agreements was implemented with TigerGraph, agreement completion moved from 13% to 61% to 96%, later sustaining around 85%. Those numbers represent the shift from an environment where agreements were assumed to one where they were explicit, tracked, and managed.
The shift was not the result of a new tool or a new process. It was the result of developing the practice of managing agreements. The specificity, the tracking, the renegotiation, the completion, and the accountability that comes with all four.
Team Agreement Template: The Five Components
Use this template for any commitment that matters. If a line cannot be filled in, the agreement is not specific enough yet.
| Component | What to write |
|---|---|
| Who | One named owner. Shared ownership is no ownership. |
| What | The deliverable, described so both people would recognize it as done. |
| By when | A date and time. Not “soon” and not “ASAP.” |
| What completion means | The conditions both people would point to and say “this is done.” |
| What happens when it changes | Who the owner tells, and by when, if the commitment is at risk. |
Most team agreements describe norms: how a team communicates, meets, and decides. Norms are useful. They are not commitments. This template turns a norm into something a person can keep, track, and complete. It is the building block of DorWay’s Network of Agreements™.
Go Deeper
Where agreements show up in team dynamics, conflict, and succession planning.
- Team Dynamics That Actually Work: Six Factors, and the Layer Most Teams Miss
- Conflict Resolution Training Programs That Address the Actual Problem
- The ROI of Workplace Conflict Resolution: What Unresolved Conflict Actually Costs
- Succession Planning Toolkit: What to Include and How to Measure It
- How to Compare Succession Planning Software
Frequently Asked Questions
How is this different from project management?
Project management organizes work. Agreement management develops the practice of making and keeping commitments. A project plan can contain vague commitments that no one manages. An agreement practice produces specific commitments that people take responsibility for. The two are complementary but distinct.
Can this work in organizations that already have strong processes?
Yes. Strong processes provide structure. Agreement management fills the gaps between process steps where assumptions live. Many organizations with excellent project management still struggle with execution because the human commitments inside the process are not specific or managed.
How does this scale across large organizations?
DorWay’s Organizational Practice System is designed to embed agreement practices across teams. The practice scales because it is a behavior, not a centralized system. Every conversation, every meeting, every handoff is an opportunity to make an agreement explicit and manage it. D3X supports individual leaders in applying the practice to daily situations through the DorWay Leadership Hub.
What about cultures where explicit agreements feel confrontational?
Making an agreement explicit is not confrontational. It is clarifying. “Here is what I am committing to” is a statement of responsibility, not a challenge. Most people experience explicit agreements as a relief once they have tried it. The ambiguity they were navigating was more uncomfortable than the conversation required to resolve it. The same pattern applies to performance improvement: specificity feels harder upfront and produces better results than vagueness.