How to measure manager capability through behaviour and team outcomes

A supervisor completes a leadership course, receives a good engagement score and keeps most of the team. Has their management capability improved? Possibly, but none of those observations is sufficient on its own.

To measure manager capability in hospitality, examine how a manager behaves during real work, whether those behaviours are sustained and what happens around the team. This guide concerns development after someone takes responsibility, not selection for promotion or a personality ranking.

Define the capability you want to see

Translate a broad aim such as “better people leadership” into a few observable practices. A front-office manager and a kitchen manager need different operational expertise, but both can be assessed against clear expectations about organising work, developing people and following through.

The US Office of Personnel Management’s guidance on developing performance standards emphasises clear, realistic and measurable expectations. Its public-sector framework is not a hospitality rulebook, but the principle is useful: specify what adequate performance looks like before judging it.

For a development cycle, choose a small number of behaviours with an explicit quality test:

• Sets clear priorities: explains the shift’s priorities, allocates ownership and checks understanding.
• Coaches constructively: uses a specific work example, listens to the employee’s explanation and agrees a practicable next step.
• Follows through: completes an agreed action or explains a delay before the promised date.
• Responds appropriately under pressure: communicates respectfully, recognises capacity limits and escalates matters outside their authority.

Avoid labels such as “natural leader” or “executive presence” without behavioural definitions. They make it difficult to distinguish useful management practice from familiarity, confidence or an assessor’s preferred style.

Use three evidence streams

Observed practice

Agree how a reviewer will sample ordinary work, such as handovers, coaching conversations or action reviews. Include different shifts and levels of pressure. Tell managers what is being observed and why; do not build the process around covert recording or surveillance.

Record the context, the behaviour and its consequence. “During the late handover, the manager allocated the unresolved arrival query and checked that the colleague understood the escalation route” is more useful than “good communicator”.

Use repeated observations rather than one staged demonstration. Where a behaviour has not had a reasonable opportunity to occur, mark it as insufficient evidence, not failure.

Team experience

Ask short questions about recent observable experience. For example: “In the past fortnight, when priorities changed, did your manager explain what you should do differently?” Include a not-applicable option where appropriate.

Explain who can see responses and whether the process is anonymous or confidential. Small teams and detailed comments can reveal identities even after names are removed. Use an appropriate aggregation rule and a separate route for concerns requiring individual follow-up.

The HSE’s Line Manager Competency Indicator Tool includes self-assessment and feedback approaches focused on management behaviours associated with preventing and reducing stress. It is a useful development resource within that scope, not a complete measure of every aspect of hospitality management.

Team outcomes

Select a few relevant outcomes, such as early retention, avoidable handover errors or completion of agreed development actions. Define each numerator, denominator and observation window. Keep guest-service measures alongside workforce measures rather than assuming one automatically represents the other.

Outcomes need context. Recruitment mix, staffing levels, property investment, pay and local demand can influence results. A manager inheriting an understaffed department should not be ranked against a stable team without considering the different starting positions.

Distinguish completion from quality

Hypothetical example: a manager has eight scheduled handovers during the review period. Seven take place. Five meet all three agreed quality criteria: priorities explained, responsibility allocated and understanding checked.

• Delivery coverage: seven of eight, or 87.5%.
• Quality-complete coverage across scheduled handovers: five of eight, or 62.5%.

Reporting only completion would hide the development need. Reporting five of seven answers a different question: quality among handovers that happened. Either can be useful when labelled, but do not switch denominators to improve the headline.

Counts also reveal whether the sample is thin. A percentage based on eight observations is a prompt for discussion and further evidence, not a precise measurement of an enduring personal trait.

Read feedback without exaggerating agreement

Independent hypothetical example: ten employees are invited to answer a question, eight respond and six of those eight give a positive answer. The response rate is 80%; positive responses among respondents are 75%.

Do not say that 75% of the whole team agrees. Two people did not answer, and their views are unknown. Show the response count, compare consistent questions over time and investigate whether some shifts or work groups have less opportunity to participate.

Do not force team feedback, observation and outcomes into a single weighted score merely because a dashboard can calculate one. Conflicting evidence is often the most useful part of a review: a manager may deliver briefings consistently while employees still find the priorities unclear.

Separate capability from conditions

Keep a context note for each review period: manager tenure, vacancies, new starters, seasonal demand, major changes and available support. Ask which issues sit within the manager’s control, which they can influence and which require a senior decision.

Rising incident reports may reflect more willingness to speak up, not worsening management. Lower absence or fewer complaints cannot automatically establish improvement. Check reporting behaviour and other evidence before drawing conclusions.

Likewise, a retention improvement after training does not isolate the manager’s contribution. Evaluate a development programme with a stronger comparison design if the organisation needs a causal claim. Individual development discussions can still use descriptive evidence honestly.

WINC Wire’s articles on why managers struggle and the manager shortage provide related context for examining the support around the role.

Close the review with a testable development plan

Choose one or two priorities rather than a long list of personality corrections. Record the expected behaviour, the support required, who will provide it and when fresh evidence will be reviewed.

For example, a manager could practise checking understanding at handover, receive observation and feedback from a peer, then review a new sample spanning early and late shifts. Judge whether the behaviour becomes more reliable and whether the team finds the communication more useful.

Calibrate reviewers using the same example cases, record disagreement and let managers correct factual errors. If evidence will inform formal employment decisions, make that purpose explicit and use the organisation’s appropriate process. A transparent development measure should help a manager improve, while giving leaders a more grounded account of what support is working.

Sources

• US Office of Personnel Management: Developing Performance Standards
• HSE: Line Manager Competency Indicator Tool

AI-generated editorial illustration.