Insights/Field notes

Field note · · Updated 27 October 2026

Why We Need to Stop Building and Start Thinking: Escaping the Modern Build Trap

The power of asking the right questions

ABAlex Bezuidenhout7 min read

In this note 9 parts · 7 min
  1. The Build Trap in Practice
  2. The Hidden Iceberg of Problems
  3. Why We Miss the Real Problems
  4. The AI Acceleration Effect
  5. A Different Approach: Questions Before Code
  6. The Cost of Shallow Solutions
  7. A small test before a new platform
  8. An assumption and test card
  9. The Competitive Advantage of Thoughtfulness

In today's fast-paced business environment, there's an almost irresistible urge to build solutions quickly. A problem emerges, and our first instinct is to create something - an app, a feature, a system - to address it. But what if this reflexive approach to problem-solving is actually holding us back?

Melissa Perri describes the build trap as a cycle of shipping products without enough investigation into what customers need. The same question is useful beyond software: have we understood the problem before committing to a solution?

The Build Trap in Practice

Consider an illustrative scenario: a company notices declining employee morale and decides to invest in a high-end coffee machine to boost spirits. On the surface, it seems reasonable - better coffee should make people happier, right? But what if the real issue isn't the quality of the coffee, but rather that employees are overworked and stressed?

This example illustrates how the build trap works. Instead of investigating the root cause of a problem, we often assume the solution is technical or procedural. We build first and ask questions later, if at all.

The Hidden Iceberg of Problems

The coffee machine scenario perfectly illustrates one of the most dangerous tendencies in modern business: symptom-solving. When we see declining morale and immediately reach for a tangible, feel-good solution, we're often missing an entire ecosystem of underlying problems that could be the real culprits.

What might actually be causing that morale issue? The possibilities are far more complex and interconnected than a simple caffeine deficiency:

Leadership and Management Issues:

  • Micromanagement culture where employees feel suffocated and untrusted

  • Lack of clear direction from leadership, creating confusion and frustration

  • Poor communication from management, leaving teams in the dark

  • Inconsistent decision-making that creates instability

  • Absence of recognition for good work, making employees feel invisible

Structural and Operational Problems:

  • Understaffing that forces everyone to work beyond their capacity

  • Inefficient processes that waste time and create unnecessary stress

  • Outdated technology that makes simple tasks frustratingly difficult

  • Poor resource allocation that leaves teams scrambling for basic tools

  • Broken workflows that create bottlenecks and delays

Cultural and Environmental Factors:

  • Office environment that's physically uncomfortable or uninspiring

  • Lack of work-life balance policies that push people toward burnout

  • Absence of career development opportunities, creating stagnation

  • Unfair compensation relative to market rates or internal equity

  • Low psychological safety where people fear making mistakes

Business Model and Strategic Issues:

  • Unrealistic expectations set by leadership or clients

  • Constantly shifting priorities that make it impossible to complete anything

  • Lack of purpose in the work itself - people don't understand why they're doing what they're doing

  • Misaligned incentives that reward the wrong behaviors

  • Unsustainable growth targets that create impossible pressure

Here's where it gets really interesting: these problems rarely exist in isolation. They're typically interconnected in ways that create cascading effects. For example: Poor management leads to unclear priorities, which creates inefficient workflows, which requires overtime to compensate, which leads to burnout, which decreases quality, which creates more pressure from clients, which makes management more stressed and reactive, which makes their management style even worse.

The coffee machine "solution" completely ignores this entire web of causation. It's like putting a Band-Aid on a broken leg.

Why We Miss the Real Problems

Several factors contribute to our tendency to focus on surface-level solutions:

The Visibility Bias: Physical problems are easier to see than systemic ones. A slow coffee machine is obvious; a culture of micromanagement is subtle and complex.

The Control Illusion: Buying equipment feels like taking control of the situation. Addressing management issues or restructuring workflows feels messier and less certain.

The Time Pressure: Surface solutions are faster to implement. A coffee machine can be ordered today; fixing a broken promotion system might take months.

The Comfort Zone: Technical solutions feel safer than addressing human and organizational issues, which can be emotionally charged and politically complex.

The same pattern repeats across organizations of all sizes. A startup sees user complaints and immediately starts developing new features. A corporation experiences communication issues and implements another collaboration tool. A government agency faces citizen frustration and launches a new digital platform.

The AI Acceleration Effect

