Systems & Design Thinking for Hospitality & Restaurant Management

Comprehensive vocabulary flashcards covering the systems and design thinking toolkit for hospitality and restaurant environments, including the Iceberg Model, Ishikawa diagrams, SMART statements, stakeholder perspectives, mapping tools, research methodologies, journey mapping, constraints, ideation, and prototyping.

Iceberg Model

A systems thinking framework that encourages looking beneath visible daily events to uncover recurring patterns, underlying systemic structures, and foundational mental models.

Events (Iceberg Model)

The visible level of the Iceberg Model representing immediate, observable occurrences and symptoms, addressed by asking: 'What happened?' (e.g., guests waiting $45\text{ minutes}$ for a table on Saturday night).

Patterns (Iceberg Model)

The hidden trends and recurring behaviors that happen repeatedly over time, investigated by asking: 'What trends repeat over time?' (e.g., long waits occurring every weekend between $7\text{ pm}$ and $9\text{ pm}$).

Structures (Iceberg Model)

The organizational rules, roles, policies, physical layouts, and systems that shape patterns, identified by asking: 'What rules, roles and layouts cause it?' (e.g., staff rosters, kitchen layout, booking systems, and table policies).

Mental Models (Iceberg Model)

The deeply held beliefs, values, and assumptions that underpin how a system operates, explored by asking: 'What assumptions sit behind the system?' (e.g., believing 'guests will wait for good food' or 'turnover matters more than comfort').

Ishikawa Diagram

A cause-and-effect tool (also called a fishbone diagram) used to systematically brainstorm, categorize, and identify the root causes of a specific problem or effect.

Ishikawa Cause Categories

The standard categories branching off the central spine of a fishbone diagram: People, Process, Equipment, Materials, Environment, and Measurement.

Ask 'Why?' 5 Times

An iterative root-cause technique used in an Ishikawa diagram to drill past superficial causes down to the fundamental root cause of an issue.

SMART Problem Statement

A structured problem statement that defines an operational challenge clearly without assigning blame, using five criteria: Specific, Measurable, Achievable, Relevant, and Time-bound.

Specific (SMART)

The problem statement component answering who is affected, what is wrong, and where the issue occurs.

Measurable (SMART)

The problem statement component that quantifies the size of the operational gap using concrete numbers or percentages.

Achievable (SMART)

The problem statement component confirming that the proposed improvement lies realistically within the team's control or influence.

Relevant (SMART)

The problem statement component ensuring that addressing the issue truly matters to guests, staff, or the business.

Time-bound (SMART)

The problem statement component that establishes a definite deadline or timeframe by which the metric must improve.

Primary Stakeholders

Individuals or groups who are directly affected by the problem and its potential solution (e.g., restaurant guests, servers, chefs, and kitchen porters).

Secondary Stakeholders

Parties who are affected indirectly or who influence outcomes from outside daily operations (e.g., suppliers, delivery partners, neighbours, and the local community).

Key Stakeholders

Individuals or entities possessing high authority, decision-making power, or control over critical resources (e.g., owners, general managers, head chefs, and regulatory bodies like SFA or NEA).

Internal Stakeholders

Stakeholders situated within the organization who carry out or manage service operations (e.g., owners, managers, chefs, servers, and housekeeping staff).

External Stakeholders

Stakeholders located outside the organization who interact with or regulate the business (e.g., guests, suppliers, regulatory bodies, delivery platforms, and the surrounding community).

Macro Perspective

The broad, external viewpoint examining how large-scale laws, economic shifts, industry trends, and cultural factors impact an organization.

Micro Perspective

The granular, day-to-day viewpoint focusing on individual human interactions, physical tasks, and immediate operational challenges.

Meta Perspective

The reflexive viewpoint concerning how an organization believes outside stakeholders perceive its reputation, identity, or service standard.

Time Horizon Perspective

A viewpoint contrasting immediate, short-term needs (days, weeks, or current season) against strategic, long-term aspirations (multi-year brand loyalty and reputation).

Explicit Perspective

Stakeholder needs, feedback, or complaints that are spoken out loud or submitted in writing (e.g., online reviews, survey comments, direct guest requests).

Tacit Perspective

Unspoken, intuitive feelings, habits, or workarounds recognized primarily through careful observation and inquiry rather than verbal expression.

Assumed Perspective

What managers or designers guess that users or staff want based solely on their own internal biases or preconceptions without verification.

Real Perspective

