You already know the moment. A staff member has been falling behind on something they were supposed to have completed months ago. You sit down, name the problem clearly, write out what needs to change, and both of you sign it. The document goes in a file somewhere. For a while, it feels finished, because the hard part, the honest conversation, the naming of the problem, is genuinely behind you.

Then months pass, and the same gap shows up again. Nobody did anything wrong the second time either. The form was accurate. The plan was reasonable. The signatures were real. What’s missing isn’t a better conversation or a stronger form. It’s whatever was supposed to happen after the ink dried.

It’s whatever was supposed to happen after the ink dried.

This shows up outside of school buildings too. In the Navy, a sailor falling behind on a required qualification would get a formal, documented counseling session, a note that named the deficiency and laid out a plan to fix it. That process was done correctly every time. But there was a second kind of documented note used elsewhere in the same organization, tied to something that happened every single week regardless of who remembered. That one got revisited automatically. The first one only got revisited if someone thought to go back and look. That was the whole difference between the two. Not the paperwork, but the circumstances that already existed around the correction.

That was the whole difference between the two.

Here’s the part worth sitting with. A signed plan tells you that a problem was seen clearly enough to put into words. It does not tell you that anyone will ever look at it again. Those are two separate jobs, and only one of them comes with a form. The second job, making sure the plan gets revisited, has no built-in reminder. It has to be attached to something that already happens on its own, or it quietly depends on someone’s memory, and memory is a poor place to store a correction.

So the next time you sign off on a plan for a staff member, a student, or yourself, it’s worth asking one question before you file it away. What already happens on a regular basis that would naturally bring the correction back into view. A standing meeting. A weekly walkthrough. A check-in that was going to happen anyway. If nothing comes to mind, that’s not a small gap. It’s the reason plans like this tend to quietly disappear, not because anyone stopped caring, but because nothing was built to make anyone look again.

There’s a fuller version of this, including the specific move that turns a signed plan into something that actually holds, in this week’s paid piece.

The signature proves you saw the problem. It was never proof that you, or anyone else, would revisit the correction again.

- Unbroken Growth

Subscribe now

New maintenance sailors who check into a helicopter squadron get sent to the line shack on a TAD assignment, temporary duty away from their parent shop, for about a year, to earn a qualification called plane captain: the sailor responsible for the aircraft itself and for staying safe working around a running engine and a turning rotor. The command runni…

Read more

A sailor sat in the open discussion at the end of passdown, back from a year on temporary assignment to the line shack, the entry-level rotation where a new maintenance sailor learns to work safely around a running aircraft. I asked how the year went. The sailor did not walk me through a skills checklist. The sailor told me about a Chief, a senior enlisted leader, who died years earlier walking into a still-turning rotor blade, a story nobody had put on that morning’s agenda. Before the sailor finished, two other sailors in the room were already nodding, adding details of their own.

Bridge leaders sign off on training constantly: a certification renewed, an onboarding checklist completed, a required module finished. None of that paperwork asks whether the person who completed it understands why the rule exists, only whether the person can perform the rule. The gap between the two rarely shows up until the rule becomes inconvenient, and by then the paperwork already says everything is fine.

None of that paperwork asks whether the person who completed it understands why the rule exists, only whether the person can perform the rule.

The squadron I served with did not leave that gap to chance. Alongside the technical steps every line shack sailor had to learn, working safely around a running aircraft, moving people and equipment near a turning rotor, command made sure every sailor also heard about the Chief. The story got taught the same way the steps got taught, deliberately, every time, not something tacked on once the real training ended.

Attaching a reason to a rule on purpose is the first move, and the first move is rarer than it should be. The second move gets skipped even more often: building a way to find out, later, whether the reason actually survived. A sailor’s return from a year away was never treated as a formality at my old command. The return came with real questions, what got learned, where gaps still needed filling, how the year actually went. That broader question is what gave the Chief’s story room to come back out, confirmed on the spot by sailors who had carried the same story since their own time in the line shack. The full version of how a leader builds that kind of check into a schedule already sitting on the calendar is worth its own conversation. The two moves above are enough to start with this week.

Picture a new hire’s first week at your school. Somewhere in that week, a specific expectation gets explained, maybe why no student waits alone outside after dismissal, tied to something that actually happened once, with a real cost attached, not just a line in a handbook. Attaching a reason to a rule on purpose, the same way a squadron attaches a story to a qualification, gives the reason a chance to survive past the day it got explained.

The second move happens later, easy to skip because nothing forces it. A one-on-one already exists somewhere on the calendar, a thirty-day check-in, an end-of-semester conversation, a debrief after a rough week. Ask one broad question inside that conversation, something like what stood out this month, instead of only the specific ones already planned. If the reasoning actually attached, the reasoning comes back on its own, sometimes with more conviction than the day it got explained the first time.

