Series: Cognitive Biases
- The Danger of Cognitive Bias
- Action Bias (this post)
- Sunk Cost Bias
Action bias is what happens when momentum becomes a proxy for competence. People feel useful. Leaders feel decisive. The team feels like it’s moving. From the outside it can look like progress.
From the inside, it often feels like relief.
I’ve seen action bias do real damage in creative teams because it tends to arrive wearing the right uniform. It looks like initiative. It looks like ownership. It looks like leadership. And in a deadline-driven environment, those are qualities you actively want.
The problem is that action bias does not ask whether the action is the right one. It asks whether doing something will reduce the discomfort of uncertainty. If you are anxious, exposed, or under pressure, taking action feels safer than sitting still long enough to think.
Wikipedia defines action bias as the tendency to favour action over inaction even when there is no evidence that action will produce a better outcome. That’s a decent start. But in games and software, the more useful framing is this:
Action bias is when you confuse movement with learning.
Why it shows up so often in games and software
Games and software are perfect environments for action bias because they reward urgency.
- Work is visible when people are doing things.
- Leadership is often interpreted as speed.
- Teams feel better when a plan exists, even if it is the wrong plan.
- Shipping something is emotionally easier than admitting you do not yet know what to ship.
Add stress, deadlines, and a few strong personalities, and you can end up with a culture where the default response to uncertainty is to produce output. The team learns to “be helpful”. The organisation learns to equate productivity with progress.
The costs of action bias
Action bias is expensive because it produces real work. That work then creates new commitments. Suddenly you are not just making a decision, you are defending a decision you have already paid for.
Here are the common failure modes.
Wasted resources
Acting without a clear plan can burn time, money, and morale. Teams start work that later gets abandoned or heavily revised. People feel busy but not effective.
Ineffective problem-solving
When the instinct is to act, the organisation can skip the step where it defines the problem properly. You get solutions in search of a question. The underlying issue remains untouched.
Burnout
A culture of constant action creates constant pressure. If the team never gets to slow down, reflect, or reset, stress accumulates. Productivity drops, attrition rises, and quality suffers.
Neglecting innovation
Action bias can crowd out curiosity. If everyone is focused on executing the current plan, there is no space to explore alternatives, test assumptions, or challenge the brief. The team becomes efficient at doing the wrong thing.
Damage to reputation
Repeated mistakes, thrash, and sudden reversals erode trust. Internally, the team stops believing leadership has a coherent plan. Externally, stakeholders lose confidence.
Action bias is not only about rushing. It can also show up as busywork. Meetings, decks, endless re-planning, “just to be safe” processes. Anything that creates the feeling of progress without changing the underlying reality.
Spotting it early
Action bias is easiest to catch when you pay attention to language. A few phrases that often signal it:
- “We just need to do something.”
- “Let’s get a quick win.”
- “We’ll fix it later.”
- “We don’t have time to think about that.”
- “Can you just…”
- “We’ll work it out as we go.”
None of these are inherently wrong. Sometimes you do need to act. The danger is when they become a default posture rather than a conscious choice.
A simple diagnostic question that helps:
What would we do if we had to justify this work in pounds, not hours?
If the action still makes sense, great. If not, you are probably watching action bias in real time.
Tips to avoid action bias
You don’t solve action bias with a poster about mindfulness. You solve it by putting friction into decision making at the points where teams tend to thrash.
Talk openly about it
Name the behaviour when you see it. “I think we’re defaulting to action because we feel pressure” is a useful sentence. If the team can’t say that out loud, the bias will run the room.
Make the objective explicit
Before anyone starts work, ask: What outcome are we trying to change? If the objective is fuzzy, action will fill the gap.
Cost the work
Estimate significant tasks and put a monetary value on them. Not to be reductive, but to make trade-offs visible. A “quick fix” can easily be a £5k decision once you include context switching and knock-on work.
Build in a pause for questions
Encourage brief-challenging and leave time for it. One of the most effective patterns I’ve used is:
“Here’s what I think we need to do. Come back tomorrow with questions, risks, and anything that does not make sense.”
That one day often saves a week.
Distinguish urgency from importance
A lot of action bias is simply mistaking loudness for priority. If everything is urgent, nothing is strategic. Make room for work that reduces future thrash: instrumentation, user feedback loops, clearer ownership, cleaner definitions.
Reward good restraint
If the only praised behaviour is delivery, you will get action bias. Praise the person who says “we’re not ready to decide” when it’s true. Praise the person who kills the wrong idea early. Make it socially safe to pause.
Conclusion
Action is vital. Games and software do not ship themselves. But action without reflection is not leadership, it’s anxiety with a to-do list.
If you recognise action bias in yourself or your organisation, the fix is not “slow down”. The fix is to build a habit of pausing at the right moments, clarifying objectives, and giving people permission to question the brief.
Do that, and you will waste less time, burn fewer people out, and make better decisions under pressure.
If you’d like a second opinion on a plan, roadmap, or a team that feels busy but stuck, do get in touch.
