A Complete 12-Week First-Time Manager Programme

Two things we will not do in this document. We will not attribute an idea to a scholar who did not have it — every source was read before it was cited, and the specific claims are quoted rather than paraphrased into something stronger. And we will not pretend twelve weeks changes things it cannot change. The section on what this design does not fix is a strange thing to publish and the most useful part of it.

The design logic

Why twelve weeks. Long enough for a behaviour to be attempted, fail, and be attempted again. Most first-time-manager behaviours fail on the first try; a six-week programme measures the first try.

Why this order. Identity, then direction, then conversations, then team — because each stage is a precondition for the next. A manager who has not accepted that the job changed will delegate badly. A manager who cannot set a clear goal has nothing to give feedback about. A manager whose team will not speak up cannot run a learning cycle.

Why the between-session work is the programme. The sessions are where the thinking happens. The application is where the behaviour does or does not change. Every module has both, and the measurement attaches to the second.

Weeks 1–3 · The transition

Week 1

From doing the work to enabling it

Capability

Recognise that the job has changed, and identify what work now belongs only to them.

Grounding

Michael Watkins, The First 90 Days (2003), for the transition frame and the breakeven point — the moment a new manager has contributed as much value as they have consumed. Cited as Watkins's framework, not as an empirical finding.

In the room

Each manager maps last week's actual time against three buckets: work anyone could do, work only they can do, work they are doing because it is comfortable. Most discover the third bucket is the largest.

Between

Track one full week against the same three buckets.

Measured by

Can name three activities they have stopped doing personally. (Level 2)

Week 2

Telling a technical problem from an adaptive one

Capability

Diagnose whether a team problem can be solved by skill, or requires someone to give something up.

Grounding

Heifetz, R. & Linsky, M., Leadership on the Line (Harvard Business School Press, 2002), ch. 1. Technical problems have known solutions applicable by expertise or authority. Adaptive challenges are "not amenable to authoritative expertise or standard operating procedures" and instead "require experiments, new discoveries, and adjustments from numerous places in the organization or community."

In the room

Each manager brings their team's three most persistent problems and classifies them. The test question: if everyone did exactly what you're asking, whose job gets harder?

Between

Bring one adaptive challenge to week 3, written up in one page.

Measured by

Correctly classifies four of five unseen scenarios. (Level 2)

Week 3

The change you have failed to make

Capability

Recognise that resistance — theirs and their team's — is usually a competing commitment doing its job.

Grounding

Robert Kegan and Lisa Lahey, "The Real Reason People Won't Change" (Harvard Business Review, 2001) and Immunity to Change (2009). People who appear to resist change are frequently working competently toward a second commitment they hold simultaneously and have never articulated.

In the room

Each manager builds an immunity map on one behaviour they have tried and failed to change. Not their team's. Their own. This module decides whether the cohort takes the programme seriously.

Between

Design and run one small, safe test of the big assumption underneath it.

Measured by

Self-reported behaviour change at week 12, with an example. (Level 3)

Weeks 4–6 · Direction

Week 4

Goals that actually move performance

Capability

Set goals that meet the conditions under which goals are known to work.

Grounding

Edwin Locke and Gary Latham, "New Directions in Goal-Setting Theory" (Current Directions in Psychological Science, 2006, 15(5), 265–268): "specific, high (hard) goals lead to a higher level of task performance than do easy goals or vague, abstract goals such as the exhortation to 'do one's best.'"

The paper also names the moderators, which is the part most goal-setting training omits: "The key moderators of goal setting are feedback, which people need in order to track their progress; commitment to the goal, which is enhanced by self-efficacy and viewing the goal as important."

In the room

Rewrite three real team goals against those four conditions — specific, hard, feedback available, commitment established.

Between

Agree the rewritten goals with two direct reports.

Measured by

Goals reviewed at week 12 against the same four criteria. (Level 3)

Week 5

Commitment, not compliance

Capability

Run the conversation that establishes why a goal matters, rather than announcing a number.

Grounding

Locke & Latham (2006) on commitment — enhanced by self-efficacy and by the person viewing the goal as important. A goal the person does not consider important is not a goal. It is an instruction.