A completed onboarding checklist only proves the rule got explained once.

Whether the reason behind the rule survived the first inconvenient moment depends on a question nobody is required to ask, and a leader who never asks that question may not find out until the day the answer would have mattered.

- Unbroken Growth

Subscribe now

The all clear had already gone out over the intercom. Teachers let their classes back into the hallway, the cafeteria line started moving again, and by the time the assistant principal finished walking the last corridor, the building had mostly moved past it. A report had come in that morning of someone unfamiliar near the fence line by the gym, and for…

Read more

One night, the call came over the ship’s intercom for real, not a drill. General quarters is the posture that sends every sailor to a designated station the moment something happens that needs the whole crew to respond at once, the shipboard version of an emergency response that pulls in every hand at the same time. My team moved to our post, gear already staged from months of practice, and we were briefed that there was a possible gas leak somewhere on the ship. My job was to check the berthing, the sleeping quarters, in a full breathing rig built for air that might not be safe to breathe on its own. Sailors were still asleep in their racks when we got there. We woke the sailors, got them clear of the berthing, and reported back to our team lead.

Nobody on the Investigator team made a mistake. The response ran exactly the way we practiced it. Once the response was over, the team lead still gathered the whole team. The team lead walked us through what we had reported and what that report set in motion above us. None of us would have otherwise seen where the report went next.

The Navy built a system that requires that follow-up conversation. Without a system like that, the debrief doesn’t happen on its own. You already know what happens instead in your own building. When a hold or a lockdown resolves without incident, the building exhales. Everyone moves on. Nobody is wrong for skipping the conversation. The conversation genuinely doesn’t feel necessary in the moment. But a clean outcome is not the same as an understood one. Understanding takes someone sitting down and asking how the event happened. Clean outcomes rarely get asked that question, because they already feel finished.

The piece that gets left behind, is the unexamined outcome. Organizations can sometimes examine what breaks and skip what works, and the outcomes that go right carry real information about how the pieces fit together, information that stays invisible to the people who created the outcome. A teacher who locked a door and a front office employee who answered a call each know their own piece. Neither one usually sees how those pieces added up to the decision made above them. Debriefing a clean event is not correction. The debrief is the only way that connection ever becomes visible to the people who created the outcome.

Back on the ship, our team lead made that exact connection visible to us. Our team’s report had gone up a direct line to the officers coordinating the response, at the same time every other team on the ship was reporting in the same way. Leadership was not deciding off one report. Leadership was piecing together several reports at once to figure out how the ship needed to respond. None of us saw that part until someone in the room named it out loud.

A school version of that moment looks smaller but works the same way. A hold resolves and the front office made a call before they knew the full picture. A teacher kept her class steady in a way nobody upstairs ever heard about. Someone was in contact with a partner outside the building the whole time, doing work the classroom never saw. None of that becomes visible unless a leader decides the conversation is worth having anyway, on a day when, by every visible measure, nothing happened.

The next time something in your building goes exactly right, notice the instinct to let it pass without a word. Then ask yourself, what you still don’t actually know, about why the outcome worked.

- Unbroken Growth

Subscribe now

The status board in our shop aboard the Nimitz said the bench was up. That was true. It was also the least useful true thing anyone could have told you about that bench.

We repaired aircraft electronics at sea, and the machines we used to find the faults were called CASS benches. When money tightened somewhere far above us, the effect reached us in a specific and unglamorous form. Parts stopped moving. A part inside a bench would fail, the replacement would go on order, and the order would sit. Meanwhile the units kept coming in, the aircraft kept needing to fly, and the flight schedule did not adjust itself to accommodate our supply problem.

So we moved things. A component could come out of one bench and go into another, and the second bench could then carry the high priority work sitting in the backlog. The first bench was not dead. It was down for one capability and still good for anything that did not require it. We put a part on order against it and kept going. On the board that read as one bench up and one bench partially degraded, with a part number and a status attached. Every word of it accurate.

Our reporting was honest. When a bench was down, the shop that fixed the benches said so, and it reported that up, and Production Control knew what was wrong, which units were affected, what part was on order, and where that part stood. The squadrons knew, because those statuses were discussed in meetings. Nothing was hidden and nobody was covering. The organization tracked the shortfall carefully and told the truth about it at every level, and the thing that actually kept us running still did not appear anywhere in it.

That is not the story where the organization is blind, the paperwork is theater, and one person is secretly holding everything together. Pretending it was that story would waste the actual lesson.

The gap was not between what was true and what was reported. The gap was between what was reported and what kept the work moving.

Two kinds of memory

There were two kinds of memory operating in that space at the same time.

The first was formal. Status, part numbers, units affected, priorities set from trend data about what deploys with which squadrons and what breaks in what season. That system was built deliberately, it was maintained, and it did its job well.

