SEVA OS Playbook· with Premm Anand · v1.0

The Invisible Advantage · Your playbook

SEVA OS

State, Environment, Values, Actions. Your four conditions, in the order your team needs them.

Your reading

Emerging Creators

Creators are appearing in your team, but they depend on particular people and particular days. The next step is to design the conditions that let what your best people do become how everyone works.

11 of 20 answered Yes. Start with State, then Values, then Actions.

Start here
I · State
2 of 5 Yes
Level 2
III · Values
2 of 5 Yes
Level 3
IV · Actions
3 of 5 Yes
In place
II · Environment
4 of 5 Yes

00

Start here

SEVA OS is your team's operating system for the four conditions behind every guest moment. Your levels are ordered by your reading: the condition with the fewest Yes answers comes first, so your effort goes where it changes most. Conditions already in place are kept short.

Your next 13 weeks

  1. Weeks 1–4State. The arrival minute · The 60-second reset · Belonging, one name at a time
  2. Weeks 5–8Values. What we protect on a busy day · Decision stories · The same experience on every shift
  3. Weeks 9–12Actions. Turn one routine into a ritual · The five-senses sweep · Meet the need before it is asked
  4. ThroughoutProtect Environment. Keep one habit going for each, so what works keeps working.
  5. Week 13Take the assessment again and compare your reading.

01

What you need

WhatWhy
Time20 minutes a week for the huddle, and 3 minutes at the start of each shift
One ownerOne person who keeps the practice going when you are away
A notebookPaper or shared notes, for what people say and what you change
HonestyYou go first. Every practice here depends on the leader modelling it

Level 1 · I

State

Start here · 2 of 5

What each person brings inside them into service.

Guests feel a person's state within seconds, before a word is spoken.

When people start work without noticing their State:

GuestsThey feel tension, distraction or impatience, or that the person is not really there. This happens even when the service is technically correct. The experience feels like a transaction.
Your businessService depends on how people happen to feel that day. More complaints come in. Putting things right costs more. Managers step in more often.
Your teamOne person's mood spreads to others. They cover for that person, carry the pressure or become defensive. Trust and teamwork grow weaker.
Your people's valueThey may be good at the job, but they are not trusted with the most important guests, more responsibility or sensitive moments.

I.1 The arrival minute

People cannot choose a state they have not noticed. One minute at the start of a shift makes the state visible, to them and to you.

  1. Gather the team for three minutes before the first guest. Standing is fine.
  2. Each person says one word for how they are arriving today. No explanations, no fixing.
  3. Each person then says one word for the state they will bring to guests.
  4. The leader goes first, honestly. "Tired" followed by "calm" is a perfect answer.
You should seeWithin two weeks, people use the words without being asked, and tell you before the shift when they are arriving low.
If notIf the answers become "fine" and "good", the leader is not being honest first. Go first with a real word for a week.

I.2 The 60-second reset

A difficult guest carries into the next one unless something stops it. The reset is that something.

  1. Agree one quiet signal the team can use, such as "Reset?" said to a colleague.
  2. The person steps out of guest view for 60 seconds while a colleague covers.
  3. Three slow breaths. Name what happened in one sentence, silently or aloud.
  4. Choose the state for the next guest, then return.
You should seeFewer moments where one difficult interaction spoils the next two. People offer the reset to each other.
If notIf nobody uses it on busy shifts, cover is the problem, not willingness. Pair people so each knows who covers them.

I.3 Belonging, one name at a time

People bring a better state to a place where they feel they belong. Belonging is built in small, specific moments.

  1. Each day, greet every team member you see by name.
  2. Add one specific thing you noticed about their work in the last shift.
  3. Once a week, ask one person: "What would make you feel more at home here?" Write down the answer.
  4. Act on one answer within the week, and tell the person you did.
You should seePeople speak up more in the arrival minute, and new joiners are greeted by others, not only by you.
If notIf the observations sound generic, they are. Keep a short note during the shift so tomorrow's is specific.

The huddle

Arrival minute huddle
Before we open, one word each: how are you arriving today?
[Everyone answers. No comments.]
Now one word for the state you will bring to our guests.
I'll start. I'm arriving tired. I'm choosing calm.
If anyone needs a reset today, say "Reset?" and someone will cover you for a minute.
For you: choose before you walk inBefore you enter the building, take 30 seconds. Name how you are arriving. Choose the state your team needs from you today. Your team reads your state before they hear your words.

Level 2 · III

Values

Next · 2 of 5

The principles your organisation truly protects, especially under pressure or when it is inconvenient.