AI-assisted drafting and prototyping make it tempting to move quickly from a question to a polished proposal. The risk is treating the quality of that proposal as evidence that the underlying problem is worth solving. A convincing draft still needs checking with the people affected.

Previously, developing an idea required time, research, and iteration. You had to speak with customers, analyze conflicting data, and wrestle with uncertainties. This process of exploration often led to unexpected insights and course corrections. You might start trying to solve one problem and discover three others that were more important.

Today, however, you can begin with a half-formed thought and quickly produce a polished solution. While this efficiency is impressive, it can lead to well-executed solutions that miss the mark entirely.

A Different Approach: Questions Before Code

At INSO, problem exploration is part of how we shape a piece of work. Our published cases include a one-day innovation sprint with the British Military Advisory Training Team and a seven-week programme for Oxford founders. These were different engagements, each shaped around the people and question involved.

Useful questions before choosing a solution include:

  • What is the real problem we're trying to solve?

  • Who is affected by this issue, and how?

  • What assumptions are we making about the solution?

  • What would happen if we approached this differently?

  • Are we solving a symptom or addressing the root cause?

This questioning process isn't always comfortable. It requires acknowledging uncertainty, challenging assumptions, and sometimes discovering that our initial problem assessment was wrong. But it's this discomfort that often leads to breakthrough insights.

The Cost of Shallow Solutions

When we skip the questioning phase, we don't just risk building the wrong thing - we miss opportunities to solve meaningful problems. Every poorly defined project that gets fast-tracked into development represents a chance to create real value that was squandered.

When we address symptoms instead of root causes, we don't just waste money on coffee machines. We:

  • Lose credibility with employees who see through the superficial gesture

  • Miss opportunities to create meaningful change that could transform the business

  • Allow real problems to compound while we're distracted by fake solutions

  • Create cynicism about leadership's ability to understand and address real issues

  • Waste resources that could have been used for actual improvements

Before committing a team’s time, make the expected improvement explicit. A finished feature is easy to point to; whether it helps someone is a separate question.

A small test before a new platform

Imagine a service team receiving repeated calls from customers asking for updates. A manager proposes a new portal. This is a hypothetical worked example, not a result from an INSO engagement.

First, describe the problem without naming the solution: customers cannot tell what will happen next, so they contact the team again. That statement can be checked against recent enquiries and conversations with customers, including people whose experience differs from the manager’s impression.

The team’s assumption is that clearer status information would reduce avoidable follow-up calls. A portal is one possible way to provide it; a clear email from the existing system is another.

For a small trial, the team could send a status message at an agreed point in the process, stating the next step, its owner and when the customer should expect an update. Compare follow-up contacts and customer understanding with a recorded baseline. Agree the review date and the improvement needed to justify more work before the trial begins.

If calls continue, examine their reasons. Customers may be chasing a missed commitment or trying to correct an error, so another screen would leave the problem intact. If contacts fall, check whether the work mix or service speed also changed before attributing the difference to the message. A small trial can guide the next question; it does not establish demand across every customer group.

An assumption and test card

Use these fields before commissioning a build:

  • Problem and people: Who is affected, what are they trying to do, and what happens today?

  • Evidence: Record observed behaviour, direct feedback and the source. Keep interpretation separate.

  • Assumption: State the uncertain claim that must be true for the proposed solution to help.

  • Alternative: Name another explanation for the problem or a simpler way to address it.

  • Small test: Define what you will change, who will take part and what you will observe.

  • Decision rule: Agree what result would justify continuing, changing direction or stopping. Record the baseline and limitations.

  • Owner and review: Name the person collecting the evidence and the date the team will decide what to do next.

An innovation workshop helps a team practise problem framing and experiments. A facilitated sprint gives a live organisational question a focused period of investigation and decision-making. The card above is a starting point for either conversation.

The Competitive Advantage of Thoughtfulness

When building gets faster, deciding what is worth building still deserves time. Give the team room to investigate the problem and agree what evidence would justify the next commitment.

This doesn't mean we should avoid action or become paralyzed by analysis. Rather, it means being intentional about the problems we choose to solve and ensuring we understand them deeply before we start building.

The next time you're faced with a problem that seems to call for a technical solution, pause and ask: Are we trying to buy a faster coffee machine, or do we need to address why everyone is exhausted?

Your answer might change everything.

The build trap is real, but it's not inevitable. By prioritizing questions over quick fixes, we can create solutions that actually matter. Because sometimes the coffee is fine. Sometimes the problem is that nobody has time to drink it.