Why Your Best Person Is Burning Out: The True Cost of Role Confusion

TL;DR

When one person owns two fundamentally different functions without clear process and accountability, both functions suffer. Your best person burns out. Your organisation looks disorganised. Your growth stalls.

The solution isn't hiring two people. It's three deliberate decisions: document how decisions get made, separate the thinking in each function, and assign explicit accountability for how they work together.

The cost of not doing this? Much higher than you think.

Here's The Problem

Across organisations, the same pattern plays out: one person ends up managing two completely different functions. Sometimes it's marketing and design. Sometimes it's product and support. Sometimes it's sales and operations.

On paper, it sounds efficient. "One person can handle both. They'll be aligned." In reality, these two functions operate from fundamentally different priorities. Product thinking is strategic. Support thinking is tactical. Marketing thinking is about conversion. Design thinking is about coherence. They're not contradictory. They're just answering different questions with different urgency levels.

When one person answers both questions, something has to give. Usually it's consistency, quality, and the person's sanity. They bounce between two mindsets all day. They make decisions that make sense in one context but create problems in the other. Nobody catches it because one person decided both sides.

The awkward truth: this happens because the company can't afford two specialists. The person is talented and willing to "help with both." So it seems reasonable short-term. Except short-term becomes permanent. And the person internalises the failure instead of recognising the setup is impossible.

What Goes Wrong (The Real Costs)

Bottlenecks That Shouldn't Exist - Every decision flows through one person; progress halts when they're busy
Duplicate Effort Everywhere - No handoff process means work gets redone from scratch months later
Decision-Making Without Full Perspective - One function's priorities win out over the other's legitimate needs
Accountability That Evaporates - The overlap becomes nobody's responsibility, so it becomes nobody's focus
Burnout Disguised as Commitment - Overwork normalised as "dedication"; the person internalises failure
Inconsistency Becomes Your Brand - Standards drift, processes get skipped, your organisation feels disorganised
Poor Scalability - You become entirely dependent on one person's capacity and attention
Credibility Problems - When things look scattered, customers assume you are; trust erodes
The Business Cost - Growth stalls, good talent leaves, customer retention suffers, revenue is affected

The Real Story: What Happens When One Person Owns Two Functions

James is a talented account manager. But he is officially employed as a sales coordinator. His manager, Lisa, runs both Sales and Customer Success. On paper, this makes sense. Lisa's vision is clear. One person driving both. Coherence. Efficiency.

In reality, James watches Lisa make decisions that contradict each other. He sees it clearly. But he is "just a coordinator."

What Actually Happens

Week 1-2: Lisa closes a big deal. It is high-value, with an aggressive timeline. James watches the Customer Success team scramble to onboard them. The implementation is solid, but it skips the customer education program that Lisa approved for all accounts last quarter. James mentions it. Gently. Lisa says: "We need the revenue. Education can happen later." He makes a note. This matters.

Week 3-4: Lisa is in back-to-back sales calls. She makes customer success decisions in Slack without the Customer Success team in the conversation. "Reduce their support tier to save costs." "Assign them a junior resource. They will not know the difference." "Skip the quarterly business review. They are not spending enough." James sees the messages. He also sees the Customer Success team's frustration in their Slack channel (the one Lisa is not in). He is caught between worlds. He is a coordinator. He forwards decisions. He watches things spiral.

Week 5-6: Customer experiences are fragmented. New customers get white-glove service because Lisa wants to close the deal. Existing customers get minimal support because their revenue is already locked in. A customer tweets: "Your support experience is completely inconsistent. New clients get attention. We get ignored." James sees it. He pulls together a customer journey analysis. He documents the inconsistencies. He leaves it in Lisa's inbox. She does not look at it for a week.

Week 7-8: Lisa is stressed. New sales are good (the metrics look impressive). But churn is quietly increasing. The Customer Success team is frustrated. They keep asking: "What is the actual customer success strategy?" Lisa says: "The strategy is new revenue." The Customer Success team knows that is not how retention works. James knows it too. He is just a coordinator. He schedules meetings Lisa does not attend. He takes notes Lisa does not read.

Week 9-10: James starts doing account management work. Unofficially. Lisa is overwhelmed. A key account is at risk of leaving. James reaches out, understands their needs, and proposes a solution that keeps them happy. It is thoughtful, strategic, and focused on the long term. Lisa uses it to save the account. Then she asks him to forecast next quarter's renewal revenue. He does. Then to develop the Customer Success playbook. He does all of it. His actual coordinator work piles up. The data gets messy. Nobody knows what is actually owned by whom. James's name is not on the strategy, so when it works, Lisa gets credit. When there is a Customer Success decision he knows is wrong (skipping business reviews), he cannot speak up because he is "just a coordinator."

