Accountability Is a Social Contract

Why your team’s follow-through problem is a meeting problem.

I was brought in to work with two organizations required to co-create an action plan. The conversation around the engagement was candid: You could feel the group had an underlying friction between them, and the work kept stalling.

Shortly into the first session, I could feel the undercurrent. Nothing had been named yet, but the tension was in the room. And one word kept getting tossed back and forth, by people on both sides of the table — accountability. We need accountability. They’re not being accountable. If we’re going to move forward, we need accountability.

No two people in that room meant the same thing by it.

So I set the agenda aside. A facilitator with proven methods in hand learns to read the room and bring in what the group needs, when the group needs it — and what this group needed wasn’t the next item on the action plan. It was a different conversation.

I ran a Focused Conversation — the ORID method: Objective, Reflective, Interpretive, Decisional — on the word itself. What does accountability look like in practice? Describe an instance you’ve seen of it, in work or out of work. Think of a time you yourself weren’t accountable — what was happening in that moment? What’s important to you about having accountability? What does it mean to have accountability for the work this group is trying to do? What would this group need to be accountable to each other? What could we put in place, together, to make accountability meaningful?

The air came out of the room.

You could feel the shift — in attitude, in relationship, in understanding, in awareness. People who had been circling each other warily were suddenly in the same conversation. The word that had been a weapon became a shared project. That single hour became the foundation of everything we built after it: not an accountability standard imposed on the group, but an accountability contract the group co-created.

We used the ToP action planning process to build in the metrics, the meetings, the tasks, and the coordination between the task teams across the two organizations. When external and internal factors shifted over the twelve-month project — and they always do — we used Secrets of Implementation tools to adjust without losing the thread. Once the action plan was complete, we ran a three-year strategic planning process to keep the groups aligned beyond the project itself, and to keep building the collaboration muscle and the accountability contract over time.

I worked with that group for a year. They moved mountains — not just in the work itself, but in how they worked with each other.

None of that would have been possible without the first hour. And the first hour only worked because the group built the contract together.

What the contract actually requires

Accountability gets asked for constantly in teams that are struggling. Leaders ask for it. Colleagues ask for it. Board chairs and coalition conveners ask for it. What almost never happens is the group sitting down and building the contract that would make accountability possible in the first place.

When accountability works, it’s not because everyone on the team is unusually disciplined. It’s because the group has built — explicitly or by accident — a working set of structural agreements that hold the commitment in place. When those structures are missing, even the most conscientious people can’t be accountable, because there’s nothing concrete to be accountable to.

A working accountability contract has six parts. All six have to be in place, and all six have to be visible to everyone involved.

Clear roles. Every person with a stake in the work knows what they are responsible for, and — just as important — what they are not responsible for. Role ambiguity is one of the most reliable accountability-killers I see. When three people think they own a decision and one person thinks the other two are helping, nobody actually owns anything.

Visible timelines. “Soon,” “when I get to it,” and “by end of quarter” are not timelines. They are polite ways of deferring commitment. Real timelines are specific, they are visible to the whole group, and they are revisited when circumstances change.

Regular check-ins. Accountability is not a single moment. It is a rhythm. A contract without scheduled check-in points is a contract that drifts. Most teams underinvest in this and then wonder why alignment decays between major meetings.

Shared norms for when things go sideways. What does the group do when an external factor makes the original plan impossible? What happens when a dependency slips? When someone realizes they took on more than they could handle? These questions need answers before the situation arrives, not in the middle of the stress.

Off-ramps and permission to fail. This is the one most teams leave out, and it’s the one that matters most. If the only way to stay in good standing is to deliver exactly what was promised, people will hide problems until they can’t hide them anymore. A real accountability contract includes explicit permission to come back to the group and say this isn’t working or we tried and it didn’t go the way we planned. Not as an excuse. As information the group needs to adapt.

The ability to name what’s happening. Underneath all five of the elements above is a deeper one: can people in this group actually say hard things out loud? Can they say I’m stuck. Can they say I don’t think this is the right assignment for me. Can they say something is off and I don’t know what yet. If they can’t, none of the other five structures will save the work.

None of this excuses ineffective work. A real accountability contract also has guard rails — ways of recognizing when a task isn’t the right fit for someone’s current skill set, ways of reassigning work without shame, ways of closing out commitments that are no longer serving the group. Accountability and grace are not opposites. They depend on each other.

