It’s annual review time. You’ve called in a high performer, someone you genuinely thought was crushing it. Halfway through, you mention something about “consistency issues” or “missing the bigger picture.” 

Her face drops. She looks genuinely shocked. 

Then comes the question that cuts:

“But nobody told me this was an issue.”

That moment. That silence. That’s when most founders realise the uncomfortable truth: you’ve been silent for 364 days, and now you’re springing judgment like it’s a surprise party nobody wanted.

Here’s the truth nobody tells you: if a performance review holds surprises, you’ve failed at leadership 364 days a year.

The problem isn’t her performance. It’s your standards. They exist perfectly clearly in your head, you can see exactly what “good” looks like, exactly where her output misses the mark. But she can’t. Your team can’t. 

They’re operating in the dark, guessing at invisible expectations, while you’re stewing silently, building resentment.

This is the founder trap. You’re conflict avoidant, most smart ones are,  so you avoid the hard conversation. You let it sit. You convince yourself it’ll resolve itself or that she “should just know.” Meanwhile your anxiety compounds, your team’s confusion compounds, and by annual review time you’re both shocked: you because the problem persists, them because they’re hearing it for the first time.

The cost is that high performers dial back effort when standards are invisible. Mid-performers plateau because they don’t know how to improve. New hires take months longer to hit your bar. And your best people leave because they’re tired of operating in ambiguity.

This isn’t a feedback problem but a standards problem. And it’s solvable, not with better conversation skills or improved annual processes, but with a system that replaces “you should just know” with explicit, observable clarity.

Three Pillars That Replace “You Should Just Know”

Most owners manage performance the way they learned it, implicitly. You do good work, I don’t say anything. You miss the mark, I mention it. Maybe. 

After I’ve stewed on it for three weeks. Every person on your team interprets “good” differently. You end up with three versions of excellence, none of them yours.

Here’s what needs to change: your implicit standards need to become visible. There’s a proven structure to make that happen.

Pillar 1: Observable Standards Translation

The problem: “Not good enough” isn’t a standard. It’s an abdication. When you tell someone their proposal is “off” or their report “feels incomplete,” you’ve outsourced the real feedback to their ability to read your mind. That’s not fair. It’s also not effective.

The method:

Step 1: Identify your top three pain points. 

Where does your team most often disappoint you? Not catastrophically, consistently “not quite right.” Client reports missing context. Project briefs that don’t tie back to strategy. Emails without clear next steps. 

Pick the three where you find yourself saying “something’s off” most frequently.

Step 2: Observe the gap, not the feeling. 

Most owners describe the problem as a feeling:

• “This report feels incomplete” — judgment, not observation
• “The brief isn’t compelling” — judgment, not observation

Instead ask: what is specifically missing or wrong?

Not: “This report feels incomplete.” Yes: “This report is missing client context in the opening, recommendations aren’t tied to specific data points, and there’s no clear next steps section.”

Now you’ve moved from judgment to description. Concrete. Actionable. Observable.

Step 3: Build your example library. 

For each deliverable, collect or create three versions:

• Subpar: what does it look like when it misses the mark?
• Meets standard: what does solid look like?
• Excellent: what does exceptional look like?

Annotate each one. Show your team exactly where the gaps are and where the strengths are. When your team sees these side-by-side, they don’t have to guess. They have a visual target.

Step 4: Share the library before work begins. 

Don’t wait until someone submits a report to show them what excellent looks like. Send your example library before the deliverable is due. Attach it to the brief. Reference it in the kickoff.

“Here’s what a meets-standard proposal looks like for us. Here’s what exceeds standard looks like. Use these as your guide.”

Now your team has a checklist built into the visual example. They’re not guessing.

Pillar 2: Behaviour vs. Person

The distinction that changes everything:

Here’s where most feedback goes wrong. You conflate behaviour with character:

• “You’re disorganised” — judgment about the person
• “You’re not a strategic thinker” — assessment of their capacity
• “You’re not a team player” — judgment about character

Your intention is to correct. What actually happens? Your employee hears “there’s something wrong with me.” Shame activates. Defensiveness follows. The feedback doesn’t land.

Compare that to behaviour-focused feedback:

