> Source: https://brendanlevin.com/insights/how-to-give-performance-feedback-as-a-founder/
> Most founders avoid performance conversations because the expectation was never written down. Here is how to structure the feedback conversation, separate an expectation gap from a capability gap, and run the single conversation that either resets or resolves.

For founders, owners, and operators

# How to Give Performance Feedback When Someone Is Underperforming

By Brendan Levin. 20+ years scaling businesses, from teams of 8 to 600 and budgets from startup to $100m.

Before the conversation, write the expectation and the threshold that was missed. Most underperformance is an **expectation gap, not a capability gap**: the person was never given a written standard to be held to. State the gap, ask what got in the way, then agree a specific recovery milestone and a review date. That one conversation either resets or resolves. See [how to build real accountability](/insights/how-to-create-accountability-without-micromanaging/).

Key takeaways

-   Unwritten expectations cannot be enforced: write the standard before the conversation, not during it.
-   Diagnose first: an expectation gap (never told clearly) and a capability gap (told clearly, still cannot do it) need different responses.
-   The feedback conversation has one job: agree a specific, dated recovery milestone, not a general improvement plan.
-   If the same gap reappears after a fair reset, you have your answer and you owe the team a decision.

## Why founders avoid performance conversations until the breaking point

The avoidance is not weakness. It is usually a structural problem. You cannot hold someone to a standard that was never written down, and most founder-led businesses run on informal expectations passed in Slack messages or hallway conversations. When performance slips, the founder either absorbs the work personally or vents privately, because walking into a formal conversation feels unfair when the bar was never explicit.

The fix happens before the meeting. You need one sentence stating what the role was supposed to produce, one number or observable outcome that proves it, and the point at which the gap became clear. Without those three things, the conversation turns into a feelings negotiation and nothing changes. With them, it is just a factual discussion about a gap between what was agreed and what happened.

This is the same structural instinct that breaks delegation generally. [First-time founders](/insights/common-management-mistakes-first-time-founders-make/) often set direction verbally, assume it landed, and then feel blindsided when it did not. Performance feedback is where that habit catches up with you most visibly.

## Expectation gap or capability gap: the diagnosis that changes everything

These two problems look identical on the surface: output is below where it should be. The response is completely different.

An expectation gap means the person did not know the standard, the priority, or the threshold. They may have been doing the wrong thing diligently. This is a management problem first. Before you can hold someone accountable, they need to have agreed to something specific. The conversation here is: here is what I needed, here is what I got, I own the fact that I did not make that clear enough, and here is what I need going forward.

A capability gap means the expectation was clear, the person understood it, and they still could not hit it. That is a different conversation and a harder one. It is not about adding more clarity. It is about whether this person can do this job at this level. [Trust erodes quickly](/insights/how-to-delegate-when-you-dont-trust-your-team/) when the capability gap is real and the founder keeps absorbing the shortfall rather than naming it.

Expectation Gap

Capability Gap

**Root cause**

Standard was never written or agreed

Standard was clear and still not met

**Who owns it first**

Manager, for not making it explicit

Employee, once the standard was fair

**Conversation tone**

Here is what I needed, let us agree it now

Here is what was agreed, here is what happened

**Likely outcome**

Reset with a written milestone

Performance plan or role change

**Timeline to resolution**

One honest conversation plus a review date

Defined window with a go/no-go decision

## How to write the expectation before the conversation

You need three lines, written before you walk in. First: the outcome the role was responsible for, in a single sentence. Second: the measurable threshold that signals the outcome was hit. Third: the point at which it became clear the threshold was missed.

A concrete example. An account manager owns renewal conversations for their account book. The threshold is 90% gross retention per quarter, measured at quarter close. At the end of Q2, retention in their book was 74% and two accounts that churned had not had a check-in call in the prior six weeks. Those three lines are all you need to open a factual conversation. There is nothing to argue about because none of it is a judgment.

If you cannot write those three lines before the meeting, the problem is structural. The expectation does not exist yet and you need to set it, not enforce it. [Setting measurable team KPIs](/insights/how-to-set-kpis-for-your-team/) is the upstream fix that makes these conversations much shorter.

## The structure of the single feedback conversation

Keep this to four moves. State the gap. Ask what got in the way. Agree a specific recovery milestone with a date. Name what happens at that date.

State the gap using the three lines you wrote before the meeting. Do not soften it into oblivion. 'Retention in your book came in at 74% against a 90% threshold, and two of the churned accounts had not had a call in six weeks. That is the gap I want to talk through.' Then stop talking.

Ask what got in the way before you offer any diagnosis. You will learn something. Sometimes the answer surfaces a resourcing problem or an expectation you set that contradicted this one. Sometimes the answer tells you everything you need to know about the capability question. After that, agree a milestone: a specific, observable outcome, with a date, that proves the gap is closing. Not 'improve your client relationships.' Something like: every at-risk account in the book has a logged call by August 1st, and retention in your book is at or above 85% at Q3 close. Then name what happens at the review date. Either the milestone was hit and you move forward, or it was not and you discuss the role. Say that clearly. Leaving it vague is kinder in the moment and unkind in every moment after.

