Role design
Stop scope creep before a new role becomes three jobs
Prevent scope creep by giving the role one primary purpose, a limited set of supporting outcomes, and explicit work it does not own. Route every proposed addition through the same test: why it belongs, what capacity it consumes, and what leaves. If the core work or level changes, reopen the brief instead of quietly stretching it.
On this page
Find the role’s centre
Write one sentence describing the problem the role exists to solve. Then group responsibilities that use related capabilities, partners, and decision rights. Work that shares only a department label may not belong together. A coherent centre helps candidates explain relevant evidence and gives the future manager a basis for protecting focus after the person joins.
Name explicit exclusions
List adjacent work that stays with other owners. This is especially useful for new functions where colleagues may assume the first hire will absorb every neglected task. Exclusions are not permanent barriers; they document the current choice. Pair each excluded area with its actual owner or a separate unresolved decision so it does not simply vanish.
Use a capacity exchange
When a stakeholder adds responsibility, ask what outcome becomes smaller, later, or removed. Estimate the attention and new relationships the addition requires. Small tasks can create substantial context switching. Requiring an exchange changes the discussion from whether the task sounds valuable to whether it is more valuable than the work already approved.
Watch for level inflation
Adding strategy, team leadership, execution, and specialist craft can cause managers to raise the title rather than simplify the role. A more senior person still has finite capacity. Check whether one person would realistically enjoy and sustain the mix. If the organisation needs separate owners, design separate decisions instead of searching for a rare all-purpose candidate.
- Does it support the primary outcome?
- Which current work leaves?
- Does the decision scope change?
- Would candidates see one coherent job?
Run the addition test
Illustrative example: a content operations role begins with workflow ownership and vendor coordination. Stakeholders add analytics, campaign strategy, internal communications, and event support. The manager applies the capacity exchange and keeps workflow ownership plus reporting that improves it. Campaign strategy stays with marketing, communications has another owner, and event support becomes a temporary project.
Reconfirm during the search
Review scope after early sourcing conversations and again before final interviews. Candidate feedback may reveal that the combination is unclear, but do not reshape the job around whoever happens to be available. If the primary outcome changes, notify active candidates and reconsider earlier assessments. A clean restart costs time; a misrepresented role costs trust and often creates a difficult first quarter. Keep a short change log with the proposed addition, proposer, capacity exchange, and decision. Patterns in that log reveal which unowned work repeatedly attaches itself to new roles.
Next step
Write the role’s primary purpose and three explicit exclusions, then require a capacity exchange for every new responsibility proposed during the search.