Why meetings are where the contract lives or dies

Here’s what tends to surprise people: almost all of this work happens in meetings. Not because meetings are magical, but because meetings are where groups co-create the shared reality that accountability depends on. The hour I spent running a Focused Conversation with those two organizations wasn’t a detour from the work. It was the work.

Think about the meetings where accountability quietly breaks down. They usually have the same features.

They start without clear aims. No one in the room can articulate what decision or output this meeting is supposed to produce, so the conversation wanders and ends with vague next steps that nobody feels bound by.

They skip shared context. The group dives into solutions before establishing a common understanding of what’s actually happening, and the solutions that get proposed are built on different assumptions — which means people commit to things they don’t really agree with.

They don’t make space for feeling. Someone in the room has real frustration, real concern, or real enthusiasm about the work, and the meeting format doesn’t let any of it surface. The unspoken reaction becomes the thing that actually drives behavior after the meeting, and it never gets addressed.

They don’t let people bring their lived experience. The person closest to the work, or the person who has seen this kind of problem before, never gets asked. The decision gets made without the information that would have changed it.

They skip the why. People commit to tasks without ever connecting to the purpose the tasks are serving. A few weeks later, when priorities compete, they deprioritize the thing because they never felt a reason to protect it.

And most commonly: they end without a clear close. No named next step. No named owner. No named date. Everyone leaves with a different understanding of what was decided, and by the next meeting, the decisions have quietly dissolved.

If any of these sound familiar, what you have is not an accountability problem. You have a meeting problem. And the meeting problem is producing the accountability problem downstream.

What alignment actually looks like

The word alignment gets used as if it’s a state a team achieves once and then has. It isn’t. Alignment is a verb. It’s the ongoing practice of a group staying connected to its shared aims as conditions change.

One-and-done doesn’t work for alignment. A single retreat, a single strategic planning session, a single team offsite — these can produce clarity, but clarity decays. Without consistent meetings with clear agendas that move items from discovery to resolve, last quarter’s alignment becomes this quarter’s confusion.

Consistent alignment meetings have a few non-negotiable features. A clear agenda, shared before the meeting. Someone in the room holding the process — whether that’s a designated facilitator, a rotating role, or the leader stepping deliberately out of the content to manage the flow. Movement from exploration to decision within the meeting itself, not parked for “later.” And no meeting that ends without the who, what, and when of the next one.

Facilitation skill, in other words, is not a specialty. It’s a core capability for anyone asking a group to move from confusion to clarity. Which is most people with a leadership role, most of the time.

This is why training in facilitation methods matters so much more than it gets credit for. The Focused Conversation Method — the ORID structure I used with those two organizations — gives you a repeatable way to move a group from data to shared awareness to decision. The Consensus Workshop Method gives you a way to co-create shared agreements a group will actually own. The ToP strategic planning process weaves those methods into a full planning arc. The implementation toolkit keeps plans alive through the twelve- and thirty-six-month grind where they usually fall apart. These aren’t abstract frameworks. They are the specific tools that let a group build, and keep building, the accountability contract. This tools have been used and adapted for more than fifty years by ICA-USA.

What this means for leaders

If your team is struggling with follow-through, it’s worth asking a different set of questions than the ones most leaders start with.

Not: why aren’t these people accountable?

Instead: have we ever written the accountability contract together? Are the roles clear? Are the timelines visible? Do we have scheduled check-ins, or are we relying on people to flag problems without a mechanism for it? Do we have norms for what happens when things go sideways? Is it safe in this group to say “this isn’t working”? And are our meetings actually producing the shared reality the contract depends on — or are they unraveling it?

This reframe is not about lowering the bar. It’s about putting the structure in place that lets a high bar actually get met. Teams that build this kind of contract don’t need to ask for accountability. They produce it as a byproduct of how they work together.

Well-run meetings produce accountable teams. Badly-run meetings produce frustration that gets misread as a character flaw in the people attending them.

The good news is that the skills underneath this are learnable. Facilitation methods that build shared context, surface feeling, co-create norms, and close with clear next steps are teachable — and once a team has them, the accountability conversation changes completely.

People want to be accountable. They want to follow through. They want to work on teams where other people follow through too. What they need is the structure that makes it possible.

Give them the contract.

Common questions