The second was not written anywhere. It was knowing that a particular component would work in a different block of bench. It was knowing which configuration could take on which unit once you moved it. None of that had a field on any form, and the second kind was what turned a shortfall into a workday.

Nothing in the formal system would have caught it if that second kind had stopped moving from one person to the next. There was no field for it, no report that would have gone red, no meeting where its absence would have surfaced. The board would have looked exactly the same the next morning.

What this looks like in your building

Your organization builds careful memory for the things that have a form attached. Master schedules, staffing rosters, intervention rosters, compliance logs, budget codes, coverage plans. Maintained, reported, largely accurate. And in a tight year the reporting stays accurate. The intervention block is still on the schedule. The duty is still covered. The program still appears in the plan under the same name it had last year.

What the schedule does not record is that the block works because one teacher knows how to run it with fewer adults in the room than it was designed for. What the coverage plan does not record is that coverage holds because a veteran teacher knows which three students to seat where before the substitute arrives. What the compliance log does not record is that the paperwork lands on time because one person knows the sequence, knows who to call at the district, and knows which step people skip.

Those are capabilities. Your systems track status.

Your building has practices like that right now. Some of them have no owner. Nobody currently in the school decided them. They arrived from the person who did the job before, and they will leave with the person doing it now unless someone intervenes.

And that is the part the reporting will not warn you about. If one of those practices leaves in March, nobody sees a practice stop. They see a limit that seems to have always been there, and they work around it, at cost, for as long as it takes.

Status survives a departure. Capability does not, unless somebody moves it on purpose.

The question

I am not going to hand you a system for this, because the useful version of it does not start with a system. It starts with knowing which thing in your building you would actually be looking at.

So ask one question, about your own building rather than about leadership in general.

Which of the things that hold here would still hold if the person carrying it left in March.

Write down whatever comes to mind in the next two minutes. Three or four things is enough. You will notice that almost none of them are the things your systems are tracking, and that the ones which worry you most are the ones you have never had a reason to write down.

That list is worth more than it looks. It is the first record anyone in your building has made of what is actually holding, as opposed to what is on file.

Your systems will keep telling you the truth about your status. They were built for that and they do it well. They were never built to tell you that the thing holding a program together is walking out the door in March, and they will not start telling you now.

Ask the question yourself, or inherit the answer by accident.

- Unbroken Growth

Subscribe now

The status board in our shop aboard the Nimitz said the bench was up. That was true. It was also the least useful true thing anyone could have told you about that bench.

We repaired aircraft electronics at sea. The units came off the aircraft and came to us, and the machines we used to find the faults in them were called CASS benches. No bench could test…

Read more

Five issues in, the pattern has probably become familiar. A meeting that looked resolved. A roster that said two. Four capable adults who walked out of one hallway with four different conclusions. Each of those asked the same question, and by now you can answer it before I finish asking. Something was already there. The event only made it visible.

That question has done its work. Recognition is where this series started but not where it will end, because seeing clearly and preserving nothing means running the same discovery over and over, one difficult day at a time.

The rest of this series is about what happens after you see it. How a lesson gets named, written in a form somebody else can use, carried into next year, and eventually retired when it stops being true. That work has a name here. Stewardship.

It starts with the smallest step. Not whether the thing gets written down, but what gets written.

The first thing anyone handed me as a junior technician in the Navy was a small green logbook. The name of the avionics gear was on the cover and on the spine, along with the date the book was opened, meaning the date the first entry was made. Inside was entry after entry, each one carrying the technician’s name, the date, the nomenclature of the piece of avionics equipment, and the serial number of the specific unit.

Then came the part that mattered. The gripe. What was actually wrong with this piece of gear, in a form a stranger could read. Which components were troubleshot by what technician. What was found. What the solution was. Every troubleshooting step taken to get there.

Including the steps that went nowhere.

That is the entry I still think about. A technician finds a fault, orders the part, waits days for it to arrive, installs it, and the gear tells them that should have resolved it. It hasn’t. So they pull the schematics and start tracing current through the circuit, and eventually they find the real fault somewhere else entirely. And then they write all of it down. The wrong diagnosis and the ordered part that was not the problem.

Nobody enjoys writing that entry. It is a record of being wrong, in your handwriting, with your name on it, in a book other people will read for years. We wrote them anyway, because the next technician standing in front of that same serial number with the same symptom needed to know which door had already been opened and found empty.

Here is what took me years to understand about that little green book. It was not valuable because it stored information. It was valuable because filling it in forced us to say things we would otherwise have only felt.

You could not write that the gear was acting weird. That is a feeling, and a feeling does not survive the trip to another person. You had to convert it into something specific enough that a technician who was not standing there could act on it. The book would not accept anything less, and so the conversion happened every single time, on every shift, whether the technician felt reflective that day or not.

