How I simplify a workflow before designing the screen
By Rosario Meza
When I worked on a warehouse management system, I reviewed many requirements. Sometimes a requirement described both what the system needed to do and how the interface should work. When I saw a simpler way to meet the same requirement, I’d prototype it so we could walk through the task together. Those prototypes sometimes led stakeholders to revise the requirements.
Start with the Task
Write down what the person needs to accomplish in one sentence. In a warehouse count, an operator needs to record how many units are physically in a bin. From there, ask what the operator already knows, what the system can look up, and which decisions require someone’s judgment.

Separate the Rules from the Steps
A rule might say that every count must be tied to a bin and an item. A proposed workflow might ask the operator to enter both identifiers by hand. If scanning the bin opens an assigned count and scanning the item validates it, the same rule can be met with fewer opportunities for typing errors.
Before
- Search for the bin.
- Select the item from the list.
- Enter the quantity on a separate screen.
- Review the bin, item, and quantity, then submit.
After
- Scan the bin and item to open the assigned count.
- Enter the quantity and submit while the bin and item are still in view.
Keep a Path for Exceptions
Walk through a damaged barcode, a scan that points to the wrong bin, and a count of zero. For an unreadable barcode, offer a manual lookup. If the item doesn’t match the assignment, show which item the operator scanned and give them a way to rescan before saving anything. The everyday path can stay short while those recovery steps remain available when needed.

Prototype the Decisions Before Polishing the Screen
I’d start with just enough of the flow to test the key decisions. Can the operator recognize the right count? Can they correct a bad scan? Do they know the quantity was saved? A short walkthrough with the business analyst and engineering can reveal which assumptions need checking before the team spends time refining the interface.
Yes
Enter quantity and confirm it saved.
No
Show the mismatch and offer a rescan.
Try this with one workflow you’re designing. Mark every step where someone searches, types, confirms, or switches screens. Pick one step and ask what it protects. If you can meet the same need within an existing step, sketch that version and walk through both the everyday task and one exception.