Restaurant skills matrix: how to build one that is useful

A skills matrix is useful when it answers an operational question in ten seconds: who can run this station, alone, this Saturday night? It crosses people with tasks, showing an observed level and a date. If it is used neither to build the schedule nor to train, it is decoration.

The Saturday schedule question

The head chef of a restaurant is building Saturday's schedule. The hot station lead is out. He looks at his notes: two people have worked the station before "as cover". But one does not know how to plate to the standard, and the other has never been alone at the pass. He mentions it to the manager, who remembers "a line cook who seemed good". He hesitates, then asks a station lead to stay later.

A sound matrix would have told him at a glance: task by task, who is independent, who is learning, who can train others, with the date of the last observation. He would also have seen that only one of the three is trained on the station's safety procedures.

Why matrices end up in a drawer

They measure the person instead of the task

A "good / average / needs improvement" box judges an employee. A box that says "plates the cold starter alone, signed off on the 12th" describes a fact.

They are too big

Fifty skill lines per role will never be kept up to date. The upkeep effort outweighs the use.

They are connected to nothing

If the schedule, the training and the job profiles live elsewhere, the matrix gets filled in once for a meeting and forgotten.

They are filled in by impression

With no observation criterion, the level shifts with the manager's mood and likes. Two locations end up with different readings.

A sample matrix (fictional example)

"Hot" station task	Person A	Person B	Person C
Station setup	Independent (12/09)	Independent (03/10)	Learning (30/09)
Cooking to spec	Can train (20/09)	Learning (03/10)	Does not know
Plating to standard	Independent (12/09)	Learning (03/10)	Does not know
Running the pass	Independent (28/09)	Does not know	Does not know
Cleaning and closing	Independent (12/09)	Independent (03/10)	Independent (30/09)

How to read it: you can see who can run what, which tasks have only one qualified person, and what training to plan next.

How to build it in seven steps

1. Start from a role, not the team. Pick the most critical one (for example the hot station, or dining room service).
2. List 8 to 12 tasks at most, taken from the typical day: the ones that block service if they are missing.
3. Define four levels and what lets you assign them: "independent" means done alone, without correction, in the expected time.
4. Name who observes. One named go-to person per role, who records the date and their sign-off.
5. Fill it in from observations, not memories. Cells with no observation stay empty, marked "not observed".
6. Connect it to the schedule and to training. Before publishing a schedule, review the tasks with no independent person. Each gap becomes a training need.
7. Review it with the team, person by person, leaving room to challenge a cell.

A practical rule: an empty cell beats a cell filled in at random. It honestly says that you do not know yet, and points to the next observation to organize.

Common mistakes

• Adding "soft" skills. They cannot be observed like a technique and slide toward judgment.
• Posting the matrix like a ranking. It is not built to compare people with each other.
• Never downgrading a level. A skill that is not practiced becomes less reliable: the date lets you see it.
• Confusing seniority with skill. Someone who has been around a long time may never have run a station alone.

What to measure

• The number of critical tasks with only one independent person, by role.
• The number of schedules built by consulting the matrix rather than from memory.
• The average age of the recorded observations: a cell dated a year ago needs a fresh look.

Where Tsuno comes in

In Tsuno, the matrix is not an isolated table. Expected skills are attached to roles, training modules (recipes, food safety, service, culture) feed them, and the chain runs from checklists to skills, from skills to roles, from roles to the schedule. Each level is a dated fact, observed by a go-to person. Tsuno connects these facts to show where a qualified person is missing. It does not rank employees, does not score a person, and nothing is decided without a human. See the features page.

To continue

The matrix builds on the definition of a role. To decide when someone can work alone, read how to know when a new restaurant employee is actually ready. The same reasoning applies to supervisors: how to know whether a manager is ready to run a location. The cluster's pillar: managers do not need another dashboard.

Key takeaway

A good matrix describes observed, dated techniques, task by task, for a given role. It is short, connected to the schedule and to training, and is never used to judge a person.