The logbook was not a storage device. It was a naming instrument.

Schools already keep passdown logs. They keep them out loud.

Consider a student whose behavior has been disruptive for most of a year. A teacher calls home. Then another teacher. Then the counselor. Then the assistant principal. Then the principal. Different people, different approaches, months of effort, and nothing changes. In June the principal takes a job at another school.

The new principal will hear about that family in the first week. Somebody will say, in a hallway or in a transition meeting, that those parents are unsupportive.

That is how a passdown works when nothing gets written down. It moves easily, it survives a leadership change, and it costs nobody any effort. It also has no author, no date, and nothing attached to it that anyone could check.

Look at what it carries. Eleven months of attempted contact, compressed into a judgment about two people. What transfers is a conclusion about a family instead of a description of a problem. The next leader arrives already knowing how the story ends, and that is difficult to un-know. And the child, who did not write that entry, carries it.

This is where a school building differs from a hangar. The logbook’s subject was a machine. A serial number cannot be characterized unfairly, and nobody’s reputation was riding on entry fourteen. When the subject of a record is a person, the same format that made us better technicians will quietly build a case file instead.

Sometimes the fault really is the component. A recurring power supply failure, replaced twice, still presenting. That entry names the unit as the problem and it is a good entry, because it says what was seen. What nobody could write was that the unit was junk.

The difference was never about who the entry named. It was about what the entry claimed. Some families have disengaged. Some homes are teaching a child something the building works against all day. Softening that in the record is not caution. It hands the next person something that reads well and tells them nothing.

The entry can be about the family. It has to carry what was observed rather than what was concluded.

Go back to that year. The verdict says the parents are unsupportive. The entry says every contact this family received was initiated after an incident, by five different adults, in writing, with no single point of contact and no conversation that began anywhere other than a problem. Or it says the family declined four offered meetings, asked for written communication only, and did not respond to two counselor referrals.

Same eleven months. The first sentence tells the next leader how to feel walking in. The other two show what has already been tried and where the ground has been worked.

The first attempt will be too vague and that is normal. It was a hard year is not an entry. Communication broke down is not an entry either, because it names a category instead of a fault. Keep going until the sentence is specific enough that a colleague from another building could read it and know what to look at. That struggle is not a sign of poor writing. It is the conversion happening, and it is the whole reason the logbook worked.

One thing about the notebook itself. Under federal law, private notes belong to the person who made them until they are shared. The moment they pass to somebody else, they become part of that student’s education record, which the family has the right to read. That is not an argument against writing them. It is an argument for writing them the way you would write anything a parent may eventually read, which happens to be the same discipline that keeps an entry an observation instead of a verdict.

One last thing about those logbooks. When a book was closed, we were required to keep it on hand for two years, and then it was done. Even the preservation had an expiration built into it. Somebody had decided how long a lesson stayed useful, which kept the shelf a working tool instead of a graveyard.

“Those parents are unsupportive”, is a verdict with no expiration on it. It will outlast the principal who first said it, the assistant principal who repeated it, and quite possibly the student it was about.

How long a lesson should stay in circulation is a question for later in this series. For now there is only the smaller one, the one that has to happen before anything can be preserved at all.

What would you write on the gripe line?

- Unbroken Growth

Subscribe now

The free article ended on a question about what you would write. This one is about the thing that has to exist before the writing matters, and about a decision some leaders make by accident.

There are two entirely different things a leader can build here, and they are not versions of each other.

The first is a private notebook. It belongs to you, it never leaves your hands, and it exists so that you remember in April what you concluded in October. Under federal law, notes kept in the sole possession of the person who made them, used only as a personal memory aid, and not shown to anyone else, sit outside the definition of an education record. That is a real and legitimate design. It also has one property worth being honest about. It dies when you leave.

Read more

While I was in the Navy, my team and I were put through a timed training exercise. The coordinators handed each team a map. The map was not precise. It had a legend, a few markers, and just enough information to get us moving. The instructions were short. Find all of the parts hidden across the course. Once you have every part, assemble them. The clock …

Read more

A student leaves a classroom after a tense exchange and grows more agitated in the hallway. Four adults respond. The teacher who saw it start follows the student out. A counselor arrives. An assistant principal arrives. A member of the school safety staff arrives. Every one of them is competent. Every one of them is trying to help.

Then the directions start to overlap. The counselor asks the student to walk with her. The safety staff member tells the student to stay where he is. The assistant principal sends the teacher back to class, while the teacher believes she should stay. Someone calls the family. Later that day, someone else gives the family a second account that does not match the first.

The event ends. The student is safe. The hallway clears. Classes resume. By every visible measure, the school handled it.

