Revolutionizing
Urban Parking.

Every great product starts with the right questions. I sit down with stakeholders, product managers, and business leads to understand not just what we're building — but why. I document functional requirements, technical constraints, business goals, and success metrics before a wireframe is drawn. This phase eliminates assumption-driven design and aligns the team from day one.

With requirements in hand, I work with PMs and engineering to map a realistic design timeline. This includes research sprints, design iterations, review cycles, and handoff windows. A clear timeline keeps everyone accountable and prevents design from being squeezed at the end of a sprint. I build in buffer for feedback and pivots.

I conduct user interviews, contextual inquiries, and usability studies to deeply understand the people we're designing for. I synthesize findings into actionable insights — not just data dumps. Every design decision that follows is anchored in real user behavior, not assumptions. Research isn't a phase; it's a continuous practice throughout the project.

I translate research findings and business goals into clear UX objectives. These become the north star for all design decisions. I define the primary user tasks, the critical paths, and the key moments that make or break the experience. Every stakeholder reviews and signs off on these objectives before design work begins.

I map the complete end-to-end user journey — from first encounter to achieved goal. Journey maps reveal emotional highs and lows, pain points, and opportunity areas. They create empathy across the entire team and inform every design decision that follows. They also surface where users drop off — and why.

I convert research insights and journey maps into well-defined user stories. These bridge the gap between UX intent and engineering implementation. Each story captures who the user is, what they need, and why it matters. Written in plain language, user stories become a shared language between design, product, and engineering.

From lo-fi sketches to high-fidelity mockups, this is where ideas become visual. I start with structure — information architecture, layout, hierarchy — then layer in visual design. I explore multiple directions before converging. Every mockup is grounded in the research and objectives defined earlier, not personal aesthetic preference.

Interactive prototypes bring designs to life before a single line of code is written. I build click-through prototypes in Figma that simulate real interactions — transitions, states, micro-animations. These are used for stakeholder presentations, usability testing, and engineering reference. Prototypes catch issues early when changes are still cheap.

A clean handoff is as important as the design itself. I prepare detailed specs, redlines, and component documentation for engineers. I stay engaged during development — reviewing builds, flagging deviations, and ensuring the implemented experience matches the design intent. QA isn't just bug checking; it's experience validation.

Launch is not the finish line — it's the starting gun. I monitor post-launch analytics, gather user feedback, and track performance against the success metrics defined at the start. Insights from real usage feed directly back into the next design iteration. Great products are never done; they evolve with their users.