The Syllabus Gap: Why Your Team Never Got the Rules
| Chris Dyer, named the #1 Leadership Speaker to Follow in 2026 by MSN.com, uses the term Syllabus Gap for the distance between the rules a team actually runs on and the rules anyone ever agreed to out loud. His fix is a team charter: six questions the team answers together in one ninety-minute session, written down with real numbers, and renegotiated on a set date.This guide covers what the Syllabus Gap costs, why manager-written expectations stop working after about six weeks, the six questions that build a charter, a ninety-minute agenda for running the conversation, and how to set an expiration date so the charter stays alive. |
Table of Contents
- The Syllabus Gap, Defined
- What Chris Dyer Hears in Pre-Keynote Interviews
- Why Manager-Written Expectations Stop Working After Six Weeks
- The Six Questions That Build a Team Charter
- How to Run the Charter Conversation in Ninety Minutes
- Charters Expire: The Renegotiation Rule
- Where I Got This Wrong
- Frequently Asked Questions
This morning I dropped my grandson at kindergarten. I stayed longer than I needed to.
Parents crowding the doorway. That particular kind of noise. A teacher at the front of the room holding one piece of paper.
She read it out loud. What they would be learning. Where the backpacks go. What to do when you need help. How you would know if you were doing it right.
Day one. Before a single lesson.
Not one of those five-year-olds had to ask three people and assemble the answer from context. Nobody had to earn that clarity. It got handed to them, because we have collectively decided that kindergarteners deserve to know how this works.
Then you grow up and the piece of paper stops coming.
The Syllabus Gap, Defined
The Syllabus Gap is the distance between the rules a team actually runs on and the rules anyone ever agreed to out loud.
Every team has operating terms. Response times. What counts as urgent. Who breaks a tie. Whether a message at 9 p.m. is a question or an emergency. Those terms exist whether or not a single word of them was ever written down.
Usually nothing was written down. People absorb the terms by watching, guessing, and getting corrected. A new hire spends her first four months decoding a system nobody ever explained to her, and the decoding is invisible, so it never shows up as a cost.
It shows up somewhere else. Gallup has been asking employees the same question since the 1990s: do you know what is expected of you at work? Roughly half of US workers strongly agree. That figure has moved very little across three decades, two recessions, and an entire industry of management software built to fix it.
Half. On the most basic question on the list.
What Chris Dyer Hears in Pre-Keynote Interviews
Chris Dyer interviews employees before most of his keynotes. Eight to fifteen people, fifteen minutes each, no leadership on the call. Across 300-plus keynotes in more than 20 countries, that adds up to a lot of quiet conversations with people who have no reason to perform.
Three patterns come up over and over.
The first is the invisible scoreboard. People can describe their tasks in detail and cannot describe what good looks like. They know what they do on Tuesday. They do not know what would get them promoted, and they have stopped asking.
Then there is the urgency lottery. Nobody on the team shares a definition of urgent, so everything arrives at the same volume, and the loudest requester wins. One operations manager at a healthcare client put it this way to me: every message looks like a fire, so I have started guessing which fires are real.
Last, inherited terms. The way the team works was decided years ago, on somebody’s first week, by people who no longer work there. The rules outlasted the humans who made them.
What almost never comes up first is burnout, and it is rarely pay. The most common thing I hear is some version of: I am not sure what I am being judged on.
Why Manager-Written Expectations Stop Working After Six Weeks
Most leaders respond to this the obvious way. They write the syllabus themselves. Expectations. Values. Meeting norms. How we handle conflict.
It goes on a slide. Maybe a poster. Everyone nods.
Six weeks later nobody can quote a word of it.
The content usually was not the problem. The delivery was. A document that arrives finished asks the team for compliance, and compliance has a short half-life. A document the team argued its way into asks for something else, and people defend what they helped build.
Michael Norton, Daniel Mochon, and Dan Ariely documented the effect in the Journal of Consumer Psychology in 2011. Participants who assembled their own IKEA storage boxes were willing to pay roughly 63 percent more for them than participants handed identical, pre-assembled boxes. Same box. Same function. The labor changed the valuation.
Team agreements work the same way. The argument is what makes the document stick.
| Issued Expectations | A Team Charter | |
| Who writes it | The manager, alone, usually the weekend before an offsite | The whole team, out loud, in one session |
| What it contains | Values and adjectives: ownership, candor, excellence | Numbers and names: four hours, Thursday, Priya breaks the tie |
| Where disagreement goes | Into private side conversations after the meeting | Into the room, which is the point of the exercise |
| Shelf life | About six weeks, then it becomes wall art | A set expiration date, renegotiated on the calendar |
| When someone breaks it | The manager enforces a rule the team never chose | Anyone can point at a line the person agreed to |
The Six Questions That Build a Team Charter
A team charter is the grown-up version of the syllabus. Same content as the poster on the wall, opposite direction of travel. The team writes it together, out loud, and every person in the room has to actually agree to it.
Six questions get you most of the way there.
1. Where do we communicate, and what goes where?
Name the channel for each type of message. Decisions go in email so they are searchable. Quick questions go in chat. Anything requiring more than three back-and-forths becomes a call. Most teams have never made this explicit, so every person applies a private rule and then gets quietly annoyed when others break it.
2. How fast do we owe each other an answer?
Put a number on it. Four business hours for chat, one business day for email, same day for anything a customer is waiting on. The number matters less than the fact that it exists. Without one, the fastest responder on the team accidentally sets the standard for everyone else, and that person is usually on the edge of burning out.
3. What counts as urgent, and what happens after hours?
Define urgent by consequence, not by feeling. A revenue-affecting outage is urgent. A slide deck for Thursday is not, even when it feels like it at 10 p.m. Then decide what an after-hours message means. Many teams land on a simple version: if it is truly urgent, call. If you send a message at night, nobody is expected to read it until morning.
4. How do we decide, and who breaks the tie?
Write down which decisions need consensus, which need input, and which one person just owns. Then name the tiebreaker by first name for each category. Teams lose weeks to decisions that were nobody’s to make. Naming the tiebreaker in advance costs one sentence and saves a quarter.
5. Which meetings would we kill if we started over?
Ask the question in exactly that shape. Assume every recurring meeting on the calendar has been cancelled, then argue for which ones to bring back and why. The meetings nobody defends should stay dead. Expect at least one person to defend a meeting purely because it is the only time they see certain colleagues, which is a real reason and worth naming out loud.
6. What do we owe each other when someone drops the ball?
This is the one teams skip, and it is the one that decides whether the rest holds. Decide the repair, in advance, while nobody is angry. Something like: you tell the person directly within a day, you say what you will do differently, and it ends there. Agreements without a repair clause turn into resentment the first time somebody misses.
Nobody agrees on the answers at first. That disagreement is the value. The argument is the deliverable, and the document is the receipt.
How to Run the Charter Conversation in Ninety Minutes
You can do this in one session. Ninety minutes, whole team, one person writing on a shared screen where everyone can see the words appear.
- Minutes 0 to 10. Frame it. Say plainly that the team is setting its own terms, that the terms will be written down, and that the leader will go last on every question.
- Minutes 10 to 25. Silence. Everyone answers all six questions on their own, in writing, before anyone speaks. This keeps the first confident voice from setting the anchor.
- Minutes 25 to 70. One question at a time. Read the range of answers out loud without attribution. Spend the most time where the answers are furthest apart, because that gap is exactly what has been causing friction.
- Minutes 70 to 85. Write the actual sentences. Every line gets a number, a name, or a channel. If a line could describe any team at any company, it is not finished.
- Minutes 85 to 90. Set the expiration date and put it on the calendar.
Two rules make or break the session. The leader answers last, every time, or the exercise becomes a guessing game about what the boss wants. And no vague verbs. Support, align, collaborate, and communicate are not commitments. Reply within four hours is a commitment.
Charters Expire: The Renegotiation Rule
School renegotiates every August. New teacher, new terms, fresh page, no grudges carried forward. That reset is the part most teams never copy.
Your team set its terms once, informally, on somebody’s first day, years ago. Half the people in that original conversation have left the company. The terms stayed.
Put an expiration date on the charter. Six months works for a fast-changing team, twelve for a stable one. Renegotiate on that date whether or not anything feels broken, because the point is to make the conversation routine rather than a signal that something has gone wrong.
Renegotiate early when any of these happen: the team gains or loses a manager, headcount crosses eight people, the team absorbs another team, or the same argument shows up three times.
Where I Got This Wrong
I ran PeopleG2 for fifteen years. At one point I sat down over a weekend and wrote out the way our teams should work. Expectations, communication norms, what to do when two people disagreed. It was good writing. I had it printed and framed, and I was proud of it.
A few months later I asked a group of managers, casually, what our operating agreements were. One person got close on one item. The rest looked at me the way you look at a pop quiz on a book you skimmed.
I had written the whole thing alone. Every one of them had nodded at it in a meeting, and nodding is not agreeing. I had produced a very expensive poster.
When we redid it as a conversation, the document that came out was shorter and uglier than mine. People used it. That version had their fingerprints on it, and mine did not.
Bringing the Charter Conversation Into a Room
Chris Dyer built this material out of what employees say when leadership is not on the call, and it shows up in his keynote work on culture and moments that shape how people experience their jobs. Inc. Magazine named Chris Dyer the #1 Leadership Speaker on Culture, and he ranks #15 on the Global Gurus Top 30 Organizational Culture Professionals for 2026. Teams that want to run the charter conversation live, with a facilitator in the room, can start at the speaking page below.
Frequently Asked Questions
What is a team charter?
A team charter is a short written agreement, created by the team together, that spells out how the team communicates, decides, handles urgency, and repairs mistakes. Chris Dyer describes it as the grown-up version of a classroom syllabus, with one difference: a syllabus is handed down by the teacher, while a charter is negotiated by the people who have to live inside it.
What questions should a team charter answer?
Six questions cover most of the ground: where we communicate and what goes where, how fast we owe each other an answer, what counts as urgent and what happens after hours, how we decide and who breaks the tie, which meetings we would kill if we started over, and what we owe each other when someone drops the ball.
How is a team charter different from company values?
Company values describe character. A charter describes mechanics. Values say we communicate openly. A charter says decisions go in email, questions go in chat, and you get an answer within four business hours. A charter line that has no number, name, or channel in it is a value in disguise and will not change behavior.
How often should a team update its charter?
Chris Dyer recommends putting an expiration date on the charter from day one, every six to twelve months, and renegotiating on schedule rather than waiting for a problem. Renegotiate earlier if the team changes managers, grows past eight people, merges with another team, or keeps relitigating the same argument.
Who should write the team charter?
The team, together, in one session. When a manager writes it alone the document usually reads better and works worse, because agreement comes from the argument that produced the words. The manager’s job in the session is to facilitate, protect the disagreement, and answer every question last.
Where to Go Next
The charter conversation is one of the seven types of moments covered in Moments That Matter. The companion workbook is free, with no email required, at chrisdyer.com/moments.
To bring this conversation to your team or conference, see chrisdyer.com/speaking, or contact Shannyn Downey at 6 Degrees Speaker Management: shannyn@6degreespeakers.com, 888-584-4177.