The next morning tells a different story. The adults who responded cannot agree on what happened. They cannot agree on who made the final decision, what was communicated to the family, whether the teacher was supported, or who is handling the student’s return. Four capable professionals stood in one hallway and walked away with four different conclusions.

The scene is a composite, drawn from situations bridge leaders describe again and again. The pattern inside it is real, and the pattern is the point.

The Easy Reading and the Useful One

The easy reading of that morning is that somebody mishandled the incident. Somebody overstepped. Somebody failed to communicate. The easy reading turns the debrief into a search for the adult who got it wrong.

The useful reading starts from a harder observation. Nobody in that hallway performed badly. Each adult did their job as they understood it, and each one can defend every decision they made. When capable people respond to the same event and reach different conclusions, the explanation is rarely found in the people.

The disagreement the next morning was not about what happened. It was proof that no one had agreed on what was supposed to happen.

Each adult resolved the event against their own private standard, because a shared one was never established. The conflicting directions in the hallway were not a clash of egos. They were four professionals discovering, in real time, that they were not working from the same understanding, and having no choice but to keep moving anyway.

I first learned to see this pattern in uniform. During one timed training exercise, several capable teams received identical instructions, identical materials, and an identical deadline, and still produced results that looked nothing alike. What that exercise revealed stayed with me longer than the exercise itself, and the short version fits in one sentence. The difference between the teams was never capability.

What a Bridge Leader Can Watch For

Here is a practice that requires no meeting, no framework, and no permission.

The next time a tense event ends, replay it before the day is over, and look for the seam. In every team response there is a visible line where following something ends and guessing begins. Up to a certain moment, people are acting on what they know. Past that moment, they are filling gaps with their best judgment, and each person fills those gaps differently. The seam is where the guessing started.

Finding the seam changes what you examine. You stop asking who performed well and who performed poorly, which is a question that puts your team on trial. You start asking where the guessing began, which is a question that puts the event on the table. The seam shows you the exact point where your team ran out of shared understanding, and that point is the same place the next difficult event will find them.

You are not looking for the mistake. You are looking for the moment people started guessing.

That observation alone will change how you read your team’s next difficult day. It costs nothing, it blames no one, and it produces something a bridge leader can actually use.

Where This Connects

For readers following the Five Pillar Framework, this pattern sits at the intersection of Pillar IV, Accountability and Trust Formation, and Pillar V, Behavioral Reinforcement. People cannot be accountable to an understanding they were never given, and teams repeat whatever their difficult days keep rehearsing.

The seam tells you where shared understanding ran out. This issue’s paid debrief goes deeper into what a leader can build there.

Four capable adults reached four different conclusions, and every one of them was being reasonable. That sentence should not be able to be true. In organizations that have never established shared understanding, it is true after every difficult day.

- Unbroken Growth

Subscribe now

I was the leading chief petty officer of the avionics division at Fleet Readiness Center West in Lemoore, California. Every Sailor in my division was required to hold a current CPR qualification. That requirement is not paperwork. Sailors whose qualifications lapse cannot work around energized equipment, which means a lapsed card does not just sideline …

Read more

I was the leading chief petty officer of an avionics division at Fleet Readiness Center West in Lemoore, California, and we were weeks out from an inspection. Part of preparing meant reviewing every program we owned, and one review stopped us cold. Every Sailor in my division needed a current CPR qualification to work around energized equipment, and a large number of those qualifications were set to expire before the audit date. The fix looked simple. Find an instructor, run the class, update the records.

The command document that tracked collateral duties showed two qualified CPR instructors in the entire organization. Neither was in my division. One was on deployment. The other was on maternity leave. On paper, we had the capability. In the building, we had no one. Nothing about the moment felt like an emergency. It felt stranger than that. It felt like standing in a fully staffed command and discovering that something we had counted on did not exist where we were standing.

Here is what made that gap dangerous. No one had done anything wrong. The instructors had been certified. The program had passed every previous review. Each individual decision that produced the situation was reasonable, which is exactly why no one was looking. Continuity is invisible while it is working. A capability that lives in two people looks identical on a roster to one that lives in ten, right up until the day you need it and both people are gone. Leaders are trained to answer the coverage question with names. Do we have instructors? Yes, two. The name becomes the answer, and the answer ends the inquiry.

The principle I carried out of Lemoore is this:

A roster is not a capability.

The real measure of any function your team depends on is not how many names are attached to it. It is how many people could actually do the work tomorrow, under the conditions your organization actually experiences. People deploy. People take leave. People resign in October. If your count assumes everyone is always present, it is not a count. It is a hope with a number attached.

