Home / Blog / Note

What a leadership programme owes the first-line manager

First-line managers are promoted for technical work and judged on people work. Replace the leadership philosophy with three recurring conversations, each with a script and a checkable artefact.

What a leadership programme owes the first-line manager
Representational image.

A shift supervisor is promoted in April because she is the fastest and most accurate operator on the line. By June her team’s output is flat, one operator has stopped speaking to her, and HR has booked her on a two-day “Leading for Results” programme. She comes back with a folder, a personality profile and a model with four quadrants. None of it tells her what to say to that operator on Monday morning. She goes back to what she knows: doing the difficult jobs herself and leaving the people alone.

That is the standard result of a leadership programme built for a first-line manager, and the failure is not about motivation or intelligence. It is about the unit of instruction. The programme taught a philosophy. The job is a handful of conversations that happen every week, in noise, inside eleven minutes, with a shift change pending. A philosophy cannot be checked on a Tuesday. A conversation can.

The promotion is the problem, not the person

First-line managers are, almost by construction, selected for the wrong skill. Benson, Li and Shue studied promotion decisions in US sales firms and published the result as “Promotions and the Peter Principle” (NBER Working Paper 24343, later in the Quarterly Journal of Economics). They found that the top-ranked salesperson in a team was almost three times as likely to be promoted as the average worker. They also found the cost: doubling a new manager’s pre-promotion sales predicted a 7.5 per cent decline in the sales performance of that manager’s subordinates. In their data each manager had about five direct reports.

Read that as a design brief. The person in your programme was chosen because they were excellent at the work, not at getting work done through other people. They have had no rehearsal for the three or four exchanges that now fill their day. Then we hand them a model of leadership and a feedback form. The model survives because it is easy to put on a slide and impossible to fail. The conversations are specific, awkward, and different on a shopfloor from a sales floor, so they are the first thing a generic programme cuts.

Why leadership programmes default to a philosophy

There are three reasons, and none of them is laziness.

First, the cohort is mixed. One room holds twenty-four managers from quality, maintenance, dispatch and sales. A script for a correction conversation on a noisy shopfloor will not fit a sales coaching call. The safest content for a mixed room is content that fits every room: a model, a set of principles, a self-assessment. We argued in a competency framework nobody uses that frameworks fail for the same reason: twelve behaviours cannot be held in one head, so the fix is subtraction.

Second, philosophy is cheap to assess. A feedback form or a 360 gives a number on the day. Whether a manager can open a difficult conversation in eight minutes and close it with a dated commitment takes an observer, a checklist and a willing line manager. That cost is real, and most programmes quietly avoid it.

Third, the buyer and the user are different people. HR buys a programme that looks complete in a proposal. The first-line manager needs three lines to say before a shift. Our training solutions start from that gap, and the programme catalogue is where the unit of instruction belongs.

Start from the conversations, not the competencies

Here is the method, in the order the work actually happens. Do it before you write a single learning objective.

Step 1. List the conversations, not the skills. Sit with three first-line managers and their boss for an hour. Ask what they actually said to someone in the last fortnight that changed what that person did next. You will get six to ten. Ignore any that is a status update; a status update transfers information, not a commitment.

Step 2. Apply three filters. Keep an exchange only if it has a named other person, recurs at least fortnightly, and ends in a decision or a commitment someone could check. Anything that fails a filter is either a meeting or a monologue. Cut it.

Step 3. For each survivor, write three things. An opening line, which must be a question and not a statement. A stop condition, which is the specific thing that ends the conversation so it does not become a grumble. And an artefact, one line in a log or a dated commitment that someone else can read. If you cannot write all three, the conversation is not teachable.

Step 4. Rank by consequence. Keep the three whose absence does the most damage within a week. Delete the rest from the programme. A competency framework that names everything names nothing a manager can use at 6.10 in the morning.

The three conversations and their scripts

For almost every first-line manager, the same three survive. The exact words differ by site, so treat these as templates to be rewritten with the cohort, not as a national script.

Conversation Opening line Stop condition Artefact Common failure
The weekly check-in “What is blocking you this week that I can move?” One blocker named, one owner agreed One dated line in the one-to-one log Becomes a status readout; manager talks most
The correction “Can I walk you through what I saw on Tuesday?” The other person restates the specific behaviour and the change A dated commitment, two lines Manager generalises to character; no date
The handover “What do you need from me before I hand this over?” A named deliverable, a date, and a check-back point One line on the task board with an owner Delegation without authority; no check-back

