A document-sharing flow names the document, recipient, permission level, and expiration before sharing. The confirmation shows the current access and a route to change it.
Chapter 12 / 14
Give people clear control over consequential choices
Explain data use, risk, and recovery so a person can make an informed choice.
Your goalChoose a permission or consent request. Write the purpose, scope, options, confirmation, and reversal route in the order a person needs them.
01 / Begin with the task
The principle
A privacy or safety decision often asks a person to trade information, access, or control for a service outcome. The interface must make the scope and consequence of that choice clear before the person acts.
- Purpose
- The specific reason a service asks for data, permission, or an action.
- Scope
- The people, information, systems, and duration affected by a choice.
- Reversal
- The route for changing a preference or recovering from a consequential action.
Name the immediate purpose of a request and the exact data or capability it affects. Show the meaningful options with equal clarity and explain the outcome of each. Put the explanation beside the choice, using language a person can connect to their task. For sensitive actions, show the affected object and a review step before commitment.
Design the later state as carefully as the first prompt. People need a place to inspect current permissions, change a preference, see an action history where appropriate, and understand the result of a report or deletion request. Test whether a person can explain the scope of the decision, choose deliberately, and find the route to change it.
02 / Follow a method
Apply it in four steps
- Name the person's task and the service purpose for the request.
- Describe the data, people, systems, and duration in scope.
- Present each meaningful choice and its consequence clearly.
- Test comprehension, reversal, and recovery across the full journey.
03 / Compare outcomes
Strong and weak execution
A document-sharing flow uses a generic Allow button and reveals the recipient list after submission. A person needs extra steps to discover the audience and change access.
Why the outcome changes
The strong flow supports an informed choice at the decision point and makes the later state inspectable. The weak flow separates scope from commitment. Test comprehension before activation, then ask the person to find and change the resulting permission.
04 / Use the method
Practice on a real screen
Choose a permission or consent request. Write the purpose, scope, options, confirmation, and reversal route in the order a person needs them.
Review your work
- The purpose and scope appear before commitment.
- Each option states its result in concrete terms.
- The person can inspect and revise the choice later.
Keep your observation, interpretation, and proposed change together. Use the related patterns to inspect complete interaction states.