Schools run on this kind of hope as well. The master schedule lives in one registrar who has built it for nine years. The state reporting process lives in one data clerk. The testing platform lives in one counselor. The relationship with the district facilities office lives in one assistant principal who happens to answer the phone well. None of this was designed. It accumulated, the way it does everywhere, and it works every day until the day it doesn’t. In the Navy, qualification systems and turnover requirements forced us to move knowledge between people whether we felt like it or not. Schools have no such machinery. Which means the work of continuity falls entirely on the leader, and most leaders inherit the gaps without ever being told they own them.

Owning them starts with one question, asked about one function at a time.

If the person who owns this stayed home tomorrow, does the work continue by noon?

Picture a department chair sitting in a Tuesday team meeting during testing season. The testing coordinator is walking through the schedule, and the chair asks the question out loud, not as an accusation but as a genuine operational check. What happens if you are out Thursday? The room goes quiet for a moment, because everyone realizes at once that the honest answer is that testing stops. That moment costs the chair something. It admits fragility in front of the team, and it adds a task to a calendar that has no room. What it produces is worth more. Within a week, a second person has sat beside the coordinator through one testing session, and the answer to the question has changed from no to almost.

That is the whole move at its smallest scale. Not a committee, not a continuity plan with a binder and a title page. One function, one honest question, one act of moving knowledge from a single head into a second one. In Lemoore we closed our gap by borrowing instructors from other squadrons and coordinating with the hospital to update the records, and it worked only because we found the problem weeks before the audit instead of the morning it mattered.

The staff absence that eventually comes for your building will not create a weakness. It will reveal one that was already there, one that someone decided to accept without ever noticing they were deciding. The only real choice you get is whether you find it first.

Subscribe now

The meeting ended without anyone raising their voice.

Two department chairs nodded, gathered their notebooks, and left within seconds of each other. The principal watched the exchange and felt relieved. No shouting, no accusations, no dramatic exit. By every visible measure, the conflict had been handled.

Three weeks later, the two departments had stopped…

Read more

The meeting ended without anyone raising their voice.

Two department chairs nodded, gathered their notebooks, and left within seconds of each other. The principal watched the exchange and felt relieved. No shouting, no accusations, no dramatic exit. By every visible measure, the conflict had been handled, and the principal moved on to the next item on a very full day.

Three weeks later, the two departments had stopped collaborating almost entirely. Information moved through email instead of conversation. Small misunderstandings multiplied into larger ones because neither side trusted the other enough to ask what was actually meant before assuming the worst. The scheduling dispute that started it had long since been forgotten. What replaced it was harder to name and harder to fix.

The meeting looked resolved because the disagreement stopped. It was not resolved, because whatever produced the disagreement never got addressed. Those are two different outcomes, and school leaders are rarely given the tools to measure the second one. The first outcome shows up immediately, in the room, where a principal can see it and feel good about it. The second outcome shows up weeks later, in an inbox full of emails that used to be hallway conversations, and by then it rarely gets traced back to the meeting that supposedly went well.

What actually happened between those two department chairs was not really a disagreement about scheduling. It was evidence. Trust is not a feeling people carry into a room. It is an operating condition: what someone believes will happen to them if they raise a concern, question a decision, or admit they are behind. When that condition is healthy, disagreement stays small and resolves quickly, because both people trust that saying the honest thing out loud will not cost them anything later. When the condition is damaged, even a minor scheduling conflict can freeze a working relationship for months, because neither person is willing to risk finding out what happens if they push back again.

An operating condition exists whether anyone names it or not. It shapes how quickly people raise concerns, how honestly they admit mistakes, and whether disagreement turns into collaboration or into distance. Like the foundation beneath a building, it goes unnoticed until the structure starts to shift.

In a healthy trust condition, a department chair walks down the hall to clarify an email before assuming the worst. In a damaged one, the same email turns into three forwarded messages, two private conversations, and a meeting nobody wanted.

The first step in separating the event from the condition is asking what the event was actually made of. The event is what happened in that meeting. The condition is whatever made the event land the way it did. Two people can have the identical disagreement in two different buildings and get two completely different outcomes, not because one building has better communicators, but because one building has a healthier trust condition underneath the disagreement. The scheduling dispute was never really about the schedule. It was the surface a much older pattern happened to break through.

Had the principal asked what the meeting revealed instead of whether the meeting ended peacefully, the question would have been about the condition instead of the event.

A leader who sees this stops asking only how to resolve the disagreement in front of them and starts asking a second question: what does this disagreement reveal about what people already expect from leadership here. That second question changes what gets addressed. Instead of refereeing who was right about the schedule, the conversation shifts toward whatever pattern taught two experienced professionals that raising a concern directly was riskier than staying quiet. That is a different repair, and it is usually the one that actually holds, because it targets the condition instead of managing the event.

The next time a disagreement on your staff resolves quickly and quietly, resist filing it as handled.

Ask instead what the disagreement revealed about the trust condition already sitting underneath it, and how long that condition has been building toward this exact moment.

