Understanding and Conceptualizing Interaction (Part 1)

The Problem Space

The Problem Space refers to the set of issues, needs, goals, and constraints that motivate the development of a system.

Before proposing a solution, designers must define the problem space by answering critical questions:

  • Creation & Audience: What are we trying to create, and for whom?
  • Assumptions: What assumptions are being made about user goals and behaviors?
  • Effectiveness: Will the solution achieve goals within the specific constraints of the context?
  • Integration: Are there existing systems or workarounds that the new design should improve upon?

Framework for Analyzing the Problem Space

There is a structured framework for critically examining the problem space and uncovering hidden assumptions.

Before building, designers must understand the current landscape of the user’s struggle. This includes identifying existing limitations. Root Cause Analysis can be used to determine the underlying cause of these problems.

Because a system doesn’t exist in a vacuum, designers must consider how it fits into the user’s existing world. They should consider Workflow Integration, Task Efficiency, and how it enhances the user experience.

This framework promotes Reflective Thinking and design Alignment to real-world needs and constraints.

Transitioning from Problem Space to Design Space

While the Problem Space defines the “What” and “Why,” the Design Space explores the “How”.

  • Problem Space: Focuses on users, their tasks, goals, and existing constraints.

  • Design Space: The realm of possible solutions, interface types, and system behaviors.

To move into the design space, designers must balance 4 pillars:

  • Translation

  • Identification

  • Exploration

  • Alignment

The Conceptual Model

The conceptual model is a high-level description of how a system is organized and operates. It is done to provide a simplified, understandable representation of complex system logic. There are 3 components of a conceptual model

  • User Actions
  • System Responses
  • Interface Representation

The primary goal of the conceptual model is to ensure the user’s mental model matches the system reality. If the model is clear, the user isn’t surprised by the system’s behavior. This reduces errors and mistakes in the system usage.

System Support, Interface Metaphors, and Interaction Styles

The system must guide the user through the process using familiar concepts. Two techniques are:

  • System Support: Providing the right functionality to the user at the right time
  • Interface Metaphors: This includes proactive guidance and clear feedback

Designers must select the “language” of the interaction based on the user’s context and needs. There are 3 common interaction styles:

  • Direct Manipulation: Dragging an icon to the trash (immediate and visual).
  • Conversational: Asking a voice assistant to set an alarm (natural language).
  • Menu-Based: Selecting options from a structured list (low memory load).