UI Design Workflow
Asynchronous Communication
I prioritize asynchronous workflows, which allows me to provide clear, documented updates rather than frequent meetings
5 reasons to work async
- More deep-focus time (fewer meetings, fewer context switches).
- Clearer requirements (written/recorded once, less misinterpretation)
- Works across time zones (progress continues while others are offline)
- Better decision trail (searchable history: why we chose X
- More inclusive collaboration (people can think and respond thoughtfully).
3 async tools for a UI designer
- Loom (or Screen Studio) — record short walkthroughs of flows + rationale.
- Clearer requirements (written/recorded once, less misinterpretation)
- Figma — comments, prototypes, and async design reviews in-context.
- Notion (or Confluence/Google Docs) — lightweight specs, decision logs, and handoff notes.
INTAKE & REQUIREMENT GATHERING
(Client → UI Designer)
WIREFRAMING &
INITIAL CONCEPT
(UI Designer → Client)
Tools
UI designer creates low-fidelity wireframes with clear annotations.
Uploads to Figma for client viewing and commenting.
Clients provide feedback asynchronously via Figma comments or a structured feedback form.
HIGH-FIDELITY DESIGN & PROTOTYPING
(UI Designer → Client)
TOOLS
ITERATIONS & FINAL APPROVAL
(Client → UI Designer)
Tools
Apply feedback, document changes, and record a
walkthrough video
(Loom) to explain updates.
Review and approve deliverables on your own schedule. I provide final designs in Figma for your feedback, with formal approvals tracked seamlessly via Jira, Trello, or your preferred project management tool.
DEVELOPER HANDOFF
(UI Designer → Developers)
TOOLS

