Great design doesn't start with a mockup. It starts with listening. Before I open Figma, I immerse myself in your users, your business, and the problem you're solving. Beautiful interfaces that confuse users aren't beautiful at all.
Not because the designers lack skills, but because they skip the work that makes the skill matter.
Standard Desinger
Most design engagements follow the same path: gather requirements, sketch wireframes, polish screens, hand off files. The deliverable looks good. It rarely works well. That's because it treats symptoms, not causes.
My Differences
My approach starts with diagnosis, not deliverables. Before I design anything, I need to understand the system as it actually operates. The user mental models, the business constraints, the technical realities. Only then can I design something that fits.
The Results
When I understand what's actually broken, I can build something that fixes it. That's the difference between a pretty mockup and a product that changes how people work, engage, and feel. Design that moves metrics, not just eyeballs.
My 4Ds Framework
Every project follows the same arc. I uncover the truth, frame the opportunity, then craft the solution. No phase is skipped, no assumption goes untested.
01
Discovery
Week 1-2
I immerse myself in your world. Stakeholder interviews, user research, competitive analysis, and technical constraints. I map the ecosystem as it actually exists, not as it was designed. This is where I find the real problem — which is rarely the one written in the brief.
Interviews
User research
Competitive audit
Problem framing
02
Define
Week 2-3
Synthesis and strategy. I distill research into insights, map user journeys, and identify the highest-leverage opportunities. We align on what success looks like — not just visually, but behaviorally. This is where we decide what to build and, just as importantly, what not to build.
Journey maps
Insight synthesis
Design principles
Success metrics
03
Design
Week 3-6
This is where the interface emerges. I work in rapid cycles — low-fi wireframes to test flow, mid-fi to validate structure, hi-fi to refine the visual language. Every decision is grounded in the research. Every pixel serves the user's goal. I design in the browser when possible, so we see the real thing, not a static picture.
Wireframes
Prototypes
Visual design
Design system
Interaction specs
04
Deliver
Week 6-8
Handoff isn't a file drop. I work alongside engineering through implementation, reviewing every screen, catching every edge case. Then we test with real users, measure against our success metrics, and iterate. The launch isn't the end — it's the beginning of learning what actually works.
Design handoff
QA review
Usability testing
Iteration
Launch support
What I believe
These aren't just words on a page. They're the constraints I design within, the tradeoffs I make, the decisions I defend.
Clarity over cleverness
A clever interface that confuses users is a failed interface. I optimize for understanding first, delight second. The best design is the one users don't notice — because it just works.
Evidence over opinion
Design decisions should be defensible. I ground every choice in research, data, or established heuristic. When we disagree, we test. When we can't test, we trace back to the user need.
Systems over screens
I don't design pages. I design systems. Components, patterns, and rules that scale. A strong design system means your product stays coherent as it grows, and your team ships faster.
Collaboration over handoff
Design doesn't happen in a silo. I work with engineers, PMs, and stakeholders throughout — not just at the beginning and end. The best solutions emerge from cross-functional thinking.
Sound like a fit?
If this approach resonates, I'd love to hear about your project. Let's explore whether we're the right match.
