Research, information architecture, and user flows — worked out first, so the design that follows has somewhere solid to stand.
"Assumptions are where projects quietly go wrong."— why discovery comes first
Most sites underperform for reasons no amount of visual polish can fix — the wrong structure, unclear priorities, a path that asks visitors to work too hard. I find those problems early, while they're still cheap to solve. That starts with real questions about your customers and what they're actually trying to do when they arrive.
How pages relate, what comes first, where a visitor goes next — these are choices, and they deserve to be made deliberately. I map the architecture and the key journeys before a single screen is designed.
Real questions about your customers, before any assumptions get baked in.
How pages relate and what comes first — decided on purpose, not by default.
The key paths a visitor takes, worked out before a screen is designed.
Understanding your customers and what they need to accomplish.
Mapping how the site is organized and how pages relate.
The key journeys, laid out before design begins.
Tell me about your business and what you're hoping changes.