Loading learning content…
Loading learning content…
Design CUA workflows for complex multi-step web tasks — booking, procurement, onboarding, and end-to-end process automation.
Read through the lesson, mark it complete when the concept is clear, then move to the next lesson in the sequence or jump back to the module map.
Simple tasks (fill one form, extract one page) are where CUAs are most reliable. Complexity compounds errors: each step that can fail creates exponential failure paths in a 10-step workflow.
The discipline of multi-step CUA design is minimizing failure points and building recovery logic for each one.
Break complex tasks into explicit phases:
Task: Onboard a new vendor in our procurement system
Phase 1: Vendor research
Phase 2: System entry
Phase 3: Document upload
Phase 4: Approval routing
Each phase is a checkpoint. If Phase 2 fails, the agent hasn't wasted time on Phases 3 and 4.
For long workflows, instruct the agent to save state:
"After completing each phase, output a status update in this format: Phase [N]: [COMPLETE/FAILED] Summary: [what was done or what failed] Data collected: [any IDs, URLs, or data gathered]"
Some steps can be parallelized (if you have multiple agent instances):
Sequential requirement: must log in before accessing the portal.
Parallel opportunity: research three vendors simultaneously in three agent instances, then enter them sequentially.
"If a page takes more than 30 seconds to load, take a screenshot, note the URL and action attempted, and try refreshing once. If it still doesn't load after refresh, mark this step as failed and continue."