This is the third in a series about HOW TO do things in the content world.

Finding a problem is a disorienting event. It throws you out of rhythm, it makes people worry about blame instead of the fix, and it exposes the organization to more risk the longer it sits unaddressed. But an organization that never hits problems isn't pushing hard enough. Progress doesn't happen without setbacks, and how well you diagnose and respond to them is mostly a byproduct of culture, not individual talent. A team encouraged to raise problems without fear of blame gets much better, collectively, at solving them. A team that discourages raising problems doesn't make the problems disappear. It just sends them underground until they're too big to fix quietly.

Here's the process I use. Some of it will sound obvious. It gets skipped more often than you'd expect.

Breathe and assess before acting

The instinct when a problem shows up is to move immediately, especially if you already think you have the answer. That's exactly the moment to slow down. If you've spent time starving for a good idea, the first one that arrives feels irresistible. Resist it anyway, long enough to check it.

Remove the emotion

Don't get emotional about who caused the problem, whether that's you or someone else. If there's no clear culprit, don't get irrationally angry at circumstance. Most problems are the result of an organization moving too fast, or not fast enough, and treating them as a chance to reset is more useful than treating them as a verdict on anyone's competence.

Assign a core team

A problem can spiral out of control, and so can the group assembled to solve it. Identify exactly what skills the fix requires and keep the decision-making team to those people. Bring in a wider group for input if you need it, but keep ownership of the final call with a small, named set of people.

Map cause and effect

By this point you likely have a few candidate solutions, some more appealing than others. Every one of them has a downstream effect the moment you act on it. Trace that effect before you commit, so today's fix doesn't quietly create two bigger problems tomorrow.

Drop everything and execute

Once you've found the right solution, commit real resources to it. Problems get worse far more often from a half-committed fix than from a wrong one. Decide, then move.

Hold the debrief

Never let a solved problem pass without a real debrief. Everyone should come with an honest account of what happened, how it was addressed, what would improve the next response, and, most importantly, how to keep the same problem from recurring.

None of this removes the discomfort of hitting a real problem. But it's the difference between a problem that costs you a week and one that quietly costs you a quarter.