Designing for Capability

Every feature teaches its users a pattern of practice, and practice is how capability is built or lost. This guide turns The Capability Fitness Framework (CH-F-001) and The Capability Model (CH-M-001) into working rules for product design and UX professionals.

In brief: decide deliberately, feature by feature, whether assistance should support a capability or substitute for it — both are legitimate, but only one develops capability. Where capability matters, keep the load-bearing work with the user: their attempt comes before your output, questions come before answers, friction is removed from logistics but preserved in the thinking, support withdraws as skill grows, uncertainty stays visible, reflection has a trigger, delegation is a visible choice, and graduation is a success state. Review features against the five capability domains — Think, Learn, Focus, Create, Adapt — and their AI failure modes, and measure success as transfer (reduced support at equal difficulty, skills applied unprompted) rather than engagement. One question governs all of it:

The Question This Guide Exists to Answer

What kind of assistance helps the user complete the present task while becoming more capable of approaching the next one?