Who Is the Guest?

The instinct to welcome everyone is a good human instinct and a bad design instinct, because design is the art of making choices, and you cannot make choices for a guest you have not defined. A hospitality business does have to be gracious to whoever walks through the door - that is hospitality itself - but the design, the brand and the offer must be shaped around a primary guest whose needs set the priorities. When they are not, every decision becomes a compromise between imagined opposites, and compromise averages everything into blandness. The lobby is a bit formal and a bit casual and therefore neither; the restaurant is a bit fine-dining and a bit family and so satisfies neither; the room has a big desk that the holidaymaker resents and a decorative daybed that the business traveller never uses. The place becomes a beige average that photographs acceptably and moves nobody.

There is a hard commercial truth underneath this, too. A hotel or restaurant earns its living from a particular market in a particular location, and that market has a shape: a central business district hotel fills on weeknights with corporate travellers and empties at weekends; a beach resort does the reverse; a highway motel lives off people who simply need to stop. Knowing who your demand actually comes from - and when, and why - is not marketing fluff, it is the basis of the whole design and business case, because it tells you how many rooms, what kind, what food and beverage, what facilities, and what price the place can command. Designing against your real market - a fine-dining restaurant in a student district, a conference hotel with no meeting space - is how beautiful places go quietly bankrupt.

So the first move in any hospitality project, before a plan is drawn, is to answer with discipline: who is the primary guest, who is the important secondary guest, and who is this explicitly not for. Naming who it is not for is as powerful as naming who it is for, because every "not for them" frees you to serve your real guest better. A hostel that admits it is not for families can build brilliant sociable bunk rooms; a silent adults-only retreat that turns away children can promise a calm no family hotel can. Clarity about the guest is permission to be excellent for somebody.

It helps to map guests on two axes that drive most hospitality demand: the purpose of the trip (business at one end, leisure at the other) and the price and service positioning the guest is buying into (from budget to luxury). Laid out this way, the familiar segments appear, each with a different centre of gravity. The business traveller values efficiency above almost everything - a frictionless arrival and departure, reliable fast connectivity, a desk and good light, a quiet room to sleep and somewhere credible to have a coffee meeting; price matters but time matters more, and much is paid by an employer. The leisure guest is the mirror image: time is the whole point, so they want to arrive into delight, linger, be surprised, eat well, and take home a memory and a photograph; they are spending their own money on an experience and judge it emotionally.

Within leisure sit distinct tribes. Families need space, flexibility and safety above style - connecting or larger rooms, somewhere to stash buggies and bags, a pool, early and forgiving dining, a cot that actually arrives - and they forgive a lot if the children are happy and nothing is dangerous. Groups - a wedding party, a tour, a team offsite, the great Indian wedding that can fill an entire hotel - bring their own social energy and need rooms near each other, generous public and banqueting space, and flows that keep three hundred celebrating guests from colliding with ordinary check-ins. The luxury guest, at either end of the purpose axis, is paying for time, space, recognition and flawlessness, and is exquisitely sensitive to anything that breaks the spell; the budget guest is making a clear-eyed trade, paying for a clean, safe, well-located bed and honest value, and resents paying for frills they did not ask for far more than they resent the absence of luxury.

The interesting truth of 2026 is that these boxes are blurring. The "bleisure" traveller tacks holiday days onto a work trip and wants both a desk and a pool. A budget-brand guest may demand a luxury-grade mattress and design-literate lobby because a well-known budget-chic brand taught them to. Treat the map as a way to understand forces and trade-offs, not as rigid pigeonholes - the point is to know which forces are strongest for your particular place.

Segments are useful for understanding the market, but you cannot design a desk for "the business segment" - it is too abstract. The move that sharpens design is to turn your primary segment into a persona: a specific, named, almost fictional individual, with an age, a job, a reason for the trip, a budget, and above all a story you can follow hour by hour. Not "business travellers" but "Priya, thirty-four, a founder flying in for two nights of investor meetings, who lands at eleven at night, needs to be working by six, lives on her phone, and will judge us on how fast she can get in, sleep, work and leave." The instant the guest has a name and a day, the design questions answer themselves: the check-in must be quick and possible late; the desk and the light and the power sockets by the bed must be real; the wifi must never stutter; breakfast must be available, or at least coffee, absurdly early; check-out must be painless. You have designed for Priya, and in doing so served ten thousand guests like her.

Good practice is to hold two or three personas - a primary one whose needs win when there is a conflict, and one or two secondaries you must not alienate. A city business hotel might design first for Priya but keep the weekend leisure couple firmly in mind, so the restaurant that feeds solo diners on Tuesday can also host a romantic dinner on Saturday. The discipline is in the conflicts: when the quiet the business guest needs collides with the buzz the social guest wants, the persona hierarchy tells you who wins where, and lets you zone the building so both can be served in different places rather than fudged everywhere.

In the Indian context the personas are often richly specific and worth naming honestly: the multi-generational family travelling together where the grandparents' comfort and the vegetarian, Jain or regional food needs are non-negotiable; the big-fat-wedding party whose three days will make or break the hotel's year; the aspirational young domestic traveller for whom this trip is a hard-won treat and a story for social media. Picture them, walk their day, and design for the person - not the average.

Designing for a guest means understanding two things about them: what they value (what they are really buying) and what they fear (what would ruin it). These are not always what the brochure says. A business traveller is not buying a room; they are buying control over a stressful, tightly-scheduled day, and they fear friction - a slow queue, a dead socket, a bad connection, a late, noisy, or unready room. A honeymoon couple is not buying a suite; they are buying a memory and a feeling of being special, and they fear anticlimax, being treated as just another booking, or a magic moment interrupted by a maintenance noise or an indifferent waiter. A family is buying a holiday that works for everyone including the children, and fears a dangerous balcony, a missed nap, a meal the kids will not eat, a day spoiled. Design lands when it speaks to the real value and quietly removes the real fear.

This is why the same physical feature reads completely differently to different guests, and why knowing your guest is not optional. An open, sociable, shared co-working lounge is a delight to a young solo traveller and an irritation to someone who needs silence to prepare. A dramatic, dim, theatrical restaurant is romance to a couple and a struggle to a family with a toddler and a grandparent who cannot read the menu. A minimalist room with hidden controls is chic to a design-literate guest and baffling to someone who just wants to find the light switch at 2am. None of these is right or wrong in the abstract; each is right for its guest and wrong for another, which is exactly why you must decide whose delight you are optimising for.

There is a universal layer beneath the differences, and it is worth holding onto: almost every guest, whatever their segment, wants to feel welcomed, safe, looked after, and that they got fair value for what they paid. Luxury and budget guests differ enormously in what they expect, but both feel betrayed by dirt, by being ignored, by feeling cheated, or by being made to feel stupid. Design to the specific guest for delight and differentiation; design to these universal human needs for the baseline trust on which everything else stands. Get both, and you have designed a genuine welcome for a real person.