The Reluctant Delegator: Priya's First Quarter as Analytics Lead
Priya was promoted eight weeks ago to lead a nine-person analytics team at a mid-sized insurer after four years as its strongest individual analyst. Two senior analysts also applied; one of them, Marcus, now reports to her and has told colleagues the process was 'political'. Priya still personally builds the quarterly reserving model, which consumes roughly 60% of her week, because she believes nobody else can do it to her standard. Two of four project deadlines have slipped, and a first-year analyst has quietly started interviewing elsewhere. Last week Priya reassigned a dashboard redesign to a junior analyst without discussion; Marcus learned about it in a cross-team meeting and escalated to Priya's manager, who then told her to 'be more decisive and stop second-guessing the team'. In five weeks the team owes its largest client a regulatory capital summary. The skip-level has scheduled a review of the team's operating model for Friday. Priya has received no further guidance on what 'decisive' should look like.
1. Diagnose the root causes of Priya's transition difficulty. Separate the leadership-behaviour problems from the structural ones (work design, role clarity, operating rhythm), and state which two you would address first and why.
Read the worked answer
Two distinct failure modes are tangled together here, and the fixes are different, so separating them is the first analytical step.
Leadership-behaviour problems
- Role confusion. Priya is still operating as an analyst. Building the reserving model herself is a delegation failure rooted in a belief that only she can meet the standard. It removes developmental work from the team and signals distrust.
- Decision-making without consent. Reassigning the dashboard with no conversation turned a routine resourcing call into a status contest with Marcus.
- Conflict avoidance. She has neither re-contracted expectations with Marcus nor addressed his public commentary, so the grievance compounds.
Structural problems
- Work design. There is no ownership map of the team's outputs; nobody is named accountable for the reserving model or the dashboard, so Priya defaults to doing the work.
- Role clarity with Marcus. His accountabilities after losing the competition were never renegotiated. Reporting to a former peer requires an explicit re-contract, not goodwill.
- No operating rhythm. No weekly plan/review forum exists, so escalations bypass her by default.
Order of attack: the ownership map first, then the Marcus conversation. Structural change is cheap, immediate, and gives her the legitimate authority to stop doing analyst work. Behaviour change announced before a visible work redesign will read as sloganeering; a redesign alone leaves the grievance live.
2. Marcus has escalated past her. Set out how Priya should handle the Friday skip-level review and the conversation with Marcus, including the key message she should actually deliver.
Read the worked answer
Before Friday she needs facts, not defence: a one-page operating-model proposal naming accountable owners per output, a decision-rights table (what she decides alone, what is consulted, what is delegated), and a list of the two slipped deadlines with causes. Walking in to explain Marcus's behaviour is a losing frame; walking in with a work design is a winning one.
In the skip-level she should own the gap without self-flagellation ('Two deadlines slipped because I was still doing analyst work and had no ownership map; here is the map and the review cadence'), state what she has already changed, and ask for two specific things - endorsement of the ownership map and agreement that escalations come to her first with a five-working-day resolution window. She should not blame Marcus or describe him as disloyal; that reads as fragility to a skip-level.
With Marcus, in private and within two days: acknowledge the disappointment without conceding the process was rigged ('You were a credible candidate and I know this is difficult; I am not going to pretend otherwise'), then be unambiguous about the standard ('Decisions about work allocation are mine, and I will consult you on the ones that touch your expertise. Escalating before raising it with me undermines both of us and I need it to stop'). Then give him something real: named technical ownership of the reserving model with review authority, which converts his expertise into formal standing. Close with a written summary of what each of them committed to, so the reset is documented rather than remembered differently.
3. Recommend what Priya should stop, delegate and continue over the next 30 days to protect the five-week client deliverable.
Read the worked answer
Stop: personally producing the reserving model. This is the single highest-leverage change, and the five-week deadline makes it urgent, not optional.
Delegate, with a control rather than a hope: hand the model to Marcus with a defined review gate (he builds, she reviews at two checkpoints with a documented checklist of assumptions and prior-period reconciliations). Pair the junior analyst with him on documentation so the model is not single-person dependent. Publish the ownership map so the delegation is structural, not a favour.
Continue: the client relationship and the regulatory sign-off conversation. Those are genuinely non-delegable at her level and are where her remaining 40% of time belongs.
Thirty-day sequence: week 1 - ownership map, Marcus reset, stop building the model, cancel or renegotiate one low-value commitment to buy capacity; week 2 - first model checkpoint, daily 15-minute stand-up on the client summary; weeks 3–4 - second checkpoint, escalation with the skip-level on any resourcing gap; week 5 - deliver, and run a short retrospective on what the transition cost.
Risk to manage: the first-year analyst who is interviewing. A stay conversation should happen inside week 1, not after the client deadline - retention problems that are deferred become resignation letters. Priya should ask directly what would keep them and be honest about what she can and cannot offer.