Most Team Charters End Up as Wallpaper
Most team charters end up in a shared drive folder that nobody opens after the offsite.
I‘ve seen it so many times it‘s almost comic—a leadership team spends a full day crafting vision, values, norms, roles. They print it on card stock. They hang it in the conference room. By week three, it‘s wallpaper. The same dynamics that existed before the charter exist after it. Nothing changed.
The problem isn‘t the charter. It‘s how it‘s built and what it‘s built for.
A charter that works isn‘t a document. It‘s a set of agreements that a team returns to when things get hard. When there‘s disagreement about who decides, when someone‘s underperforming and nobody knows whose job it is to address it, when the team is drifting and can‘t articulate why.
I‘ve built these across vastly different environments: from post-conflict governance teams to corporate leadership teams navigating mergers. The principles are the same. The charter needs to answer the questions that cause real friction, not the questions that feel comfortable to discuss at an offsite.
The Three Questions Your Charter Must Answer
Most charters focus on aspirational language: “We value transparency, collaboration, and excellence.“ Fine. But when the Product lead and the Engineering lead disagree on a deadline and both believe they‘re being transparent, collaborative, and excellent—what happens? The aspirational language doesn‘t help. It‘s the equivalent of building psychological safety without standards—nice in theory, useless under pressure.
Your charter needs to answer three questions that shape day-to-day behavior:
Question 1: How do decisions get made here?
This is the biggest source of dysfunction in teams. Not personality. Not culture. Decision rights.
Be specific: What decisions does the team leader make unilaterally? What decisions require input from the full team? What decisions get delegated to individuals? When there‘s disagreement, who breaks the tie?
I once worked with a team that spent three months paralyzed because nobody had explicitly agreed whether the team lead could make hiring decisions alone or whether the full team needed to weigh in. Three months. A single sentence in a charter would have prevented it.
Get specific. Name the categories of decisions and who has authority for each.
Question 2: What Do We Expect From Each Other?
Not values. Behaviors.
“We value accountability“ is useless when someone misses a deadline. “If you‘re going to miss a commitment, you notify the team 48 hours in advance and propose a revised timeline“ is useful.
Build your behavioral expectations from the friction points your team has faced. What‘s gone wrong before? Where have you been frustrated with each other? Those are the norms you need.
I recommend each team member contributes one behavior they need from the group to do their best work. You‘ll see patterns. You‘ll also see blind spots. One person needs advance notice on changes. Another needs direct feedback instead of back-channel conversations. A third needs meetings to end with clear decisions, not open-ended discussion.
Collect these. Turn them into explicit agreements. Write them in active, behavioral language.
Question 3: How Do We Handle Breakdown?
Every team will have breakdowns. Missed deadlines and dropped commitments. The question isn‘t whether this will happen. It‘s what happens when it does.
Most teams don‘t have an answer. So breakdowns become interpersonal dramas instead of process problems. Someone‘s angry, someone‘s defensive, and it escalates.
Your charter should include a simple repair process—what Kerry Patterson and colleagues call a crucial conversation structure. When a commitment breaks: (1) Name it directly, without blame—share the facts, not your story about what the facts mean. (2) Understand what happened—not to assign fault, but to learn. Make it safe enough for the other person to tell the truth. (3) Decide what changes. (4) Move forward.
This borrows from Chris Argyris‘s Ladder of Inference—the idea that we all climb a mental ladder from raw data through interpretation, assumptions, and conclusions to action, usually without examining the rungs below. When a commitment breaks, most people jump straight to the top of the ladder: they interpret, assume intent, and react. This repair process forces you back down the rungs. What actually happened? What did each person understand? You‘re climbing toward understanding, not toward judgment.
Building the Charter: A Process That Works
Don‘t build a charter in a single afternoon session. That produces documents people forget.
Phase 1: Individual reflection (before you meet). Each team member answers: What are the three biggest friction points on this team? What do you need from your colleagues to do your best work? What‘s one thing you‘d change about how we operate?
Phase 2: Facilitated conversation (90 minutes max). Share answers. Look for patterns. Where are you aligned? Where are you in tension? The tensions are the gold. That‘s where the charter needs to live.
Phase 3: Draft the agreements. Not aspirations but agreements: behavioral, specific, testable. “We provide feedback directly to each other, not through the team leader“ is an agreement. “We value open communication“ is wallpaper.
Phase 4: Revisit regularly. This is the step that separates real charters from decorative ones. When you‘re first building the habit, revisit monthly, spend 15 minutes reviewing: Are we living these agreements? Where did we fall short? What needs to adjust? Once the practice is embedded, shift to quarterly. The charter is living or it‘s dead. Regular check-ins keep it alive.
Why Charters Fail
They fail when they‘re aspirational instead of operational. When they answer “Who are we?“ instead of “How do we work together when it‘s hard?“ When the leader builds them alone and announces them to the team. When there‘s no mechanism for accountability or revision.
They succeed when the team builds them together, when they address real friction, and when someone has the courage to say, “We agreed to something different. Let‘s talk about what happened.“
A working charter doesn‘t eliminate conflict. It gives you a shared language for navigating it.