Week 11-12: James stops offering suggestions. It is exhausting to see problems and not be empowered to fix them. Lisa is asking him to do more account management work, but he does not have an account manager title. He does not have a budget. He does not have a seat in Customer Success decisions. He is stretched thin: coordinator work and account management and frustrated watching. A new hire asks him what the customer success strategy is. James laughs. Not a happy laugh. The new hire looks confused. James says: "Good question. Lisa probably knows." What he means but does not say: Lisa has been making it up as she goes. She contradicts herself. I can see it. But I cannot fix it.

Lisa notices James is quieter. She assumes he is fine. He is not. He is job hunting. He is looking specifically for roles that say "Account Manager" or "Customer Success Manager" in the title. He is looking for managers who understand the difference between new sales and customer retention. Managers who can hold both priorities without sacrificing one. He is looking for organisations where talented people are not locked in coordinator roles, watching dysfunction from the sidelines with no power to change it.

The cost of this arrangement? Nobody thinks it is a cost because it looks efficient from the outside. Lisa is running two functions. James is picking up account work. The business is moving fast. New sales are healthy. But customer experience is a mess. Churn is creeping up quietly. Nobody really knows what is happening. Talented people are frustrated and job hunting. And the person who could solve this (James) cannot. He does not have the authority to match his responsibilities.

Why This Happens & Why It Fails

The pattern is pervasive, and understanding why helps explain the damage.

How We Got Here

The company can't afford two specialists. The person is talented and willing to "help with both." It seems reasonable short-term. Except short-term becomes permanent. The person gets blamed for outcomes that actually stem from an impossible setup. Nobody discusses it because it's awkward.

Quick tip: Look at your org right now. Who's wearing two hats? If you can't immediately name them, ask your team. They know.

Why It Fails: Conflicting Priorities

When two functions exist in the same person, they answer fundamentally different questions.

One function asks: "What's the long-term strategic move?" The other asks: "What's the immediate tactical need?" Both questions are legitimate. Both matter. But they have different priority orders, and one person can't answer both fairly at the same time.

For example:

Product asks "Will this solve the customer's core problem?" Support asks "Can we resolve this quickly?"
Marketing asks "Will this convert prospects?" Design asks "Is this coherent with our brand?"
Sales asks "Can we close this deal fast?" Operations asks "Can we deliver this sustainably?"

When one person answers both, the urgent one usually wins. Strategy bends to tactics. Long-term thinking bends to short-term pressure. Quality bends to speed. This isn't bad decision-making. It's impossible decision-making.

The Consistency Problem

Here's what most people miss: customers build an impression of you through multiple interactions over time.

If everything feels consistent and intentional, you look professional. If things feel scattered, you look disorganised. And here's the hard truth: if you look disorganised, people assume you are. They assume your standards are loose. They assume you're not worth paying a premium for.

When one person makes decisions for two different functions without clear process, consistency becomes impossible. Standards drift. Decisions get made differently depending on that person's stress level and which function they're thinking about right now.

Quick tip: Ask three people in your organisation what your company's decision-making process is. If they give three different answers, you have a consistency problem.

What Actually Works

Clear roles and process don't require hiring two people immediately. They require being deliberate about how decisions get made. Yes, it takes effort. But it's the kind of effort that pays for itself.

1. Document Your Decision Framework (Three Pages)

This doesn't need to be elaborate. The best frameworks fit on three pages.

Page 1 - How Function A Makes Decisions

Function A Decisions: We ask ourselves:
1. Does this move us toward our strategic vision?
2. Does this solve a core customer problem?
3. Can we execute this in the next quarter?
4. Does this align with how we work?

Priority order when we disagree:
Vision > Customer Problem > Feasibility > Other factors

Page 2 - How Function B Makes Decisions

Function B Decisions: We ask ourselves:
1. Does this resolve the immediate need?
2. Can we implement this quickly?
3. Does this prevent future issues?
4. Can we afford this?

Priority order when we disagree:
Resolve now > Customer satisfaction > Efficiency > Cost

Page 3 - Where They Overlap

When they disagree:
1. Both functions discuss the impact
2. [Whoever has decision authority] makes the call
3. We document the decision and why
4. We measure what happens next

Print it out. Stick it on a wall. Reference it constantly. Update it every quarter based on what you learn.

We've created a free downloadable template at the bottom of this post.

Quick tip: The document itself matters less than using it. Even an imperfect framework used consistently beats a perfect one that sits in a folder.

2. Separate the Conversations

One person can facilitate both conversations. But the thinking needs to be genuinely separate.

Here's what a decision process looks like:

Step 1 - Function A proposes (30 minutes) "Here's what we need and why. Here's the impact on our goals."

Step 2 - Function B responds (30 minutes) "Here are our concerns. Here's what we'd need to make this work."

Step 3 - Agreement (15 minutes) "We're doing this. Here's how we'll handle the concerns. Here's how we'll measure if it worked."

Then execute. Not "one person decides everything for both because they're in the room."

The key difference: both perspectives get heard and documented. Nobody can claim later "we didn't know this would be a problem."

