High-level summary
- Connects evidence of readiness to a specific business need and a proposed next-level contribution, rather than a general request to "be considered".
- Prepares you to negotiate title, remit, decision rights, resources, development and reward as a single coherent package, benchmarked against the role rather than history.
- Sets boundaries against absorbing permanent extra scope without recognition, and defines what happens if progression is delayed or denied.
Outputs the client receives
- ✓A written progression case linking business need, evidence and proposed contribution
- ✓A negotiation brief covering title, remit, decision rights, resources, team, development and reward
- ✓A benchmarking summary of the target role and scope, not just historical salary data
- ✓A delay-response plan with specific evidence, exposure, milestones and a review date
- ✓A 30-60-90 transition outline for operating differently once progression is granted
Career OS™ principle
“A progression conversation is strongest when responsibility, authority, resources, recognition and reward are negotiated as one system.”
Who this stage is for
- Professionals with a genuine track record who are unsure how to convert it into a formal case
- Anyone facing a performance review, talent panel, promotion interview or scope discussion
- People who have been told informally that they are "ready" but have no defined process or timing
- Specialists at risk of absorbing a bigger job in practice while being paid and titled for the old one
- Candidates preparing to negotiate an internal move, secondment or head-of-function appointment
- Anyone weighing whether to keep pushing internally or treat an external move as the credible path
Why this stage matters
Strong performance in a current role and demonstrated readiness for the next one are not the same thing, and organisations rarely translate one into the other automatically. Without a deliberate case, capable people are left waiting for someone else to notice, decide and act on their behalf — a position that quietly transfers control of the career timeline to the organisation.
Progression conversations also fail when they are treated as single-issue negotiations. A promotion agreed without a matching mandate, resource or reporting line produces a bigger job with no more authority to do it. A pay rise agreed without a defined remit produces resentment on both sides within a year. Treating responsibility, authority, resources, recognition and reward as one connected system is what separates a durable progression outcome from a cosmetic one.
The cost of getting this wrong compounds. People who accept expanded scope informally, without a title, budget or decision rights to match, often find that scope becomes permanent while the recognition does not follow. Those who instead build one coherent, evidence-based case — and are prepared to treat an external move as a legitimate outcome if the internal path is not credible — retain far more control over how their career actually moves.
Cost of skipping it
- Operating at the next level in substance while remaining at the current level in title and pay
- Vague verbal encouragement ("you're definitely in the mix") replacing a defined process, owner and timing
- Negotiating salary in isolation while remit, authority and resources stay unresolved
- Scope creep becoming permanent without any corresponding recognition
- Losing a credible external option by waiting indefinitely for an internal decision that never arrives
Related Career OS™ tools
Practical resources that turn this PROPEL stage into action inside your current organisation.
Next decision
Leverage & Progression closes the PROPEL sequence, but it rarely closes the career decision. A successful outcome opens a 30-60-90 transition in which the new remit has to be established deliberately, not assumed.
An unsuccessful or delayed outcome is not a dead end. It converts into a specific plan — named evidence, named exposure, a named review date — or, where the organisation cannot offer a credible path, a considered case for an external move.
Leverage & Progression is the point at which everything built earlier in PROPEL — clarity of direction, credible positioning, evidence, visibility and delivered results — is converted into a specific, negotiable ask. It is not a single conversation but a structured case: a defined business need, demonstrated evidence that you can meet it, and a proposed next-level contribution that connects the two.
The case is future-facing rather than retrospective. It does not simply list what you have already done; it argues, with evidence, what you are now positioned to do next and why the organisation benefits from formalising that shift in title, remit or reward.
Many strong performers assume that consistent delivery will eventually be recognised without a case being made. It sometimes is, on the organisation's timeline rather than theirs, and often only partially. Others make a case but pitch it as a single-issue request — usually salary — leaving remit, authority and resources unaddressed and therefore unresolved.
A further common trap is discomfort with negotiation itself. Capable professionals who are entirely comfortable defending a technical position often find it far harder to hold a calm, evidence-based line on their own progression, and either over-apologise for asking or overstate their case defensively when challenged.
The mistakes here are less about competence and more about structure, timing and nerve.
- Asking to "be considered" rather than presenting a defined case with a business need attached
- Negotiating salary alone while leaving title, remit, decision rights and resources unaddressed
- Benchmarking against personal salary history instead of the market rate for the target role and scope
- Accepting expanded scope informally, with a vague promise that recognition will "follow" later
- Bringing ultimatums or a tone of entitlement instead of a calm, evidence-based request
- Having no answer prepared for what happens if the answer is "not yet"
PROPEL treats progression as a system negotiation, not a single-variable request. Before any conversation happens, the work is to establish explicit criteria: what evidence the organisation actually requires, who owns the decision, what process it runs through and what timing is realistic. Without this, a case is being pitched into a vacuum.
The case itself connects three elements — the organisation's genuine business need, the evidence already demonstrated, and the specific next-level contribution being proposed — into one coherent narrative. Negotiation preparation then treats title, grade, remit, reporting line, decision rights, resources, team, development, review date, salary and reward as a single connected package, benchmarked against the target role and scope rather than historical pay. Policy, budget, grade structures and approval limits are understood in advance, so the options proposed are ones a decision-maker can actually approve.
In the room, the posture is calm and evidence-led: one coherent request, comfortable silence, and questions that surface the real constraints, rather than ultimatums or appeals to fairness alone. A firm boundary is held against absorbing permanent extra scope without recognition. If the answer is delayed, the response is to agree specific evidence, exposure, milestones and a review date rather than accepting an open-ended "soon". Where the organisation genuinely cannot offer a credible path, an internal alternative or an external move is treated as a legitimate, sometimes better, decision.
A candidate for a head-of-function role had already been informally told they were the leading internal candidate, and their instinct was to focus the entire conversation on salary. Working through this stage, they instead built a case that separated three questions: the grade and title appropriate to the role, the mandate — decision rights, reporting line and which budgets and teams would sit under it — and the resources needed to deliver against it, including headcount and a development allowance.
Salary was benchmarked against the market rate for that scope of role, not against their previous pay, and was proposed last, once mandate and resources were agreed in principle. The organisation could not immediately match every element, so the candidate agreed a phased mandate with a defined six-month review rather than accepting the full title with a reduced remit. The result was a progression outcome that matched authority to accountability from day one, instead of a promotion in name that would have taken a year to become real in practice.
Draft a single page with four sections: the specific organisational need this role or level change addresses; the evidence that demonstrates you can meet it; the exact remit, resources and reporting line being proposed; and the reward package benchmarked to that scope. Test it by asking whether a decision-maker with no prior context could follow the logic in under two minutes.
- State the business need in the organisation's own language, not yours
- Attach two or three concrete evidence points, not a general summary of good performance
- Separate remit and resources from reward, then show how they connect
- Name the decision owner, the process and a realistic timeline
- Prepare one fallback position if the full case is not approved immediately
Before any conversation, gather the material that will make the case credible rather than aspirational: documented outcomes attributable to you, any instances where you have already operated at the next level, market and internal benchmarking on the target role, and a clear note of the criteria and process the organisation actually uses to decide.
- Outcomes and decisions attributable to you, with scale and stakeholder context
- Instances of already operating at the next level, formally or informally
- Market benchmarking for the role and scope, not historical personal salary
- The organisation's stated criteria, decision owner, process and typical timing
- A record of any prior informal commitments made about progression
A delay is not a refusal, but it needs converting into something specific or it will drift indefinitely. The right response is to agree, in the same conversation, exactly what evidence is missing, what exposure or projects would build it, and a fixed date to revisit the decision. Vague reassurance without these elements should be treated as a soft no.
Where the organisation is genuinely unable to offer a credible path — through structure, budget or politics rather than your readiness — an internal lateral move or an external opportunity is not a failure of the process. It is a legitimate and sometimes stronger route to the same destination, and should be evaluated with the same rigour as the internal case.
Once progression is granted, the most common failure is continuing to operate exactly as before, only with a new title. The first 30 days should reset stakeholder expectations explicitly — what you now own, what has changed, and what you will stop doing personally. The next 30 focus on establishing new decision rhythms and delegating the work that belonged to the previous role. The final 30 consolidate the new remit through visible decisions that only someone at the new level would make.
Done well, this transition prevents the common pattern of a newly promoted professional quietly reverting to being the most reliable expert in their old job, rather than genuinely occupying the new one.