पाठशाला Pathshala · दल Dal, The team · Lesson 15 · Build

One-on-ones and feedback that actually lands

Most performance problems that end in a firing were visible months earlier and never said. A weekly one-on-one the report owns, and a feedback method that names behaviour rather than character, fix them while they are small.

Pathshala, The Founder Library · 11 October 2026 · 7 min read

Two simple chairs side by side against a textured wall casting long shadows, in black and white. — Photograph: YANG HAI · Pexels

Most performance problems that end in a firing were visible months earlier and never said out loud. The manager noticed, meant to mention it, waited for the right moment and then for the review. By the time it was said it had become a verdict rather than a correction. A weekly one-on-one and a feedback method that names behaviour rather than character are how a small problem gets said while it is still small.

This lesson sets out what the one-on-one is for, how to run it, a feedback method that lands, what the cadence costs and saves, how feedback becomes a written plan when it has to, and what changes in an Indian team.

What a one-on-one is for

Ben Horowitz describes the one-on-one as part of a company’s communication architecture: the channel through which problems and ideas that would otherwise stay with one person reach someone who can act on them. That makes it the report’s meeting, not the manager’s. It is not a status update, which belongs in a written note or the team meeting. It is the half hour in which the person can raise what they would never raise in a group: the colleague who is not pulling their weight, the doubt about the strategy, the offer they have received.

For the manager it does three jobs. It is where small corrections happen, while they are still small. It is where the manager learns what is actually going on, which is rarely what the dashboard says. And it is the early warning system: Molly Graham, writing about scaling teams, suggests watching for warning signs in one-on-ones, such as questions about why a new hire was made, long before they show up as a resignation.

The weekly thirty minutes

Weekly, thirty minutes, the same slot, rarely cancelled. Horowitz’s rules are the right defaults: the employee sets the agenda, ideally sent ahead so that the meeting can be skipped when there is nothing pressing, and the manager does about ten per cent of the talking and ninety per cent of the listening. A shared running document, one per person, with the newest meeting at the top, holds the agenda, what was agreed and anything the manager promised to do. Promises kept in that document are what make people bring real problems to the next meeting.

Two small cups of coffee on a rustic wooden table. — The first answer to a hard question is usually the polite one. The useful one comes after the pause. Photograph: Pedro Dias · Pexels

When the report brings nothing, the manager asks. Horowitz’s list works: if we could improve in any way, how would we do it; what is the biggest problem in the organisation and why; what is not fun about working here; what do you not like about the product. Ask one per meeting and wait through the silence. The first answer is usually the polite one. The second, after a pause, is usually the useful one.

Start every working relationship with a first one-on-one that is about the relationship itself. Lara Hogan’s questions for it are the best set in print: how do you like feedback, in what medium and whether in one-on-ones or as it happens; how do you prefer recognition, in public or in private; what are your goals for this year and the next three months; what do you need from your manager; and what makes you grumpy, and how will I know. Write the answers down and reread them before every difficult conversation.

Feedback that lands

Feedback fails in two familiar ways. It is so soft that the person does not know they have been corrected, or so personal that they hear an attack and defend themselves. Kim Scott’s Radical Candor names the target: care personally and challenge directly at the same time. Caring without challenging is ruinous empathy, the more common failure among founders who like their teams. Challenging without caring is obnoxious aggression. Doing neither, with flattery to the face and criticism behind the back, is manipulative insincerity, and teams see it immediately.

The method that turns the principle into words is the Center for Creative Leadership’s situation, behaviour, impact, with a fourth step that makes it a conversation. Situation: when and where, specifically: “In Tuesday’s call with the Pune distributor.” Behaviour: what you saw or heard, without adjectives: “You quoted a delivery date before checking with operations.” Impact: what it caused: “We now have to go back and move it, and the distributor has asked twice whether our dates are real.” Intent: ask, and listen: “What were you hoping to do there?” Often the answer changes the next step: they were trying to save a deal the founder had told them to save.

Two rules make it land. Say it within the week, because feedback about something three months ago is a judgement on a memory. And use the same form for praise. “Good job on the launch” teaches nothing. “The release notes you wrote on Thursday answered the three questions support usually gets, and tickets that week were half the usual” tells the person exactly what to repeat.

How often, and what waiting costs

Cadence is the decision that matters most, and founders usually get it wrong by meeting too rarely. A problem the manager notices at a random moment waits, on average, half the gap to the next conversation. Weekly, that is three or four days. Monthly, about two weeks. With a quarterly review as the only fixed occasion, about six weeks, by which time it has become a pattern. Weekly costs time: a manager with five reports spends about fourteen hours a month, including preparation and notes. Set your own team.

Read the hours against what they buy. Fourteen hours a month is a real cost for a founder who manages five people and also sells. It is small against one replacement hire, and smaller still against a quarter in which a problem everyone could see went unsaid. If the hours do not fit, shorten the meetings before you space them out: a fifteen-minute weekly one-on-one beats a sixty-minute monthly one, because the wait is what does the damage.

Feedback is only useful while the thing it describes can still be changed. Say it within the week, about behaviour, in the same form you use for praise.

From feedback to a written plan

Most corrections end with the conversation. When the same gap shows up three weeks running, the one-on-one changes: the manager names it as a pattern, the two of them write down what good looks like with a measurable target and a date four to six weeks out, and they review it weekly in the same meeting. This is not a warning dressed as support. It is the last honest chance to close the gap, and it should be offered as one.

Most people who are told clearly what is wrong, and helped, close the gap. Those who do not have been treated fairly, and the decision that follows is no surprise to anyone. The [firing lesson](/library/firing-fast-and-fairly-in-india) picks up from there. A company that runs weekly one-on-ones fires fewer people, and fires them faster and more fairly when it must.

In an Indian team

Two things make one-on-ones harder in many Indian teams. Deference to seniority means a report may agree with everything and raise nothing, especially with a founder. And a habit of politeness means bad news arrives late and softened. The [lesson on politeness in customer interviews](/library/mom-test-for-indian-politeness) describes the same effect with customers; inside a company it is stronger, because the manager controls the appraisal.

The fixes are practical. Ask about specifics rather than feelings: not “is everything fine” but “what slowed you down this week”. Thank people visibly for bad news, every time, until it becomes normal. Go first, by telling the team about a mistake of your own and what you changed. And keep the one-on-one in a language and a setting where the person is most at ease; a walk round the block often gets more truth than a glass meeting room.

The weekly ritual

Every week, for every direct report: thirty minutes in the same slot, their agenda in the running document, one question from the list when they bring nothing, at least one piece of specific feedback, praise or correction, and any promise you make written down and kept by the next meeting.

Every month, reread each running document from the top. Look for a gap that has appeared three times and has no written plan, and for a person who has raised nothing difficult in a month, which usually means they have stopped trusting the meeting rather than that nothing is wrong. Every quarter, ask each report how the one-on-ones could be more useful, and change one thing. The [meetings lesson](/library/meetings-that-earn-their-time) has the same test for every other meeting on the calendar.

The hours in the figure are an estimate; the cadence that works is the one a manager actually keeps.