Three details matter more than the wording. The opening is a question, because a statement invites agreement and a question invites the actual problem. The stop condition is what keeps an eleven-minute window an eleven-minute window. And the artefact is the only part a busy line manager can audit.

Build the programme backwards from the scripts

Now, and only now, write the programme. Each of the three conversations gets a practice block, not a lecture. The block is a role-play with a stopwatch: eight minutes, an observer with a four-line checklist (opened with a question, named one behaviour, set a stop, wrote the artefact), and a second attempt after feedback.

Assessment replaces the feedback form. At the end of the programme each manager runs one of the three conversations in front of their own line manager, who scores the checklist. The line manager gets a copy of the checklist and the log format. That is the handover: the manager’s boss now owns whether the conversations keep happening. The same point applies to coaching that survives the end of the engagement: change that stops when the specialist leaves was never change.

What to cut. The leadership philosophy module goes. The personality instrument goes. A 360 used as a teaching tool goes, not because feedback is useless but because a first-line manager cannot act on twelve dimensions on a Tuesday.

A worked example, illustrative

The numbers below are illustrative. They are not a client result and should not be quoted as one.

A plant has 24 first-line supervisors, each with five operators. Before the change, a one-to-one log exists for 9 of the 24 supervisors, and correction conversations are documented in 4 cases a month across the whole plant. The old leadership programme runs for 40 people over two days and the feedback average is 4.4 out of 5.

The redesigned version runs for the 24 supervisors only, in two half-days four weeks apart. Over the next eight weeks the plant counts three things: logs with a dated commitment, correction conversations with a dated commitment, and handovers with a named owner and check-back date.

Illustrative outcome at week eight: 21 of 24 logs are complete, 31 correction conversations are documented in the month, and 19 handovers carry a check-back date. The interesting number is not the rise. It is that the boss of each supervisor can now see, on one page, whether the three conversations happened. The 4.4 feedback score is gone, and nobody misses it.

Where this stops working

Four boundaries, stated plainly.

This works for recurring, observable exchanges. It does nothing for a manager whose span is fifteen people across three shifts, because a weekly check-in cannot happen for all of them. Fix the span or lower the frequency; do not pretend the script scales.

It does nothing when the organisation punishes the conversation. If a supervisor who names a blocker is told to stop making excuses, the opening question becomes a trap. Scripts cannot survive a culture that punishes honesty, and no programme should promise otherwise. Here the answer turns on the line manager above the first-line manager, not on the training.

It also turns into theatre when nobody reads the artefact. A log that the boss never opens is a compliance exercise, and within a month the dates are filled in on Friday afternoon. The checklist has to have a reader with the authority to act. Name who that is, in writing, before session one.

These are three conversations, not a full job description. The claim is narrow: of everything a programme could teach, these are the exchanges a new manager will run this week, badly, without help.

What to do on Monday

Open the current first-line manager programme’s objectives. For each objective, write three things beside it: which conversation, what opening line, what artefact an outsider could check. Any objective that cannot name all three is a philosophy. Delete it. You will probably delete most of the document.

Then take the survivors to one line manager and one first-line manager and ask them to rewrite the opening lines in the words people actually use on that site. Book an eight-minute role-play with a stopwatch and a four-line checklist for the next session. Give the checklist to the line manager, on paper, with the log format attached. That is the whole change. It fits on one page, and it is the part a first-line manager will still be using on the Monday after the programme ends.

Sources

The three promotion findings come from Benson, Li and Shue, “Promotions and the Peter Principle”. The eight-week example is illustrative and uses no client data.

https://www.nber.org/system/files/working_papers/w24343/w24343.pdf http://danielle.li/assets/docs/PromotionsAndThePeterPrinciple.pdf https://www.weforum.org/stories/leadership/he-peter-principle-isnt-just-real-its-costly

Keep reading
E-learning

"A playlist is not a blend: designing dependencies that hold"

Most blends are a video library with a workshop bolted on. Design the chain so each stage consumes the last one's output, and skipping a step becomes visible on the floor.

AI training

"The three manager tasks worth automating first"

"Most AI literacy budgets buy awareness and no change. Pick three recurring manager tasks with a readable artefact, and show the before and after for each."

Want this applied inside your organisation?

Talk to us