Systems & Design Thinking: Hospitality & Restaurant Module Revision

Vocabulary practice flashcards covering systems thinking models, root cause analyses, stakeholder perspectives, journey mapping, research methodologies, ideation techniques, and prototyping strategies within hospitality and restaurant operations.

Iceberg Model

A systems thinking framework used to look beneath visible occurrences by analyzing four levels: events, patterns, structures, and mental models.

Events (Iceberg Model)

The visible level of the Iceberg Model representing what happened; addressing only this level treats symptoms rather than root causes.

Patterns (Iceberg Model)

The recurring trends and behaviors that repeat over time beneath visible events (e.g., long restaurant waits every weekend between 7 and 9 pm).

Structures (Iceberg Model)

The organizational rules, roles, operational schedules, layouts, and policies that shape and drive recurring patterns.

Mental Models (Iceberg Model)

The deeply held beliefs, values, and underlying assumptions that sit behind and sustain the entire system.

Ishikawa Diagram

A visual cause-and-effect tool (also known as a fishbone diagram) used to identify and map the potential root causes of a specific problem or effect.

Ishikawa Cause Categories

The six standard operational branches on a fishbone diagram: People, Process, Equipment, Materials, Environment, and Measurement.

Five Whys

An iterative questioning technique applied to each potential cause on a fishbone diagram to drill down to its underlying root cause.

SMART Problem Statement

A structured, objective problem description that is Specific, Measurable, Achievable, Relevant, and Time-bound, avoiding vague complaints or blame.

Primary Stakeholders

Individuals or groups who are directly affected by an operational problem and its eventual solution (e.g., guests, servers, chefs, kitchen porters).

Secondary Stakeholders

Individuals or entities affected indirectly by the problem, or who influence the outcome from outside daily service operations (e.g., suppliers, delivery partners, neighbors).

Key Stakeholders

Individuals or governing bodies holding significant decision-making power, authority, or control over resources (e.g., hotel owners, general managers, regulatory agencies).

Macro Perspective

The broad, external viewpoint focused on wider environmental factors, including regulations, the economy, cultural trends, and industry-wide forces.

Micro Perspective

The granular viewpoint focusing on individual daily human experiences and personal day-to-day interactions.

Meta Perspective

The viewpoint of how a stakeholder or organization believes other people perceive them—their perceived image or reputation in someone else's eyes.

Time Horizon Perspective

The stakeholder perspective examining tensions between immediate, short-term needs (this week/month) and enduring, long-term strategic goals (e.g., brand value over 5 years).

Explicit Perspective

Needs, feedback, or opinions openly spoken aloud or submitted in writing via reviews, surveys, and formal requests.

Tacit Perspective

Felt or experienced knowledge and emotions that stakeholders hold but rarely verbalize; typically uncovered through direct observation and asking probing questions.

Assumed Perspective

What an organization or designer guesses users want based on personal preconceptions rather than verified data.

Real Perspective

The genuine thoughts, feelings, and requirements that stakeholders actually have, established through empirical evidence and research.

System Map

A visual mapping tool that captures the big picture by identifying all the actors, groups, and locations inside a system and how they relate before process flows are drawn.

System Diagram

A diagram that maps out operational flows, illustrating how inputs, processes, outputs, and feedback loops move resources, goods, money, and information.

Influence Diagram

A cause-and-effect modeling tool that illustrates how variables positively ($+$, reinforcing) or negatively ($-$) impact one another to anticipate ripple effects.

Usability Test

A qualitative research method where researchers observe users attempting realistic tasks on an interface or physical collateral to identify design friction.

Card Sorting

A user research method in which participants organize topics into categories to inform the intuitive structuring of menus, signage, and digital layouts.

Diary Studies

A longitudinal research method where users self-record their daily experiences and reflections over days or weeks to capture behavioral shifts over time.

Journey Map

A visual timeline detailing every touchpoint in a user's experience, tracing their actions, mindsets, emotional fluctuations, and frustrations from start to end.

Zone A: The Lens

The topmost zone of a journey map that defines the scope by establishing the persona ('who'), the specific scenario ('what'), and user expectations.

Zone B: The Experience

The central section of a journey map displaying sequential stages, concrete actions, user thoughts, and an emotional curve across touchpoints.

Zone C: The Insights

The bottom section of a journey map translating findings into actionable pain points, design opportunities, and internal team ownership assignments.

Constraint

A limit or boundary (such as time, budget, staffing, space, or legal regulations) that frames a problem, focuses creativity, and keeps solutions realistic.

Low System Interoperability

A technical constraint where disparate systems (e.g., POS terminals, reservation engines, kitchen displays) cannot share data or communicate seamlessly.

Braindump

An ideation technique where participants independently and rapidly write down every idea they have in a set time before pooling them with the group.

Reverse Brainstorming

An ideation technique where teams explore how to deliberately make a problem worse, and then reverse each destructive concept into a viable solution.

Benchmarking

The process of comparing an organization's practices, services, or metrics against leading industry rivals to adopt proven operational methods.

Three Principles of Ideation

The foundational mindset rules for creative problem-solving: 1) Go beyond the obvious, 2) Explore untried ideas, and 3) Focus on users' outcomes.

Low-Fidelity Prototype

A quick, inexpensive, and rough physical or conceptual mock-up (e.g., paper sketches, cardboard models, sticky notes) used to test early ideas rapidly.

Medium-Fidelity Prototype

A prototype providing structured detail without final polish (e.g., wireframes, clickable screen flows) aimed at validating layout and navigation.

High-Fidelity Prototype

A highly realistic, functional model closely mirroring the visual appearance, materiality, and mechanics of the intended final product for pre-launch checks.

Throwaway Prototype

A temporary prototype built exclusively to test a specific hypothesis and rapidly discarded once the learning objective is achieved.

Skipping Steps (Pitfall)

A design thinking pitfall where practitioners jump straight to generating solutions before thoroughly researching, empathizing, and defining the problem.

Working in Isolation (Pitfall)

A design thinking pitfall where individuals design interventions in a silo without actively engaging end-users, operational staff, or cross-functional team members.