March 26, 2026
Protection from You

The team had a phrase for it. When their director was in a good mood, they called it a “green light day.” Projects moved. People spoke freely in meetings. Ideas surfaced without fear. On green light days, the team looked like one of those high-performing units that gets profiled in leadership magazines. Then there were the other days. The director would walk in silent, jaw tight, responding to greetings with a nod that communicated nothing except “not now.” Within twenty minutes the entire floor recalibrated. Voices dropped. Emails replaced hallway conversations. The junior analyst who had been planning to pitch a new reporting approach quietly closed her laptop and decided to wait for a better day. Nobody told her to wait. Nobody had to. The team had learned to read the weather, and the weather was always determined by one person. That director believed he was protecting his team from external threats: unreasonable clients, shifting corporate priorities, budget cuts. He never considered the possibility that the most consistent threat to his team’s psychological safety walked into the building every morning wearing his badge.

Yesterday we examined the brutal mathematics of relational equity, the reality that deposits are small and slow while withdrawals are efficient and devastating. Today the lens turns inward, to a question most leaders instinctively resist: what if the threat your team needs protection from is not the difficult stakeholder, the unreasonable deadline, or the toxic culture three levels above you? What if the threat is you?

This is not a rhetorical provocation designed to produce guilt. It is a structural question with structural consequences. In the first book of this series, we established that one of a leader’s core duties is protection: shielding the team from forces that would consume their energy, erode their morale, or compromise their ability to do meaningful work. That framework assumed the threat was external. The client who changes scope every week. The executive who demands results without providing resources. The peer who takes credit for collaborative work. Those threats are real, and governing them remains essential. The harder truth, the one that Chapter 13 of The Decision Fortress forces into the open, is that a leader who lacks self-governance does not just fail to protect the team. That leader becomes the threat the team needs protection from.

The symptoms are specific and measurable. When a leader is moody, the team walks on eggshells. They spend cognitive energy that should go toward the work on monitoring the leader’s emotional state instead. They develop early warning systems: checking the leader’s email tone before approaching with a question, asking the executive assistant what kind of morning it has been, reading body language in the first five minutes of a meeting to determine how honest they can afford to be today. That surveillance is not loyalty. It is survival behavior, and it extracts a tax on every person who has to pay it. When a leader is reactive, the team hides bad news. They learn, through painful experience, that bringing a problem to the leader’s attention triggers a response that makes the problem worse rather than better. The leader shoots the messenger, escalates prematurely, assigns blame before gathering facts, or simply makes the bearer of bad news regret the decision to be transparent. The team adapts. They delay reporting issues. They minimize the severity of problems. They solve things in the shadows where the leader’s volatility cannot reach. The leader, now operating on sanitized information, makes increasingly disconnected decisions and wonders why execution keeps breaking down. The information was not the failure. The leader’s ungoverned response to information trained the team to stop providing it.

Proverbs 25:28 (NLT) describes it with architectural precision: “A person without self-control is like a city with broken-down walls.” The image is not accidental. Throughout this month we have been building the Decision Fortress: integrity as the foundation, emotional governance as the walls, relational discipline as the gates. A city with broken-down walls is not just vulnerable to external attack. It is incapable of providing shelter to anyone inside it. The residents of that city are exposed. They are unprotected. They live with the constant awareness that danger can arrive from any direction at any time, and no one is governing the perimeter. That is what it feels like to work for an ungoverned leader. The team is inside the walls, looking to the leader for structure and safety, and the walls are rubble. The leader’s lack of self-control is not a private struggle. It is a public failure that renders the entire structure uninhabitable.

The most insidious version of this is the leader who believes they are self-aware. They have read the books. They know the vocabulary. They can describe emotional intelligence in a performance review, coach a direct report on managing reactions, and deliver a compelling talk on psychological safety at a leadership offsite. Then they return to the office and snap at an intern for asking a clarifying question during a stressful week. The knowledge is real. The governance is not. Knowing that self-control matters and practicing self-control are separated by the same gap that separates owning a gym membership and being physically fit. The membership is not the fitness. The vocabulary is not the governance. The team does not experience your awareness of the problem. They experience the problem.

Ephesians 4:29 (NLT) sets the standard plainly: “Don’t use foul or abusive language. Let everything you say be good and helpful, so that your words will be an encouragement to those who hear them.” Paul is not asking leaders to be artificially positive or to suppress honest assessment. The standard is not “say only nice things.” The standard is that everything you say should be good and helpful. Correction can be good and helpful. Direct feedback can be good and helpful. A hard conversation about underperformance can be good and helpful. The test is not whether the words feel pleasant to receive. The test is whether they build up or tear down. The leader who humiliates a team member in a meeting has failed the test regardless of whether the underlying feedback was accurate. The leader who delivers the same feedback privately, with specificity, with a clear path forward, and with the dignity of the person intact, has passed it. The content might be identical. The governance determines whether it constructs or demolishes.

The AUDIT question for today is direct. Do your people flinch? Not visibly, necessarily. Flinching in a professional environment is subtle. It is the half-second pause before someone responds to your question, calculating whether honesty is safe. It is the junior team member who used to volunteer ideas in brainstorms and quietly stopped three months ago. It is the direct report who schedules difficult conversations for Friday afternoons, hoping your energy will be too low to react badly. It is the resignation letter that cites “pursuing other opportunities” when the real reason, the one they will tell their spouse that night, is “I could not take the unpredictability anymore.” If your team flinches, the cause is not their weakness. The cause is your pattern. They are not fragile. They are responding rationally to an environment you created with your ungoverned moments.

The repair path is not a personality transplant. It is structural. It begins with an honest accounting, the kind of audit we described on March 25, except the ledger you are examining is not just the balance of deposits and withdrawals. It is the pattern of your behavior under stress. When are you most dangerous? Most leaders know the answer if they are willing to be honest. It is Monday mornings before coffee. It is the hour after a difficult call with a board member. It is the last meeting of the day when energy is depleted and patience is a memory. Identifying the pattern is the first brick. The second is establishing pre-decisions, standing orders that govern your behavior in those predictable danger zones. “I will not respond to Slack messages in the first thirty minutes of my day.” “I will not give feedback within one hour of receiving bad news.” “I will take a walk before the 4 PM meeting.” These are not wellness tips. They are structural reinforcements for a wall that has proven it cracks under specific, predictable loads.

The aspiration is not perfection. It is governance. The governed leader still feels frustration, still disagrees, still carries the weight of decisions that affect people’s livelihoods. The difference is that the governed leader processes the frustration before it reaches the team. They bring the anger upward, as we discussed on March 18, through lament and honest prayer, before they bring it outward through words that cannot be retracted. They become what Chapter 13 calls a “Safe Place,” not because they are soft, but because they are disciplined. People bring their best work and their hardest problems to a governed leader because they know they will not get burned by the leader’s lack of discipline. That safety is not a perk. It is the structural condition under which teams produce their highest quality work and their most honest communication.

Tomorrow we will examine the practical discipline of governing your written communication, the moment between composing the message and pressing send. The draft you should have deleted. The cc you should not have added. The email that felt righteous at 9 PM and looked reckless at 7 AM. If the relational gate governs what comes out of your mouth, the draft folder is where that governance gets its hardest test.

I write about leadership at the intersection of timeless principles and modern workplaces. Follow for weekly insights on building teams that actually work. For more articles like this consider subscribing to my Substack at: https://christianleadership.now