In the room

Observed practice. Half the room announces a target; half establishes importance first. The difference is audible.

Between

One goal conversation with a direct report, self-scored against a short rubric.

Measured by

Rubric self-score plus one observed conversation. (Level 2 → 3)

Week 6

Delegation as capability building

Capability

Delegate work that develops someone, and name what the delegation costs the delegator.

Grounding

Watkins on reaching the breakeven point; Kegan & Lahey on the competing commitment underneath chronic non-delegation — commonly a sincere commitment to developing the team, held alongside an unspoken commitment to never being the person whose work was late.

In the room

Delegation planning on real tasks, with an explicit column for what could go wrong and what that would cost me personally.

Between

Delegate one thing that genuinely makes them uncomfortable.

Measured by

One task permanently transferred, still transferred at week 12. (Level 3)

Weeks 7–9 · Conversations

Week 7

Why feedback often makes performance worse

Capability

Give feedback under the conditions where it helps, and recognise the conditions where it does not.

Over a third of feedback interventions decreased performance.

Kluger & DeNisi (1996) · 607 effect sizes · 131 papers · 12,652 participants

Grounding

Avraham Kluger and Angelo DeNisi, "The Effects of Feedback Interventions on Performance" (Psychological Bulletin, 1996, 119(2), 254–284).

The headline is encouraging — a weighted mean effect of d = 0.41, "suggesting that, on average, FI has a moderate positive effect on performance." The finding underneath it is not: "over 38% of the effects were negative."

The mechanism is the useful part. Feedback that draws attention to the self rather than the task reliably underperforms — which is precisely what most well-intentioned developmental feedback does.

In the room

Managers bring three real feedback moments from the last quarter and classify where the recipient's attention went. Self, or task.

Between

One feedback conversation deliberately designed to hold attention on the task.

Measured by

Can state, unprompted, the condition under which feedback harms performance. (Level 2)

Week 8

The conversation being avoided

Capability

Hold the conversation that has been deferred, without softening it into meaninglessness.

Grounding

The week 2 technical/adaptive test applied to a person rather than a problem; Kegan & Lahey on what the other party would lose by changing.

In the room

Structured practice with an observer, on real deferred conversations. Each manager names theirs at the start of the session, which is most of the work.

Between

Hold it.

Measured by

Count of deferred conversations actually held, self-reported and spot-checked. (Level 3)

Week 9

Receiving feedback, in public

Capability

Solicit upward feedback in a way that makes it safe to give.

Grounding

Kluger & DeNisi on self-focus — a manager who defends is modelling the exact response that makes feedback useless. Edmondson (1999) on interpersonal risk.

In the room

Each manager asks their peer group for one piece of feedback and responds to it live. Observed, and uncomfortable by design.

Between

One upward-feedback request to each direct report.

Measured by

Team survey item at week 12 — "I can tell my manager when something isn't working." (Level 3)

Weeks 10–12 · Team

Week 10

Psychological safety, precisely

Capability

Build the specific team behaviours that psychological safety enables — not the feeling of comfort.

Grounding

Amy Edmondson, "Psychological Safety and Learning Behavior in Work Teams" (Administrative Science Quarterly, 1999, 44(2), 350–383). She defines it as "a shared belief held by members of a team that the team is safe for interpersonal risk taking." The study covered 51 work teams at a 5,000-employee manufacturer, with data from 427 team members and 135 external observers.

The finding that should drive the design, and rarely does: learning behaviour mediates. In Edmondson's own analysis, "the contribution of team psychological safety becomes insignificant when entered into the regression model together with team learning, which remains significant."

Read plainly: safety does not improve performance directly. It enables learning behaviours — seeking feedback, discussing error, asking for help — and those improve performance. A programme that builds comfort and stops there has built the enabler and skipped the mechanism.

In the room

Identify which learning behaviours are absent in their team, and what specifically prevents each one.

Between

Run one after-action review on something that went wrong.

Measured by

Team-level survey at weeks 1 and 12, on the learning behaviours rather than on comfort. (Level 3)

Week 11

Naming what the programme cannot fix

Capability

Identify the structural barriers to the target behaviour, and put an owner's name against each one.

