A manufacturing line stops at 2 a.m. Every hour it stays down costs tens of thousands in lost output, and customers are waiting on shipments due by the end of the week. The engineering team knows how good problem-solving is supposed to work: gather data, map the system, trace symptoms back to root causes, generate options, test them. That process might take a fortnight. They have hours.

Most problem-solving training leaves this gap open. The frameworks we learn treat time as a neutral background condition. It isn't. Time pressure changes the nature of the problem itself. The cost of delay becomes part of the problem, and sometimes the largest part. A perfect answer delivered late can be worse than a rough answer delivered now.

Yet speed brings its own failure modes. Under pressure, people grab the first plausible fix, skip the checks that matter, and create tomorrow's crisis while solving today's. The goal isn't simply to go faster. It's to change your method deliberately, knowing which steps to compress, which to defer, and which you can never afford to skip.

Every problem carries two costs that pull against each other. The cost of delay is what you lose for each hour without a solution: revenue, customer trust, safety margin, momentum. The cost of error is what you lose if your solution is wrong. Slow, careful methods minimise error. Fast methods minimise delay. Neither is correct in general. The right balance depends on how those two costs compare in your specific situation.

The variable that most changes this calculation is reversibility. Jeff Bezos described it as the difference between one-way and two-way doors. A two-way door decision can be undone cheaply if it turns out wrong, so speed wins: decide, observe, adjust. A one-way door locks you in, so even under pressure it deserves more deliberation. Many decisions made in a crisis are two-way doors that only feel like one-way doors because of the stress surrounding them.

This gives you a practical guide to cutting corners. Some steps are safe to compress: exhaustive option generation, polished documentation, broad consensus, and precision beyond what the decision actually needs. If two options both work, knowing which is three percent better rarely matters at midnight. These steps have real value, but you can recover most of it later, once the pressure lifts.

Other steps are unsafe to compress: problem definition, safety checks, and anything guarding against irreversible harm. Skipping the definition step is the classic mistake under pressure. Teams solve the most visible problem rather than the one that matters, and lose more time than they saved. Ten minutes spent asking 'what exactly are we trying to fix?' is rarely wasted, however loud the alarms.

Takeaway

Time pressure should change how much you analyse, not whether you think. Cut corners where mistakes can be undone, and slow down only at the doors that lock behind you.

Under time pressure, the aim of assessment shifts. You are no longer trying to understand the problem completely. You are trying to understand it well enough to take a useful first action. Emergency medicine has refined this approach for decades through triage: a quick, structured look that sorts what needs attention now from what can wait, without attempting a full diagnosis.

A useful rapid assessment asks three questions in order. First, is it getting worse? A stable problem buys you time. A deteriorating one demands containment before diagnosis. Second, what can't be undone? Identify the irreversible risks and protect against them first. Third, what changed? A system that worked yesterday and fails today usually fails because something shifted: a new supplier, a software update, a staffing change. This question is often the fastest route to a probable cause.

It also helps to inventory your constraints before generating ideas. After an explosion crippled Apollo 13 in 1970, carbon dioxide began building up dangerously inside the spacecraft. Engineers on the ground worked from an inventory of what the astronauts actually had on board, then designed an improvised adapter from those items: plastic bags, cardboard, tape. Defining the solution space first meant no time was lost on ideas that could never be built.

Finally, time-box the assessment itself. Decide upfront how long you will investigate before acting, whether fifteen minutes or an hour, and hold to that limit. Assessment can easily become a comfortable way to avoid committing. When the time is up, act on your best current hypothesis and treat the result as your next piece of evidence. In fast-moving situations, intervening is often the quickest way to learn. A well-chosen action can tell you more in ten minutes than another hour of discussion.

Takeaway

Rapid assessment isn't a shallow version of full analysis. It asks a different question: not 'what is everything that's wrong?' but 'what do I need to know to act safely next?'

The economist and decision theorist Herbert Simon coined the term satisficing to describe choosing the first option that meets an acceptable threshold rather than searching for the best possible one. It is often treated as a compromise. Under time pressure, it is the rational strategy. Searching for the optimum costs time, and when time is expensive, the search itself can destroy more value than the better answer would create.

The difficulty is that 'good enough' is usually left undefined, which turns it into an excuse rather than a standard. Before choosing a solution, state explicitly what adequate means. What must the solution achieve? For how long? Which risks are acceptable, and which are not? A fix that keeps a system running safely for two weeks is good enough if a permanent repair can be completed within those two weeks. It is not good enough if nobody plans the repair.

This points to the second test of a good-enough solution: does it preserve future options? Engineers distinguish between containment, which stops damage from spreading, and correction, which removes the cause. A tourniquet is containment. It is exactly right in the moment and harmful if left on too long. Prefer solutions that are easy to remove, avoid permanent changes made under stress, and don't lock in decisions that deserve proper analysis.

The real danger lies not in the quick fix but in forgetting that it was quick. Temporary workarounds have a habit of becoming permanent infrastructure, quietly accumulating risk. Treat every solution made under pressure as a loan against the future. Label it as temporary, assign an owner, set a review date, and schedule the root cause analysis that the crisis didn't allow. The fix buys you time, and it is only valuable if that time is spent well.

Takeaway

A good-enough solution has two jobs: meet a clearly defined standard today, and leave the door open for a better answer tomorrow. If it fails the second test, it isn't good enough.

Time pressure doesn't make rigorous problem-solving impossible. It calls for a different kind of rigour: discipline about where to spend scarce attention, rather than thoroughness everywhere.

When the clock is running, work through four steps. Price the delay and check reversibility to decide how fast to move. Assess rapidly by asking what's worsening, what's irreversible, and what changed, within a fixed time-box. Define enough before choosing, and favour solutions that can be undone. Then schedule the return, so the root cause gets the attention the crisis denied it.

Next time pressure builds, notice the urge to skip definition or to chase perfection. Both lose time while making you feel busy. The skill isn't working faster. It's knowing precisely what speed is allowed to cost.