Multi-step work, approvals, scheduling, review queues, checkout, and task completion.
Browse all problem familiesA workflow joins actions across time, people, and systems. Each step gives the person enough context to continue, review, pause, or recover.
Strong: A booking flow carries the selected room and date through review, payment, and confirmation, with a clear route back to edit details.
Weak: A booking flow resets the room after payment fails and sends the visitor to the beginning of the process.
Try it: Map a five-step task and annotate where information is saved, reviewed, transferred, and confirmed.
Begin with the core behavior, apply it in different contexts, then review cases that reveal the quality boundary. Open each entry for its decision rule, states, example, and source trail.
0 of 23 studies complete
Start this family →Learn the shared task and the core interaction choices.
A user is about to start one named service, transaction, booking, application, check, request, or registration.
A page needs to display a known set of tasks with status and links to start or resume them.
New users need orientation, setup, personalization, or instruction before the regular interface can deliver value.
Users reserve an offered appointment, service, class, room, resource, seat, table, pickup window, or visit.
A team or individual repeatedly reviews many independently queued items.
Choose a specialized form for the context and follow its complete behavior.
Users need to save and resume drafts, regularly update their data, manage records, check ongoing status, collaborate, or protect repeated access.
Users need to create a visible profile for collaboration, community, directory, marketplace, public contribution, support, or social interaction.
Users already have an account or profile and need guided help to complete, review, enrich, or update it.
Users need to access an existing account or protected destination.
Users have submitted credentials or authenticator output and need a safe verification result.
Users need to recover an account because the existing password is forgotten, suspected compromised, or unusable.
A sign-in, new device, risk signal, or sensitive action requires proof beyond the primary credential.
A user must prove access to a mailbox before account activation, invitation acceptance, recovery eligibility, or sensitive notifications.
A captured phone number must be proven reachable before activation, contact-route reliance, recovery eligibility, phone-number change, or a sensitive action continues.
A user is ready to purchase selected items, services, tickets, subscriptions, donations, or orderable options.
The user must pay a known fee, invoice, balance, application charge, renewal, subscription, donation, deposit, or service amount.
Users coordinate time across people, resources, calendars, availability, or recurrence.
A transaction has several meaningful sections or tasks and progress is saved.
A user must set, change, or clear who is accountable for a work item.
A submitted request needs authorized approval before a deployment, purchase, access grant, publication, content change, policy exception, financial action, or workflow step can proceed.
Users need to make content, products, pages, releases, site changes, campaigns, or configuration visible to an audience.
Users need to inspect and change persistent app, account, workspace, privacy, notification, display, integration, device, or system behavior.
A view, editor, canvas, media surface, table, or selection needs repeated related commands close to the work area.
Try fewer words, clear the filter, or search across all pattern families.
Search all patterns