Summary: Hiring a UX Designer requires more than reviewing portfolios or asking generic interview questions. Strong candidates should show user-centered thinking, structured problem-solving, collaboration, data-informed decision-making, and clear communication. This practical guide helps interviewers evaluate UX and Product Designers more effectively, identify red flags, and make better hiring decisions with a more structured interview process.
When I listen to a case study presentation, the same question often comes to mind: Why? The more frequently this question arises, the more likely it is that the case study will fall short of its goal — because too many questions remain unanswered. One of the most common “why” questions relates to the use of modeling methods. Just as I often see gaps in planning across other areas of UX, this issue shows up here as well.
What criteria does a designer use to decide which modeling method to apply? Unfortunately, the answer is often disappointing: they choose based on what they know — not based on what would be optimal. I’d like to offer some guidance on how modeling methods are structured. This article doesn’t dive deeply into each model, but it provides a helpful overview to highlight why expanding our knowledge in this area is so important.
Effective product design models aspects of the real world — user behavior, system dynamics, and business context — to create solutions that are both usable and viable. To do this well, teams need modeling methods: structured approaches to represent human behavior, system function, and strategic value.
This article introduces modeling methods as a critical component of the design process and organizes them into three interrelated categories:
- UX and HCI Methods — Represent user behavior and cognitive processes.
- System Methods — Describe the technical and interaction structure of the system.
- Strategic Methods — Align design decisions with business, market, and service ecosystems.
We will explore what these methods are, why they are important, how they fit into the design process, and how to choose the right one based on context.
What Are Modeling Methods?
Modeling methods are tools used to represent different dimensions of a design problem. They help designers and cross-functional teams explore, evaluate, and communicate ideas about how people interact with products and systems. These representations may be visual, narrative, diagrammatic, or conceptual. Some modeling methods, like Journey Maps or Use Cases, span multiple phases and purposes depending on the project context. The key is in how they’re framed and used at each stage.
Rather than serving as static documentation, modeling methods are working artifacts that evolve with the design process. They clarify assumptions, foster collaboration, and surface critical decisions early — before they become expensive mistakes.
Why Are They Important?
Modeling methods serve multiple purposes:
Clarify Complexity: Modeling methods help make complex problems easier to understand. They break down user experiences, systems, or tasks into smaller parts so teams can focus on what matters most and solve problems more clearly.
Align Teams: They also help everyone on a team stay on the same page. Designers, engineers, product managers, and business leaders often speak different “languages,” and models give them a shared way to talk about ideas, challenges, and solutions.
Guide Design Decisions: These methods also support better design decisions. By turning abstract ideas into something more visual or concrete, teams can explore options, test ideas, and decide what works best based on real understanding — not just guesswork.
Support Evaluation and Risk Management: Modeling is useful for spotting problems early, too. It can reveal confusion in a user flow, gaps in the experience, or risks that could lead to user frustration or technical issues later on.
Communicate with Stakeholders: Finally, models are great tools for sharing your work with others. Whether you’re talking to developers, stakeholders, or executives, using the right model helps you explain what you’re building, why it matters, and how it works in a way that makes sense to them.
Integrating Modeling Methods into the Design Process
Modeling methods are used throughout the design process, from early research to final delivery:
- Discovery Phase: Capture insights, user motivations, pain points, and mental models.
- Definition and Ideation Phase: Envision future states, explore task and interaction flows.
- Design and Prototyping Phase: Refine functionality, interactions, and edge cases.
- Delivery and Communication Phase: Translate design intent for developers and stakeholders.
The appropriate method depends on the design stage, the nature of the problem (behavioral, technical, or strategic), the audience (designers, developers, executives), and the project goal (ideation, validation, communication, documentation).
Choosing the Right Modeling Tool
Choosing the right modeling tool is important because it helps teams understand problems clearly, find better solutions, and work together more effectively. Each tool has a different purpose — some help you learn about user needs, others show how a system should work, and some are used to plan strategy.Using the wrong tool at the wrong time can mislead teams and create confusion. For instance, applying a technical model too early may obscure user needs, while skipping behavioral tools can overlook critical insights.
On the other hand, skipping tools that focus on user behavior might cause you to miss important problems in the experience. The right modeling method helps you focus on what matters most at each step — like learning about users in the early stages, designing how things work in the middle, or sharing plans with stakeholders later on. It makes communication clearer, decisions easier, and helps avoid mistakes by giving structure to your thinking.
Selecting the right modeling method depends on:
- Stage of the design process
- Nature of the problem (behavioral vs. technical vs. strategic)
- Audience (design team, engineers, stakeholders, leadership)
- Project goals (ideation, validation, alignment, documentation)
For example:
- In early discovery: empathy maps, JTBD, and problem scenarios help define direction.
- In mid-design: journey maps, task flows, and use cases help detail functionality.
- In strategic conversations: service blueprints and opportunity mapping frame business alignment.
Categories of Modeling Methods
1. UX and HCI Methods (Design Scenarios)
These methods focus on how users perceive, think, feel, and act when interacting with a product. They emphasize cognition, goals, emotions, context, and tasks — often in the form of design scenarios or narrative models.
These are best used:
- Design Stage: Discovery and ideation (more about it under the methods)
- Problem Nature: Behavioral, experiential
- Audience: Designers, researchers, product teams
- Project Goals: Understanding users, generating ideas, validating experience quality
How to Choose the Right Scenario Type
Different scenario types align with different needs:
- Problem Scenarios — Reveal current issues and frustrations
- Goal-Based Scenarios — Focus on what the user wants to accomplish
- Activity Scenarios — Highlight new behaviors enabled by the solution
- Interaction Scenarios — Dive into task sequences and UI interaction
- Full Task Scenarios — Detailed walk-throughs of task completion
- Information Scenarios — Reflect how users interpret and use information
But scenarios are just one of many modeling methods. Depending on the complexity, maturity, and purpose of your design work, you may need to augment or replace scenarios with other modeling techniques. Below is a structured framework.
Methods
- Design Scenarios — Narrative representations of use in context.
Used to imagine and explore use cases, empathize with users, and evaluate design ideas.
→ Aligned with: Goal-Based, Activity, and Problem Scenarios — depending on whether the focus is on user intent, new behavior, or existing pain points.
→ Design phase: Ideation and early concept development - Personas — Fictional profiles representing user segments.
Useful for aligning on user needs, goals, and behaviors early in the process.
→ Aligned with: Goal-Based Scenarios — by defining motivations and intentions behind behavior.
→ Design phase: Research synthesis and problem definition - Journey Maps — Visual timelines of the user’s experience across touchpoints and emotions.
Ideal for identifying pain points, opportunity areas, and emotional context.
→ Aligned with: Problem and Activity Scenarios — uncovering pain points and highlighting desired future-state behaviors.
→ Design phase: Discovery and experience diagnosis - User Flows — Step-by-step user actions for completing a task.
Effective for designing and validating interaction logic and efficiency.
→ Aligned with: Interaction and Full Task Scenarios — focused on task-level flows and efficiency.
→ Design phase: Interaction design and wireframing - Walkthrough Scenarios — Detailed step-by-step walkthroughs of product use.
Suitable for usability evaluations or internal reviews of key flows.
→ Aligned with: Full Task Scenarios — validating full flows in context.
→ Design phase: Usability testing and design iteration - Mental Model Maps — Diagrams of how users understand systems and tasks.
Helpful in aligning design to existing cognitive frameworks.
→ Aligned with: Information Scenarios — reflecting users’ internal understanding and structure.
→ Design phase: Research analysis and structural design - Empathy Maps — Visual tools to explore users’ thoughts, feelings, actions, and needs.
Ideal in early research synthesis and team alignment.
→ Aligned with: Problem Scenarios — uncovering emotional needs and frustrations.
→ Design phase: Early research and stakeholder alignment - Storyboards — Sequential visual stories representing use moments.
Powerful in design presentations and concept testing.
→ Aligned with: Activity and Goal-Based Scenarios — illustrating future behaviors or desired outcomes.
→ Design phase: Ideation, prototyping, and stakeholder communication - Card Sorting — A method for organizing content based on user logic.
Often used in information architecture or navigation structure design.
→ Aligned with: Information Scenarios — revealing how users classify and relate content.
→ Design phase: IA design and structural prototyping
2. System Methods
These methods define the logic and structure of a system — its components, interactions, and internal workflows. They are critical for technical accuracy, development planning, and implementation.
These are best used:
- Design Stage: Mid-design and prototyping
- Problem Nature: Functional, structural, technical
- Audience: Developers, product managers, architects
- Project Goals: Clarify system logic, support implementation, define scope
Methods
- Use Cases — Descriptions of interactions between an actor (user/system) and the system.
Used to define functional requirements and clarify what the system must do. - Use Case Diagrams — UML-based visuals showing actors and their interactions with system features.
Ideal for system design discussions and communicating scope with developers. - Interaction Models — Visual or narrative models of user-system interaction steps.
Useful for designing interface behaviors and edge-case handling. - Information Architecture — Structuring of content, categories, and labeling within a system.
Critical for content-heavy applications and digital navigation. - Wireframes and flows — Screen-level wireframes combined with flow connections.
Used in early UI prototyping and interaction testing. - System Architecture Models — Represent technical components and their relationships.
Important for development planning and systems integration.
3. Strategic Methods
These methods link product decisions to broader service ecosystems, market conditions, and long-term value creation. They support framing, prioritization, and high-level alignment.
These are best used:
- Design Stage: Discovery and definition
- Problem Nature: Strategic, market-driven, organizational
- Audience: Executives, stakeholders, business strategists
- Project Goals: Define product strategy, map services, identify market opportunities
Methods
- Jobs To Be Done (JTBD) — Framework for identifying user goals in terms of progress they want to make.
Helps prioritize features based on real user motivations. - Service Blueprints — Maps that connect front-stage user experience with backstage systems and processes.
Used to design end-to-end services and align internal teams. - Business Model Canvas — Visual tool to describe value proposition, customer segments, revenue, and delivery.
Supports early product planning and business alignment. - Experience Maps — Macro-level journey maps across personas, channels, and time.
Useful for aligning teams on long-term experience strategy. - Design Principles — Guiding statements to inform product decision-making.
Valuable for driving consistency across features and teams. - Risk Analysis — Identification and mapping of potential usability, adoption, or business risks.
Useful for anticipating failure points before launch. - Opportunity Mapping — Highlights gaps between user needs and current product capabilities.
Helps prioritize roadmap based on user-centric value.
Categories Based on Stage and Focus
In Early Discovery
- Use Empathy Maps to synthesize qualitative research and bring emotional context to design discussions.
- Apply Jobs to Be Done (JTBD) to frame user motivations and desired outcomes independently of solutions.
- Create Problem Scenarios to clarify current-state frustrations and environmental challenges.
- Introduce Personas to build shared understanding of key user archetypes.
In Mid-Design
- Use Journey Maps to trace the user’s end-to-end experience and identify key friction points and design opportunities.
- Apply Task Flows to break down functional interactions and evaluate task efficiency.
- Develop Use Cases to define system behavior from a user perspective and guide implementation.
- Create Interaction or Full Task Scenarios to walk through specific use contexts and validate flow logic.
In Concept Communication and Evaluation
- Use Storyboards to present key usage moments visually, especially in stakeholder presentations or concept reviews.
- Apply Walkthrough Scenarios to simulate real usage and identify usability issues during reviews and tests.
- Conduct Card Sorting to refine content groupings and inform navigation design.
In System and Structural Design
- Use Mental Model Maps to align system logic with how users conceptualize workflows and content.
- Apply Use Case Diagrams to model system functions, actors, and dependencies from a technical standpoint.
- Build Journey Maps and Information Scenarios to improve clarity in how users process and access information.
In Strategic Framing and Cross-Team Alignment
- Use Service Blueprints to map both user interactions and back-end processes, ideal for aligning service delivery with business operations.
- Apply Opportunity Mapping or Value Stream Mapping to identify leverage points, inefficiencies, or areas for investment.
- Develop Activity Scenarios to visualize new behavioral possibilities introduced by the solution.
- Facilitate discussions using Future-State or Visionary Scenarios — narratives exploring possible long-term outcomes aligned with business goals.
Conclusion
These mappings are not fixed rules but guidelines. Methods often overlap and evolve as the design matures. Modeling methods are not auxiliary tools — they are central to thoughtful, evidence-based design. Whether crafting a feature, scaling a system, or aligning cross-functional teams, modeling brings clarity, direction, and confidence to complex product challenges.
By categorizing modeling methods into UX and HCI, System, and Strategic groups, teams can more effectively choose the right tool for the job — depending on the design stage, nature of the problem, intended audience, and desired outcome.
Design scenarios remain a foundational tool in UX, especially when modeling behavior, context, and user goals. But a mature design practice leverages a broader modeling toolkit to inform decisions, align vision, and create better user experiences — strategically and systemically.
