The Core Problem
The Industry Default
Most hotels are designed as buildings first. Teams optimise for real estate value, operational efficiency, and standardised systems. The focus remains on square metreage, yield per room, and construction costs.
This approach treats hospitality as a product to be manufactured and distributed. But something fundamental is lost in this translation.
The Hidden Truth
Hospitality does not live in objects. It cannot be found in marble lobbies, thread counts, or amenity lists.
It lives in sequences—in the carefully orchestrated progression of moments that shift how a guest feels, thinks, and remembers.
The building is simply the stage. The experience is the performance.
The Fundamental Reframe
The Old Mental Model
A hotel is a collection of rooms, facilities, and services. Success is measured in occupancy rates and revenue per available room.
The New Reality
A hotel is a temporary transformation of mental, physical, and emotional state. A guest arrives in one condition and departs in another.
Design the transformation. Not the container.
This shift in perspective changes everything. When you design for transformation, every decision—from door handles to lighting sequences—becomes a tool for emotional and psychological change. The architecture serves the experience, not the other way round.
Why Hotels Become Interchangeable
Despite millions invested in differentiation, most hotels feel remarkably similar. The culprits are familiar, yet their effects remain misunderstood.
Experience Becomes Branding
Real experience is replaced with messaging. Visual identity substitutes for emotional impact. Guests see promises, not realities.
Architecture Becomes Form
Iconic buildings prioritise exterior impact over internal flow. Photographs matter more than inhabitability. Form becomes disconnected from function.
Operations Take Control
Efficiency protocols override experience intent. What can be measured replaces what should be felt. Systems optimise for speed, not sentiment.
Data Becomes Reporting
Numbers describe the past but don't steer the future. Dashboards show symptoms, not causes. Information exists without interpretation.
Experience Architecture
Experience architecture is not interior design with a new name. It is the deliberate design of interconnected systems that shape how guests move through time and space.
State
The psychological and physiological condition of the guest at each moment
Sequence
The orchestrated progression through distinct phases of transformation
Infrastructure
The physical and sensory elements that enable state changes
Operations
The protocols that protect experience intent during delivery
Control
The systems that monitor, measure, and maintain experience quality
These five elements must function as one continuous system. When any component operates independently, the experience fragments. Integration is not optional—it is the foundation of lasting hospitality.
Start with the Arrival State
Do Not Start With
- Target demographic profiles
- Guest personas and archetypes
- Brand concepts and positioning
- Competitive benchmarking
Start With
- How does someone arrive?
- What are they carrying—physically and mentally?
- What must be released first?
- What transition must occur immediately?
Traditional hospitality design begins with market segmentation and brand positioning. But abstractions create generic solutions. Real experience design begins with observable human states.
A guest arriving at your hotel is not a persona. They are a specific person in a specific condition: tired, stressed, excited, uncertain, rushed, or overwhelmed. Until you understand and design for this arrival state, everything that follows will be guesswork.
Arrival States Shape Everything
Business Guests
Arrive fragmented. Mind still in the last meeting, body catching up with travel. They need immediate grounding and a clear sense of control.
Leisure Guests
Arrive overstimulated. Anticipation mixed with fatigue. They need gradual decompression and permission to slow down.
Boutique Seekers
Arrive uncertain but curious. Testing whether this place will deliver on its promise. They need immediate reassurance through considered details.
Experience Is a Sequence
Hospitality is not a collection of moments
It is a progression in time
Hotels obsess over peak moments: the stunning lobby reveal, the exceptional restaurant, the luxury spa. These moments generate social media content and award submissions. But they don't create lasting memory.
Experience lives in transitions. The thirty seconds between car and entrance. The shift from public lobby to private corridor. The moment between waking and leaving the room. These thresholds are where emotional transformation actually occurs.
Design the transitions with the same rigour you apply to the peaks. Memory is formed in the connective tissue, not just the highlights.
The Experience Sequence
Every successful hotel follows a natural rhythm, whether consciously designed or not. Making this sequence explicit transforms hospitality from intuition to architecture.
Anticipation
The psychological preparation before arrival
Arrival
First contact with the physical environment
Threshold
Crossing from public to semi-private space
Orientation
Understanding layout, norms, and possibilities
Control
Establishing personal agency and routine
Pause
The first true decompression moment
Peak
The memorable high point of the stay
Release
Letting go of the space before departure
Afterglow
The emotional residue that becomes memory
Memory is formed between moments, not inside them. The pause after the peak often matters more than the peak itself.
Sequence Over Spectacle
Peaks Impress
Transitions Stay
Spectacular moments generate immediate reactions. Guests photograph them, mention them in reviews, remember them clearly.
But transitions create the emotional foundation that makes peaks meaningful. A stunning rooftop bar feels hollow if the journey to reach it was confusing or uncomfortable.
Timing Matters More Than Decoration
When something happens shapes its impact more than what happens. A simple gesture at the right moment outperforms luxury at the wrong one.
Flow Matters More Than Features
How smoothly guests move through space determines their overall state. Friction accumulates. Grace compounds.
From Experience to Infrastructure
Once the experience sequence is clear, infrastructure design becomes logical rather than arbitrary. Every physical and sensory element exists to enable specific state changes.
Light
Controls energy levels, signals time of day, creates privacy or openness. Brightness, colour temperature, and direction shape emotional tone.
Sound
Manages stimulation, defines boundaries, enables focus or social connection. Acoustic design is psychological architecture.
Routing
Determines what guests see, when they see it, and how they feel about their choices. Circulation is narrative structure.
Waiting
Shapes perception of service quality and respect. Productive waiting feels different from dead waiting.
Visibility
Balances security and privacy, creates energy or calm. What can be seen changes how space is inhabited.
Infrastructure Is Behavioural
Infrastructure teaches people how to behave. Not through signage or instruction, but through physical and sensory cues that make certain actions feel natural and others feel awkward.
A wide, brightly lit corridor invites exploration. A narrow, dimly lit one suggests moving quickly. Furniture arrangement determines whether strangers will make eye contact. Acoustics shape whether conversation feels intimate or public.
If infrastructure contradicts experience intent, operations will neutralise it. Every time.
You cannot ask staff to create intimacy in a space that broadcasts every conversation. You cannot expect guests to feel relaxed when every surface is hard and reflective. Infrastructure must enable the experience you intend, or your intent becomes irrelevant.
The Building Comes Later
Wrong Question
How do we fit this concept into this building? How do we adapt our vision to work within these constraints?
This approach treats experience as decoration applied to a predetermined structure.
Right Question
What kind of building can carry this experience? What physical form enables the transformation we've designed?
This approach treats architecture as infrastructure for experience, not the other way round.
Most hotel projects begin with a site, a budget, and an architectural vision. Experience design is commissioned later to "fill in" the spaces. This sequence guarantees compromise.
When experience architecture comes first, building design becomes a tool for enabling specific sequences and states. Form follows psychological function.
Form Is Not Neutral
Buildings Impose Rhythm
Ceiling heights, corridor lengths, and room sequences create temporal patterns. Some rhythms induce calm. Others generate restlessness.
They Enforce Movement
Spatial configuration determines where people go, how fast they move, and what they encounter. Architecture is choreography.
They Shape Behaviour
Proportions, materials, and details signal expected conduct. Formal spaces demand formality. Casual spaces permit relaxation.
Not every iconic building is a good hotel.
Award-winning architecture often prioritises external recognition over internal inhabitability. A building can photograph beautifully whilst feeling uncomfortable to occupy. Experience architecture demands that form serves feeling, not just aesthetics.
Why Experience Disappears After Opening
The pattern repeats across the industry. A hotel opens with a strong, clearly articulated experience vision. Reviews are exceptional. Press coverage is glowing. Then, gradually, the experience fades.
Strong Concept
The design phase produces a clear, compelling vision. Everyone understands and believes in the intended experience.
Strong Opening
Launch energy maintains focus. Founders and designers are present. Staff are trained intensively. Experience is protected.
Operations Take Over
Routine sets in. Efficiency becomes the priority. Small compromises accumulate. Experience becomes "nice to have."
The Real Reason
Experience Has No Owner
This is the structural problem behind experience degradation. No single role is accountable for protecting experience integrity across departments and over time.
Design Moves On
After opening, designers exit. Their knowledge leaves with them. Intent becomes memory.
Operations Optimise
General managers focus on efficiency, cost control, and immediate problems. Experience is difficult to measure, easy to defer.
Marketing Brands
Marketing owns messaging, not delivery. They can promise experience but cannot enforce it.
When experience belongs to everyone, it belongs to no one.
Without clear ownership, experience becomes an aspiration rather than a standard. It persists only when individual staff members choose to protect it—a fragile foundation for consistent delivery.
Experience Governance
Experience must be governed, not just designed. Governance means establishing systems that protect experience intent through the pressures of daily operations and across multiple properties.
Clear Intent
Document the specific states and sequences that define your experience. Make the invisible explicit. Create shared language.
Explicit Ownership
Assign a role with authority to protect experience across departments. Not as a coordinator, but as an architect with decision rights.
Decision-Making Power
Give the experience owner authority to override efficiency when experience is at stake. Without power, ownership is symbolic.
Governance is not bureaucracy. It's the difference between a cathedral and a pile of stones—structure that preserves intention across time and change.
The Role of the Experience Architect
In fine dining, the executive chef doesn't leave after designing the menu. They remain present through opening and early operation, training the team, maintaining standards, and making real-time adjustments.
The same principle applies to experience architecture. The designer cannot simply hand over documentation and disappear.
Build Phase
Ensuring infrastructure delivers the intended experience mechanics
Launch Phase
Training staff to recognise and protect experience principles
Early Operation
Observing actual guest behaviour and refining delivery
The experience architect remains present just like an executive chef—not forever, but long enough to embed the practice.
This extended engagement transforms theoretical design into operational reality. It creates the muscle memory that allows experience to persist without constant supervision.
Operations Are Not the Enemy
The Inherent Tension
Operations are necessary. Hotels cannot function without systems, protocols, and efficiency. But operational thinking is rational by nature—focused on consistency, speed, and cost control.
Experience is emotional by nature—focused on feeling, timing, and context. These two modes often conflict.
The Translation Gap
Without deliberate translation, operational efficiency overrides experience intent. Staff follow procedures because procedures are clear, measurable, and enforced.
Experience principles, by contrast, require interpretation and judgment. When pressure increases, judgment gives way to process.
From SOP to ESP
Standard Operating Procedures
Optimise for efficiency, consistency, and speed. Designed to eliminate variation and reduce training time. Focus on task completion.
Example: "Check-in should take no longer than 3 minutes."
Experience Supporting Procedures
Optimise for emotional states, transitions, and memory. Designed to protect experience principles whilst maintaining operational viability. Focus on guest condition.
Example: "Check-in should allow guests to shift from transit mode to settled mode."
Arrival is not administration. It is a psychological threshold.
ESPs reframe operational tasks as experience enablers. They give staff permission to deviate from standard timing when guest state requires it. This doesn't eliminate efficiency—it contextualises it within emotional outcomes.
Experience Must Be Steerable
Most hotels measure experience only through hindsight. Guest reviews arrive days after departure. NPS surveys capture memory, not experience. By the time you receive feedback, dozens of other guests have already had the same problem.
Reviews Are Hindsight
They tell you what happened, not what's happening. By the time patterns emerge in review data, weeks or months have passed.
NPS Is Memory
Net Promoter Score measures remembered experience, filtered through recency bias and overall impression. It's a lagging indicator.
Platforms Serve Their Logic
TripAdvisor, Booking.com, and Google prioritise their business models, not your experience intent. Their metrics don't align with your strategy.
Ownership Requires Control
To genuinely own your experience, you must own the systems that monitor, interpret, and improve it. Dependence on external platforms means you're renting your understanding of your own hotel.
Own Your Data
Capture experience signals directly, in your own systems. This includes behavioural data, staff observations, and structured guest input.
Own Your Interpretation
Develop frameworks for translating data into experience insights. External platforms provide scores, not understanding.
Own Your Feedback Loops
Create mechanisms to act on insights quickly. Control means the ability to adjust, not just observe.
Without this infrastructure, you are reacting, not designing. You become dependent on aggregators, algorithms, and averages—none of which understand your specific experience intent.
Experience Control Infrastructure
A mature hotel needs its own control layer—not to replace distribution platforms, but to retain strategic agency over how experience is understood and improved.
What This Means
- Direct channels for capturing guest sentiment
- Behavioural observation protocols
- Real-time dashboards showing experience health
- Feedback loops connecting insight to action
What This Isn't
- Eliminating external review platforms
- Building a proprietary booking system
- Ignoring distribution partners
- Creating a data silo
Distribution ≠Control
Platforms drive bookings but don't provide strategic intelligence about your experience quality.
Reporting ≠Steering
Dashboards that show past performance don't enable real-time adjustments or predictive action.
From KPIs to Signals
Traditional hotel metrics measure outcomes: occupancy, ADR, RevPAR. These numbers describe business performance but reveal nothing about experience quality. Opinions from surveys add guest perspective but remain subjective and delayed.
Experience signals are different. They emerge from observing actual behaviour in real time.
Where Guests Slow Down
Lingering indicates comfort, interest, or uncertainty. Context determines meaning. Staff can observe and log these moments.
Where They Rush
Speed suggests discomfort, confusion, or purpose. Rushed movement through a space meant for pause signals misalignment.
Where They Avoid Interaction
Some spaces should invite engagement but are consistently bypassed. Avoidance patterns reveal friction or intimidation.
Where They Linger
Repeated dwelling indicates successful design. If the bar is empty but the corridor alcove is always occupied, behaviour speaks clearly.
Behaviour reveals experience. What people do is more honest than what they say. Observation creates a foundation for evidence-based experience refinement.
The Digital Architect
Buildings require architects because complex systems need coherent design thinking. The same principle applies to experience control infrastructure.
Not IT
Technology departments build systems but don't design experience frameworks. They implement requirements, not strategies.
Not Marketing
Marketing interprets brand and messaging but typically lacks operational integration and behavioural design expertise.
An Architect of Signals
Someone who understands experience principles, data interpretation, and operational reality. They design the control layer that makes experience governable.
This role doesn't replace existing functions—it connects them. The digital architect ensures that technology serves experience architecture, that data reveals experience health, and that feedback loops enable continuous refinement.
Scaling Without Losing the Soul
Single-property hotels can maintain experience through founder presence and tight operational control. But scaling typically destroys what made the original special. Everything becomes standardised to enable replication.
What Scales
Principles. The fundamental experience intent—the states, sequences, and transformations that define your hotel.
Principles can be adapted to different contexts whilst maintaining core identity. They provide direction without dictating details.
What Should Not Scale
Details. Specific design elements, exact procedures, and aesthetic choices that work in one location may fail in another.
Forcing uniform details across properties creates lifeless consistency. Local adaptation within principled boundaries creates authentic variety.
Successful scaling requires clear articulation of non-negotiable principles paired with explicit permission for contextual adaptation. This is harder than simple replication, but it's the only path to maintaining soul at scale.
Define Non-Negotiables
Before scaling, you must explicitly define what aspects of your experience cannot be compromised. This clarity prevents slow degradation as new properties open and operational pressures mount.
Not Aesthetics
Colour palettes, furniture styles, and decorative elements are contextual. They can vary by location, culture, and building constraints without losing identity.
Not Features
Specific amenities—rooftop bars, particular restaurant concepts, spa services—are tactical choices. Features should serve principles, not define them.
Experience Principles
The core transformations and sequences that make your hotel distinctive. These must remain consistent even as execution adapts.
Documenting these non-negotiables creates a constitution for your experience—guidance that empowers local teams whilst protecting core identity.
The Full System
Experience
Define the states and sequences that create transformation
Infrastructure
Design physical and sensory elements that enable those states
Operations
Create procedures that protect experience during delivery
Control
Build systems that monitor and maintain experience quality
In That Order. No Shortcuts.
Each layer depends on the clarity of the previous one. Infrastructure without experience definition is guesswork. Operations without infrastructure support become theatre. Control without operational integration is surveillance, not stewardship.
This sequence requires patience and discipline. Most projects want to jump straight to operations or aesthetics. But the system only functions when built in the correct order, with each layer informing and enabling the next.
The Hard Truth
Architecture without experience is empty
Beautiful buildings that feel uncomfortable to inhabit
Experience without operations is naïve
Compelling visions that cannot survive delivery pressure
Operations without control are blind
Efficient systems that unknowingly compromise quality
Control without ownership is illusion
Dashboards and data that nobody has authority to act upon
These truths are uncomfortable because they reveal that most hotels are incomplete systems. Components exist in isolation, never fully integrated. The result is mediocrity—not from lack of investment or talent, but from structural fragmentation.
Excellence requires the full system, properly sequenced, genuinely integrated. Anything less is compromise.
How to Design a Hotel from Experience First (draft)