Capability 12 · Lead Others
Give Feedback & Hold the Standard
One founder went from a single sideways comment and months of silence to a standing feedback rhythm — the firing that was quietly brewing became a turnaround instead.
Founders say
“I noticed he hadn't closed anything in two months. I mentioned it once, kind of sideways… and then I didn't say anything else until the day we let him go.”
Where you are today
- Feedback only happens when something has already gone wrong — so everyone flinches at the word.
- You hint at a problem once, then go quiet; months later it ends in a firing that shocks them.
- The hard conversation gets rehearsed in your head at night and never happens in the room.
Where you’re headed
- A standing feedback session with the key people in your orbit — structured, bilateral, normal.
- In-the-moment feedback lands within 24 hours, cleanly, without a month of buildup.
- Performance problems move up an explicit dial with a number and a date — no silent escalation to fired.
Feedback is a dirty word only because of how we use it: rarely, and only when something bad happened. Hear "can I give you some feedback?" a handful of times a year, always after a mistake, and of course the word means trouble. You get rid of that by normalising it — a regular cadence and a regular structure, until feedback stops meaning trouble and starts meaning attention. The structure that works: a standing Keep / Start / Stop session with the key people in your orbit, both directions, short doc prepared by each side, roughly fifty minutes split between your KSSs and theirs. The cadence is what does the magic — by the third session, nobody flinches.
Distinguish the two types of feedback, because they run on different clocks. Someone rude in a meeting hears about it within 24 hours — cleanly, without a month of buildup. Patterns — proactivity, attention to detail — get collected over time and brought to the regular session, where there's room to actually work on them. And whatever the type: never deliver anything critical over Slack. The characters don't carry the emotional weight of a call. Praise in public, criticise in person.
The nothing-to-fired jump
The hook above is the failure mode I've watched most: one oblique mention, months of avoidance, then a termination that shocks everyone — including the founder. The silence isn't kindness; it's the cruellest available option, because the person never got a real chance to change. The other classic is the generalisation: "you always do this" triggers "no I don't" — defensiveness, not change. Keep it to one situation, one behaviour, one impact: what happened, what they did, what it caused.
The two paths of performance
The happy path is development: find where the pipeline is constricted — insight, motivation, skills, practice or accountability — and coax rather than tell. "What's the number one thing you want to improve right now?", "What happens if nothing changes?", "Where do you see yourself in this company, and what's the main gap between here and there?" Get them excited about the gap and they do the rest. The unhappy path is accountability: an explicit, graduated dial from a casual mention to a final warning, attached to a timeline — so the difficult conversation happens in steps, instead of never and then all at once.
On either path, people respond far better to a picture of a positive future than to an autopsy of a broken present. "Next month is going to be our best month ever, because you're going to make more calls than ever" moves someone that "you've been underperforming" never will.
For the conversations at the hard end: two minutes of prep before any of them, the four-part sentence when emotions are tight, and a clean playbook for the day the dial runs out.
What you can do right now
- Book the standing KSS session. With your cofounder and each direct report. Both sides bring a short doc; split the time bilaterally. The cadence is what makes feedback stop being scary. KSS Feedback →
- Deliver the one you've been sitting on. Use Situation, Behaviour, Impact — one concrete moment, what they did, what it caused. This week, not next month. SBI Feedback →
- Locate the stuck person on the pipeline. Before prescribing training, find the constriction: do they know? Are they willing? Can they? Are they getting reps? What holds them to it? Development Pipeline →
- Put a number and a date on it. If it's the unhappy path: "you're at a five, I need a seven by end of month" — and name what happens next on the dial if nothing moves. Accountability Dial →
The toolkit
Work with Ben
Want help installing this?
Outstride OS is the system behind Ben's founder coaching — pre-seed to Series C. If this page names something you are living right now, start a conversation.