Quick tip: The worst decision happens in silence. The moment you name the disagreement, you've already improved the process.

3. Get Fresh Eyes From Outside

One person's vision is just one person's vision.

Ask someone who's never been inside your organisation: "Does this feel intentional? Or does it feel like we're making it up?"

A new customer will spot inconsistencies the person inside never will. They're not emotionally invested. They just experience the outcome.

Do quarterly reviews with someone outside your team. They'll see patterns you can't.

4. Assign Accountability for the Overlap

Someone needs to be the keeper of "are we handling this well?"

This person's job:

Check in monthly: Are these two functions working together smoothly?
Spot inconsistencies before customers do
Document learnings
Suggest improvements

It doesn't have to be full-time. But it needs to exist as someone's actual responsibility. Otherwise it's everyone's and nobody's.

Quick tip: If nobody can name who's accountable for the overlap, you have your answer.

5. Plan for the Handoff

While one person still owns both, document everything they do. Not in their head. On a wiki. In runbooks. In decision logs.

Two reasons: when you hire the second person, you have a playbook. If the first person leaves, you don't have a catastrophe.

Also, the act of documenting clarifies what's actually happening. You might realise half of what they do could be automated, delegated, or eliminated.

What Happens If You Don't Address This

The degradation is not linear. There is no magic moment when things break. It is messier than that.

First few weeks: Everything seems manageable. The person is working hard, staying late sometimes. Metrics still look okay. Nobody sees a problem yet.

Month 2-3: Small inconsistencies start appearing. A customer notices something does not feel right. The person is checking email in the evenings. They mention being "a bit stretched" but they are handling it. Their manager assumes they will adjust.

Month 4-6: Things slip. A deadline gets pushed. A quality issue appears that should not have. The person is quieter in meetings. They decline social events. They are not sleeping well. They mention having trouble focusing. Their manager thinks they might be struggling with the role. They do not realise the role itself is impossible.

Month 7-10: The person is job hunting. You do not know it yet. They are still showing up, still trying, but they are disengaged. They stop suggesting improvements. They stop staying late. They do the minimum because they are conserving energy for interviews. A key customer mentions the experience has felt "inconsistent lately." Performance reviews show decline across the board. Attrition creeps up in the team.

Month 11-12+: The person leaves, or they stay but they are not really there. Growth stalls because decisions take forever and lack direction. Your best people have left because leadership is unclear. New hires are confused about how things actually work because nobody documented anything. Customer retention is quietly degrading.

By the time you notice the real problem, you have already lost momentum, lost knowledge, lost credibility. You will spend 40-80k GBP hiring and training a replacement. You will spend months rebuilding what eroded slowly over time.

The "temporary" solution became permanent. And it cost way more than hiring a second person would have.

Real Example: How One Company Fixed This

A B2B SaaS company had one person owning both marketing and design. The to-do list was neverending. Brand consistency was suffering. The marketing person was working weekends. The designer was frustrated.

Here's what they did:

Named the conflict: Marketing prioritises conversion. Design prioritises coherence. Different questions.
Created a one-page framework:
- Brand consistency non-negotiable
- Conversion wins if it doesn't break brand
- Quarterly design system update (gives Marketing consistent building blocks)
Built a process:
- Marketing briefs Design on campaign needs
- Design proposes how to execute it
- They iterate (30 min sync)
- Execute
Assigned accountability:
- Marketing: campaign performance
- Design: brand coherence
- Manager: make sure they're not fighting

Result? Marketing campaigns launched faster. Brand stayed coherent. The marketing person stopped working weekends.

Cost? Zero. Same budget. Different structure.

The Bottom Line

One person can absolutely help with a second function. One person can even make some decisions in both areas. But one person shouldn't be the sole decision-maker for two fundamentally different functions without:

Clear documentation of how decisions get made
Separate thinking in each domain
Explicit accountability for the overlap
A plan for eventual separation

When you skip these, your organisation doesn't feel intentional. It feels like you're making it up as you go. And in business, that's the opposite of trustworthy.

If you're running a small team, you probably don't have the luxury of separate specialists. That's fine. That's real. That's temporary.

But be intentional about how you work around it. Document. Separate the thinking. Get feedback from outside. Assign accountability.

Because your credibility, your ability to scale, your capacity to serve customers, and the wellbeing of the person doing the work all depend on it.

And here's the hard truth: the person doing this work is probably your best person. They're capable, committed, willing to help.

Don't burn them out on an impossible setup.

Fix the setup. Free them to do their best work.

Next Steps

Identify who's wearing two hats - What two functions is one person managing?
Have a conversation - "We know this is hard. Let's make it easier."
Create one document - Your decision framework
Try one process - Use it on the next decision that touches both functions
Measure what happens - Did it save time? Reduce stress? Improve quality?

This isn't about being perfect overnight. It's about being intentional.

Start with one conversation. See what changes.

You might be surprised.

Blog header photo by Tim Gouw on Unsplash