## What happens after the conversation

Send a written summary the same day. One paragraph, no drama. What the gap was, what the milestone is, what the review date is. The writing matters for two reasons: it makes the agreement real for both of you, and it removes ambiguity about what was said.

Check in once before the review date, not to pressure but to surface blockers. If something is genuinely in the way, you want to know now, not at the review. [A standing weekly cadence](/insights/how-to-build-an-operating-rhythm/) with your team makes this feel like a normal operational conversation rather than a special event, which takes a lot of the charge out of it.

At the review date, be honest about what you see. If the milestone was hit, say so clearly and name what comes next. If it was not hit, you owe the person a direct conversation and you owe the team a decision. The longer a clear capability gap goes unaddressed, the more the rest of the team recalibrates their own effort downward. [Accountability without micromanaging](/insights/how-to-create-accountability-without-micromanaging/) depends on the whole team seeing that the standard is real.

## The upstream fix: written decision thresholds so expectations never go missing

The reason performance conversations feel so hard in founder-led businesses is that expectations live in the founder's head and thresholds are never stated until something goes wrong. The structural answer is to write the expectation and the threshold into the role before performance becomes an issue.

For decision-making, this looks like: any client spend adjustment under $2,000, the account manager acts and tells you after. Any adjustment above $2,000 requires your sign-off before it goes to the client. That is a written threshold. The person knows exactly where their authority ends and you are not involved in decisions below the line. When something goes wrong below the line, the conversation is straightforward because the standard was agreed in advance. [Setting decision rights this way](/insights/how-to-set-decision-rights-in-your-business/) is the structural change that makes performance feedback a normal part of running the business rather than a crisis event.

If your business still does not have written expectations and thresholds for each role, that is the gap to close first. The [free Operating Diagnostic](/executive-diagnostic) maps exactly where that structure is missing and what it is costing you.

Feedback lands better when expectations were clear before the work started. The Momentum Engine helps you set those expectations in writing, as part of a wider 12-week operating build.

[See the Momentum Engine](/momentum-engine)

## Common questions

What if I never gave the person a written expectation? Can I still have the performance conversation?

Yes, but you own the first part of it. Acknowledge that the standard was not made explicit, state what it is now, and agree it together going forward. You cannot hold someone to a threshold they never saw. Once the expectation is written and agreed, you can enforce it. Think of this conversation as setting the expectation, not judging the past performance.

How do I know if it is a capability problem or just a motivation problem?

Ask what got in the way before you decide. A capability problem shows up when the person understood the standard, had the resources, and still could not hit it across a fair timeframe. A motivation problem is rarer than founders assume. More often what looks like low motivation is unclear direction, conflicting priorities, or no feedback loop telling the person how they are tracking. Diagnose before you label.

How specific does the recovery milestone need to be?

Specific enough that on the review date, neither of you has to debate whether it was hit. 'Better client communication' is not a milestone. 'Every at-risk account has a logged outreach by August 1st and retention in your book is at or above 85% at Q3 close' is a milestone. If you cannot tell on the review date whether it was met or not, you need to rewrite it.

How long should I give someone to hit the recovery milestone?

Long enough to be fair, short enough to be real. For most output-based roles, four to eight weeks is typical. For a complex deliverable or a role with a long feedback cycle, you may need a full quarter. The test: would a reasonable person have a genuine opportunity to demonstrate the change in this window? If yes, the timeline is fair. Anything longer than a quarter usually means the decision is being deferred, not managed.

What if the underperformance is affecting the rest of the team?

That raises the urgency, not the approach. The conversation structure is the same, but you may compress the timeline. The thing that does the most damage to team performance is a visible gap that leadership does not address. Your team is watching. A clear, fair conversation followed by a genuine reset or a real decision is far better for the team than sustained silence.

Can I have this conversation if I am still working in the business every day alongside this person?

Yes, and it is often harder in that context because the relationship is closer. The structure matters more, not less, in a small team. Write the expectation before the meeting, state the gap using facts, and send the written summary the same day. Keeping it factual protects the relationship because it removes the impression that it is personal.

Related: [how to set decision rights in your business](/insights/how-to-set-decision-rights-in-your-business/) · [how to create accountability without micromanaging](/insights/how-to-create-accountability-without-micromanaging/) · [delegation comes back broken](/insights/delegation-comes-back-broken/) · [how to set kpis for your team](/insights/how-to-set-kpis-for-your-team/) · [common management mistakes first time founders make](/insights/common-management-mistakes-first-time-founders-make/) · [how to delegate as a founder](/insights/how-to-delegate-as-a-founder/) · [more insights](/insights).