Your team learns what you value from your decisions, not from your tagline or value statement.

When Values are spoken but not lived:

GuestsThey notice the gap between what the brand promises and what people actually do. Luxury without integrity soon feels like acting.
Your businessCulture depends on slogans, not decisions. Your team learns that targets, rank or convenience matter more.
Your teamPeople stop believing each other. Favourites, shortcuts and unfair decisions create mistrust.
Your people's valuePeople whose values cannot be relied on are rarely trusted with discretion, private information or more authority.

III.1 What we protect on a busy day

A value that has never been tested under pressure is a wish. Write down what it means when it costs something.

  1. Choose no more than three values your organisation truly means.
  2. For each, complete: "On a busy day, this means we will ___, even when ___."
  3. Read the three sentences to the team and ask: "Where did we not do this last month?"
  4. Keep the sentences where people work, not only in the handbook.
You should seePeople quote the sentences when making decisions, and challenge each other with them.
If notIf the sentences sound like a brochure, rewrite them with the team using a real, recent busy day.

III.2 Decision stories

Your team learns your values from your decisions. Tell them about the decisions.

  1. Once a week, share one decision you made that cost you something.
  2. Name the value that led it, and what it cost.
  3. Invite one team member to share a decision of their own.
  4. When you make a decision that went against a value, say so.
You should seePeople start explaining their own decisions by value, without being asked.
If notIf the stories feel staged, choose smaller, everyday decisions. They are more believable.

III.3 The same experience on every shift

Guests do not see your values. They see whether the experience changes with who is on shift.

  1. Choose one guest moment, such as arrival, a request or a complaint.
  2. Watch it on three different shifts, or ask a trusted guest about it.
  3. Compare what happened. Agree with the team what the standard is.
  4. Check the same moment again in two weeks.
You should seeThe chosen moment feels the same whoever is on shift, and the team names the next moment to work on.
If notIf shifts disagree on the standard, the value was never made concrete. Go back to the busy-day sentences.

The huddle

Hardest value huddle
Which of our values was hardest to keep this week, and when?
I'll start. On Saturday I chose speed over care with one guest. I'd choose differently now.
[Everyone answers. No judgement.]
What would help us keep it next time?
For you: say which value is leadingBefore a decision that costs you something, say out loud which value is leading it. If you cannot name one, pause. Your team will remember the decision long after they forget the value statement.

Level 3 · IV

Actions

Next · 3 of 5

The visible behaviour through which State, Environment and Values are finally experienced.

Routines finish tasks. Rituals, done with full attention, create moments guests remember.

When Actions do not show the standard every time:

GuestsPromises stay invisible. Guests judge you by what actually happens: what was noticed, remembered, anticipated, solved or ignored.
Your businessYour premium promise is hard to defend when guests do not experience it every time. Loyalty, reputation and revenue are at risk.
Your teamOthers must check, correct and rescue. Your best people carry more than their share, and average work becomes normal.
Your people's valueGood intentions do not create professional value. Repeated actions do.

IV.1 Turn one routine into a ritual

A routine is done to be finished. A ritual is done with full attention. The steps can be the same.

  1. Choose one routine guests experience every day, such as a greeting, a room check or a table reset.
  2. Ask the team: "What would this look like done with full attention?"
  3. Agree two or three details that show attention. Keep it small.
  4. Practise it together once, then watch it on shift for a week.
You should seeGuests comment on the moment you chose, and the team adds its own details.
If notIf it slips back to routine, the details were too many. Keep one detail and make it non-negotiable.

IV.2 The five-senses sweep

People notice what they have practised noticing. Sensing a situation fully is a skill.

  1. Before guests arrive, each person walks their area for two minutes.
  2. They ask: What do I see? Hear? Smell? Feel? (Taste, where it applies.)
  3. Each person fixes one thing they would not have noticed otherwise.
  4. Share the most surprising find at the next huddle.
You should seeSmall problems are fixed before guests meet them, and people point things out to each other.
If notIf it becomes a checklist, change who sweeps which area each week.

IV.3 Meet the need before it is asked

Your most valuable guests rarely say what they expect. The team that notices wins their loyalty.

  1. Keep a simple shared note of what returning guests prefer, in their own words where possible.
  2. Each day, ask: "Who is arriving, and what will they not tell us?"
  3. Each person tries one anticipated need per shift.
  4. Collect the stories weekly. Name the noticing, not only the gesture.
You should seeYou can name a moment this week when the team met a need before the guest asked.
If notIf the notes stay empty, give time at the end of the shift to write them.

The huddle

