Nobody has ever praised an app for its navigation. The highest compliment an interface can earn is invisibility — the user gets what they came for and remembers the outcome, never the clicks. Getting there is not luck; it is a set of habits repeated on every project.
Start with the job, not the screen
Every design review at Quillmark opens with the same question: what is the user trying to finish? We write that job on the wall — “pay the electricity bill before Friday” beats “improve the payments module” every time. Screens designed around finished jobs need fewer explanations, fewer tooltips, and far fewer support tickets.
Map the journey before drawing a pixel
Journey mapping sounds like ceremony, but a single afternoon with sticky notes routinely exposes the same villains: duplicate steps, dead-end errors, and confirmations that confirm nothing. On the Lumen banking project, the map showed nine sections collapsing naturally into four — the redesign practically drew itself.
Test with five users, fix, repeat
You do not need a lab. Five users from the real audience, a clickable prototype, and thirty minutes each will surface the vast majority of problems. We test twice per project: once on rough flows to catch structural mistakes cheaply, and once on polished screens to catch wording and trust issues. Then we ship — and keep watching the analytics, because launch day is the start of the research, not the end.
Seamless is a discipline, not a style. Research the job, map the journey, test with real people, and the “intuitive” part follows on its own.