• “Your project files weren’t tagged consistently last week, so I spent 20 minutes finding the latest version”
• “Your recommendations in the strategy brief didn’t include the business case analysis we discussed in the kickoff”
• “You’ve sent three emails this week without a clear summary of decisions or next steps, which meant the client had to follow up for clarification”

These aren’t judgments about the person. They’re observations about what happened. Fixable. Actionable. Shame free.

The Observe-Impact-Suggest framework:

Step	What you do	Example
Observe	State the specific behaviour or deliverable issue	“I noticed the client handoff doc didn’t include their preferred communication channel”
State Impact	Explain what consequence that created	“This meant we reached out via email when they prefer Slack, delaying their response by a day”
Suggest	Offer a concrete alternative for next time	“Use the pre-submission checklist, it catches contact preference gaps before it goes to them”

You can deliver this in 60 seconds. The feedback lands quickly, softly, and sticks because it’s not about who they are, it’s about what they did and how to adjust.

Pillar 3: The No-Surprises Weekly Rhythm

The problem with annual check-ins:

Quarterly reviews are too infrequent. Issues compound, You stew silently, Your team is unaware. By the time you meet, three months of frustration is sitting on the table. The conversation feels heavy. You’re delivering judgment, not coaching.

The solution: 60 seconds per week, per person.

Each week, carve 10 minutes per direct report for a micro check-in. Not a formal sit-down. Not a big deal. Just 10 minutes. One piece of feedback, corrective or developmental, plus one recognition. Use the Observe-Impact-Suggest framework. 

Keep it specific, timely, brief.

Your team gets feedback every week. They know where they stand. There are no surprises at annual review time because you’ve been transparent for 52 weeks.

What the weekly rhythm looks like:

Monday–Thursday, 60 seconds: brief, specific, timely. 

One corrective observation. One recognition.

Example: “I noticed the client deck you sent Friday didn’t have the competitive comparison we discussed. This made them ask about how we stack up in the call. Next time, reference the pre-submission checklist before sending. But I appreciated how you handled their question, you turned it into a conversation about our positioning.”

That’s 60 seconds. Two pieces of information. The person knows what went wrong and what went right.

Monthly, 20–30 minutes: a deeper calibration session. Walk your team member through your judgment framework. Show side-by-side examples. Narrate your thinking: 

“Notice how the excellent version includes a case study from our files? That’s intentional. 

That gap, that’s what I’m looking for.”

This is judgment transfer. You’re not just telling them what to do. You’re teaching them how you think about quality. Over time, they internalise your standards and start catching their own gaps before you do.

What happens over 12 weeks:

• Weeks 1–2: your team notices the new rhythm. Slightly nervous, but feedback is delivered without shame so it’s digestible.
• Weeks 3–5: patterns emerge. They’re connecting weekly feedback to the observable standards you’ve shared.
• Weeks 6–8: self-assessment improves. You’ll notice people asking: “Does this meet the standard, or does it need the extra element?”
• Weeks 9–12: the magic moment. Your team starts catching their own gaps before you mention them. 

You hear: “I know this is missing X, I should add that before I send it.” Your leadership burden lightens.

Your 30-Day Clarity Build

Days 1–7: Identify and translate your top three deliverables

Write down the deliverables where your team most often disappoints, where you’re always saying something’s off but never spelling out what. 

Pick three.

Then translate your internal judgment into observable, describable criteria. 

Wrong: “this report feels incomplete.” 

Right: “this report is missing client context in the opening, recommendations aren’t tied to specific data points, and there’s no clear next steps section.”

For each deliverable, collect or create three versions, subpar, meets standard, excellent. Label them. Annotate them. This is what you share with your team before they start the work.

Days 8–14: Build your pre-submission checklist and recognition system

For each of your three deliverables, create a one-page checklist your team uses before submitting work to you. 

Five to eight items maximum. Longer checklists become ignored.

Also identify eight categories where you want to acknowledge good performance: output quality, output speed, teamwork, communication, initiative, learning, self-correction, and resilience. 

Pick two or three to focus on this month. Set a goal: one recognition per person per week.

Days 15–21: Run calibration sessions and teach the framework

