Design for X
Quality technique · See it on the map
Guide only — Applying a design guideline is a judgment call.
A family of design rules that shapes a product around one specific later concern, like safety or cost.
When to use it
Early in design, while changing the design is still cheap and the downstream concern (how it will be built, maintained, or paid for) is already known.
When to avoid it
Once the design is locked and in production — applying Design for X at that point turns a pencil edit into an expensive redesign for a benefit that no longer offsets the cost. Also avoid piling on every possible X for a low-stakes deliverable; pick the X that actually matters for that product.
Steps
What it produces
- A design revised against explicit, named criteria.
- A documented record of trade-offs made between competing X's.
Common pitfalls
- Treating 'Design for X' as one generic review instead of naming the specific X and its guidelines — a design reviewed against no explicit criteria isn't Design for X, it's just a review.
- Applying it after the design is already committed, when the fix costs a redesign instead of an edit.
- Optimizing one X, such as cost, while quietly degrading another, such as serviceability, without anyone deciding that trade-off on purpose.
Worked example
Larch & Rowe is designing a custom stair railing bracket for a repeat client. A Design for Manufacturability pass catches that the sketch specifies three different screw sizes; standardizing to one cuts fabrication time and inventory. A separate Design for Serviceability pass flags that the mounting screws would be hidden behind finished trim once installed — the design is changed to leave an access panel, because a future maintenance callback to remove trim would cost more than the panel does now.
Source
- PMBOK-6 §8.2
Where it comes from: this technique is named by the PMBOK Guide, 6th edition.