Almost every serious organisational failure, looked at closely afterwards, turns out to have had a long warning period. Someone noticed something was slightly off \u2014 a process that took a bit longer than it should, a client who seemed a little less happy than usual, a piece of equipment that made an unfamiliar noise \u2014 and decided, reasonably enough at the time, that it wasn’t worth stopping everything to address. Months or years later, the small thing has become a large, expensive, sometimes reputation-damaging one, and the postmortem inevitably asks the same question: why didn’t anyone catch this sooner?<\/p>\n
The honest answer is usually that someone did catch it. They just didn’t act on it, because on any given day, a small problem competing against urgent, visible priorities almost always loses.<\/p>\n
Small problems have a specific psychological profile that makes them easy to deprioritise. They’re rarely urgent in the moment \u2014 nothing is on fire today, so there’s no immediate cost to waiting. They’re often ambiguous \u2014 is this actually a problem, or just normal variation? And addressing them properly usually requires effort now in exchange for a benefit that’s uncertain and in the future, which is exactly the kind of trade-off human judgement is notoriously bad at prioritising correctly.<\/p>\n
There’s also a social dimension. Raising a small, unglamorous concern repeatedly can start to feel like crying wolf, particularly if nothing visibly bad has happened yet. People learn, often correctly within their specific environment, that flagging minor issues gets less reward than solving visible, urgent ones \u2014 so the incentives quietly point away from exactly the behaviour that would prevent the bigger problems later.<\/p>\n
The danger of an unaddressed small problem isn’t that it stays the same size. It’s that it interacts with everything around it, and those interactions compound in ways that are hard to predict from the outset.<\/p>\n
They erode the systems meant to catch them.<\/strong> A small process gap that goes unaddressed for a while starts to feel normal \u2014 not just to the people who first noticed it, but to everyone who joins afterwards and never learns it was ever a problem. The baseline for “normal” quietly shifts, and the mechanism that would have caught it early stops functioning as intended.<\/p>\n They multiply in combination.<\/strong> A minor issue that’s manageable on its own can become genuinely serious when it coincides with something else \u2014 a busy period, a departing team member, an unrelated crisis competing for the same attention. Small problems rarely fail in isolation; they fail in combination, at the worst possible moment.<\/p>\n They become more expensive to fix the longer they sit.<\/strong> Almost universally, addressing an issue early costs a fraction of what addressing it later does, once it’s had time to affect downstream systems, relationships, or decisions that were built on the assumption that everything underneath them was sound.<\/p>\n They erode trust quietly.<\/strong> A client who mentions a minor frustration once and sees no change doesn’t necessarily complain again \u2014 they simply factor it into a broader, gradually forming judgement about whether the relationship is worth the friction, a judgement that often surfaces all at once, at renewal time, with no warning.<\/p>\n Create a genuine, low-friction way to flag minor issues.<\/strong> If raising a small concern requires the same formal process as raising a major one, most small concerns simply won’t get raised. A lightweight, quick way to flag something \u2014 without it needing to be framed as urgent to be taken seriously \u2014 catches far more early signals.<\/p>\n Treat “this seems fine for now” as worth a second look, not a final answer.<\/strong> The most dangerous small problems are the ones that seem tolerable precisely because no one has stress-tested what happens if they combine with something else.<\/p>\n Build in regular, deliberate reviews of things that aren’t currently on fire.<\/strong> Most management attention naturally flows toward whatever’s urgent. A periodic, structured look at things that are quietly “fine” \u2014 not broken, but not quite right either \u2014 catches issues that would otherwise only surface once they’ve become genuinely serious.<\/p>\n Reward people for raising unglamorous concerns, not just for solving visible crises.<\/strong> If the only visible recognition in an organisation goes to firefighting, people will rationally learn to let small fires grow large enough to be worth fighting publicly, rather than reporting the smoke.<\/p>\n Ask, specifically, what’s been quietly tolerated.<\/strong> In one-to-ones and team discussions, a direct question \u2014 what’s something we’ve all just gotten used to that probably shouldn’t be normal? \u2014 surfaces issues that would never come up unprompted.<\/p>\n A operations manager notices that a particular client’s onboarding process has been taking slightly longer than the target for months \u2014 not dramatically longer, just consistently a bit over, in a way that nobody had escalated because no single instance seemed worth flagging. Rather than accepting the slippage as the new normal, she asks specifically what’s causing the delay and discovers a small, unaddressed gap in a handover process between two teams \u2014 each team assuming the other was covering a particular step.<\/p>\n Fixed on its own, the gap would have been a minor process tweak. Left alone, it was on track to compound: a busier season was approaching, during which the same small gap, combined with reduced staff availability, would likely have caused a genuinely serious service failure with a major client. The fix took an afternoon. The version of the problem that never got the afternoon would likely have taken weeks to repair \u2014 and a client relationship along with it.<\/p>\n Waiting for a problem to become urgent before addressing it.<\/strong> By the time a small issue becomes urgent, it has usually also become more expensive, more entangled with other systems, and harder to fix cleanly.<\/p>\n Dismissing minor concerns because “nothing’s actually gone wrong yet.”<\/strong> The absence of a visible failure isn’t the same as the absence of a real problem \u2014 it often just means the problem hasn’t yet combined with the specific conditions that would expose it.<\/p>\n Only rewarding visible crisis management.<\/strong> An organisation that celebrates firefighting more than fire prevention will, over time, get more fires.<\/p>\n Treating every small concern as equally worth immediate action.<\/strong> Not every minor issue needs urgent attention \u2014 the skill is in distinguishing background noise from genuine early warning signs, not treating everything as a crisis.<\/p>\n The gap between a minor inconvenience and a genuine crisis is rarely a single dramatic event \u2014 it’s usually months of small, reasonable decisions to wait, made by people who had other, more urgent things competing for their attention. Building a habit of catching and addressing small problems early isn’t glamorous, and it rarely gets the recognition that solving a visible crisis does. But it’s consistently cheaper, and it’s the difference between an afternoon fix and a multi-week recovery.<\/p>\n How do I know if a small problem is actually worth addressing now?<\/strong> Why don’t employees report small problems more often?<\/strong> Is it possible to over-invest in fixing minor issues?<\/strong> How can leaders build a culture that catches small problems early?<\/strong> What’s the difference between a minor issue and normal variation?<\/strong> Should every small concern be escalated formally?<\/strong> The biggest crises rarely start as crises. They start as small, ignorable problems that nobody quite got around to fixing. Here’s how to catch them earlier.<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"site-sidebar-layout":"default","site-content-layout":"","ast-site-content-layout":"default","site-content-style":"default","site-sidebar-style":"default","ast-global-header-display":"","ast-banner-title-visibility":"","ast-main-header-display":"","ast-hfb-above-header-display":"","ast-hfb-below-header-display":"","ast-hfb-mobile-header-display":"","site-post-title":"","ast-breadcrumbs-content":"","ast-featured-img":"","footer-sml-layout":"","ast-disable-related-posts":"","theme-transparent-header-meta":"default","adv-header-id-meta":"","stick-header-meta":"","header-above-stick-meta":"","header-main-stick-meta":"","header-below-stick-meta":"","astra-migrate-meta-layouts":"set","ast-page-background-enabled":"default","ast-page-background-meta":{"desktop":{"background-color":"var(--ast-global-color-5)","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""},"tablet":{"background-color":"","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""},"mobile":{"background-color":"","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""}},"ast-content-background-meta":{"desktop":{"background-color":"var(--ast-global-color-4)","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""},"tablet":{"background-color":"var(--ast-global-color-4)","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""},"mobile":{"background-color":"var(--ast-global-color-4)","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""}},"footnotes":""},"categories":[19],"tags":[9,20,35,34],"class_list":["post-2012","post","type-post","status-publish","format-standard","hentry","category-management-skills","tag-leadership","tag-management-skills","tag-organisational-culture","tag-risk-management"],"yoast_head":"\nHow Good Managers Catch Small Problems Early<\/h2>\n
A Practical Scenario<\/h2>\n
Common Mistakes<\/h2>\n
Action Steps<\/h2>\n
\n
Key Takeaways<\/h2>\n
\n
Conclusion<\/h2>\n
Frequently Asked Questions<\/h2>\n
\nAsk what would happen if it combined with a busy period, a staffing change, or another unrelated issue. If the combination looks genuinely damaging, it’s worth addressing before those conditions occur, not after.<\/p>\n
\nUsually because raising minor concerns feels like it carries some cost \u2014 time, credibility, the risk of seeming overly cautious \u2014 with no clear reward, especially in cultures that only visibly recognise crisis response.<\/p>\n
\nYes \u2014 not every small issue needs urgent attention, and treating everything as a crisis creates its own kind of fatigue. The goal is discernment, not maximal vigilance.<\/p>\n
\nBy creating low-friction reporting channels, periodically reviewing things that aren’t currently urgent, and visibly recognising people who raise concerns early rather than only those who solve visible crises.<\/p>\n
\nThis isn’t always obvious in the moment, which is exactly why periodic, deliberate review matters \u2014 a pattern that repeats consistently over time is a stronger signal than a single instance.<\/p>\n
\nNo \u2014 formal escalation for every minor issue creates its own friction. A lightweight, informal way to flag things is usually more effective than requiring the same process for everything.<\/p>\n","protected":false},"excerpt":{"rendered":"