Schedule 20–30 minutes per person. Show side-by-side examples. Narrate your thinking, not just what to do, but how you think about quality. Let them ask questions.

Then teach the Observe-Impact-Suggest framework explicitly. 

Explain that this is how you’ll be giving feedback going forward. Make it your universal feedback language.

Days 22–30: Launch the weekly 10-minute rhythm

Block 10 minutes per direct report every week. Same day, same time, Friday afternoon works well. The week is closing, you’re both fresh on what happened, and feedback lands while it’s relevant.

Each check-in follows the same structure: Observe (15 seconds), Impact (15 seconds), Suggest (15 seconds), Recognition (15 seconds). 

Track your commitment: one corrective observation and one recognition per person per week. By month two, you’re rotating through different recognition categories systematically. Recognition stops feeling random and starts feeling strategic.

What Actually Changes

For you: your anxiety drops. You’re not stewing silently, replaying conversations, wondering if you were too harsh or too soft. Feedback happens weekly in 60 seconds. It’s done. No more dreading the annual review because there is no annual review, there’s just a confirmation of what everyone already knows. Decision making becomes consistent because you have a framework.

For your team: they stop guessing. They know exactly where they stand every single week. Feedback stops feeling like judgment and starts feeling like coaching. High performers feel genuinely recognised with specific acknowledgment, not hollow praise. New hires stop burning 12 weeks figuring out your culture, they get the playbook on day one and hit your bar 4–6 weeks faster.

For your business: consistency becomes your competitive advantage. Output isn’t wildly variable anymore because your standards are explicit. Work quality becomes predictable. Retention stabilises. Your best people stay because they’re not lost in ambiguity. 

Mid-performers don’t plateau because they can see exactly what separates “meets standard” from “excellent.”

What changes is that you stop being the person who hoards standards and doles out judgment once a year. You become the person who makes success visible, attainable, and repeatable. 

That’s the difference between a business held together by your anxiety and a business held together by clarity.

Frequently Asked Questions

1. What if I give weekly feedback and people become dependent on constant reassurance?

The goal is the opposite. Weekly feedback is training wheels, temporary scaffolding while your team internalises your standards. By weeks 9–12, you’ll notice people self-correcting before they submit work. The check-ins get shorter because there’s less to cover. You’re building independence, not dependency. If someone is still seeking constant reassurance at month three, that’s a different conversation, about their confidence, not your system.

2. What if the person gets defensive even when I use the Observe-Impact-Suggest framework?

Defensiveness usually means one of two things: either the feedback feels personal despite the framing (check that you’re describing behaviour, not character), or there’s a trust deficit from months of unaddressed issues arriving at once. The second one takes time. Keep the feedback specific and behaviour focused. Over three to four weeks of consistent, shame free delivery, defensiveness typically dissolves. If it doesn’t, you’ve likely got a deeper fit issue that no feedback framework will solve.

3. I manage people doing very different roles. How do I build observable standards across all of them?

Start with one role. Build the example library for your highest-pain deliverable in that role, then move to the next. You don’t need all of it built before you start. One annotated example is infinitely better than nothing. Most of the Observe-Impact-Suggest framework applies regardless of role, you’re always describing specific behaviour and specific impact. 

The example library is role-specific; the feedback framework is universal.

4. How do I handle a long-term team member who’s been coasting under the old vague system?

Carefully and explicitly. Don’t ambush them with the new standard, that’s the same problem in a different wrapper. Sit down, show them the example library, and have an honest conversation: “I haven’t been clear enough about what good looks like. Here’s what I mean by excellent. Here’s where your recent work sits. I want to help you get there.” Give it 30 days under the new system before drawing any conclusions. Most coasting is a response to unclear expectations, not permanent disengagement.

5. What if I’m too busy to do 10-minute check-ins every week?

Then you’re too busy to lead. That’s not a criticism, it’s a structural problem worth naming. If your week doesn’t have 10 minutes per direct report, you’ve got a capacity issue that’s going to compound into something much more expensive: turnover, underperformance, client errors. The check-ins don’t add time to your week, they save it. 

Every conversation you’re not having now is a longer, harder conversation waiting six months down the track.