Grounding

Heifetz on adaptive work — the work belongs to the people with the problem, and some of those people are not in the room.

In the room

Each manager names the three barriers they cannot influence: the metric that contradicts the behaviour, the promotion that rewarded the opposite, the senior leader who undermines it.

Between

Escalate one, in writing, to the person who owns it.

Measured by

A barrier register with named owners, handed to the sponsor. (Level 3 → 4)

Week 12

Evidence, not reflection

In the room

Each manager presents one behaviour they have changed, with evidence a sceptic would accept. Not what they learned. What is different.

Measured by

The full measurement set below.

The measurement plan

Kirkpatrick-aligned, and deliberately modest about what it can claim.

Level	What is collected	What it is allowed to claim
1 — Reaction	Two questions, used to detect a broken session	Nothing about learning. A fault detector, not a success measure. High satisfaction scores are not evidence and are not reported as such.
2 — Learning	Scenario classification; rubric scores on observed conversations	That the manager can distinguish and articulate. Not that they act.
3 — Behaviour	Tasks permanently delegated; deferred conversations held; goals meeting the four conditions; team learning-behaviour survey	That behaviour changed. Not that the programme caused it.
4 — Results	Whatever the sponsor named in week 0 as the observable outcome	Contribution, not causation.

Why level 4 says contribution. Week 11 produces a register of the drivers that sit outside the programme's reach. If three of five drivers are structural, a behaviour measure is a measure of this programme's contribution alongside those — and claiming otherwise is a claim the design cannot support. Kirkpatrick's levels are often blamed for encouraging overclaim. The model is not what produces the overclaim. Skipping the diagnosis is.

Section 4

What this design does not fix

Published deliberately, because a proposal that omits this section is selling rather than designing.

Incentives that reward the opposite behaviour

If the quarterly number rewards heroics, a delegation module produces managers who delegate for eleven weeks.

A manager's manager

The strongest predictor of whether new-manager behaviour survives is what the level above tolerates. That person is not in this programme.

Promotion criteria

If the last three promotions went to the best individual contributors, the cohort has already learned what the organisation values, and it was not this.

Overload — and there is evidence on this specifically

Locke & Latham (2006) report a study in which "goals affected performance only when overload was low." A manager at capacity will not set better goals because they attended a session about goals. If the sponsor cannot name what comes off these managers' plates, the goal modules will not work — and that should be said before the programme is bought, not after it is evaluated.

A problem that was never a capability gap

If people in the same role already do this well under the same conditions, the capability exists in the system and the question is why it is not spreading. That is a different piece of work.

What was deliberately left out

Several models common in first-time-manager curricula do not appear here. That is a choice, not an oversight: we excluded frameworks we could not trace to a primary empirical source we had actually read. Where a model is useful as shared vocabulary but not as evidence, we say so rather than dressing it as science.

If you want a module built on one of them, it can be — labelled as a practice heuristic rather than a finding.

Sources

Every source below was read before it was cited. Quotations are verbatim.

Edmondson, A. C. (1999). "Psychological Safety and Learning Behavior in Work Teams." Administrative Science Quarterly, 44(2), 350–383.
Heifetz, R. & Linsky, M. (2002). Leadership on the Line. Harvard Business School Press, ch. 1.
Kegan, R. & Lahey, L. (2001). "The Real Reason People Won't Change." Harvard Business Review, November 2001.
Kegan, R. & Lahey, L. (2009). Immunity to Change. Harvard Business Review Press.
Kluger, A. N. & DeNisi, A. (1996). "The Effects of Feedback Interventions on Performance: A Historical Review, a Meta-Analysis, and a Preliminary Feedback Intervention Theory." Psychological Bulletin, 119(2), 254–284.
Locke, E. A. & Latham, G. P. (2006). "New Directions in Goal-Setting Theory." Current Directions in Psychological Science, 15(5), 265–268.
Watkins, M. (2003). The First 90 Days. Harvard Business Review Press.

Published free and in full by ProgramArchitect. If this looks like something your team would otherwise spend three weeks building, that is the point. Want one designed around your own framework and your own gap? Get your design — or browse more resources.