Decision Making Decision method

Constraint Analysis

Constraint analysis makes hard and soft boundaries visible and shapes them into decision rules and option impact notes.

Constraint analysis classifies boundaries by their binding force and distinguishes changeable limits from conditions that must be worked around. This makes the available design space and its dependencies visible.

Core question

Which limit currently binds the system goal, which apparent limits are rules or assumptions, and what does a controlled relief test show?

Plan Constraint Analysis Method guide

Start comparison

Give feedbackIs this method useful to you?

Participants: 2-8
Time: 90–150 minutes for one bounded system flow; measurement and test extra.

The steps form one complete method run.

Paper illustration for Constraint Analysis.

Boundary
System frame
Set system goal, flow unit, demand, period, and flow start/end.
Register
Constraint register
Capture physical, capacity, policy, and assumed limits with evidence, upper bound, and slack.
Binding
Binding limit
Test candidates against demand and system throughput; observe blockage before and idle time after.
Test
Relief finding
Protect or relieve the constraint and set a measurable prediction and stop rule beforehand.
Decide
Constraint plan
Record binding limit, exploit/elevate action, and next constraint search with owner and review.

Add new evidence at review and version decisions with the prior state.

A good fit when

Wenn ein Vorhaben stockt, liegt die Grenze oft nicht in der Idee, sondern in harten oder weichen Rahmenbedingungen. Constraint Analysis trennt diese Begrenzungen und zeigt, welche davon tatsächlich gestaltbar sind.

Ideal for

Planning under constraints
Architecture and product decisions
Strategic options

Not good for

Free ideation without limits
Simple root-cause analysis
Already fully governed decisions

Outputs

Constraint plan
Evidence-based constraint register with binding limit, buffer effect, relief test, new limit, and decision rule.

Constraint Analysis · working structure

Fictional example

Fictional values show the actual method fields.

Constraint Analysis · working structure
Limit	Type	Upper bound	Evidence	Buffer pattern	Binding?	Relief test	Action
PreparationAdd evidence and rationale.	Capacity	14 units/h	Time study over four Saturdays	No buffer before; 11 wait after handoff later	Yes after test	Observe after handoff relief	Protect as new constraint
HandoffAdd evidence and rationale.	Policy/capacity	9 units/h with one lane	Scanner and handoff log	11 units before; pickup idle after	Yes before test	Second lane 60 min → system 14/h	Set lane standard and owner
Warehouse feedAdd evidence and rationale.	Capacity	18 units/h	Warehouse log	No persistent buffer	No	No test needed	Monitor only

1. Type
Preparation
Capacity
Handoff
Policy/capacity
Warehouse feed
Capacity
2. Upper bound
Preparation
14 units/h
Handoff
9 units/h with one lane
Warehouse feed
18 units/h
3. Evidence
Preparation
Time study over four Saturdays
Handoff
Scanner and handoff log
Warehouse feed
Warehouse log
4. Buffer pattern
Preparation
No buffer before; 11 wait after handoff later
Handoff
11 units before; pickup idle after
Warehouse feed
No persistent buffer
5. Binding?
Preparation
Yes after test
Handoff
Yes before test
Warehouse feed
No
6. Relief test
Preparation
Observe after handoff relief
Handoff
Second lane 60 min → system 14/h
Warehouse feed
No test needed
7. Action
Preparation
Protect as new constraint
Handoff
Set lane standard and owner
Warehouse feed
Monitor only

All values are fictional.

Reference · original teaching example

First step

Set system goal, flow unit, period, demand, and boundary; capture capacity and actual throughput in the same unit.

Open the method guide

Good to do first

Decision Making

Decision Framing Workshop

Supplies the decision frame and goals against which constraints are classified.

Where to go next?

Decision Making

Trade-off Analysis

Uses the shapeable constraints as the basis for comparing options.

Architecture

Architecture Inception Canvas

Feeds confirmed system boundaries and constraints into the architecture inception picture.

Deep dive

Purpose

When an initiative stalls, the limit often lies not in the idea but in hard or soft boundary conditions. Constraint Analysis separates these limits and shows which of them can actually be shaped.

How it works

Boundary conditions are examined for how binding they are and broken down into firm, changeable, or merely bypassable limits. This makes it distinguishable where shaping is possible and where the solution must adapt to reality. This guards against false alternatives that fail against the environment.

In detail

Constraint Analysis treats constraints not as a side note, but as a central structure of the problem. The method distinguishes hard constraints, soft constraints, assumptions, and self-imposed limits. That makes it clear which options are impossible, costly, risky, or only possible under certain conditions. Good constraint work can shrink the solution space while still allowing creative workarounds.

Facilitation

Collect constraints from technology, organization, law, time, budget, people, and market. Mark each constraint as hard, soft, assumed, or negotiable. Ask deliberately which constraint could be relaxed and which one truly cannot be negotiated.

The method guide walks execution through 5 phases, timing, 5 pitfalls, and clear stop criteria.

Open method guide

Your perspective

Does this method help with your work?

Your feedback helps shape the next improvements to methodatlas.

Sources and topics

Topics

Constraints Decision Planning Options

Sources

Constraint Analysisweb.archive.orgArchived TOCICO conference material by Ferguson and Lenhartz on metrics and constraint logic in the Theory of Constraints.

Artifact templates

Constraint Analysis: WorksheetSet subject, evidence, roles, flow, and review.

markdown

constraint-analysis-working-template.md

Set subject, evidence, roles, flow, and review.

Constraint Analysis: Worksheet

Question

To be confirmed

Desired outcome

To be confirmed

Scope

Complete run Time: 90–150 minutes for one bounded system flow; measurement and test extra.

Complete this worksheet on paper or in your own document during the work.

Preparation for this scope

Method setup

Materials: System goal and boundary, throughput/demand data, process or dependency map, constraint register, and test access
Roles: System owner · process participants · data owners · constraint owner · facilitator
Advance information: Set system goal, flow unit, period, demand, and boundary; capture capacity and actual throughput in the same unit.
Overall time needed: 90–150 minutes for one bounded system flow; measurement and test extra.
Setup: Prepare a workspace with Boundary · Register · Binding · Test · Decide; separate example from live data.

Prepare for the work steps

Boundary: System frame

Set system goal, flow unit, period, demand, and boundary; capture capacity and actual throughput in the same unit.
System goal and boundary, throughput/demand data, process or dependency map, constraint register, and test access