That question tends to matter more than whichever version of the disagreement everyone just agreed to stop discussing.

Subscribe now

By the time the assistant principal reached her office, three emails were already waiting.

One came from the principal asking if she had seen the Facebook post. Another came from the district communications office requesting background before responding to questions from the superintendent. The third came from the teacher at the center of the complaint.

“…

Read more

Most school leaders can recall the exact moment a complaint became public. The phone call from the district office. The screenshot a colleague forwarded. The faculty meeting where everyone already knew before the agenda reached that item.

Far fewer can recall the moment that complaint actually began.

A complaint feels sudden because the public version of it is sudden. One day the situation seems fine. The next day there is a social media post, an angry email thread, or a parent standing in the front office asking to speak with someone in charge. The timeline appears to start there.

The true origin sits further back.

Public complaints arrive after private frustration has run its course. By the time something becomes loud enough for an organization to notice, it has usually been building for a while.

That seemingly innocuous period is where the real story lives.

Somewhere before the public moment, a conversation went differently than someone expected. A phone call got delayed. An email sat in an inbox longer than felt reasonable. A decision was made and the person affected by it learned about it secondhand. Each of these moments felt manageable at the time, the kind of thing that could wait, or that someone else would surely handle.

The waiting stretches on. The assumption holds until it doesn’t.

Most of the people involved in these situations are trying to do their jobs well. Teachers are managing more students than they have time to individually follow up with. Administrators are juggling priorities that compete for the same hour. Everyone involved genuinely intends for families to stay informed.

Intentions are real, and so are outcomes. Somewhere, a conversation that needed to happen kept slipping. The person waiting on that conversation eventually stopped waiting.

That is the actual sequence behind most public complaints. People doing reasonably well at hard jobs, with one conversation arriving too late too often, until the lateness itself became the message.

This reframes what a complaint really is.

The instinct, when a complaint becomes visible, is to treat it as the problem that needs solving. Respond to the post. Correct the misinformation. Smooth things over with the family. Move on.

Those steps matter. They also address only part of the picture.

A complaint functions as evidence. It surfaces once a communication gap has existed long enough to become visible to people who were never part of the original situation.

Resolving the complaint addresses what is visible. The conditions that produced the complaint, stay exactly where they were. Which means, eventually, a different family experiences a similar gap, and a different complaint follows a similar path into public view.

Leaders who only respond to what is loud will keep responding to what is loud. Breaking that cycle starts with a different question than the one most leaders instinctively ask.

The instinctive question is, “How do we resolve this?”

The more useful question is, “What happened before this became visible?”

That second question takes more effort to ask. It requires looking past the immediate fire and into the conditions that allowed it to start. It also requires resisting the pull toward finding one person to hold responsible, since these gaps usually trace back to a system that missed the moment to catch them, more than to any single failure.

Bridge leaders are uniquely positioned to ask that second question. They sit close enough to daily operations to notice where conversations stall before anyone above them does. A teacher mentions, in passing, that a parent has been hard to reach. A coordinator notes that a particular type of update always seems to lag. These observations feel minor in the moment. Each one is a small signal of the same gap that, left alone, eventually becomes someone’s public complaint.

The leaders who catch those signals early are paying close attention to what is quiet, ahead of what eventually becomes loud.

That habit will not erase every complaint. People carry different expectations, different communication styles, and different thresholds for frustration. Complaints will always be part of leading an organization full of people.

What changes is the organization’s relationship to surprise. Some organizations are caught off guard by what becomes public. Others have already noticed the pattern forming before anyone outside the building does.

The complaint that reaches social media, the superintendent’s office, or a parent’s attorney usually arrives late in a longer story. Everything before that point was quieter, smaller, and easier to address than the version everyone eventually sees.

The leaders who learn to notice the quiet version spend less time managing crises and more time leading organizations that rarely produce them.

- Unbroken Growth

Subscribe now

Every August, something happens in schools across the country. New teachers arrive. Returning staff settle back in. Leadership teams set goals. Calendars fill with meetings and professional development days and first-week logistics. The year begins with energy and intention.

And somewhere in that first month, a problem appears that someone on the team quietly recognizes. They have seen this before. Not this exact situation, but something close enough that the memory surfaces. They know how it ended last time. They know what made it harder than it needed to be.

But the documentation from that previous experience does not exist. The people who navigated it have moved on, or moved up, or simply moved their knowledge somewhere inaccessible. The organization is about to pay tuition on a lesson it has already learned.

This happens in nearly every school, every year. Not because the people are careless. Not because leadership is indifferent. It happens because most organizations have never separated two things that feel identical but produce very different outcomes.

Remembering is personal. Preserving is organizational. And only one of them survives when people leave.

What the Debrief Revealed

