The promoted peer: performance, conduct or transition?
Priya has just been promoted to manage a 14-person claims processing team at an insurance company. She was previously the team's senior processor and now manages three former peers, two of whom - Marcus and Elena - applied for her job and did not get it. In the six weeks since her appointment, average processing time has risen from 3.1 to 4.4 days, overtime has reached £18,000 against a monthly budget of £6,000, and two experienced staff have resigned. In one-to-one conversations, several team members say Marcus openly questions Priya's decisions in meetings and that Elena has been telling colleagues that 'nothing will change'. Marcus's own output remains the highest in the team. Priya's manager has told her to 'sort it out quickly' but has not defined what that means, and HR has offered only a standard performance-improvement process. Priya has a team meeting on Friday and a backlog that must be cleared before quarter end in three weeks.
1. Diagnose what is happening in Priya's team. Separate the performance, conduct and transition issues, and say which most threatens the quarter-end backlog.
Read the worked answer
Three strands are being treated as one, and that is the core error.
- Transition friction (normal, time-bound). Two internal candidates lost out. Resentment, testing behaviour and a period of lower trust are predictable. If Priya treats this as misconduct she will confirm the team's fear that promotion has changed her, and she will escalate a problem that partly resolves with consistent leadership.
- Conduct (not performance). Marcus challenging decisions in the forum she chooses is legitimate; Marcus questioning her authority in front of the team and Elena predicting failure are behavioural issues. These are contagious because 12 other people are watching to see what is tolerated. They need a conduct conversation, not a performance-improvement plan.
- Performance (a system symptom). Processing time rising from 3.1 to 4.4 days is an output measure, not a cause. Before attributing it to attitude, Priya should check claim volumes, absence, system downtime, error and rework rates, and whether Marcus's high output is comparable - high individual output is sometimes built on cherry-picking easy claims and leaving complex work to others.
What most threatens quarter end is the overtime and absence spiral plus the loss of informal influence: two resignations already signal that good people are choosing exit over loyalty to Priya. A formal process against the team's highest producer would look punitive and remove capacity at the worst moment.
Practical test: ask what evidence would change her mind. If output is falling only in the teams Elena influences, it is a conduct and climate issue. If it is falling everywhere, it is capacity, process or system - and the two individuals are a symptom, not the cause. Diagnose first, then choose the instrument: performance plan, conduct conversation, or workload and process fix.
2. Recommend a sequenced 30-day course of action, including what Priya should say to Marcus and Elena and what she should not do yet.
Read the worked answer
Week 1 - reset the standard, not the blame. At Friday's meeting Priya should state three things plainly: how decisions will be made and where challenge belongs, the behaviour standard she will hold everyone to, and the quarter-end target with daily numbers. She should acknowledge the appointment openly - 'I know two of you wanted this job; I need you to judge me on what I do' - because naming it removes its power as gossip.
Week 1–2 - two private, documented conversations. With each of Marcus and Elena separately: describe specific observed behaviour, its impact, ask for their account, state the standard, and agree what will change. Give a face-saving route: ask Marcus to lead a bottleneck review, which uses his credibility rather than confronting it, and ask Elena what she wants from the next 12 months. The line is: challenge in the right forum is welcome; predicting failure to colleagues is not.
Week 2–3 - attack the backlog with data. A daily huddle, age profile of the backlog, one bottleneck identified and relieved (temporary resource or targeted overtime), removal of low-value checks. This converts anxiety into visible progress and gives Priya evidence of who is contributing.
Escalate the risk, not the people. Tell her manager in numbers that quarter end is at risk and what resource or decision she needs. Get HR advice before any formal process.
What not to do yet: do not open a performance-improvement plan against Marcus. He is the highest producer, the evidence of underperformance is not established, and it would look retaliatory. Do not name individuals at the team meeting, and do not absorb the backlog personally - it models firefighting, not management.
3. How should Priya measure whether her approach is working, and what should trigger escalation?
Read the worked answer
Measure leading and lagging indicators, and review at 30 and 60 days.
Lagging: weekly average processing time and backlog age profile (not just volume), overtime against the £6,000 monthly budget, absence rate, voluntary turnover, and quality or rework rate so speed is not bought with errors.
Leading: attendance and contribution at the daily huddle, the number of issues brought to Priya rather than to Marcus or Elena, completion of the actions agreed in the two conversations, and a two-question pulse on 'I know what is expected of me' and 'I am treated fairly'.
Interpretation matters more than the numbers. Overtime falling while processing time falls is genuine recovery. Overtime falling while processing time stays flat means work is being hidden or deferred. Turnover stabilising within four weeks suggests the transition is settling; continued exits suggest the climate is still toxic.
Escalation triggers: no improvement in processing time by week four; a further resignation; repetition of the behaviour after a documented conversation, which moves the issue to formal conduct handling; overtime above budget for a second month with no capacity decision from above; or any indication that Priya is expected to meet quarter end through unsustainable overtime that conceals a structural capacity gap. In that last case she should escalate the capacity problem in writing - protecting her own position and giving her manager a real decision to make rather than an impression of failure.