The Role That Grew Without Being Redesigned: How to Recognize When a Position Has Outpaced Its Original Purpose

Most roles in a mature organization were designed once, at a specific moment, to solve a specific problem. A head of partnerships was chartered when the company had two channel relationships. A director of operations was scoped when the team had forty people. A senior strategist was hired to support one executive during a particular planning cycle. The role made sense then. The question worth asking periodically is whether it still makes sense now.

What changes is rarely the title or the reporting line. What changes is the actual work: what gets routed to that person, what decisions land on their desk, what relationships they are expected to maintain, and what the organization implicitly holds them accountable for. This accumulation is gradual enough that no single addition seems significant. But over eighteen or thirty-six months, a position can shift substantially from its original design without anyone formally acknowledging the shift.

The friction this creates is real and recognizable. The person in the role operates at the edge of their defined authority constantly, because the work has grown past the authority that was ever granted. Their peers are uncertain which decisions belong to them. Their direct reports receive guidance that conflicts with direction from adjacent functions, because the scope boundaries were never updated. The role occupant may feel perpetually under-resourced, not because the budget is wrong, but because the resourcing was calibrated to a smaller, earlier version of the position.

What Role Drift Actually Looks Like

Role drift rarely announces itself. Instead, it tends to surface through symptoms that appear to be people problems or communication problems when they are actually structural problems.

Consider a hypothetical: a director of customer success who was hired to manage a small team focused on onboarding. Over two years, that director absorbed responsibility for renewal forecasting, executive relationship management, and cross-functional escalation handling. None of these additions came through a formal redesign. Each one arrived as a practical response to a gap that existed and a person who was capable of filling it. The role now requires substantially different skills, carries substantially greater organizational influence, and demands a level of cross-functional coordination the original job description never contemplated. If the formal definition of the role has not kept pace, several problems follow: compensation conversations become difficult to conduct fairly, succession planning produces candidates calibrated to the wrong scope, and the director operates without the formal authority their actual work requires.

Three Questions That Reveal Whether a Role Has Drifted

A useful diagnostic does not require an external assessment. It requires honest answers to three questions.

First, if you compared the written job description or the original scope document for the role against what the person actually does in a given week, how large is the gap? If a substantial portion of the real work would not appear in the formal definition, the definition is outdated. This is worth examining not just for the person currently in the role, but for what the organization would communicate to a replacement if the seat became vacant tomorrow.

Second, does the person in the role have the authority to make the decisions the role actually requires? Authority that trails scope is a consistent source of organizational friction. It forces the role occupant to either seek approval for decisions their scope implies they should own, or to act without clear authorization and absorb the political cost of doing so. Neither outcome serves the organization.

Third, do the people who interact most regularly with this role share a consistent understanding of what it covers? If peers and cross-functional partners hold materially different views of what the role is responsible for, the ambiguity will generate conflict that looks interpersonal but is actually structural. A brief, informal audit of how adjacent leaders describe the role's scope can surface this quickly.

How to Approach the Redesign Conversation

Recognizing that a role has drifted is the easier step. Addressing it requires a conversation that most leaders avoid because it feels like reopening something that was settled. The practical reframe is that the original design was not wrong; the organization simply changed around it, as organizations do.

The most productive starting point is a scope mapping exercise conducted with the role occupant and their direct supervisor. The goal is not to evaluate performance but to document, as concretely as possible, what the role currently does, what authority it currently exercises, and what relationships it currently maintains. This documentation becomes the basis for a deliberate decision: whether the role should be formally redesigned to match its current reality, or whether some of the accumulated scope should be redistributed to better align with organizational structure.

Both outcomes are legitimate. Sometimes the right answer is to expand the formal definition, update the authority level, and ensure resourcing reflects the actual scope. Sometimes the right answer is to recognize that the role absorbed work that was never meant to be permanent, and to return that work to its appropriate home. The important thing is that the choice is made explicitly rather than left to drift further.

The Succession Risk Inside the Drift

One consequence of role drift that receives insufficient attention is what it does to succession planning. When a role has grown significantly beyond its formal definition, the organization may believe it is preparing successors for the documented version of the position while the actual work requires something substantially different. A candidate who looks well-prepared on paper may be underprepared for the real scope. A leader who is calibrating development assignments to the formal job description may be developing people for a role that no longer exists in its original form.

Updating role definitions is not a bureaucratic exercise. It is a practical act of organizational accuracy. It ensures that compensation benchmarking reflects the real work, that performance expectations are anchored to the right scope, that succession pipelines are built for the position that actually exists, and that the person in the role has formal standing that matches their actual responsibility.

The roles that cause the most organizational confusion are rarely the ones that were poorly designed at the outset. They are the ones that were designed well for an earlier version of the organization and never revisited as the organization grew. A periodic review of whether formal role definitions still reflect operational reality is among the quieter forms of structural maintenance that compound in value over time.