There is a story I return to often when thinking about this distinction. It comes from my first year as a Chief in the United States Navy, during what is known as Chief Season. This is the annual period when newly selected Chiefs are initiated into the Chiefs Mess, the senior enlisted leadership community that forms the backbone of every Navy command.

I was on the planning committee that year. First-year Chiefs rarely serve in that role, but participation was needed and I was given the opportunity. Our committee ran the fundraising effort for the season, and we did well. When it was over, the planning team gathered for a debrief.

The room was relaxed but focused. Each committee lead walked through what happened on their end. What worked, what did not, what adjustments were made on the fly, and what ideas should carry forward. The CMC, the Command Master Chief, listened and then gave his own debrief of the season as a whole.

At one point during the discussion, I referred to the CMC as Master Chief. The room reacted immediately. A few Chiefs laughed. Heads turned in my direction.

I was still new. The reaction was not correction. It was recognition. Inside the Mess, rank does not operate the way it does in the open passageway. You address your fellow Chief by his first name, because you are brothers. I had not yet internalized that, fully. The room reminded me.

But what I remember most about that debrief was not that moment. What I remember is what happened after. The lessons from each committee were documented. Processes that worked were recorded. Adjustments were noted. That information went onto a shared drive where future planning teams could find it. The next season would not begin from zero. It would begin from what we had learned.

The season had succeeded. The debrief happened anyway. That sentence describes something most organizations never achieve.

Most organizations debrief failure. The strongest organizations debrief everything. Because learning is not a function of what went wrong. Learning is a function of what happened.

The Gap Most Organizations Never Close

There is a specific point in every organization’s learning cycle where the process breaks down. It is not the point where experience occurs. Organizations have plenty of experience. It is not the point where lessons are identified. Most teams, after a difficult or significant event, can name what they learned if someone asks.

The breakdown happens between the lesson and the memory. The conversation ends. The meeting room empties. The email thread stops. And the lesson, which felt solid and shared just moments ago, begins to dissolve back into the individuals who were present for it.

Six months later, when a similar situation arises, those individuals may or may not still be in the same roles. They may or may not remember the specifics. They may or may not be consulted. The organization has no mechanism for accessing what it learned, because what it learned never became organizational property. It remained personal property.

Bridge leaders sit in a particularly important position when it comes to this gap. They are close enough to the work to see recurring patterns before senior leadership does. They hear the same frustrations across different staff members. They notice the same confusion repeating itself in different forms. They watch the same operational breakdown appear in September that appeared the previous February under a different set of circumstances.

That proximity is one of the most underutilized assets in educational leadership. The bridge leader who recognizes a pattern is not just solving today’s problem. They are sitting on information that could prevent tomorrow’s problem, if that information is captured and preserved rather than managed and forgotten.

What This Series Is About

The Debrief is a series about organizational learning. Each issue examines a real scenario from educational leadership, identifies the organizational pattern the scenario revealed, and explores what a genuine debrief of that moment would surface.

The series is not about how to run a debrief meeting. It is not a crisis management framework. It is not a collection of case studies about what went wrong and how to fix it.

It is about developing the ability to see what a moment reveals. Because moments are always revealing something. Pressure reveals patterns. Success reveals patterns. Conflict reveals patterns. Routine reveals patterns. The leaders who improve culture over time are not the ones who experience the most. They are the ones who learn to see what their experiences are teaching.

Every issue begins with an event. Not with a problem statement or a theory, but with a moment that will feel familiar. From that moment, the series traces the pattern underneath it, examines what a bridge leader should recognize, and moves toward the question that separates organizations that evolve from organizations that repeat themselves.

What should be preserved? That question is where organizational learning either begins or stops.

The debrief in the paid issue that accompanies this article goes deeper into the organizational learning cycle itself. It examines how learning becomes memory, how memory becomes practice, and what bridge leaders can do to close the gap between what their organization experiences and what it actually retains.

If you have ever watched a school navigate the same challenge two years in a row and wondered why nothing changed, you already understand what this series is exploring. The problem was rarely the event itself. The problem was what happened, or did not happen, in the space between the event and the next time.

Organizations do not improve because events occur. They improve because someone preserved what those events revealed.

- Unbroken Growth

Subscribe now

The free article in this issue made one central argument. Remembering is personal. Preserving is organizational. And most organizations mistake the first for the second, which is why they keep paying tuition on lessons they have already learned.

This article does not repeat that argument. It builds on it.

If the free article answered the question of what …

Read more

The assistant principal saw it from the end of the hallway before the bell rang. A student was leaning against the wall with his hood up, shoulders tight, jaw set, already separated from the stream of students moving toward class. A teacher stood a few feet away, voice low, not escalating. She gave him space, waited for his eyes to come up, then said so…

Read more