Constraint Thinking
Designing for the budget, skills and regulations that actually exist.
4 to work through
-
beginner
A pipeline has four stages. Three run at about 30% utilisation and one runs at 95%. The team adds capacity to all four. Throughput barely moves. Why?
2 min answer -
beginner Multiple choice
A team must ship a compliance-driven reporting system by a fixed statutory date nine months away. There are three engineers, no operations staff, an existing Postgres database, and no budget for new licences. Which constraint should drive the architecture?
3 min answer -
intermediate
A stakeholder states a requirement as an adjective. How does constraint thinking convert it into something designable?
2 min answer -
intermediate
Treat an operator's attention late in an incident as a hard constraint rather than a behaviour to coach. In January 2017 a GitLab engineer working past the end of their shift ran a destructive command against the primary database host instead of the replica. Which controls change that outcome and which are theatre?
3 min answer
3 terms in this topic
Binding Constraint
The one resource in a chain whose capacity sets the throughput of the whole chain - so that investment anywhere else buys idle capacity rather than output.
practiceConstraint Thinking
Designing within the real limits — budget, skills, timeline, existing estate, organisational politics — rather than for the abstractly best answer.
conceptTheory of Constraints
The principle that a system's throughput is set by a single binding constraint, so improvement anywhere else produces nothing.
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.
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.