I've watched someone spend 20 minutes trying to find a simple contact form, seen brilliant researchers give up on data they desperately needed, and witnessed teams abandon tools that could have transformed their work—all because the interface got in the way. I design experiences that feel less like using software and more like having a conversation with someone who actually gets what you're trying to do.
Start a Conversation
My approach centers on one key question: How will the learner best understand the story of this product? I've built VR training simulations for technical teams and designed web navigation for enterprise platforms serving thousands of users. In every case, I focus on making the story flow naturally—no interface distractions, no hunting for what comes next.
Creating interactive courseware and LMS interfaces that engage learners through adaptive paths, gamification, and progress tracking that shows not just completion, but competency—across all learning levels.
Designing VR, AR, and game-based training environments where complex skills—like equipment maintenance or emergency procedures—are learned through natural interaction and spatial interfaces, not text-heavy tutorials.
Designing websites and corporate platforms where users can find what they need in 2-3 clicks, content adapts to their context, and mobile experiences don't sacrifice functionality for simplicity.
Building data-driven platforms where multiple teams collaborate effectively—turning overwhelming dashboards into role-based views that show each user only what they need to act on, when they need it.
These principles guide every design decision: choosing what to show first, deciding when to interrupt a user, balancing power-user efficiency with first-time learnability.
Users are interrupted, multitasking, and often working with incomplete information. I design for scenarios like a researcher who's been in meetings all day and has 10 minutes to find a report—not the focused user in a usability lab. This means prioritizing search over navigation, defaults over configuration, and recovery over prevention.
Making complex systems feel learnable through progressive disclosure—showing 3 primary actions up front, hiding 20 advanced features behind a single "More" menu. Clear visual hierarchy means users can scan a page in 5 seconds and know where to start.
Building confidence through reliable interactions:
• Buttons that look the same do the same thing
• Destructive actions always ask for confirmation
• Error messages explain what went wrong and how to fix it, not just "Error 400"
Navigation confusion, buried features, unclear information architecture
Information overload, cluttered interfaces, too many choices at once
Inconsistent behavior, unclear feedback, lack of error prevention
Sometimes the most powerful story is told in the space between "before" and "after." These transformations show the impact of information hierarchy, progressive disclosure, and designing for scanning instead of reading.
Great design doesn't happen in isolation—it emerges from a careful dance between curiosity and craft, between listening and creating. Here's how I move from problem to solution, balancing user needs with business constraints and technical feasibility.
Through stakeholder interviews and user observations, I identify the 3-5 pain points that will drive design priorities—not every complaint, just the ones blocking the most users.
I map user journeys to find where they hesitate, backtrack, or give up entirely. This reveals not just what users do, but where the interface is forcing workarounds.
Insights become wireframes and prototypes. Every interaction is chosen with intention—I iterate until the right path is obvious, not just possible.
Through testing, I validate assumptions and identify what needs to be redesigned. If users can't find a feature, it's a design problem—not a training problem.
Great design is never finished—it evolves. Post-launch, I track analytics, review support tickets, and prioritize improvements based on what's blocking users most. Iteration means fixing what's broken before adding what's new.
Whether your audience is navigating a website, exploring interactive media, or immersed in a game world, they're all trying to accomplish a task—and the interface is slowing them down. Let's figure out what's breaking down and fix it.