What Are Your Users Practicing?

The mechanism is almost embarrassingly simple: design shapes use, use becomes practice, practice becomes capability.

A tool that always hands over the finished answer trains one pattern. A tool that asks a good question first, offers a hint before a solution, or invites the user's rough take before generating — that trains another. Neither pattern shows up in a usability test. Both compound over months, and your users carry the result into every task they face, inside your product and far beyond it.

This matters more now than it ever has, because our products are no longer just holding our users' work — they're participating in their thinking. AI assistants, copilots, learning tools, decision support: these do cognitive work the user might otherwise do. Done thoughtfully, that's a gift: users do better work and become more capable doing it. Done carelessly, it does the work in their place and leaves them less practiced at the very things they came to us to do well.

To be clear about what this is not: it's not an argument against assistance, and it's certainly not a call to make products harder. A speech-to-text tool that lets a stroke survivor write to his family again is restoring capability — beautiful, ship it, make it effortless. The same tool letting a student skip the writing practice her coursework was meant to provide is quietly replacing capability instead.

Same feature. Opposite outcomes. The difference is context — and the guide's first move is to give you a clean way to tell them apart. Some effort in a task is incidental: formatting, boilerplate, retrieval logistics. Remove it ruthlessly. Some effort is load-bearing: framing the problem, weighing evidence, forming a first idea. That effort is the practice. The craft is knowing which is which, feature by feature.

The worst designs, the guide notes, are substitution that believes it is support.

The full guide translates Capably Human's two framework publications — the Capability Fitness Framework and the Capability Model — into working rules you can use in your next design critique. You'll find eight design principles, each with concrete techniques: inviting an attempt before assistance, asking questions before answers, keeping friction adaptive rather than absent, scaffolding that gracefully withdraws itself, uncertainty you can actually see, reflection built into the flow of work, delegation as a visible choice, and — our favorite — treating the moment a user no longer needs a feature's help as a success state rather than a churn risk.

There's also a five-domain review lens for spotting where a feature quietly substitutes for the thinking it means to help, a section on measuring what actually matters (hint: it isn't engagement), and a ten-question capability design review you can run against any feature before it ships.

We think there's something genuinely hopeful here. The same care we've spent decades pouring into making products usable can now be pointed at making people more capable. Imagine shipping something and knowing that the people who use it are becoming sharper thinkers, better questioners, more confident judges of their own work — and that they'd choose your product for leverage, not out of need. That's a product worth building, and a legacy worth leaving.

The guide is a working draft — offered to be tested, critiqued, and improved. Read it, run the ten questions against something you're building this week, and tell us what you find.

→ Read the full guide: Designing for Capability (CH-G-001)

Capably Human · November 3, 2026