Goals set for restaurant employees fail when they are vague ("be faster"), impossible to observe, too numerous or without a review date. A usable goal describes a specific situation, a visible behavior or result, a time frame, and the moment you will talk about it again. Without that, it disappears at the first rush.
"Be faster"
After a busy service, a manager tells a server: "You need to be faster on the floor." The server nods. The manager writes the goal in a notebook. A month later, the review happens and nobody can say whether the server has improved. The manager thinks not, the server thinks so, and no fact settles it.
The server did not need speed. He needed to know when to take orders from the tables at the back, and access to a tablet in working order. The goal was not about the real issue.
Why a goal falls flat
It describes a trait, not a situation. "Faster," "more independent," "more engaged" are qualities. They cannot be observed at a specific moment.
It ignores the conditions of the job. A server without reliable equipment, a line cook with no training on the station, a short-staffed team: the goal targets the person when the obstacle is elsewhere.
It has no review date. With no appointment, the goal stops existing after a few days. It resurfaces at the next review with no history.
It piles up. After two reviews, the employee has five goals nobody follows. They no longer know which one counts.
It is not tied to what happens day to day. It lives in a review, not in the tasks of the job.
Rewriting a goal: examples
| Vague goal | Why it fails | Observable version |
|---|---|---|
| Be faster | No moment, no criterion | At lunch service, take the order of the back tables within five minutes of seating, unless a stockout was flagged |
| Be more independent | Cannot be observed | Do the cold station prep alone three Saturdays in a row, with the checklist signed |
| Communicate better | A character trait | Announce the dishes that are out of stock to the team before each service |
| More engagement | A judgment on the person | Choose a training from the catalog with the manager and complete it before the review date |
The five minutes in the table are a fictional example: set your own durations with the employee, based on what the job allows.
A six-step method
1. Start from a real situation
Pick a specific moment in service where the gap is visible. The manager and the employee talk it through together. Format: a shared, dated memory.
2. Identify what is blocking
Training, equipment, schedule, an instruction poorly passed on? Write it down. If the obstacle is organizational, deal with it first: it is not a goal for the employee.
3. Phrase it in observable terms
Who, in which situation, does what, and how a third party can see it. One sentence, not a paragraph.
4. Limit it to one or two goals
Keep other topics for later. Write them in a "to revisit" list, with no commitment.
5. Set the review date right away
On the day the goal is set, not later. It goes into the manager's calendar and is shared with the employee.
6. Plan what will help
A short training, a pairing with a colleague, a written aid. The goal comes with a means, otherwise it becomes one more instruction.
When the goal changes along the way
A schedule change, a long absence or a reorganization of the station changes the conditions of the goal. Note it and push back the review date, rather than judging the goal over a period that was no longer the same. A goal that ignores reality loses the employee's trust.
Common mistakes
- Setting a numbers goal without specifying the quality to preserve.
- Using the goal as a disguised sanction.
- Writing the goal without letting the employee adjust it.
- Ignoring a schedule or team change during the period.
- Forgetting to note interim progress, which motivates more than the final assessment.
What to measure
- The share of goals with a review date recorded as soon as they are set.
- The number of open goals per employee.
- The number of goals whose obstacle turned out to be organizational, so you fix the process and not the person.
Where Tsuno comes in
Tsuno keeps dated records of agreed goals, the training and expected skills for the role, signed tasks and actions taken, with the provenance of each fact. At review time, the manager finds what was agreed and what has happened since, and knows when data is missing. Tsuno does not grade the employee, does not conclude on their behalf whether the goal was reached, and does not infer motivation or mood. See the features page for training and skills.
Further reading
Preparing the conversation where these goals are set and reread is detailed in how to prepare an employee conversation with facts, not impressions. To know when an independence goal has been reached, see how to know when a new restaurant employee is actually ready. To recognize progress without being patronizing, recognition at work: use facts, not childish badges. The general framework of management by facts is in managers do not need another dashboard.
Key takeaways
A goal holds if it describes an observable situation, if the organizational obstacle has been removed, if it stands alone or nearly so, and if its review date is set the same day. A missed goal is first of all information about the process.
Frequently asked questions
Why are goals set for restaurant employees often not met?
Most often because they are vague, there is no way to tell whether they have been reached, and no review date was set. Nobody then knows whether to keep pursuing them.
How do you phrase an observable goal for a line cook or a server?
Describe a specific situation and what should be visible in it, for example "during lunch service, announce the allergens at every table without a reminder." A colleague or the manager must be able to see it.
How many goals should you give an employee at once?
Few: one or two over the same period. Any more and attention scatters without any of them really moving forward.
Should speed or sales targets always be avoided?
Not always, but you need to specify the context and what must not suffer (quality, food safety). A speed target on its own pushes people to cut corners.
What if a goal is not reached by the review date?
First check whether the training, the schedule or the procedure made it possible. Then reword, extend or drop the goal. A missed goal is information, not a reproach.
Keep reading
Team and management
How to prepare an employee conversation with facts, not impressions
Prepare an employee conversation with facts: reread dated commitments, training and wins, separate fact from opinion, and leave the decision to a person.
Team and management
Employee recognition: praise with facts, not badges or rankings
A specific compliment (what was done, when, with what effect) beats a badge. Here is how to prepare it from facts and say it yourself, in your own voice.
Team and management
Management software or surveillance: where is the line?
Management software turns into surveillance depending on purpose, transparency, access and what the vendor rules out. Five questions to tell which one you have.