INTRO: The Rules Nobody Wrote Down

Every organization has a set of invisible rules. Not the ones in the employee handbook or the org chart — the ones that live in behavior. In what people do automatically. In what nobody says out loud, but everyone adjusts to.

These aren’t accidents. They’re adaptations. They develop in the gaps — when formal systems don’t cover everything, when a conflict feels too risky to name in the moment, when someone steps into a breach once and then keeps stepping in. Nobody announces them. But people learn them fast.

In the early stages of an org, a lot of these informal rules are actually useful. They fill in the white space. They let a small team move quickly without stopping to negotiate everything. The problem isn’t that they exist.

The problem is what happens when they stop being temporary workarounds and start being load-bearing walls. When the org grows around them. When decisions, relationships, and entire workflows start depending on rules no one has actually agreed to — and that no one feels safe questioning. That’s when unspoken agreements stop being adaptive and start being a design problem.

PART 1: Why They Stay Hidden

Unspoken agreements are invisible by design. They don’t live in documents. They live in patterns — in what people consistently do, and more importantly, in what they consistently don’t do.

The first reason they’re so hard to name is that they usually feel like kindness or loyalty. The ED absorbs the hard donor conversations because she doesn’t want to put her development director in an uncomfortable position. The ops lead quietly covers budget gaps because she doesn’t want to alarm the team. These feel like generous accommodations. But over time, they harden into expectations — and expectations are much harder to renegotiate than decisions.

The second reason: naming an unspoken agreement can feel like making an accusation. Once it’s visible, someone has to own it. That can feel like you’re calling out a person instead of a pattern. So it stays quiet. And the pattern continues.

Think about a path worn into a lawn. Nobody decided to make a path there. People just kept walking the same route because it was easier. But once the path is worn in, changing course means stepping deliberately into the grass — more intention, more effort than just following what’s already there. That’s what surfacing these agreements requires.

PART 2: What They’re Actually Costing You

Here’s the reframe: unspoken agreements don’t just shape how your organization behaves. They shape what your organization is capable of. And that’s the part most leaders underestimate.

When the ED is the only one who handles hard conversations, the org never builds that capacity anywhere else. When budget gaps get quietly absorbed, the leadership team never has to grapple together with hard financial tradeoffs. When a board member goes unchallenged, governance stays polite — but never gets sharp enough to actually be useful.

Every unspoken agreement sets a ceiling. On your team’s growth. On accountability. On how clearly leadership can see what’s actually happening inside the organization.

This is what I think of as one of the quieter faces of the Design Deficit — not the chaos that’s visible, the fire-fighting and the overwhelm and the missed deadlines. But the friction that’s been normalized. The structural drag no one talks about because talking about it feels too risky. The things everyone knows and nobody says.

I’ve worked with EDs across dozens of organizations at this inflection point — the $1M mark, the $2M, the $3M threshold — and almost every single one has a layer of these running. The agreements themselves aren’t always catastrophic. But when growth comes and they get pressure-tested, that’s when you feel how much weight they were silently carrying.

PART 3: Three Places Worth Looking First

This isn’t a comprehensive audit. It’s just three places I consistently see unspoken agreements doing the most structural damage — and where it makes sense to look first.

Inside the leadership team’s division of labor. Not who’s on the org chart — but who actually carries what. Who quietly absorbs the things that fall through the cracks? Who consistently steps back when someone else has a strong opinion? Who does the emotional labor of keeping team morale steady, even though it’s nowhere in their job description? These informal distributions of burden often go unexamined the longest because they feel interpersonal. They’re not — they’re structural. And they shape who gets stretched and who gets protected.

In how accountability actually works. Every org has a formal accountability structure and a real one. The formal one lives in job descriptions and org charts. The real one lives in patterns — who gets honest feedback and who doesn’t, whose commitments get followed up on and whose get quietly forgiven, what kinds of misses get named out loud and what gets absorbed. That gap between the official structure and the actual one is visible to everyone on your team — even when it’s invisible to you.

At the board level. This is where unspoken agreements tend to be the oldest and the most entrenched. Three questions to sit with: Which board members’ voices consistently carry more weight than their role suggests — and why? What topics always get tabled for “next time”? What does the ED actually share with the board versus what she manages quietly on her own, because it just feels easier?

PART 4: The First Move

The goal isn’t to root out every informal norm in your organization. Some informal rules are fine. Some are even good. The goal is to know which ones are actually running things — and to make a conscious choice about whether those are the rules you want.

The first step in surfacing an unspoken agreement is almost always naming it as a pattern, not as a problem. Not “why does this keep happening” — but “I notice this keeps happening. Can we talk about what’s underneath it?” That move — from accusation to inquiry — is what makes it possible to look at. It’s where the work starts.

An organization that runs primarily on unspoken agreements has an operating manual that exists only in people’s heads. What lives only in heads doesn’t survive transition, growth, or change. You can’t build on it.

A Process to Surface Unspoken Agreements in Your Organization

Step 1: Look for patterns in behavior, not policy.
Pay attention to what consistently happens — especially what people avoid. Where do conversations get sidestepped? What decisions always follow the same unwritten script? The pattern is often more visible in what doesn’t happen than in what does.

Step 2: Notice who carries invisible weight.
Who absorbs tension, fills gaps, or takes on responsibilities that aren’t formally theirs? These informal burden-holders often signal the deepest unspoken agreements — the ones the organization has built around without examining.

Step 3: Compare formal accountability to actual accountability.
Look at your org chart and job descriptions, then compare them to reality. Who actually gets feedback? Whose commitments are enforced? The distance between the formal structure and the real one reveals where invisible rules are doing the governing.

Step 4: Name the pattern out loud.
This is the hardest step. Frame it as an observation, not a blame statement — you’re identifying a system, not calling out a person. The move from accusation to inquiry is what makes it possible for the team to look at the pattern together.

Step 5: Decide what’s intentional going forward.
Not every informal rule is bad. The goal isn’t elimination — it’s conscious choice. Decide which norms you keep because they serve the organization, and which ones you redesign because they’ve become structural constraints.