Computational Kindness

The design principle of reducing the cognitive burden on others in your communications and interfaces—making it easy for people to respond, decide, and act by doing the computational work for them. Instead of 'when are you free?' (forcing them to compute availability and construct a response), send 'Would Tuesday at 2pm or Thursday at 10am work?' (giving them a simple choice). Computational kindness means pre-computing the hard parts: filtering options, structuring decisions, providing defaults, and formatting information for easy processing rather than dumping raw complexity on the recipient.

When to use it

When communication isn't producing timely responses (you may be imposing too much cognitive work); when designing user interfaces, forms, or processes; when requesting decisions from busy people; when any interaction could be restructured to reduce the cognitive load on the other party.

How it can help

For every communication and interface: ask 'how much work am I asking the recipient to do, and can I do more of it for them?' Emails: propose specific times rather than open-ended scheduling. Decisions: present curated options with recommendations rather than all possibilities. Reports: lead with conclusions and recommendations rather than raw data. Requests: make the desired action as easy as possible (pre-filled forms, clear next steps, direct links). The principle extends to product design: defaults, wizards, and guided flows are computational kindness at scale.