Defining a concept before designing it

Ask most operators to describe their concept and you will get a cuisine, a price bracket and an adjective: modern Italian, casual, premium. None of those tell a designer what the room should feel like, a chef what belongs on the menu, or a marketer what to say. So each of them fills the gap with their own interpretation, and the guest receives the average.

## What a definition has to answer

A concept is defined when it answers five questions in a way that could be argued with.

**Who is it for?** Not a demographic. A demographic is a description of who happens to walk past. The useful answer is a person with a reason.

**What occasion does it serve?** A weekday lunch that must be finished in forty minutes is a different business from a Thursday dinner that should last two hours, even with the same food.

**What is the offer?** The structure of the menu, not the recipes. How many categories, what the ordering pattern looks like, whether it is designed for sharing or for individual plates.

**Where does it sit on price?** Relative to the specific alternatives in the same catchment, not in the abstract.

**Why here rather than the alternative?** This is the question that separates a concept from a description, and the one most often skipped.

## The test of a real definition

A definition is finished when someone can disagree with it. "Modern Italian, casual, premium" cannot be argued with, because it makes no claim. "A neighbourhood pasta counter for people who want to eat well on a weekday without committing an evening to it" can be argued with — you can tell me the catchment does not have those people, or that the format cannot turn tables fast enough to work at that price.

That is the point. A definition that cannot be wrong cannot guide a decision either.

## What follows from the definition

Once the definition is settled, a large number of downstream decisions stop being matters of taste.

Menu length follows from the occasion and the kitchen. Seating and layout follow from the dwell time the occasion implies. Service model follows from both. Price position follows from the competitive set and the occasion. Brand voice follows from who it is for. Marketing channels follow from where those people are.

None of these become automatic, but they all become arguable against something, which is the difference between a decision and a preference.

## Where concepts most often go wrong

**Defining by cuisine.** Cuisine is an input, not a proposition. Several venues in the same catchment can share a cuisine and serve completely different occasions.

**Defining by aspiration.** "Premium" and "authentic" describe how the operator wants to be seen, not what the guest is buying.

**Defining by the space.** A concept built around a room that was already leased inherits the room's constraints as if they were choices.

**Defining after the identity.** A logo and a name can express a concept beautifully. They cannot define one, and building on an undefined concept is why they so often need replacing within two years.

## Practical recommendations

1. Write the definition as one sentence containing a person, an occasion and a reason to choose you. If it takes a paragraph, it is not yet decided.
2. Name the three alternatives a guest would realistically choose instead, by name, in your actual catchment. If you cannot, you do not know your competitive set.
3. Give the sentence to three people who will build from it — a designer, a chef, a marketer — and ask each what they would do. If the answers diverge, the definition is not specific enough.
4. Test it against the room and the budget before committing. A definition the site cannot deliver is a plan to disappoint.
5. Revisit it annually. Catchments change, and a definition that was right at opening can quietly stop being true.

## In short

The concept is the cheapest thing to get right and the most expensive thing to fix. Time spent making the definition specific enough to be disagreed with is repaid every time a decision downstream would otherwise have been made on instinct.