What happens to a company when folks realize its purpose is disconnected from reality? Flock Safety is finding out.

A rule that's doing its job doesn't get announced, because nobody's worried about it. Think about your office building. There's no sign that says "We promise not to lock the fire exits." The fire code covers it, and so does habit. Now imagine the tenants asked the building manager, in writing, whether the exits would stay unlocked this year. The manager's reply doesn't tell you much, but the question does. Something gave the tenants doubt, which created the need to ask.

In situations where the underlying cause of the issue is structural, swapping in a new CEO doesn’t work. The new leader walks into the same failed (and invisible) Rules layer. The targets and the penalty for missing them haven't moved. The people who learned to smooth results are still there, and so is the founder's influence. So the new leader either keeps the pressure on and inherits the problem, or backs off and gets blamed for missed results. Either way, they're the one w

It’s not that hard to find your opposite. Telling that person the things they’re supposed to stop you from doing is, though. Writing down that list means admitting that there’s a chance we’re wrong. Which, I think, is why we generally don’t go through the painful process of doing it. We find our counterweights, and then we don’t give them permission to sit opposite us on the seesaw. We’ll listen to their opinions, but nothing they do can move us until they’re on the same bar

Organizations that can’t identify the people who know stuff that no one has asked them to explain, or can’t help those people learn how to communicate what they know, are ceding control of their organizational knowledge and institutional memory to whatever the next hire brings with them.

We’re stuck with two options. Keep the decision open and pay for it with bursts of energy, or plan ahead and pay for it in missed predictions and wasted effort. Most leaders and orgs pick a lane, and the failure they can't manage is the one that hides in their strength.

Want to know what your culture actually is? Don't read the values page. Don't check at the annual meeting... the annual meeting knows it's being watched. Watch what people do when they think nobody's checking. Every organization has a way it runs naturally, and that default is the real culture.

You can’t learn what’s safe in an organization by reading the handbook. You learn it by watching what happens to the last person who shared a hard truth, or admitted a mistake. That outcome outweighs the entire universe of inspirational posters about open communication and trust.

Building a team around one star is brittle and failure-prone by design, not by bad luck. A star is temporary. Stars transfer, retire, burn out, or leave for an avocado farm, so the club that rests its results on them is running on a clock it can’t see. The problem shows up while the star is still there. Every team skill the star replaces just rots on the vine. By the time the star is gone, the team has spent months destroying the crop it will depend on.

Early in the first season of Ted Lasso, the show stages a training session that anyone who's ever been new at a job will recognize from the inside. In this instance, a young defender keeps getting beaten by the team's star, who celebrates each win by mocking him in front of the squad. Watch the kid through the whole drill and you can see the real problem: every mistake costs him a few seconds of replaying it in his head, and those few seconds are exactly the window the next m

Six months after a change effort is when you find out whether it actually worked. Not during the rollout, when attention is high and the new way of working is still novel. Six months later, when the next crisis has arrived and the champion who drove the initiative has moved on to something else. That's when you find out whether the improvement was built into the structure or just held in place by effort.

Sometimes, the reason the problem persists isn't that leadership doesn't see it. It's that fixing it requires someone powerful to give something up. To accept a constraint. To close off an option they've been keeping quietly open. When that's the case, no framing fixes it completely. What good framing can do is make the cost of doing nothing explicit enough that the conversation has to happen, even when it's uncomfortable.

What most organizations do under pressure is fix things near the surface. The urgency is real, and fixes at the execution and systems level produce visible results fast. The problem is that a fix at the wrong level doesn't just fail to solve the problem. It spends capital, creates change fatigue, and gives the skeptics more evidence that nothing ever really changes. The willingness to attempt the harder fix, the one at the right level, gets weaker every time the wrong one is

What makes organizational diagnosis so hard? The place where the pain is visible and the place where the pain originates are almost never the same.

The team that needs to move fast is stuck in an approval process built for work that needs to be stable. The team that needs to think carefully before acting is being pushed into sprint cycles built for work that benefits from moving fast. Each of them is working against the structure rather than with it. Under normal load that's a manageable annoyance. Under higher load it's the thing that's breaking everything. Understanding this changes how you read what you're seeing.

If a system keeps producing the same problem, what's it actually doing? The answer, more often than most leaders expect, is that it's protecting something. That's a loaded way to put it, so let's get specific about what it means. Organizations aren't conscious, so they can’t make decisions to protect things. But they do develop patterns over time, and those patterns tend to persist, even when they're also causing visible harm.

Recognizing that feeling of "here we go again" is one of the most useful signals an organization or team can produce. But we don't treat it that way because repetition feels like failure. If the problem came back, someone didn't fix it right or didn't follow through. So the response to the repetition is usually the same as the response to the first one, just with more frustration behind it. Added threats or incentives. A more detailed plan. And usually, a similar result.

It’s a meeting every leader is familiar with. The problem on the table isn't new. It might have been around for months, maybe longer. The people in the room understand that it’s important to fix the issue. But somewhere in the middle of the discussion, you can feel the conversation start to circle. Someone suggests a fix that was tried before. Someone else raises the same objection that was raised before. The meeting ends with an action item or two, but a couple months later

The points where work breaks down are often the same points where teams are pushing back against each other the hardest. From the outside, it looks like a people problem. So the natural response is to get everyone on the same page. Leaders push shared goals, encourage more collaboration, try to get teams working the same way. The assumption is that if everyone agrees on what matters, the friction goes away. It rarely does. The tension is usually coming from the work itsel

By the time something surfaces as a visible issue, the conditions that produced it have already been in place for a while. Work has already moved through several stages. Decisions have already been made. Tradeoffs have already been accepted, often without anyone realizing they were making them. The system has already narrowed things down to a small set of possible outcomes, and one of them just showed up as the problem. And now, the org is reacting to something it has no hope