See Problem, Fix Problem . . . Repeat
Most organizations don’t fail because of one catastrophic problem. They erode under hundreds of small ones that everyone can see and no one fixes. The broken intake form. The handoff that drops information every third shift. The report that takes four hours to compile and that nobody reads. Each problem is minor on its own. Together they act as a steady tax on time, morale, and results.
The organizations that consistently outperform their peers rarely have a secret strategy. They have a habit. Someone sees a problem, someone fixes it, and then they do it again tomorrow. The phrase is simple, and the discipline behind it is uncommon.
A Story from the Floor
Consider a composite drawn from situations I’ve seen many times.
A nurse on a busy medical unit kept running out of a particular supply kit partway through her shift. It wasn’t dramatic. It cost her about ten minutes each time: walking to another unit, borrowing a kit, and coming back. Everyone on the unit knew about it, and everyone had a workaround. The workaround had simply become part of the job.
One week she decided to stop working around it. She counted how often the kit ran out and when. She found that the restocking level had been set years earlier, before patient volumes had grown. She took that to the materials coordinator, and they adjusted the restock level together in an afternoon. Part of the problem was outside her reach, though: the vendor shipped late about one week in four. She didn’t own that piece, so she documented it and passed it to her manager with the data attached.
The result was about ten minutes recovered per nurse, per shift, on one unit. It’s a modest number. What mattered more was what happened next. Two colleagues who watched her do it began fixing things of their own. Within a few months the unit had a running list of small improvements, and people had started to see problems as things to solve instead of conditions to endure.
That is the whole idea. It isn’t heroics. It’s repetition.
Habit Over Heroics
Organizations tend to celebrate the big turnaround: the transformation initiative, the consultant-led redesign, the bold restructuring. Those efforts have their place. But large initiatives are episodic. They start, they peak, and they fade.
Small, repeated fixes work differently because they compound. A team that solves two minor problems a week solves more than a hundred a year. Very few transformation programs can claim that many concrete improvements, and none of them can claim the cultural effect of people learning, firsthand, that their observations matter and that their effort changes things.
The goal isn’t to find the one big fix. It’s to make fixing normal.
Fix What You Can, Flag What You Can’t
“See problem, fix problem” doesn’t mean everyone should solve everything. It means everyone should solve what is genuinely within their reach, and should hand off the rest well.
Most problems fall into one of three groups:
Within your control. You can fix it yourself, today, without permission. Do it.
Within your influence. You can’t fix it alone, but you can fix it with one or two colleagues or a nearby team. Bring them in.
Beyond your reach. It requires decisions, budget, or authority you don’t hold. Escalate it, and escalate it well.
Escalating well is a skill, and it differs from complaining in a few specific ways. A complaint describes frustration. A good escalation describes the problem specifically, shows its impact (ideally with some data, even a rough tally), notes what you’ve already tried, and offers a possible next step. The nurse in the story didn’t say “the vendor is always late.” She said “late shipments occurred in four of the last sixteen weeks, and here is what it cost us.” The first statement gets sympathy. The second gets action.
Why Organizations Quietly Suppress This
If the habit is so valuable, why is it rare? In my experience the obstacle is seldom the people. It’s the system around them.
Organizations suppress problem-solving in predictable ways:
Problems are treated as failures. When raising a problem invites blame, people stop raising problems. The issues don’t go away; they go underground.
Fixing requires too many permissions. If changing a simple process takes three approvals and a committee, people rationally conclude it isn’t worth it.
No one closes the loop. When people escalate an issue and never hear back, they learn that escalation is a dead end.
Work is so full that improvement has no room. If every minute is consumed by the daily work, there is no time left to improve it.
None of this is fixed by asking people to take more initiative. It’s fixed by building a management system in which seeing and solving problems is part of the expected work rather than an extra.
What Leaders Must Do
Leaders don’t create this habit by solving problems themselves. They create it by making it easy, safe, and visible for others to do so. A few practices make the largest difference:
Ask for problems, and thank people for them. The first time someone raises an issue and is met with curiosity instead of defensiveness, the culture shifts slightly. Repeat that often enough and it shifts a great deal.
Push decision rights down. Be explicit about what teams can change without asking. Most leaders underestimate how much permission people believe they need.
Make the work visible. A simple shared board of problems identified, in progress, and solved does two things. It keeps work from disappearing, and it shows progress, which fuels more of it.
Close every loop. Escalated issues deserve an answer, even if the answer is “not now, and here’s why.” Silence teaches people to stop trying.
Protect time for improvement. Even a small, regular amount of time, such as a few minutes in a daily huddle, signals that improvement is part of the job.
A Practical Tool: See. Size. Solve. Share.
For individuals and teams who want to build the habit, here is a short sequence to work through whenever something isn’t working.
See it. Name the problem specifically. “Things are slow” isn’t a problem statement. “Discharge paperwork waits an average of two hours for a signature” is.
Size it. Is it within your control, your influence, or beyond your reach? How often does it happen, and what does it cost in time, quality, money, or frustration?
Solve it, or flag it. If it’s within your reach, try a fix, starting small and adjusting as you learn. If it isn’t, escalate with specifics: the problem, its impact, what you’ve tried, and a suggested next step.
Share it. Tell your team what you found and what changed. Sharing spreads the fix and, just as important, spreads the habit.
Then repeat.
Leaders can use a parallel set of questions in their own reflection:
What problems have I heard about this week, and did each one get a response?
Where are people waiting for permission they don’t actually need?
What did my team fix this month, and did anyone notice?
The Repeat Is the Point
Anyone can fix a problem once. What distinguishes high-performing organizations is that they fix problems continuously, at every level, without waiting for a mandate. Individuals build it as a personal discipline. Leaders build it by designing systems that make it the natural thing to do.
See problem. Fix problem. Repeat. The ellipsis in the title is deliberate, because the third step never really ends.
Comments