Conceptual Models and User Interface Design

Chapter III: Understanding and Conceptualizing Interaction

•  This chapter aims to explain the problem space, conceptualizing interaction, conceptual models, and the use of interface metaphors.
•  It also outlines core interaction types, and introduces paradigms, visions, theories, models, and frameworks in interaction design.
•  Conceptualizing design is crucial for a design project, involving idea generation by defining what a proposed product will do, sometimes referred to as a proof of concept.

Objectives

•  Explain the meaning of the problem space.
•  Explain how to conceptualize interaction.
•  Define a conceptual model and how to develop one.
•  Discuss the role of interface metaphors in a conceptual model.
•  Outline core interaction types to develop a conceptual model.
•  Introduce interaction design paradigms, visions, theories, models, and frameworks.

Proof of Concept (POC)

•  A POC pertains to defining what the proposed product will do.
•  For example, a POC for a voice assistant for smart homes could involve voice commands, basic commands (e.g., "turn on the lights," "play music"), and simple visualizations (e.g., animations, text feedback).

Conceptualizing Design

•  Examining ambiguous notions and presumptions about a product or service's merits is crucial in establishing feasibility.
• Evaluating current tools, machinery, and technology to determine the practical development of the design.
• The efficiency and desirability of a product are equally significant aspects to be assessed during the conceptualization process.

Steps in Conceptualizing a Design

•  Formulate all possible presumptions/assertions concerning the new design.
•  Investigate the product's factual data, functionality, and limitations.
•  Outline how users will overcome these limitations.

Describing Complex Concepts

•  Articulate, or provide detailed explanations of multifaceted notions.
•  Illustrate the specifics of a design that may appear vague or unrealistic.
•  Assess whether the design is achievable with current technology and equipment.
•  Consider individual activities and interactions that might pose problems for the proposed design.
•  Iteratively devise strategies to enhance and develop designs.

Analyzing the Problem Space

•  After identifying issues, the project proceeds to analyze the problematic areas.
• A framework of questions can guide designers in analyzing problem spaces.

Example Questions for Analysis

•  Are there existing product or user experience complications? List them.
• What causes this problem to exist?
• How would you address the identified complications in your suggested design?
• How appropriate your designed solution is in relation to existing practices, and is it beneficial or detrimental in its impact to the user experience?

Conceptual Model Definition

•  A model is a simplified portrayal of a system or process, illustrating how it functions.
• In interaction design, conceptual models specifically articulate problem and design spaces.

Key Components of a Conceptual Model (according to Johnson and Henderson)

•  Metaphors and analogies that explain a product's application and function (e.g., a browsing metaphor for a web portal)
•  Concepts that are presented through the product, allowing manipulation and actions (e.g., saving, organizing, revisiting)
•  Interrelationships between the concepts (e.g., one object containing another)
• Mappings between the concepts and the user experience (e.g., navigating to a saved page)

Benefits of Conceptualizing

•  Aligning design teams through a common understanding on perception of the design model.
•  Encouraging a broad perspective during the early conceptualization stage to avoid narrow thinking.
•  Fostering consensus among all members of the design team.

Interaction Types

•  Instruction, conversation, manipulation, and exploration are essential components of the user experience of a product or application.
• Responding as an additional interaction component that initiates user interaction.

Interface Styles

•  Different approaches to interact with a product.
• Examples include command-line interfaces, graphical user interfaces, menu-based interaction, and voice input.

Paradigms

•  A community of researchers and designers' general approach to their work, encompassing shared ideas, values, and practices.
• Examples include the desktop paradigm and ubiquitous computing.

Visions

•  Future states that guide the design and development process, often presented figuratively (e.g., through narratives or movies).

Theories

• Well-founded descriptions of specific aspects or behaviors in a phenomenon (e.g., theory of information processing).

Frameworks

•  Sets of linked notions used to gain insight into a particular field or method (e.g., ethnographic studies).

Interface Metaphors

• Conceptualizing the actions of users, such as surfing the internet, instantiating conceptual models.
• Examples include the desktop metaphor and shopping cart concepts.

Benefits of Interface Metaphors

• Simplification of learning new systems.
• Enhancing understanding of underlying conceptual models.
• Enabling computers and applications to cater to a variety of users.

Problems with Interface Metaphors

• Potential conflicts with existing conventions
• Constraint on designer perspectives
• Users might only grasp the system using the metaphor
• Inadvertent adoption of poor features from existing designs.
• Restriction of design imagination

Examples of Core Interaction, Interface Metaphors and Conceptual Models

•  Online shopping experiences (e.g., using a cart metaphor).
• Everyday computer operations (e.g., desktop metaphor, web browsing).

Conclusion

• Conceptual models and interface metaphors provide the building blocks for creating user experiences.
• The ability to analyze complex concepts is crucial in the design process.
• Current designs may inherit poor aspects from existing designs, which can hinder the imaginative potential.