Skip the research and the visual layer just paints over the problem. I work from evidence, not from opinion or aesthetics.
Interviews, usability testing, analytics. Decisions trace back to something real, not a hunch.
Information architecture, flows, journeys. The bones of the product, sorted before the surface.
Interactive prototypes in front of real users before a single line of production code is written.
A prioritised list of what to fix and why, ranked by impact. No 90-page report that nobody acts on.
Interviews, surveys, usability testing, analytics review, competitor analysis. Understanding the people who use your product before designing anything.
Site maps, content hierarchy, navigation design, card sorting. Structuring content so people find what they need without thinking about it.
Task flows, user journey maps, service blueprints. Mapping every step a user takes and identifying where things break down.
Low-fidelity layouts, content prioritisation, responsive wireframes. The structural blueprint before any visual design begins.
Interactive prototypes, click-through demos, user testing prototypes. Making ideas tangible and testable before building anything.
Heuristic evaluation, accessibility review, conversion analysis. A thorough assessment of your existing product with a prioritised fix list.
User personas, use cases, jobs-to-be-done. Giving your team a shared understanding of who you are designing for.
Content audit, content hierarchy, content planning. Making sure the right content is in the right place at the right time.
User interviews, usability testing, analytics review, competitor analysis. Findings come back as a short, opinionated read with recommendations, not a slide deck nobody opens.
Lo-fi structure first. Then interactive prototypes you can actually click through. Tested with real users before any visual design or code is touched.
A heuristic and accessibility review of your current product. You leave with a ranked list of what to fix, what to leave, and what to revisit. Plain language, no jargon.
UX and product design for Tata Communications' global eSIM platform, from provisioning tools to a branded self-service store.
End-to-end UX for an Employer of Record platform helping SMBs scale cost-effectively in the Philippines.
UX (user experience) is about how something works: the structure, flows, and logic. UI (user interface) is about how it looks: the visual design, colours, and typography. I do both, but they're different disciplines that happen at different stages.
Yes. Research is where every good UX project starts. Interviews, surveys, usability testing, analytics review, and competitor analysis. The depth depends on the project scope and budget.
Absolutely. A UX audit evaluates your current product against usability heuristics, accessibility standards, and conversion best practices. You get a prioritised report of what to fix and why.
Interactive prototypes tested with real users, either moderated (I watch and ask questions) or unmoderated (remote testing at scale). I can also run A/B tests on live products.
Figma for wireframes and prototypes, Miro or FigJam for workshops and mapping, and various research tools depending on the project. Everything is shared and collaborative.
Show me where people get stuck and I'll show you how I'd fix it.