Before-it-was-asked huddle
Name one moment this week when you met a need before the guest asked.
What did you notice first?
I'll start. [Leader shares one.]
[Everyone answers.]
Which guest arriving today might need something they won't ask for?
For you: one shift of watchingOnce this month, run a shift where you only observe. Note what runs well without you, and what waits for you. The aim is a team that can run everything well, even when you are not there.

Level 4 · II

Environment

In place · 4 of 5

This is in place. Protect it.

Keep the weekly "what went wrong" question even when things are going well. Safety is kept by use, not by a policy.

See the full Environment practices anyway

II.1 Safe to tell the truth

You can only fix what you hear about. People tell the truth where the truth is met with thanks, not blame.

  1. Once a week, ask the team: "What went wrong this week that I should know about?"
  2. Go first with a mistake of your own.
  3. Thank every answer before you respond to it. Do not solve it in the room.
  4. Within the week, tell the team what changed because someone spoke up.
You should seeProblems reach you earlier, and people start the sentence with "I" rather than "they".
If notIf the room stays quiet, ask people to write one line anonymously for the first two weeks.

II.2 Trusted to decide

A team that must ask permission makes guests wait. Trust is something you can define.

  1. Choose the guest situations your team meets most often.
  2. For each, write what any team member may do without asking, and the limit of it.
  3. Share it, and say clearly: "Use this. I will back you."
  4. Each week, ask for one story where someone used it. Celebrate the judgement, not only the result.
You should seeFewer "let me check with my manager" moments, and stories of people solving things you never heard about until after.
If notIf nobody uses it, someone was once criticised for a decision. Name that, and repeat that you will back them.

II.3 The first 90 days

New team members decide early whether this is a place to stay. Settling well is designed, not hoped for.

  1. Give every new joiner a named buddy for the first month.
  2. Hold a short conversation at day 30, 60 and 90.
  3. Ask the same three questions: What surprised you? What is harder than it should be? What should we keep?
  4. Fix one thing they raise each time, and tell them.
You should seeNew joiners speak up in their first month, and fewer leave in the first 90 days.
If notIf the conversations slip, put all three dates in the calendar on the joiner's first day.
Obstacle huddle
One question this week: what got in the way of serving a guest well?
No names. Just the obstacle.
I'll start. I kept you waiting for a decision on Tuesday. That was on me.
[Everyone answers. Thank each one.]
I'll come back to you by Friday with what we changed.

02

The Tuesday check

Once a week, on an ordinary day, ask these four questions with your leaders. Twenty minutes is enough.

  1. Which practice did we actually run this week?
  2. What did we see change, in guests or in the team?
  3. Where did it slip, and why?
  4. What one thing will we do differently next week?

03

When it slips

What you noticeLikely causeWhat to do
Everyone gives the same word every dayIt has become a routine, not a checkChange the question each week: "What do you need today?" or "What will you notice first?"
The team laughs it offThe leader is not modelling itGo first with a real, slightly uncomfortable word for a week
Resets never happen on busy shiftsNobody is sure who coversName reset partners at the start of each shift
Values are quoted but not usedThey are not tied to real situationsRewrite them as busy-day sentences
Some people seem to be exemptFavourites or rank decide, not valuesApply the same standard visibly, starting with senior people
The experience still varies by shiftThe standard lives in one leader's headWrite the standard down with the team and check it
Rituals slip back into routinesToo many details to holdKeep one detail and make it non-negotiable
Only one or two people notice needsNoticing is not sharedShare one noticed story at every huddle
Everything waits for the leaderDecisions and standards are not handed overDo the watching shift and hand over one thing you saw

04

Questions

Do we need a training budget?

No. Every practice here costs time and attention, not money.

How long should we spend on one condition?

About four weeks. Long enough for a practice to become a habit, short enough to keep energy.

What if I am not the one who decides on team development?

Run the practices with your own team. Results are the best argument to the person who decides.

Can we do all four conditions at once?

We suggest not. Start where your reading points, and let the others follow.

How do we know it is working?

Take the assessment again after twelve weeks and compare your reading.

05

Your checklist

Your ticks are saved in this browser.

06

All huddle scripts

Level 1 · Arrival minute huddleState →Level 2 · Hardest value huddleValues →Level 3 · Before-it-was-asked huddleActions →Level 4 · Obstacle huddleEnvironment →

Premm Anand · Founder, The London Butler Academy® · Author, Becoming Extraordinary

This playbook is a reflective tool. It offers practices for conditions, not a judgement of people. Results depend on how consistently the practices are used.