Name the current state
Make the distinction between missing, invalid, processing, and complete information explicit. Different states should not share an ambiguous message.
03 / Interaction & state design
Design the next step.
Especially when things go wrong.
An interaction is more than its happy path. Progress, incomplete information, errors, and recovery all need a clear response.
The design question
Can someone recover from an incomplete task without losing their work?
Offer an actionable recovery
Explain what needs attention and where to correct it. Preserve the valid information and keep the person in the context of their task.
Make the result visible
Show what changed and whether the workflow can continue. Where sensitive data is involved, permissions and traceability matter.
In practice / HRMS
A decision in context.
HR teams may receive incomplete salary details after an employee is already onboarded. The design provides a way to correct the existing record instead of repeating the entire onboarding journey.
Explore the project evidence
The details that matter
Make the reasoning reviewable.
| Situation | Response to design | Review question |
|---|---|---|
| Missing salary details | Update the existing employee record | Can HR continue without re-onboarding? |
| Invalid upload data | Identify the record and correction needed | Is the message specific enough to act on? |
| Payment not confirmed | Distinguish preparation from paid status | Can the team tell what still needs action? |
Next / Design, in practice