Design: Outcomes Over Intentions
What Is Good Design?
Today’s Lens: Stafford Beer — Revealed Purpose Over Stated Intent
“The purpose of a system is what it does. This is a basic dictum. It stands for bald fact…” — Stafford Beer. (en.wikipedia.org)
Beer’s provocation is surgical: judge design by outcomes, not intentions. If your product “intends” to empower but routinely traps users in detours, its real purpose (for now) is detouring. Good design makes the intended purpose and the observed behavior converge—and keeps watching for drift. (en.wikipedia.org)
- Try this 10‑minute “revealed purpose” audit:
- Name your feature’s stated purpose in one sentence.
- Pull one week of behavioral traces (the most common user paths, drop‑offs, and workarounds). What behavior does the system actually produce? (forbes.com)
- Close the gap with one change that alters behavior immediately (e.g., remove a step, shift a default, or change an affordance). Re‑measure the path users now take.
Design maturity isn’t how elegant the plan looks—it’s how honestly your system reveals itself in use, and how quickly you reshape it so what it does matches what it’s for. (en.wikipedia.org)
—
Sources (full URLs):
- https://en.wikipedia.org/wiki/The_purpose_of_a_system_is_what_it_does
- https://www.forbes.com/sites/benjaminkomlos/2021/09/13/the-purpose-of-a-system-is-what-it-does-not-what-it-claims-to-do/
- https://en.wikipedia.org/wiki/Stafford_Beer
- https://www.wiley.com/en-us/Classic%2BBeer%2BSeries-c-6056 (The Heart of Enterprise)