> Markdown version of [/videos/2105-unbiased-decision-making-designing-better-decisions-in-high-pressure-engineering-teams](https://www.wearedevelopers.com/videos/2105-unbiased-decision-making-designing-better-decisions-in-high-pressure-engineering-teams). Every page supports `.md` or `Accept: text/markdown`. Links point to the HTML versions so they work for humans too. Agent guide: [/agents.md](https://www.wearedevelopers.com/agents.md).

---

# Unbiased Decision-Making: Designing Better Decisions in High-Pressure Engineering Teams

In 2018, high-pressure deadlines and cognitive bias led to a fatal autonomous crash. Learn how to use the DECIDE framework to bypass blind spots and engineer better decisions.

- **Speakers:** [Anna W Kriss Petersson](https://www.wearedevelopers.com/@anna-w-kriss-petersson)
- **Event:** World Congress 2026 Europe - Virtual Stage
- **Published:** July 3, 2026
- **Duration:** 27:35
- **URL:** https://www.wearedevelopers.com/videos/2105-unbiased-decision-making-designing-better-decisions-in-high-pressure-engineering-teams

## Summary

The fatal 2018 autonomous vehicle crash caused by Uber’s testing shortcuts serves as a stark warning about the dangers of cognitive bias in high-pressure engineering environments. Faced with intense investor expectations and competitor deadlines, leadership disregarded critical safety concerns and defaulted to "System 1" thinking—the brain's fast, automatic, and emotionally driven response mode. To prevent high-stakes failures caused by the sunk cost fallacy or survivorship bias, technical leaders must deliberately activate the analytical, resource-intensive "System 2" cognitive mode through disciplined structural processes.

To counteract the biological tendency toward bias, engineering and product teams can implement the DECIDE framework, a structured methodology designed to separate objective reality from assumptions. The process originates with a Problem Statement Canvas to isolate the true systemic issue, followed by establishing criteria via the 10-10-10 model. By evaluating the ripple effects of a technical decision across 10 minutes, 10 months, and 10 years, organizations prevent immediate resource constraints from overshadowing long-term scalability and employee experience.

Executing viable solutions requires bypassing the "false binary" trap using methods like the impossible scenario exercise, which forces divergent ideation by hypothetically eliminating the most obvious paths. Subjecting these newly generated alternatives to weighted scoring against established criteria ensures that the most robust solution prevails over the most convenient. While completely eliminating human bias is impossible, adopting milestone-mapped execution and systemic decision frameworks protects technical deployments, user safety, and organizational alignment from the blind spots of pressure-driven development.

**Keywords:** cognitive bias mitigation, system 1 vs system 2 thinking, decide decision framework, high-stakes engineering decisions, product development sunk cost fallacy, survivorship bias in data analysis, problem statement canvas, 10-10-10 consequence model, false binary avoidance, impossible scenario ideation, weighted scoring criteria, engineering milestone mapping, technical leadership objectivity, scalable organizational design, leadership decision structures

## Chapters

1. **The fatal consequences of biased decisions at Uber** (01:08) — Business pressure to deploy self-driving cars led leadership to ignore engineer warnings and shortcut safety testing.
1. **Understanding system one and system two thinking models** (06:16) — System one relies on fast emotional patterns, while system two handles complex analytical trade-offs.
1. **Recognizing survivorship bias through historical bomber plane data** (08:23) — Analyzing missing damage data from surviving planes reveals how quick pattern recognition leads to faulty conclusions.
1. **Contextual factors triggering cognitive biases in modern work** (10:18) — High stress, excessive data, and extreme time pressure force brains to default to fast autopilot reactions.
1. **Adopting a structured approach to reduce bias influence** (11:42) — Implementing disciplined decision-making processes helps counteract biases and activates analytical thinking during high-impact situations.
1. **Identifying and overcoming the sunk cost fallacy** (13:00) — Evaluating required measurable goals and opportunity costs prevents continuous investment in failing product development features.
1. **Applying the decide model for structured team choices** (17:10) — The five-step decide framework provides a systematic process for making high-stakes decisions without relying on individual intuition.
1. **Defining the core problem and establishing baseline assumptions** (18:43) — A problem statement canvas narrows down specific situations, affected stakeholders, and underlying assumptions before seeking solutions.
1. **Establishing consequence timelines with the 10-10-10 model** (20:52) — Projecting the organizational impact of decisions across short, medium, and long-term horizons prevents over-optimizing for immediate needs.
1. **Overcoming false binaries using the impossible scenario tool** (23:24) — Forcing the elimination of obvious paths generates viable new alternatives and prevents teams from stalling between two choices.
1. **Evaluating alternatives against criteria using weighted scoring** (24:31) — Ranking generated options against established timeline and cost criteria helps teams select the best path based on objective priorities.
1. **Drafting execution plans through milestone timeline mapping** (25:31) — Mapping weekly and monthly milestones rapidly validates whether team resources and technical skills can actually execute the chosen solution.

## Related Moments

- [Mitigating hardwired cognitive biases in technical decision making](https://www.wearedevelopers.com/videos/1992-thoughts-on-modern-software-development-observations-from-a-21-year-journey) (from "Thoughts on (Modern?) Software Development - Observations From a 21-Year Journey")
- [Fostering empathy and accountability in engineering decisions](https://www.wearedevelopers.com/videos/2110-the-algorithm-that-nearly-killed-me-when-testing-isn-t-enough) (from "The Algorithm That Nearly Killed Me: When Testing Isn't Enough")
- [Overcoming cognitive biases in software tool evaluation](https://www.wearedevelopers.com/videos/1916-old-tools-new-tricks) (from "Old tools, new tricks")
- [Cognitive bias and uncritical tech adoption in architecture](https://www.wearedevelopers.com/videos/1438-why-most-software-projects-fail-silently) (from "Why (most) software projects fail silently...")
- [Why existing knowledge fails to reach decision points](https://www.wearedevelopers.com/videos/1933-why-smart-engineering-teams-make-bad-decisions) (from "Why Smart Engineering Teams Make Bad Decisions")
- [Mitigating groupthink through diverse and inclusive software engineering teams](https://www.wearedevelopers.com/videos/43-algorithmic-bias-preventing-unfairness-in-your-algorithms) (from "Algorithmic Bias- Preventing Unfairness in your Algorithms")

## Related Articles

- [Navigating the AI Shift](https://www.wearedevelopers.com/magazine/629-navigating-the-ai-shift)
- [Ignore the Hype: How to Avoid Being Deceived by Technological Trends](https://www.wearedevelopers.com/magazine/528-ignore-the-hype-how-to-avoid-being-deceived-by-technological-trends)
- [Never delegate the understanding](https://www.wearedevelopers.com/magazine/749-never-delegate-the-understanding)
- [Panel Discussion: Responsible AI in Practice - Real-World Examples and Challenges](https://www.wearedevelopers.com/magazine/488-panel-discussion-responsible-ai-in-practice-real-world-examples-and-challenges)

## Related Jobs

- [Tribe Lead - ( Software) Engineering Centre of Excllence](https://www.wearedevelopers.com/jobs/ext/1475530-tribe-lead-software-engineering-centre-of-excllence) at **SD Worx**
- [Head of AI Applications](https://www.wearedevelopers.com/jobs/ext/1231536-head-of-ai-applications) at **ZEISS Group**
- [Staff Software Engineer, Copilot Experiences](https://www.wearedevelopers.com/jobs/ext/164361-staff-software-engineer-copilot-experiences) at **GitHub**
- [Principal Software Engineer, Enterprise AI Platform](https://www.wearedevelopers.com/jobs/ext/1467292-principal-software-engineer-enterprise-ai-platform) at **GitHub**
- [Head of AI Applications](https://www.wearedevelopers.com/jobs/ext/1456210-head-of-ai-applications) at **ZEISS Group**
- [Senior Engineer, Infrastructure Platform](https://www.wearedevelopers.com/jobs/ext/328836-senior-engineer-infrastructure-platform) at **Intercom, Inc.**