Failure Thinking
Asking of every box and arrow how it fails and how you would know.
5 to work through
-
intermediate
A major platform launch is three months away. How would you run a pre-mortem, and why bother?
2 min answer -
advanced
Between August and early September 2025 three separate infrastructure bugs degraded Claude's output quality - one affected 16% of Sonnet 4 requests in the worst hour of 31 August - while error rates and latency stayed normal. What class of failure is this, and what would you have had to build beforehand to notice it?
2 min answer -
advanced
What does it mean to design by thinking about failure first, and what does that produce that requirement-driven design does not?
2 min answer -
advanced
What does it mean to think in failure modes as a habit rather than as a checklist item, and which questions consistently produce findings?
3 min answer -
advanced
What questions characterise failure thinking, and which are most often skipped in design reviews?
2 min answer
4 terms in this topic
Degradation Blindness
Designing and monitoring for components that are either working or failed, when the dangerous and more common state is working slowly - which health …
practiceFailure Thinking
The habit of asking what happens when each part fails, applied systematically during design rather than during the incident.
practicePre-Mortem
An exercise in which a team imagines a project has already failed and explains why, surfacing risks that a forward-looking risk assessment misses.
conceptSilent Quality Regression
A defect that leaves status codes, latency and throughput normal while making the content of responses worse - so every envelope-level alert stays gr…
Neighbouring topics
Meta-Skills
General material on how architects think and work.
Systems Thinking
Interactions and feedback loops rather than isolated components.
Trade-off Analysis
Making costs explicit and comparable rather than asserting a preference.
First-Principles Reasoning
Reducing to physics, mathematics and economics, then reasoning up.
Constraint Thinking
Designing for the budget, skills and regulations that actually exist.
Pattern Recognition
Seeing a familiar problem, and checking whether the forces match.
Pragmatism
The simplest architecture that meets the requirements usually wins.
Judgement Under Uncertainty
Choosing the best worst case when information is missing.
Business Understanding
Connecting a design to the outcome that pays for it.
Influence Without Authority
Getting decisions adopted when you cannot mandate them.
Mentoring
Growing architectural judgement in other people.
Continuous Learning
Staying current without chasing every new thing.
Estimation
Sizing work and cost honestly, with the uncertainty stated.
Prioritisation
Choosing what not to do, and defending it.
Research & Evaluation
Assessing a technology quickly without adopting it by accident.
Handling Ambiguity
Making progress when the requirements are not yet knowable.
Technical Leadership
Setting direction and carrying accountability without a team reporting to you.
Ethics in Architecture
Privacy, accessibility, sustainability and the consequences of a design.
Career Development
Growing from senior engineer to architect and beyond.