.png)
Diary of a Leader: The Founder Operator Partnership Conversation Most People Never Have
- Lindsay Sheldrake
- 22 hours ago
- 5 min read
Welcome to Diary of a Leader: Real Stories, Leadership Lessons, and Personal Growth
I was talking with a founder a few months ago who was describing her operations manager in a way I'd heard before, just never said quite so plainly.
"She's basically running half the business already," she told me. "I just haven't told her that's what I need from her."
I asked why not.
She thought about it for a moment. "I think I'm worried it'll feel like too much. Or like I'm asking her to be something she didn't sign up for."
So she hadn't said it.
And her operations manager, as far as I could tell from what the founder described, had no idea this was the hope sitting quietly underneath every project handed her way.
Welcome back to Diary of a Leader, where we explore what is really happening beneath leadership, growth, and the structures meant to support both.
This week is about a conversation that almost never happens, and what it costs both people when it doesn't.
What the Founder Wants and Rarely Says
Here's a pattern I see often enough that I no longer think of it as unusual.
A founder hires someone into an operational role. Operations Manager. Studio Manager. Director of Operations. The title is functional. It describes tasks, responsibilities, a lane of ownership.
But underneath the title, there's often something else the founder is quietly hoping for.
They want this person to become someone who thinks at the level the business now requires. Who can hold scope, not just tasks. Who can sit beside them, not just below them. Someone who makes the founder feel like they are not entirely alone at the top of the business they built.
That is a much bigger ask than the job description usually says.
And founders rarely name it directly, because naming it feels like a risk. What if the person isn't capable of it? What if asking for more creates pressure instead of growth? What if the founder is wrong about what this person actually wants for themselves?
So the hope stays unspoken. And the operator keeps doing an operational job, without ever knowing a much bigger one is quietly being offered to them.
What the Operator Senses and Can't Quite Name
On the other side of this, something just as real is happening.
Many operators in these roles sense that more is being asked of them than what's written down. They notice they're being looped into conversations that go beyond their formal scope. They feel the weight of decisions that seem to be drifting toward them, even when no one has explicitly handed those decisions over.
But sensing an expectation is not the same as understanding it.
Without the founder naming what they actually want, the operator is left to guess. Some guess generously and start operating at a higher level, hoping that's what's being asked. Others hold back, worried about overstepping a boundary that was never actually drawn. Either way, they're navigating blind, doing their best to read a signal that was never clearly sent.
This is rarely a competence problem. It's a communication gap, sitting quietly in the middle of one of the most important relationships in the business.
Why This Conversation Is So Hard to Start
If the upside of having this conversation is so clear, why does it stay unsaid so often?
For the founder, naming the hope out loud means admitting how much they're relying on someone else. It means facing the possibility of disappointment, the possibility that the person they've invested in might not want this, or might not be ready for it yet.
For the operator, raising the question themselves can feel presumptuous. Asking "do you see me growing into more?" risks sounding like overreach, especially in a role where staying in your lane has often felt like the safer choice.
So both people wait.
And the business absorbs the cost of that silence, quietly, in the form of missed alignment, unclear ownership, and a partnership that could be much stronger than it currently is.
What Becomes Possible in a Founder Operator Partnership When It's Named
I've watched this conversation happen, on the rare occasions it does, and the shift afterward is hard to miss.
When a founder is honest about what they're hoping for, the operator finally has something real to respond to. They can say yes with clarity, ask questions about what that would actually require of them, or be honest if it's not the direction they want for themselves. Any of those outcomes is better than guessing.
And when the operator's response is heard and taken seriously, something changes for the founder too. The relationship stops being something they're privately hoping will evolve and becomes something they're actively building together.
That shift doesn't require a formal program or a new title.
It usually just requires one honest conversation that most founders have been quietly avoiding.
Reflection Questions
What are you hoping your operator becomes that you've never said out loud?
What would change if you named that hope directly, even imperfectly?
If you're an operator reading this, what have you sensed being asked of you that's never been confirmed?
What is the cost, in your business right now, of this conversation staying unspoken?
Wrapping Up: Say the Thing
Most founders are not bad at communication. They're careful with it, sometimes to a fault, especially when the stakes feel personal.
But some conversations don't get safer by waiting. They just stay unclear for longer.
The founder-operator relationship is one of the most important partnerships inside a growing business. A strong founder operator partnership deserves more than an unspoken hope sitting quietly underneath the day-to-day.
It deserves the conversation.
When You're Ready to Have It
If this resonated, the next step is usually a conversation about where your business is and what would help most.
You can start with a conversation here.
If you recognized your operator in this post, the Trusted Operator Academy was built for exactly this moment. It gives your operator the structure, the language, and the map for the role you're quietly hoping they'll grow into.
Frequently Asked Questions
Why don't founders tell their operators they want them to take on more? Often because naming the hope directly feels risky. Founders worry about creating pressure, overestimating someone's readiness, or facing disappointment if the operator doesn't want that path. It's easier, in the moment, to let the expectation stay implicit.
How can an operator tell if their founder wants them to grow into a bigger role? Common signals include being looped into conversations beyond the formal job description, decisions quietly drifting toward them, or a founder who seems to be leaning on them more than the title would suggest. These signals are real, but they're not a substitute for a direct conversation.
What should this conversation actually sound like? It doesn't need a formal structure. It starts with the founder being honest about what they're hoping for, and genuinely curious about whether the operator wants that too. The goal isn't to assign a new title. It's to replace an assumption with an actual answer.
Continue Reading
If this resonated, these posts go deeper:
Stay tuned for more real-world reflections on leadership, operational clarity, and purposeful growth in the next installment of Diary of a Leader.
