Handling Ambiguity
Making progress when the requirements are not yet knowable.
5 to work through
-
intermediate
The constraint that shaped your design - order records must stay inside the country - came from a conversation with the VP who commissioned the work. She leaves in month three. What happens to the design next and what should have been in place?
3 min answer -
intermediate
You must start designing and the requirements are genuinely unclear. What do you do?
2 min answer -
advanced
An architect is asked to design a system where the requirements, scale and business model are all still changing. How should they proceed?
2 min answer -
advanced
An architect is asked to design something where the requirements are genuinely unclear and the stakeholders disagree about the goal. What is the productive approach?
2 min answer -
advanced
An executive says "we need an AI strategy" and asks you to come back in two weeks. How do you handle the ambiguity?
1 min answer
2 terms in this topic
Ambiguity Tolerance
The capacity to make progress on a problem before it is fully specified, which is the normal condition of architectural work.
practiceHandling Ambiguity
Making progress when the requirements are unclear, the stakeholders disagree, and waiting for clarity is not an option.
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.
Failure Thinking
Asking of every box and arrow how it fails and how you would know.
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.
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.