ActiveDraftPrinciple
05
Build for Humans
Design APIs, tools and docs around the people who use them.
StatusActive
MaturityDraft
Versionv0.1.0
Created2026-07-01
Updated2026-07-01
References2
#dx#ux#empathy
Overview
Software is a human interface first. APIs, error messages, tooling and documentation are designed for the humans who depend on them, not for the machine.
Why
The reasoning behind "Build for Humans" will be captured here — grounded in real engineering trade-offs rather than theory.
Standard
The concrete, enforceable expectations for "Build for Humans" will be defined here as the principle matures into a standard the team can hold each other to.
Examples
- A real example will be added once this principle has guided a shipped decision.
Counter Examples
- A real counter-example will be added from a decision that ignored this principle and paid for it.
Lessons Learned
- Lessons will accumulate here through applied engineering experience.
Related Documents· 2
Referenced By· 2
Version History
- v0.1.0
Principle established with placeholder content.