You’ve delegated well, coached thoughtfully, and set clear expectations. So why is the work still not delivered? It’s a common founder frustration, and one caused by a tangling of many interrelated factors. Unravelling the answer starts by diagnosing the real problem first.
I’m sure most founders reading this will recognise the situation: you’re sitting at your desk late at night, doing the work you delegated three weeks ago for the pitch / investor meeting / application deadline [delete as appropriate] tomorrow.
It comes with waves of frustration: you delegated the work, you had the 1:1s, you set clear expectations. You’ve tried to be clear, supportive, and human. Yet here you are, rewriting the work because what was delivered is… well, not quite right. Or technically fine but somehow not what you meant. Or the deadline passed… again.
And alongside those frustrations, the self-critique begins: “I need to hold them more accountable”.
Yet accountability feels different as a founder.
In theory, it sounds simple: set expectations, review outcomes, address gaps. But as a founder it’s messier. You may have delegated the task, but you’re still emotionally attached to the outcome – you care about how it’s done, not just that it’s done – and you can intuitively see second‑order consequences that others can’t. Those outcomes reflect on you – as a leader, as a founder, as a person – such is the complicated boundary-blurring life of leading as a founder.
Those late night redos result in a heavier question too: At what point is this on them, and at what point is this on me?
That question has uncomfortable consequences: There’s a point (that many founders grapple with) when the second chances need to end, and you need to part ways. But getting there makes us question if we’ve done enough to stand behind the decision.
It’s messy. It’s head and heart. So let’s look at ways to approach it.
The TLDR for you…
Diagnosing your delegation vacuum
It’s common to hear claims that “founders don’t delegate” – but it’s not as accurate as the reputation will have us believe. I’m not denying we have some unique challenges and common traits that make it less intuitive(!), but anyone beyond a team of about five has usually gotten pretty good at delegating. We’ve built a team, stopped doing everything ourselves, learned to let go (sometimes), granted autonomy and even managed to lean on those coaching skills we practise so much in FounderCircles!
The real challenge is that delegation creates a vacuum behind it. We hand over the what, why and when. Then wait.
In the three weeks between “great, they’ve got this”, and the deadline, is the accountability gap—that space between delegating the task and getting it delivered (and delivered at the level you need.)
Hiding in that gap is the information we need to understand where delegation is falling down. To fix accountability, we need to understand what’s actually going wrong in the gap:
- Is it a clarity problem?
- Is it a context problem?
- Is it a motivation problem?
- Is it a capability problem?
Really sense check clarity and context
Clarity: did I actually set expectations?
Before we interrogate the integrity of the person responsible for the task, we need the humility to ask the uncomfortable question first – was I really clear on what was needed? (and this is key if we can have confidence to act and initiate a parting of ways later).
We all think we’re being clear – especially if we wrote it down – but that doesn’t necessarily lead to clarity. Let’s have a little play…
We’ve all seen the pictures below and been asked “what do you see?”
Some say old woman, others say young woman.
For this image, I’ve had auditoriums of founders shouting at me “Candle stick!” and “faces!” at the same time, then arguing about what is there. We don’t always see what others see.
That said, it’s quite common to agree we can ‘see’ different things. And many a technical founder has said “and that’s why I write everything down”. I agree that is a solid start, but not infallible. Let’s play again…
“I never said she stole my money”
That sentence has seven words. It also has seven meanings – depending on where you put the tonal emphasis… go ahead – try it.
Clarity is not as easy as we think.
As founders this is particularly hard: first, the pace and breadth that we operate at leaves less reflection and clarifying time. Second, we have context that others don’t. It could be company-context – from wearing every hat – or problem-context from living and breathing it for months. Either way, it’s easy for us to assume others get it as much as we do.
Clarity doesn’t have to stray into micromanagement. It’s about removing guesswork where it matters by having a conversation.
Clarity tools
The 3Cs of clarity can be a useful framework for checking if the conditions for effective delegating are present first, and there are some critical nuances for founders:
- Context:
- Why this matters (critical for founders, as it might really matter to you)
- How it fits the bigger picture,
- What success enables
- Constraints:
- What is non-negotiable vs. where there is freedom
- What is the quality bar? (critical for founders: is it a “perfect” or a “70% is good enough” job?)
- Check-in approach:
- When and how will you review progress? (also critical for founders, as this is directly tied to your perception of risk, interest and skill-level)
Our effective delegation brief can be a useful tool to build this out and do the pre-delegation thinking. But the brief is only the starting point, not the finishing line. We can’t assume we’re on the same page, we need to clarify you’re aligned.
This makes a conversation invaluable: a starting point is to ask them to play back what they’ve understood. “So just to make sure we’re aligned, can you tell me what you’re going to deliver and by when?” I’d also dig a little deeper, to get their initial thoughts on next steps. This helps surface any misalignment or complete “I’m lost” blockers, that can be corrected there and then.
The level of clarity (or your confidence in the clarity) can then govern how much you want to lean in or lean out – which ties back to the critical final question for founders in the delegation brief around the Check-in approach.
Context: did I create the conditions to succeed?
Context features in the 3Cs, but there’s an additional aspect of context that crops up: the contextual conditions.
In the delegation vacuum a lot happens in the weeks between delegated and delivered, and your Check-in approach is key to closing that vacuum. This is tough on founders, because we have that “you’re micromanaging / rubbish at delegating” voice nagging in your mind, and don’t want to fall into that space. Yet you still own the outcome, so finding the right balance is key (and probably different with different people).
Hiding in those check-in moments is all the information you need to understand where tasks, projects and people are getting stuck. This is where the contextual conditions crop up:
- Do they have authority to make the decisions needed? > people or structures could be a blocker here
- Are they encountering competing priorities with others? > people or projects could be a blocker here
- Do they have agency to manage their own priorities? > overwhelm and over-commitment could be creeping in here.
Everyone in your team operates as a part of the system. Sometimes it is the system and the processes that are blocking the ability to deliver, other times it is personal challenges – like not being able to say no to things and reprioritise. Once you understand this context, you can work together to unblock it in ways they maybe can’t.
Capability: is this a skill gap or a will gap?
Dissecting Can’t vs. Won’t
When someone isn’t delivering, it’s tempting to assume a lack of effort. In fact, it’s so common to do this that Hanlon’s razor emerged as a mental model to counter it:
Never attribute to malice that which is adequately explained by competence
Picking up on assumptions we make is helpful in unpicking what is happening when accountability is falling down. If we’ve covered clarity and context, we need to assess whether the real gap is a Skill gap or a Will gap:
- Skill gap: they don’t yet have the capability, experience, or confidence to deliver at the level required
- Will gap: they’re capable, but not engaging fully – motivation, ownership, or priority is missing right now
These require very different responses. Training and coaching can help with skill. Coaching, clarity and consequences can address will. Confusing the two keeps everyone stuck, and can waste weeks and months of time and energy. Setting stretch goals for someone who lacks the capability, and you’re expecting magic. Push harder on someone who’s burned out, and you’ll lose them.
The Skill/Will Matrix
The Skill/Will Matrix, developed by Max Landsberg, in his book The Tao of Coaching, let’s you consider where someone might be on two axes:
- Skill: Their competence, capability, and experience to do the task
- Will: Their motivation, confidence, and drive to actually do it
This gives you a lens to think about the accountability challenge you’re encountering. The matrix creates four distinct quadrants, each with its own characteristics and response:
I like to think of this as a starting point: you can’t know what is going on with them – but you can use coaching-style one-to-one conversations to surface the challenges and motivations.
To assess Skill, consider:
- Have they done this successfully before?
- Do they have the technical knowledge required?
- Can they articulate a plan for how to approach it?
- When they struggle, is it conceptual understanding or execution?
To assess Will, consider:
- What could be going on for them inside or outside of work?
- Do they proactively engage or avoid the work?
- Are they asking questions and seeking help?
- Do they show energy and commitment when discussing it?
Low Skill tools
Common situations: They’re eager, motivated, trying hard, but they just don’t have the capability yet. This is your junior hire who’s hungry to learn, your career-switcher who brings great attitude but not the technical chops, your early team member now facing challenges beyond their current level.
- Provide structured task-related training to close the knowledge gap.
- Use regular coaching in your one-to-ones – using frameworks like GROW – to build confidence and break down barriers quickly.
- Break down complex tasks into smaller chunks they can successfully complete, which also builds confidence through small wins.
- Pair them with mentors on the team or let them shadow someone who does the task well.
- Increase check-in frequency early on, then gradually reduce as they build capability
Timeline: Give it 4-6 weeks with clear milestones. If you’re seeing progress and learning, keep investing. If not, reassess what might be blocking accountability. A red-flag would be if they’re not asking questions and seeking help – then it might be a mindset or will problem.
Low Will tools
Common situations: You believe they can do this – you’ve seen them deliver before – but something’s off. Maybe they’re going through the motions, missing deadlines or producing work below their capability.
First, investigate the root cause with them:
- Are they bored? (task is too routine, not challenging enough)
- Is there misalignment? (they don’t see how this connects to what they care about or the company mission)
- Are they burned out? (too much on their plate, need recovery time)
- Is something happening outside work? (personal circumstances affecting energy)
- Have you changed as a leader? (your behaviour might be demotivating them)
Then, consider the motivation framework:
- Challenge (mastery): Give them something meaty that stretches them
- Meaning: Reconnect them to the why – be it how the task impacts customers, the mission, or even their growth
- Autonomy: Give them more control over the how, delegate the outcome not the method
Timeline: In truth, this depends on the root cause – but it’s likely you’d like to see an adjustment in a few weeks, or at least have closer contact to understand external conditions causing issues. A red-flag would be if they can’t articulate what’s going wrong or blame everything externally (the team, the market, you) without taking ownership.
Building accountability IN, not bolting it on
The nuances of accountability demonstrate that it isn’t something we can add at the end when things go wrong. It’s something we build into the structure from the start. We need to create a system that makes accountability easier.
Think of accountability as a continuous loop, not a one-time handoff:
- Brief: Set clear expectations using the 3Cs (Context, Constraints, Check-in) – the brief template can help
- Check-in: Review progress at agreed points, catch issues early when they’re small and course correct
- Coach: Utilise coaching-style conversations to work through blockers and challenges, which keeps you away from micromanaging, but still making progress
- Review: When it’s done, reflect together on what worked and what didn’t for next time.
The key is that check-in approach. Don’t say “let me know if you need anything” and disappear for three weeks. That’s not delegation, that’s abdication. The odds are stacked against everyone in that situation.
The difficult decision: when to move them on
Let’s talk about the elephant in the room, that weighs on many founders’ minds: when do you actually move someone out?
It’s hard as a founder because we want to believe in people. We’ve seen potential. We’ve invested time. We care about them. And the idea of having that conversation feels awful.
But here’s what I’ve learned from founders who’ve navigated it: the decision point isn’t about giving up on someone – it’s about being honest about fit. And hanging on too long usually leads to regret.
This is where the accountability loop can help build confidence in the decision: Before you have the coaching-out conversation, you need to be able to honestly answer yes to these questions:
- Have I set clear expectations (in writing) and clarified understanding?
- Have I provided specific, timely feedback with concrete examples?
- Have I offered support, resources, or training to help close the gap?
- Have I given them a reasonable timeline to improve?
- Have I documented these conversations?
If you can’t answer yes to all of these – there might be a bit more to do before you can confidently make the call.
So, what’s your next move?
Let’s come back to where we started – that team member who’s not delivering.
You now have a framework to diagnose what’s actually happening. Is it a skill gap? A will gap? Both? Or did you miss the clarity step? Each diagnosis leads to a different response, and trying to solve for the wrong one wastes time.
To wrap up:
- Accountability isn’t something you add later, it’s built into how we delegate from the start
- Before fixing accountability, diagnose the real problem – considering Clarity, Context and the Skill/Will Matrix
- Different gaps require different responses—guide, excite, direct, or decide
- Before moving someone on, run through the diagnosis to understand where things are falling down
- Build accountability loops into your delegation structure – to set yourself up for an easier journey from the start.
The hard truth? Sometimes people are in the wrong role at the wrong time. The kindest thing you can do – for them and for you – is acknowledge that honestly and quickly.
Other FounderFuel articles on a similar theme
The simple questions that can set you free as a startup leader (coaching frameworks)
5 simple questions to empower and delegate effectively as a founder (the brief framework)
Motivating others and creating a culture of continuous improvement
How to let go and delegate as a founder – whether you employ 1 or 100 people
How to have those difficult conversations and unlock potential
The art of bringing people with you, with communication frameworks