What stakeholders genuinely need, believe, and experience, substantiated through empirical research, user interviews, and observation.

System Map

A high-level systems tool used to identify and visually place all actors, groups, physical places, and elements to see who and what exists inside a system before drawing flow lines.

System Diagram

A systems tool using connected lines to illustrate the movement of goods, capital, information, inputs, processes, outputs, and feedback loops across actors.

Influence Diagram

A systems tool utilizing directional arrows labeled with positive ($+$, reinforcing) or negative ($-$) signs to map cause-and-effect relationships and predict ripple effects.

Interviews (Research Method)

One-on-one qualitative discussions designed to uncover personal motivations, emotional drivers, underlying reasons, and detailed guest or staff stories.

Observation (Research Method)

A field research technique involving watching real behaviors in real time or shadowing workers to capture what people actually do rather than what they report doing.

Usability Test

A research method where participants are observed while completing realistic tasks on an interface, digital tool, or physical menu to detect friction points and confusion.

Card Sorting

A generative research technique where participants organize topic cards into logical categories to assist in structuring menus, signage, and user interfaces.

Diary Studies

A longitudinal qualitative method where users record their experiences, thoughts, and habits over multiple days or weeks to track behavioral patterns over time.

Competitor Analysis

A strategic research method comparing competitors' service offerings, menu pricing, policies, and guest reviews to spot unaddressed market gaps.

Journey Map

A visual framework that charts every sequential touchpoint of a guest's service experience, recording their actions, thoughts, emotional highs/lows, and pain points to reveal opportunities.

Zone A: The Lens

The top layer of a journey map that defines the scope and boundaries by establishing the persona ('who'), the scenario being evaluated ('what'), and guest goals/expectations.

Zone B: The Experience

The central body of a journey map displaying the guest's progression across chunked phases, visualizing their sequential actions, thoughts, quotes, and emotional curves.

Zone C: The Insights

The bottom section of a journey map detailing the critical pain points identified, actionable opportunities for improvement, and internal organizational ownership.

Pain Points

Specific moments during a customer journey where users experience friction, frustration, excessive waiting, repetition, disorientation, or anxiety.

Opportunities (Journey Map)

Actionable service or operational design interventions created to resolve identified pain points and elevate the customer experience.

Constraint

A non-negotiable boundary, limitation, or operational rule (involving time, budget, personnel, space, or regulations) that directs creativity toward realistic solutions.

Low System Interoperability

A technological constraint occurring when legacy systems (such as POS, kitchen display, and table booking platforms) cannot communicate or exchange data seamlessly.

Brainstorming

A collective ideation method where participants rapidly generate a broad volume of creative solutions while deferring all criticism and judgment.

Braindump

An ideation exercise where team members independently write down all their initial concepts as quickly as possible within a timed window before sharing them with the group.

Reverse Brainstorming

A problem-solving technique where a team brainstorms ways to intentionally worsen or trigger a problem, subsequently flipping those negative ideas into constructive fixes.

Benchmarking

An ideation technique that examines operational practices and performance metrics of best-in-class competitors to identify proven ideas that can be adapted.

Prioritisation (Ideation)

The practice of evaluating and ordering generated ideas according to their anticipated impact versus required effort to single out high-impact 'quick wins.'

Low-Fidelity Prototype

A quick, low-cost, rough prototype (e.g., paper floor plans, cardboard physical cutouts, or sticky-note workflows) built for fast validation of early concepts.

Medium-Fidelity Prototype

A prototype exhibiting moderate detail and structure (such as clickable wireframes or digital app mock-ups) optimized for assessing layout, navigation, and user flow.

High-Fidelity Prototype

A realistic prototype that closely mirrors the appearance, behavior, and mechanics of the final offering (e.g., a live pop-up dinner with full plating and pricing) for final validation.

Throwaway Prototype

A prototype built exclusively to test a targeted hypothesis or learn a specific lesson, intended to be discarded after testing regardless of its fidelity level.

Skipping Steps (Pitfall)

A design thinking pitfall that occurs when a team jumps prematurely into creating solutions without thoroughly understanding users or defining the root problem.

Working in Isolation (Pitfall)

A design thinking pitfall where designers develop concepts disconnected from front-line staff, end guests, and key cross-functional team members.

Being Too Rigid (Pitfall)

A design thinking pitfall characterized by executing the process as an inflexible linear checklist rather than looping back and iterating as new findings emerge.