Skip to main content

Middle Managers as Incentive Interpreters: Making Performance Expectations Coherent

How everyday feedback, targets, and resource choices shape what teams believe matters.

Middle Managers as Incentive Interpreters: Making Performance Expectations Coherent

A support organisation asks teams to improve customer experience while reducing the time needed to close requests. One manager emphasises rapid closure in weekly reviews. Another asks whether customers had to contact support again. The formal targets are the same, but staff receive different signals about what a good decision looks like.

Middle managers interpret incentives through the work they prioritise, the questions they ask, and the feedback they give. Their interpretation can help people connect a target to its purpose. It can also introduce another source of confusion when local expectations conflict with the wider performance system.

The effects are not automatic. Staff have professional standards, personal goals, customer relationships, and different understandings of the work. A target does not determine everyone’s behaviour. It creates a signal that people interpret alongside the consequences they observe. Managers can make that signal clearer by discussing actual trade-offs and obtaining decisions where expectations remain incompatible.

Distinguish a Goal, a Measure, and a Reward

The support team’s goal might be to resolve customer problems promptly and reliably. Closure time is one measure of part of that goal. A bonus or performance rating tied to closure time creates a further consequence. These should not be treated as equivalent.

A measure can be useful without being a suitable individual target. Slow requests may reflect difficult cases, waiting for a customer, or a dependency on another department. Comparing staff without considering that work can turn a diagnostic indicator into a misleading judgement.

The manager needs to understand how the measure is used. Is it intended to identify process delays, estimate staffing needs, or assess individuals? If leadership has not decided, different managers may make different assumptions and communicate them as policy.

Steven Kerr’s On the Folly of Rewarding A, While Hoping for B examines mismatches between desired behaviour and reward systems. It provides a useful way to question alignment. It does not establish that every disappointing result comes from cynical staff or an intentionally misleading leadership message.

Interpretation Happens in Ordinary Management Decisions

A manager tells an adviser to spend longer understanding a recurring customer problem. If the next review criticises that adviser for handling fewer requests, the instruction and evaluation conflict. The adviser has to decide which signal will matter the next time a difficult case arrives.

The same pattern can appear in resource allocation. A manager may praise prevention while assigning all available time to the current queue. Staff then have little practical opportunity to improve guidance or remove a recurring source of requests. Their behaviour may reflect the allocation of time as much as their motivation.

Recognition also carries information. Highlighting only the fastest closures can suggest that speed is sufficient evidence of good work. Recognising a carefully resolved complex case can broaden the account, provided it does not simply replace one narrow example with another.

Managers should connect these decisions to an explicit standard. For the support team, a reasonable expectation might include checking that the proposed answer addresses the stated problem, recording relevant context, and using a defined route when another team must contribute. The precise standard belongs to the service, but staff should be able to understand and apply it.

Examine Conflicting Signals Before Inferring Bad Intent

Suppose closure time improves while repeat contacts rise. Several explanations are possible. Staff may be closing requests prematurely. A product change may have introduced more difficult problems. A reporting change may have altered what counts as a repeat contact. The pattern justifies investigation, not an immediate accusation of gaming.

Look at representative cases and speak with the people handling them. Compare the original issue, the response, the customer’s subsequent contact, and the dependencies involved. Ask what the adviser believed the target required and what feedback they expected.

The findings may reveal a genuine incentive problem. They may also reveal inadequate training, an unsuitable tool, or a target that fails to account for case mix. These causes can coexist and require different interventions.

Holmstrom and Milgrom’s multitask principal-agent analysis models how incentives across tasks can affect the allocation of effort, particularly when performance is easier to measure in some tasks than others. It is a theoretical framework, not direct evidence about this support team. Its relevance is the question it raises: what important work may receive less attention when one measurable activity is strongly rewarded?

Make the Trade-Off Reviewable at the Right Level

A manager can often improve local clarity. They can explain how to handle a complex request, distinguish avoidable delay from necessary investigation, and stop using a single measure as a complete account of contribution if their mandate permits it.

Some conflicts sit outside that mandate. A central bonus scheme may reward closure speed even when the local manager asks staff to prioritise resolution quality. The manager should raise the inconsistency with evidence and request a decision about the scheme or the standard.

The escalation should identify the behaviour required, the conflicting consequence, and the alternatives. The organisation might change how cases are grouped, introduce a quality check, revise the bonus criteria, or use closure time for process diagnosis rather than individual ranking. Each option should be assessed for administrative cost and possible unintended effects.

Privately telling staff to ignore the official measure leaves them exposed if it still affects pay or promotion. The manager may support a different interpretation, but should distinguish that recommendation from an agreed change. Teams need to know what is settled, what remains under review, and which expectations currently apply.

Use Several Forms of Evidence Without Creating Another Scoreboard

A broader review can include time to resolution, sampled response quality, repeat contact, customer feedback, and the complexity of work handled. No combination automatically captures every contribution. The point is to make a judgement better informed, rather than produce a new composite number that hides the same uncertainty.

Include work that enables other people. An adviser who improves a troubleshooting guide may reduce future requests while closing fewer cases that week. A colleague who handles difficult escalations may have a different pattern from someone working a routine queue. The manager should be able to explain those contributions without inventing a precise conversion rate between them.

Be cautious about adding measures without removing old requirements. A team already maintaining several dashboards may spend more time proving its work while the underlying conflict remains unresolved. Choose evidence that can inform a decision and explain who will use it.

The purpose of the discussion also matters. A process improvement meeting should help the team understand where requests wait and what would improve service. An individual performance review should consider the person’s conduct, responsibilities, available support, and evidence across time. Mixing those purposes can make staff reluctant to describe problems honestly.

Explain What Staff Can Rely On During a Change

A revised performance measure may take time to approve. During that period, the manager should state which expectations are current and what they are seeking to change. Staff should not have to infer that a supportive local conversation has overridden a formal assessment rule.

Where a transition decision is needed, request it explicitly. The sponsor may be able to confirm how exceptional cases will be reviewed, whether a temporary adjustment applies, and how decisions will be documented. The manager should communicate the authorised arrangement consistently and make room for staff to raise cases it does not cover.

The manager’s own uncertainty also belongs in the account. If they do not know how a central scheme will treat a complex case, they should obtain an answer or preserve the question as unresolved. A confident prediction about what leadership really values can create a promise the manager cannot keep.

Check Consistency Across Managers and Over Time

Ask several managers to assess the same anonymised examples. A request that stayed open for an extra day to verify a fix may reveal different interpretations of the standard. Discuss those differences before assuming staff have received a coherent message.

Calibration should preserve relevant context. The aim is not to force identical ratings for different work or remove all professional judgement. It is to identify where two managers are applying incompatible expectations to comparable cases, and settle what guidance should change.

After a target changes, explain which previous requirements remain and which are replaced. Adding a new priority without revisiting the old one can leave managers trying to satisfy an expanding collection of promises. A decision about priority should reach staffing plans, review questions, and recognition practices as well as the announcement.

The work connects to role clarity: people need to understand what their contribution requires and how it will be evaluated. It also depends on decision rights, because a manager cannot resolve every inconsistency in a performance system they are not authorised to change.

Revisit the effect through actual cases. If staff can explain the expected judgement, feedback follows that account, and difficult work receives appropriate attention, the interpretation is becoming more coherent. If contradictory signals persist, the next task is to resolve the operating choice behind them rather than ask managers to communicate the same unresolved conflict more persuasively.