Hi Reader,
Today's newsletter is guest-written by our good friend Sam Spurlin, the founder and principal consultant of Deliberate Works. Deliberate Works helps leaders craft ever better organizations by building their own internal capacity to change gracefully and deliberately.
What makes the best stories feel real, even when set in fantastical environments, is the internal coherence of the world in which they exist. Before a single character speaks, they've worked out how the economy functions, where the borders are, which old wars are still remembered, what is forbidden and why. This is worldbuilding, and its purpose is not decoration. It's infrastructure. A well-built world makes some events possible and others impossible; it gives whatever happens inside it weight and coherence. The writer isn't narrating what happens — they're constructing the conditions under which anything that happens will make sense.
I think this is what teams and organizations often lack. What is done and not done, what is focused on and what is de-prioritized, what is celebrated and what is ignored, feels random and incoherent. This randomness and incoherence builds and builds. The entropy rises. And eventually things fall apart.
I've come to think this is the most useful way to understand what a team charter is actually for. It's also the clearest diagnosis of why most of them fail.
Most Charters Are Just Rulebooks
Open a typical team charter (if it exists at all) and you'll find values, behavioral norms, a meeting cadence, communication agreements, and maybe a section on how the team gives and receives feedback. It tells the members how to behave toward one another. That's not worthless — a team with no agreements about conduct will reliably reinvent its dysfunctions every quarter — but it is thin.
A simple organization can run on a rulebook, because its situations repeat — write a good enough procedure and you've covered most of what will arrive. A complex one can't. It generates more novelty than any set of rules can absorb, which means the decisions that matter most will be the ones nobody wrote a rule for: made by people far apart, under pressure, with no chance to check in. You can't pre-load the right behavior in a situation like that. What you can do is build a world — a shared sense of what's real, what's at stake, where the edges are, and why any of it matters — coherent enough that people improvise well in situations a typical charter never anticipated. A business-as-usual charter tries to specify conduct in advance. A charter as an act of worldbuilding tries to make good judgment possible when no one is there to direct it.
The Components That Actually Build a World
If you want to add a taste of world building to your next team charter, explore the following sections and see if they make the world your team inhabits feel more cohesive or real. These parts of a charter try to shift us away from describing behavioral expectations and into articulations of what matters and why.
Interfaces. This is the geography — the team's borders and the goods and/or services that flow across them. Where does this team end and the next one begin? What crosses the boundary in each direction? What do the neighboring territories expect from us, and what are we owed in return? It's no accident that this cross-functional work is often the most fraught that — the missed handoff, the duplicated work, the thing everyone assumed someone else owned.
Who We Serve. Every world is filled with characters who want things. Who are the characters we care about in this world? Who has standing to make a claim on this team's work, and — just as important — who doesn't? A team that can't answer this says yes to everyone, prioritizes by volume and proximity, and ends up serving no one in particular. Naming the people or roles that have an outsized impact in our world is one of the most clarifying and least common things a charter can do.
History. This is the lore. Why does the team exist? What has it tried and abandoned, and why? What are the scars, and what has the group quietly agreed not to relitigate? Teams that skip this hand new members the present with none of the past, and then watch them step on buried wires no one warned them about. A world without history has no explanation for its own shape.
A pair of others belong here too: Victories and Defeats — what the team has decided, learned from, and/or overcome — and the Unknown, the open questions we don’t have easy answers for, but are on our mind nonetheless.
None of these tell anyone how to behave. They instead try to articulate what's true. That is the difference between a world and a rulebook, and it's why a charter assembled only from norms tends to feel weightless.
A World is Tended, Not Finished
Folks love to call charters "living documents," and then treat them like monuments. Write it once and never look at it again. When it goes stale we blame ourselves for not "revisiting" it, as though the missing ingredient were discipline. It isn't. The missing ingredient is continuity.
A fictional world dies the instant its rules change without explanation. Two seasons in, a character does something the established world said was impossible, nobody accounts for it, and the audience stops believing. The world has lost its canon. Exactly the same thing happens to teams. The charter says decisions are made by consent; in practice the loudest voice wins. It names a customer the team stopped serving a quarter ago. The contradictions pile up, everyone notices, and the document becomes fiction in the bad sense — something no one trusts, because it no longer matches the world it claims to describe.
Keeping a charter alive, then, is not a recurring reminder on someone's calendar. It's a role and a practice. Every enduring fictional universe has someone keeping the codex — tracking what's canon, catching contradictions, deciding what is now true and noting when it changed. A team needs the same function: someone who carries the thread forward from the last decision, names when something has shifted and why, flags when a new agreement quietly contradicts an old one, and keeps the canon visible enough that a new joiner can be told here's what we've decided, here's why, and here's what we still haven't figured out.
That final clause is the one most teams miss. A living world includes its open questions. Canon isn't only the settled stuff; it's also a map of what remains unsettled. A charter that only records what's certain will always read as either naive or out of date.
The Codex, Not The Contract
So stop treating the charter as a document the team signs once and files. Treat it as the team's codex — the canonical reference for the world the team works inside. Its job is not to constrain behavior. Its job is to make the team's reality coherent enough that the team's actual story can happen and mean something.
Most teams are working without a world. They have rules of conduct and no map of the territory: no clear borders, no named claimants, no memory of their own history. Then they wonder why the laminated page on the wall feels so dead. Nothing can live in a place that was never really built.
-Sam Spurlin
Sam Spurlin is the founder and principal consultant of Deliberate Works. Deliberate Works helps leaders craft ever better organizations by building their own internal capacity to change gracefully and deliberately.
Enjoying this newsletter?
You’ll love the conversations happening on our Leading Together Podcast and YouTube channel, where we dive deeper into how you can build a high performing leadership team
|
Check Out Our Latest Podcast Episode
When team tension and conflict arises, it's often because something significant is unclear. Team Agreements can go a long way towards driving clarity and alignment.
In this episode, we sit down with organizational consultant and Deliberate Works founder Sam Spurlin to explore the practices that help teams work better together over time. We discuss team agreements, team charters, operating rhythms, retrospectives, decision-making, psychological safety, and why trust is built through meaningful shared work.
Sam shares lessons from his work with the Ready where he worked with fortune 500 companies in several industries, including how teams can create greater clarity, strengthen connection, improve accountability, and build the habits that sustain long-term performance.
If you're part of a leadership team, executive team, or any group working to improve how you collaborate, this conversation offers practical insights you can put into practice immediately.
Upcoming Events & Opportunities: