Before we look outward, we look at ourselves
This guide isn't a diagnosis we're handing to someone else. It's something we're sitting inside together. If we want to invite transformation in the teams and organization around us, we start by being honest about where we have contributed to the loop — not to assign blame, but because credibility to lead change starts with the willingness to own our part in what isn't working.
One of the most common ways leadership teams contribute to a vacuum isn't through bad decisions — it's through abdicated ones. Decisions that were ours to make, that we deferred up, out, or into ambiguity because taking a clear position felt risky. The sections below name the patterns honestly. Tap each to explore what abdication looks like versus what ownership looks like in that area.
Leadership teams often genuinely believe they're waiting for "more clarity from above." But frequently the clarity they need is theirs to create — at their level, for their teams.
- "We're waiting for the strategy to solidify before we communicate anything"
- "We can't prioritize until leadership decides"
- "We gave the team a holding message"
- "Here's what we know, what we don't, and how we're making decisions in the meantime"
- "We're setting our own north star at this level until we have more"
- "We named the ambiguity to the team rather than hiding it"
Harmony-keeping feels like leadership maturity. Sometimes it is. But often it's the avoidance of a difficult conversation that compounds over time into something much more expensive.
- "We didn't want to raise it before we had all the facts"
- "We let it play out — maybe it would resolve itself"
- "We flagged it to HR rather than having the conversation directly"
- "We named what we were seeing early, even without a full picture"
- "We had the direct conversation rather than routing around it"
- "We acknowledged the tension in the room rather than performing harmony"
When we don't name missed commitments clearly, we inadvertently teach the team that commitments are suggestions. The bar we walk past is the bar we set.
- "We moved the goalposts without acknowledging we did"
- "We let the deadline slip without a real conversation about why"
- "We privately knew this wouldn't land but didn't say so publicly"
- "We named the miss and what contributed to it — including our own decisions"
- "We changed the scope but we said we changed it and why"
- "We closed the loop on what we said we'd do"
Culture is what we do when no one's watching, and what we tolerate when everyone is. If we want psychological safety, candor, or accountability in the team, we have to visibly embody it first.
- "We asked for candor but got quiet when something uncomfortable was said"
- "We talked about psychological safety but the last person who spoke up paid a cost"
- "We ran retros but didn't change anything we ourselves were doing"
- "We named something we each got wrong in the past quarter — without being asked"
- "We thanked the person who raised the uncomfortable thing and acted on it"
- "We changed our own behavior before reinforcing the standard in others"
These are questions to sit with as a leadership team, not to answer alone and compare. The point isn't to feel bad about what we haven't done — it's to get honest about where we have agency that we may not have used. Check the ones that feel true for your team this past quarter.
We deferred a decision upward that we actually had the authority and information to make ourselves
We saw something going wrong and waited for someone else to name it first
We asked our teams for something we weren't consistently doing ourselves
We let a missed commitment pass without a real conversation about what happened
We performed alignment in a meeting and then did something different afterward
We contributed to the leadership vacuum by not filling space that was ours to fill
"The most powerful thing a leadership team can do is go first — name what it got wrong, own what is in its control, and model the standard before requiring it of anyone else."
Patterns we might be living inside right now
These aren't verdicts. They're invitations to look honestly at what's familiar. Some of these will resonate strongly — and that's useful information, not a failure. Notice which ones prompt a reaction as much as which ones feel true.
Every week is a crisis
Urgent problems crowd out strategic work. Planning feels optional because the plan rarely survives first contact with Monday.
Heroes, not systems
Results depend on specific people's effort. When those people are stretched or leave, things fall apart quickly — and we quietly know it.
Vision that doesn't travel
There's a strategy somewhere. But it hasn't been translated into something teams can actually use to make decisions at their level.
Silence flowing upward
Problems don't reach leadership — not because things are fine, but because people have learned, somewhere along the way, that raising issues costs more than absorbing them.
Decisions that loop back
Nothing feels truly decided. Conversations revisit the same ground. It's not clear who owns what — so decisions either get made multiple times or not at all.
Metrics without shared meaning
There's data. Maybe dashboards. But there's no shared agreement on what the numbers mean or what to do when they move.
Teams optimizing in isolation
Product, engineering, and design each do their best work. But coordination across those teams carries more friction than it should.
Alignment performed, not achieved
Agreement shows up in meeting rooms. It dissolves in the hallway. People nod and then do something different — not out of bad faith, but because the alignment was never real.
We've been "working on our process" for more than six months without a clear change in behavior
New people join and within 30 days they've learned to stay quiet about what they notice
We say we want candor — but the last person who was candid paid some kind of cost
We don't have shared definitions for basic things like "done," "priority," or "success"
The most influential person in a room tends to determine the outcome — not the best argument or evidence
We run retrospectives but can't easily name what changed because of the last one
The thinking patterns that keep us here
These aren't character flaws — they're predictable responses to pressure, uncertainty, and systems that have historically rewarded certain behaviors. Naming them together makes them easier to notice in real time, which is when it matters.
"Silence flowing upward isn't an employee engagement problem. It's a leadership design problem. And it's one we can actually do something about."
What people are protecting when things don't change
Resistance to change is almost never irrational. People are protecting something real — identity, safety, relationships, status. Understanding what's genuinely at stake in a shift helps us design change that doesn't just demand something different, but makes it easier to let go of what's being held.
- Status built on knowing how things work here — process clarity distributes that knowledge more widely
- Identity as the person who gets things done, rather than the person who built the system that gets things done
- Safety from being visibly wrong — new processes make performance more legible
- Relationships with leaders who benefit from the current ambiguity
- The familiarity of a known dysfunction over the uncertainty of something new
- A leader's informal authority — clear decision rights distribute power downward
- Plausible deniability — vague accountability means no one is cleanly at fault when things go wrong
- Short-term velocity — building process genuinely feels slower before it makes things faster
- The appearance of alignment without the effort required to achieve it
- A culture where relationship capital matters more than clarity and follow-through
"Dysfunction that persists isn't persisting by accident. Something is being served by it. Understanding what that is — without judgment — is how you find the real lever for change."
How to actually move — starting with ourselves
The shift from Foundational to Developing isn't a project to manage. It's a series of honest conversations followed by structural changes that make the new behavior more natural than the old. Start small. Start real. Start with what's in our own control first.
Name one thing we're each going to own differently
Before this guide goes anywhere near another team, each of us names one concrete thing in our own behavior — a pattern we've seen in ourselves — and commits to something specific and observable. Not a value. An action.
Trace one recent failure upstream
Pick something that went wrong in the last quarter and map accountability backward: what was decided, by whom, with what authority, and at what level. Most teams find the visible failure was downstream of an invisible decision made higher up — sometimes by us.
Define one thing that everyone means differently
Pick a single term — "priority," "done," "owner," "aligned" — and get explicit, written agreement on what it means. Then test it in the next real situation. Watch how quickly shared language shifts behavior.
Create one real escalation moment — and close the loop on it
Invite a specific type of feedback, act on it visibly, and tell the team what you heard and what you changed. Do this once genuinely and the signal about safety spreads without an announcement.
Bring in an outside perspective
The people inside the system are inside the system. An external facilitator, org designer, or executive coach — not to validate our read, but to challenge it — is often the most efficient path. Not a sign of failure. A sign of seriousness.
Understand who has the most to lose from clarity — and design for that
Process clarity distributes power. Someone currently benefits from ambiguity. We don't need to confront them — but we do need to understand their stake and find a path that doesn't make them an enemy of progress.
How we'll know we've made the shift
Developing stage isn't frictionless. It's not even always comfortable. But it's honest — and it's self-correcting. These are the behavioral signals that we've genuinely crossed over, not just talked about crossing over.
Decisions have clear owners
Not everyone who was involved — one owner. That's known before the decision, not discovered after it goes wrong.
Problems travel upward
People surface issues because the last person who did experienced something other than silence or consequence. The feedback loop works.
Strategy is operational
The direction has been translated into something teams can actually use. "Is this on strategy?" is a question people can answer for themselves.
Disagreement is productive
People push back in real time — not to perform, but because it's actually safe. And the idea usually improves as a result.
Shared language holds
When we say "priority one," everyone means the same thing. Language is precise because someone made it precise intentionally — and it stuck.
Retrospectives produce real change
One genuine change per cycle — not 12 action items that disappear. The rhythm of learning and adjusting becomes the team's normal.
New people don't learn to hide
When someone joins, they're not socialized out of candor within 30 days. Their fresh perspective is actually used — not gradually dulled.
Accountability is systemic
When something goes wrong, the first question is "what in the system allowed this" — not "whose fault is it." And that question gets asked honestly, without theater.
"Developing stage doesn't mean things are easier. It means problems are visible earlier, owned more clearly, and addressed before they become crises. That compounds over time in ways that are hard to overstate."