by Rat Race Rebellion November 8, 2026
There’s a particular kind of job description that is easy to recognize once you’ve seen it.
The title sounds reasonable. The company looks credible. Then the responsibilities begin, and they keep going: develop the strategy, manage the pipeline, own the relationships, execute the campaigns, track the results, coordinate with product, support the sales team, keep the documentation current, and step in wherever needed.
Individually, most of those responsibilities make sense. Together, they raise a question the job description itself rarely addresses: Is this one job?
The tension isn’t simply about workload. It’s about something more fundamental – the difference between a role that asks someone to take ownership of a function and a role that asks one person to be the function.
Those are not the same thing. And recognizing the difference matters, both for the people considering these opportunities and the organizations creating them.
Owning the work and doing all the work aren’t the same thing
Accountability and execution are different things, and conflating them creates problems on both sides.
A product manager may own the direction and outcomes of a product without writing every line of code, designing every interface, or conducting every user interview. They’re accountable for what the product becomes. The work required to get there involves people, tools, and functions beyond any single person’s direct capacity.
The same logic applies well beyond management roles. Consider a remote administrative coordinator expected to handle executive scheduling, customer inquiries, social media updates, bookkeeping, and operational reporting. Each of those responsibilities exists somewhere in many organizations. But they don’t always exist together, in one role, for one person, at the same pay grade.
The issue isn’t the breadth itself. Some positions genuinely require someone who can work across different kinds of tasks. The problem emerges when accountability for an outcome becomes an expectation that one person will personally execute every supporting task, regardless of the time, resources, or authority available.
Why roles become overloaded
Job scopes can expand for different reasons.
Sometimes it’s a deliberate organizational choice – a conscious decision to build flexibility into a role, or to create positions that can adapt as a team or business changes. Sometimes it’s the result of restructuring, with responsibilities redistributed rather than reduced after a team contracts. Sometimes it’s a matter of budget constraints limiting hiring, and existing roles absorbing work that new ones might otherwise have handled.
And sometimes, frankly, it’s the result of a job description that has accumulated responsibilities without anyone pausing to consider what that combination actually looks like in practice.
In some situations, a broad role is a reasonable response to genuine organizational conditions. An early-stage company may need people who can move across functions precisely because the infrastructure for specialization doesn’t yet exist, and that experience can be genuinely valuable. But there’s a difference between roles that are broad because the organization has thought carefully about what versatility requires and roles that are broad because the work needed to be somewhere and there was only one place to put it.
When versatility becomes overload
A job that asks someone to stretch is different from a job that asks them to be everywhere at once.
The stretching kind can be genuinely rewarding – unusual exposure to parts of a business that a narrower role wouldn’t offer, the autonomy to make decisions across a wider range of work, and the development of capabilities that take longer to build in more structured environments.
But there’s a subtler problem with roles that combine strategy, execution, and operations that goes beyond the simple volume of work: those three things require fundamentally different kinds of attention.
Strategic work requires space – time to think ahead, evaluate options, and consider what a function should be doing differently six months from now. Execution requires sustained focus on delivering specific outcomes. Operations require responsiveness; something is always needing attention right now.
One person can contribute meaningfully to all three. But when a job is structured so that all three compete equally for that person’s time, the immediate work tends to win. Emails get answered. Problems get resolved. Deliverables get produced.
What gets displaced, often without anyone noticing, is the strategic work the role was supposedly designed to advance. The organization has hired someone to move a function forward and structured the job in a way that leaves little room to do so.
This creates a particular kind of performance problem. The employee is evaluated on strategic outcomes. Their time is consumed by operational responsibilities. When the strategic goals aren’t achieved, is the employee underperforming, or has the organization built competing expectations into a single role and made success genuinely difficult?
That’s a question worth asking before concluding that someone wasn’t up to the job. Employees still have a responsibility to communicate competing priorities. But when those conflicts are visible and remain unresolved, the problem becomes bigger than individual time management.
What an expanding job description can reveal
A long list of responsibilities isn’t automatically a signal of a poorly designed role. What’s more revealing is how those responsibilities are structured.
Who makes the decisions? Who performs the work? What support exists? Which responsibilities take priority when demands compete – and in a role this broad, they will compete? How will success be measured, and against how many different dimensions at once?
A job description that combines strategy, execution, and operations might represent a genuinely interesting leadership opportunity at the right kind of organization. It might also represent a position where no one has clearly defined where one person’s responsibilities end and another’s begin.
The scope alone doesn’t answer that question. The structure does.
A job description can’t tell you everything about how a role operates. But it can reveal where clarification is needed – particularly when expectations span multiple functions without explaining how the work will be prioritized or supported.
The Bottom Line
A well-designed role can be demanding, ambitious, and broad. It can ask someone to learn, adapt, and take ownership of work that stretches their abilities. Professional growth often comes from exactly that kind of challenge, and there’s nothing wrong with pursuing a role that asks you to grow into something bigger.
But ambition alone doesn’t make a job achievable. The expectations have to be matched by the authority, resources, and time available to meet them.
There’s a difference between being given room to grow and being expected to fill every gap.