Stop calling it a programme — that's the first thing I tell any leadership team that asks me about “role expansion”. The moment you build a scheme with a name, a badge and an application form, you've turned growth into a bureaucratic event instead of a daily practice. I don't run role-expansion initiatives with my clients. I redesign how work gets assigned.
Most organisations think the problem is motivation — that people aren't hungry enough to grow. It isn't. The problem is architecture. Roles are drawn as fixed boxes on an org chart, and then leaders wonder why nobody steps outside the lines. You can't coach someone into expanding a role that was designed to be static. You have to change the design first.
That's the reframe this article is built on: expanding roles isn't a reward you hand out to high performers. It's a structural decision about how much latitude every role carries by default. Get the structure right and expansion becomes the normal way work evolves — not a special initiative someone in HR has to keep alive.
Why Most Role-Expansion Efforts Quietly Fail
I've sat in enough calibration meetings to see the pattern. A capable employee starts absorbing more responsibility — covering a colleague's project, owning a client relationship nobody else wanted, fixing a broken process off their own back. Six months later they're doing a materially bigger job for the same title and the same pay. Nobody decided this. It just happened, and then it quietly resents everyone involved.
That's the failure mode nobody names in the generic advice: role expansion done badly doesn't produce growth, it produces exploitation with better PR. The employee either burns out carrying undocumented scope, or leaves the moment a competitor offers to pay for what they're already doing. Either way, the organisation loses the capability it was trying to build.
The fix isn't more encouragement. It's making expansion visible, bounded, and paid attention to at the point it happens — not eighteen months later at a performance review when the gap between job description and actual job has become impossible to unwind fairly.
How I Evaluate Whether a Role Is Actually Expandable
- Decision rights, not task lists: I ask what decisions this person can make without asking permission. If the answer hasn't changed in a year, the role hasn't expanded — regardless of how many new tasks have been bolted on.
- The named-successor test: If nobody else in the building could describe what this person actually does day to day, that's not expansion, that's a single point of failure wearing a job title.
- Scope versus title lag: I look for the gap between what someone is accountable for and what their title implies. A large, unacknowledged gap is the clearest predictor of a resignation letter I've seen.
- Who benefits from the ambiguity: When a role's edges stay deliberately fuzzy, ask who that vagueness serves. Usually it's whoever signs off the budget, not the person doing the work.
- Recoverability: Could this person step back from the expanded scope without the business breaking? If the honest answer is no, you haven't built a bigger role — you've built dependency.
The Real Reason People Stay in Boxes
It's rarely ambition that's missing. In my experience, most people under-reach not because they lack drive but because they've correctly read the incentives around them. Volunteering for more work with no formal change to title, pay or authority is a bad trade in almost every organisation I've worked with — and employees are far better at spotting bad trades than the leadership literature gives them credit for.
I'll say the unfashionable thing directly: asking people to “step up” without changing anything structural around them is not leadership, it's outsourcing risk to the person least equipped to carry it. If you want expansion to be real, the organisation has to move first — with resourcing, with sign-off authority, with a named conversation about what changes if this goes well. Enthusiasm from a manager is not a substitute for any of that.
There's also a trust dimension that gets skipped in most advice on this topic. People expand roles for leaders they believe will notice and credit the expansion. The moment someone senior takes credit for a junior colleague's initiative — and I've watched this kill three separate growth cultures from the inside — the whole organisation recalibrates downward. Everyone quietly returns to the box marked “safe.”
What Actually Works: Designing Roles with Slack Built In
The organisations that do this well don't run a “stretch assignment” scheme bolted onto an otherwise rigid structure. They design roles with deliberate slack — a portion of every role, usually somewhere between a tenth and a fifth of someone's time, that isn't pinned to a fixed task list. That slack is where expansion actually lives, because it gives people room to try something bigger without abandoning what they're already accountable for.
Second, they separate the conversation about scope from the conversation about pay, but they run both conversations on a fixed clock — not “whenever it comes up.” I recommend a quarterly checkpoint specifically about role shape: what's changed, what's been absorbed, what needs to be formally recognised. Waiting for the annual review to catch up on a year of quiet expansion is how resentment gets baked in.
Third — and this is the one most leaders skip — they make the handover explicit. If someone is picking up a bigger piece of work, something else has to come off their plate, or be shared, or be deprioritised out loud. A role can't expand indefinitely in one direction without something giving elsewhere. Naming that trade-off is what separates a genuine expansion from a slow-motion overload.
Fourth, expansion has to be visible to people other than the direct manager. The single biggest predictor of whether an expanded role gets formalised — rather than quietly absorbed and forgotten — is whether more than one person in the leadership chain knows it happened. Make it a standing agenda item, not a private arrangement between two people.
Two Traps That Look Like Progress
The first trap is the title-only fix. A leader notices someone's been doing a bigger job for a while, feels a pang of guilt, and changes the job title without changing the resourcing, the authority, or the pay. This is worse than doing nothing, because it announces publicly that the organisation knows how to reward people cheaply. Everyone watching learns the lesson: expand quietly, get a nicer business card, keep waiting for the raise. I've seen this specific move destroy more trust than an outright refusal to promote would have.
The second trap is what I call phantom ownership — handing someone the responsibility for an outcome without the authority to make the decisions that drive it. It shows up as “you own the client relationship” without any say over pricing, or “you own the project” without budget sign-off. This isn't expansion, it's accountability without power, and people figure that out within a matter of weeks. It's arguably more damaging than not expanding the role at all, because it burns the individual's credibility when things go wrong for reasons entirely outside their control.
Both traps share a root cause: they let leaders feel like they've done something about growth without actually shifting where power sits. Real role expansion always involves giving something up — sign-off authority, budget control, a decision that used to sit two levels above the person now doing the work. If nothing above the role has moved, the role hasn't actually expanded, whatever the new title says.
Where Coaching Fits — and Where It Doesn't
I get brought in when the structural piece is already broken and everyone's hoping a coaching intervention will paper over it. Sometimes it can, partially. Coaching helps a manager get better at noticing expansion in real time, naming it, and having the conversation about pay and title before it curdles into resentment. That's genuinely useful work and I do a lot of it.
But coaching cannot fix a structure that punishes initiative. If your job architecture, your pay bands, or your promotion cycle actively discourages people from taking on more, no amount of coaching the individual manager will overcome that. I've turned down engagements where the client wanted a workshop on “encouraging growth mindset” when the actual problem was a promotion committee that met once a year and required a vacancy to exist before anyone could be considered for one.
The honest diagnostic question I ask every client before agreeing to any coaching engagement on this topic: if your best person expanded their role dramatically tomorrow, is there an existing mechanism to recognise it within the quarter, or would it sit informally for a year? If the answer is the latter, we fix the mechanism first. Coaching people into a broken system just produces better-coached frustration.
A Conversation Worth Having Word for Word
When I coach managers through their first structured expansion conversation, I ask them to cover four things explicitly, in this order: what's changed in scope over the last quarter, named specifically rather than gestured at; what that change means for title and pay, even if the honest answer right now is “nothing yet, and the date we'll revisit it”; what's coming off the person's plate to make room, because expansion without subtraction is just overload with a better story; and who else in the organisation now knows about this, because visibility is what turns a private arrangement into a durable change.
Managers resist this structure at first because it feels bureaucratic for something that's supposed to be organic. I understand the instinct, but I'd push back on it directly: informal recognition is exactly how expansion becomes invisible labour. The structure isn't there to make growth feel corporate. It's there to make sure the person doing more work isn't the only one who remembers it happened six months from now when the pay review comes round.
The other resistance I hear is “but this makes it feel transactional.” My answer is that the current default — vague praise, no timeline, no named trade-off — is already transactional, just dishonestly so. The organisation is extracting more output for the same cost and calling it mentorship. A direct conversation about scope, authority and pay isn't transactional in the bad sense; it's simply honest about a trade that was already happening.
The Distinction I Want You to Take Away
If you remember one thing from this, make it this: role expansion is not a talent problem, it's a design problem wearing a talent problem's clothes. Every organisation I've worked with that struggled to grow people internally had plenty of ambitious, capable staff. What they lacked was a structure that let ambition surface safely, get named, and get rewarded on a predictable timeline.
So the practical shift I ask leadership teams to make is this: stop asking “how do we encourage people to take on more?” and start asking “what in our current structure makes taking on more a bad bet?” The second question is less comfortable, because the honest answers usually point at the organisation, not the individual. But it's the question that actually moves the number.
I'd also push back on the idea that this is primarily an HR initiative. It isn't. It's a line-management discipline — the quarterly noticing, the explicit trade-off conversation, the willingness to change a title before someone else offers to. HR can build the scaffolding, but the behaviour has to sit with the manager closest to the work, because they're the only one positioned to see the expansion happening in real time.
None of this requires a big budget or a formal programme launch. It requires leaders willing to have an uncomfortable conversation on a fixed schedule, and an organisation willing to change a job description faster than its own bureaucracy is comfortable with. That's the whole method. Everything else is detail. Further reading: Why Your Company Works Twice as Hard for 10% More Output.