How I Work

Systematic rigor applied to human-centered design.

A structured approach bridging human-centered design with rigorous systems architecture. This process prioritizes data modeling, structural alignment, and scalability before applying interface solutions, ensuring complex workflows translate into intuitive, buildable products.

Phase 1: Problem Definition & Systems Alignment

Before defining the interface, the underlying structures, data models, and business logic must be understood and mapped.

• Define the Core Challenge: Isolate the true structural problem by balancing stakeholder objectives with the realities of end-user constraints.
• Establish Product Strategy: Utilize frameworks to capture assumptions, constraints, and hypotheses, ensuring alignment across all cross-functional teams.
• Model the System: Map the underlying data relationships, constraints, and system logic. Designing the data model before the interface prevents rigid structures from breaking under the weight of real-world use.

Phase 2: User Research & Synthesis

Research is focused on uncovering the why behind user behaviors, moving beyond surface-level feature requests to understand deeply ingrained workflows and mental models.

• Contextual Inquiry: Conduct targeted interviews to understand real-world workflows, environmental constraints, and core user motivations.
• Synthesize Context: Develop artifacts like Customer Profiles and Value Proposition Canvases to organize complex qualitative data into actionable insights.
• Prioritize Function over Friction: Utilize structured matrices to evaluate user needs, clearly separating critical structural pain points from easily resolved surface-level annoyances.

A Value Proposition Canvas mapped against a real-world workflow diagram. This visual illustrates how scattered qualitative user pains and gains are systematically grouped and connected to specific functional requirements in the product architecture.

Phase 3: System & Design Strategy

This phase translates the structural constraints and synthesized research into a coherent spatial and navigational logic.

• Establish Interaction Principles: Define the foundational rules for how the system will behave, grounded in natural human behavior, progressive disclosure, and contextual memory.
• Information Architecture: Map comprehensive user journeys and clear data hierarchies to simplify complex, high-density information.
• Wireframing & Flow: Translate the structural models into low-to-mid fidelity wireframes. Focus heavily on state changes, navigation pathways, and interaction rules rather than visual polish.

A multi-layered Information Architecture and State Transition map. This diagram visually separates the persistent navigation layer from dynamic data states, demonstrating how the underlying data model flexes across different user scenarios and screen sizes.

Phase 4: Validation & Refinement

Design decisions must survive contact with reality. This phase aggressively tests interactions against constraints, edge cases, and user expectations.

• Prototype Usability: Test interactive prototypes to evaluate cognitive load and identify points of workflow friction.
• Stress-Test Constraints: Validate interactions against real-world limitations, including physical ergonomics, device variability, and complex overlapping tasks.
• Error Prevention (Poka-yoke): Iterate the design to proactively prevent user errors through clear progress states, built-in validation checks, and simplified data formats.

Phase 5: Documentation & Developer Handoff

A design is only successful if it can be built and scaled cleanly. This phase ensures airtight alignment between design intent and technical execution.

• Scalable Design Systems: Develop modular systems utilizing atomic design principles, semantic design tokens, and context-aware components.
• Comprehensive Documentation: Create exhaustive handoff materials featuring fully annotated behaviors, logic rules, tap targets, and screen states to eliminate developer guesswork.
• Technical Collaboration: Work directly with cross-functional and offshore development teams, participating in QA and ensuring accurate, frictionless deployment of the final product.