My Design Process
I've managed design work using Notion, Google Drive, Miro, and Figma. Sometimes, the easiest solution was just sharing links in Slack, since that's where the team spent most of their time. My approach is straightforward: the best tool is the one the team feels comfortable with and that keeps everyone on the same page. I believe tools should support the process, not dictate it.
[ 01 ]
Research & Planning
When a project calls for it, I begin by gathering everything in one place. This includes competitive analysis, user insights, secondary research, and sprint timelines.
For tight deadlines I map deliverables against dates so nothing slips.
[ 02 ]
Lo-fi & Drafts
I start rough on purpose
Example of sections organized in Figma
[ 03 ]
Mid-fi to Hi-fi
Wireframes and final designs live in Figma, linked from wherever the team's source of truth is.
I leave comments directly in Figma to explain my decisions as I go. When a design needs more context, such as how it works or what triggers certain actions, I add sticky-note annotations on the sides of the frames.
[ 04 ]
Prototyping
When time allows I always build a working prototype
Example of working prototype from Lookr
[ 05 ]
Handoff
When the build goes live, I review it against my designs. I prefer to do this with the PM so we can answer questions right away rather than wait for another development cycle. Design continues even after handoff.
Example of fast handoff annotations for engineers from Nkomar
[ 06 ]
QA & Iteration
When the build goes live I check it against my designs — ideally with the PM together so questions get resolved immediately, not after another dev cycle. Design doesn't stop at handoff.
[
WORKS
]
