Threshold is centered on you, your leadership, and the impact you want to have.
Select the level that best reflects your current role. This is your starting point, not a judgment.
Month Four gave your team a delegation system. RASCI made ownership explicit. The 1:3:1 protocol kept the work on their side. The development plans made growth intentional. You built the infrastructure of a Head Coach.
Here is what Month Four did not solve: a system built on the right tools still breaks down when the culture underneath it cannot support honest execution. You can have the best accountability structure in the world and watch it quietly fail because people are not saying what they actually think.
Month Five addresses that layer directly. This is the work beneath the work: creating the conditions where your team can surface problems early, challenge assumptions out loud, give direct feedback without fear, and learn from experience without blame. That set of conditions has a name. It is called psychological safety, and it is not the same thing as comfort.
Safety means your team knows it is acceptable to be wrong in front of you. Comfort means nobody has to be uncomfortable. The first builds organizations. The second stalls them.
This month you will learn to distinguish the two, diagnose where your team currently sits, and build the structural conditions that make honest execution possible. The goal is not a warmer culture. The goal is a more capable one.
Before we begin, assess where your team culture is today. Be honest about what is actually happening, not what you intend. No one sees these results.
My team openly challenges ideas in meetings, including mine, without it feeling like a personal risk.
When something is going wrong, team members bring it forward before it becomes a crisis rather than hoping it resolves on its own.
Feedback on my team flows in multiple directions. People give it upward, sideways, and downward. It is expected, not feared.
When things do not go as planned, my team analyzes what happened to improve the next attempt rather than moving on silently or assigning blame.
My team understands not just what we are deciding but why. People know where they have input and where decisions have already been made.
When someone raises an uncomfortable truth or flags a real risk, they are recognized for it rather than quietly penalized for disrupting harmony.
The most damaging misconception in leadership: believing that a team where everyone is comfortable is a team that is performing well. Comfort and safety are not the same thing. Confusing them is expensive.
Amy Edmondson's research maps team culture across two dimensions: how much accountability the team holds for results, and how much psychological safety exists to take risks, speak up, and be wrong. The intersection produces four distinct cultures.
The trap: The Comfort Zone feels like success because team morale is high and nobody is upset. The Learning Zone can feel harder because productive conflict is visible. Most leaders who think they are building psychological safety are actually building comfort. The difference shows up when something goes wrong.
Based on the four zones, where does your team sit right now? Name one specific behavior you observe regularly that places them there. Be precise. Vague diagnoses produce vague interventions.
One of the most consistent and costly dynamics in team culture: the moment where everyone in the room privately disagrees with a decision and nobody says so. This has a name. Understanding it is the first step to interrupting it.
The distinction: The Abilene Paradox is not disagreement that is suppressed. It is agreement that is assumed. The silence is not fear of conflict. It is misread context. Fixing it requires making actual alignment visible before decisions are finalized.
Most teams spend their planning time building confidence in their plan. The highest-performing teams also spend time systematically trying to destroy it before execution begins. That discipline has a name and a structure.
Using your Month Three charter, run the Pre-Mortem prompt on yourself right now. It is six months from now. The initiative came in late, over budget, or achieved the wrong outcome. What is the most likely reason? Name the risk you have been carrying privately that has not made it into the plan.
Most teams vote by silence. Someone makes a proposal, nobody objects, and the group assumes alignment. The Abilene Paradox is born in exactly that gap. Fist to Five is a structural tool that closes it.
Every person in the room simultaneously shows their level of support using their hand. Simultaneous display prevents anchoring, where one person's visible position pulls everyone else toward it. There is no single correct answer. The goal is to surface the real distribution of alignment before the group moves forward.
The protocol: Any fist or 1 must be heard before the decision moves forward. A room of 3s is a legitimate go. A room of 5s on a contentious issue is a signal to probe further. If everyone immediately shows 5, you may have created an environment where showing anything less feels unsafe.
| Decision Type | What It Means | What the Team Needs to Know |
|---|---|---|
| Consensus | The group decides together | Every voice has equal weight; the group must reach agreement |
| Consent | Move forward unless there is a blocking objection | Not everyone has to love it; fists and 1s must be heard |
| Consultative | Leader decides after gathering input | Input is genuine and will be considered; the leader chooses |
| Directive | Decision has already been made | The team's job is to execute well; input is not being solicited |
Most feedback fails not because it is too direct but because it is too vague, too personal, or not connected to a path forward. The COINS1 model gives feedback a structure that is specific enough to land, strong enough to matter, and forward-facing enough to be useful.
Every team accumulates experience. Not every team converts that experience into learning. The difference is structural. Without a deliberate practice for capturing and applying what the team knows, the same costly patterns repeat across projects, quarters, and people.
| Field | What Goes Here | Why It Matters |
|---|---|---|
| What We Did Well | Specific strength that contributed to a positive outcome | Codifies what to replicate and builds on existing capability |
| What We Would Strengthen | One process, habit, or approach that could improve | Keeps learning forward-facing rather than blame-oriented |
| Systemic Fix | The structural change that prevents recurrence | Moves from individual learning to organizational learning |
| Owner | One person accountable for implementing the fix | Prevents the insight from staying a conversation and never becoming a change |
| Timeline | When the fix will be tested or implemented | Creates accountability without a named due date, nothing changes |
Start your Lessons Learned Log with an entry from the last 30 days. Begin with something that went well. Then name what you would strengthen. Then name the systemic fix. This is yours. Write it honestly.
Most teams have norms. Few teams have working agreements. The difference is specificity and accountability. A norm is a general expectation. A working agreement is a behavioral commitment that the team can observe being kept or broken.
Lencioni's model is a hierarchy. Each dysfunction blocks the one above it. Working agreements address the base. Without the base, the rest will not hold.
| Dysfunction | What It Looks Like | Working Agreement Fix |
|---|---|---|
| Absence of Trust | People guard information and avoid vulnerability | "We share concerns before they become problems" |
| Fear of Conflict | Artificial harmony; issues resolved in side conversations | "We use Pre-Mortem before every major launch" |
| Lack of Commitment | Verbal agreement without follow-through | "We use Fist to Five on every significant decision" |
| Avoidance of Accountability | Low standards tolerated to preserve relationships | "We use COINS1 to address performance gaps directly" |
| Inattention to Results | Individual priorities override team goals | "We update the Lessons Learned Log after every milestone" |
Write three to five working agreements for your team. Each agreement must be behavioral: observable and measurable. If you cannot describe what keeping or breaking it looks like in practice, it is not specific enough.
The same diagnostic discipline that applies to organizational problems applies to culture problems. Knowing whether the root cause is structural or behavioral determines whether the right response is a tool or a conversation, a process change or a belief change.
| Problem | The Fix |
|---|---|
| Group decisions driven by the most senior voice | Fist to Five with simultaneous reveal before the leader speaks |
| Risks not surfaced until they become crises | Pre-Mortem embedded at the start of every project |
| Feedback that does not produce behavioral change | COINS1 structure with a named next step and support |
| Experience not converted into team intelligence | Lessons Learned Log with named owner and timeline |
| Unclear decision-making authority | Decision type named at the top of every relevant meeting |
The key principle: Structural tools lower the cost of candor. Adaptive work changes the belief that candor is costly in the first place. You need both. The tools are faster to deploy. The adaptive work is what makes them last.
This is the applied work for Month Five. You are building the cultural infrastructure that makes your Month Four delegation system sustainable. Work through each section using your actual team and real dynamics.
Using the Performance-Safety Square, place your team on the grid. Then name the specific evidence that places them there. Be precise.
Run a Pre-Mortem on your current or upcoming initiative. Document the top risks that surface. Then name what structural change would address each one.
Identify one person on your team who needs specific feedback right now. Draft the COINS1 script. You do not have to have delivered it yet. Write it so you could deliver it today.
Choose one recurring meeting. Name the current dynamic and then redesign it with at least two of the tools from this month: Fist to Five, Pre-Mortem, decision type transparency, or After-Action Review.
Create the first two entries in your team's Lessons Learned Log. Entry one is yours. Write it about something real from the last 90 days.
This month's capstone is group work. Your advisory team applies the frameworks from Month Five to what is happening inside Northstar. Work through each task using evidence from the case. Do not speculate beyond what the material supports.
Come prepared to share your dual-layer analysis and your re-entry conditions. The facilitator will name what the case is teaching about the difference between a leader who changed and a system that is still catching up. Bring that distinction clearly. The groups that get the most from this debrief are the ones who held the two layers separate rather than letting Alex's progress collapse the harder diagnosis about the team.
Month Five is where the system you built in Month Four gets its operating conditions. You have learned to create the cultural infrastructure that makes honest execution possible. That is not a soft skill. It is an organizational capability.
“What would my team say honestly about our culture if there were no professional consequence to saying it?”
“What is the single behavior I model that most powerfully shapes whether candor is safe on my team?”