Free Calculator

How Often Should You Actually Give Feedback?

Most managers either under-deliver feedback (annual review only) or random-batch it when something goes wrong. Neither produces growth. The right cadence is per-report, weighted by tenure, performance state, and the complexity of the work.

1 5 people 15
0 1 person 10

Below the bar, need active coaching

0 1 person 10

Stretch + developmental conversations

$

Used for the loaded hourly cost of your feedback time

Recommended weekly feedback time

2.8 hrs

Sustainable. This is the sweet spot for most teams.

At this cadence, struggling reports get weekly course corrections, steady reports get biweekly developmental conversations, and strong reports get monthly stretch discussions. The math works without eating your week.

Per report avg

34 min/wk

embedded in 1-on-1s

Annual investment

146 hrs/yr

structured feedback

% of work week

7%

of 40 hours

Current vs target

-1.2 hrs

delta from now

Time allocation by report category

Annual Review Only vs Real-Time Cadence

Both cost time. Only one produces behavior change. Here is what each actually adds up to per year for your team.

Annual review only

20 hrs/yr

4 hrs × team size, once a year

Gallup: 14% of employees say their review inspires them to improve

Real-time cadence (recommended)

146 hrs/yr

Weekly embedded, scaled by report state

Gallup: weekly meaningful contact predicts performance

What This Number Means for You

Struggling reports eat the biggest share, and that is correct.

Counterintuitively, struggling employees need more feedback, not less. Most managers do the opposite: they avoid the difficult conversations and over-feedback the people already doing well. The result is that struggling reports get a vague signal that something is wrong but no clear data on what to change. If you have any struggling reports, that budget needs to be real.

The 15-script library is your scaffolding.

Cadence without quality is just more meetings. The cluster on constructive feedback examples for every workplace situation covers fifteen specific feedback scripts (missed deadlines, quality slipping, defensiveness, plateaued performer, raise asks) with the bad version and the good version side by side. Pair that with the cadence here.

If the math feels unsustainable, the answer is not less feedback.

When the calculator output crosses 6 to 8 hours per week, the signal is rarely "cut feedback." It is "your span is wrong." Either too many direct reports, too high a concentration of struggling performers, or both. The Span of Control calculator confirms whether team size is the actual problem. Cutting feedback to manage span dysfunction is a way to make the dysfunction permanent.

About the numbers: Time-per-report baselines: struggling = 25 min/week (deep weekly check-in), steady = 12 min/week (biweekly average), strong = 8 min/week (monthly developmental + ad-hoc). Adjustments: tenure multipliers ±15-30%, complexity multipliers ±15-25%. Loaded labor cost = manager salary × 1.3 (benefits and overhead). Annual review baseline = 4 hours × team size per year (DDI Global Leadership Forecast estimate of total review-cycle time). Gallup engagement findings cited from State of the American Workplace and "Employee Recognition: Low Cost, High Impact" research. These are planning baselines; your real numbers may differ.

Why "Just Have More 1-on-1s" Is the Wrong Answer

The most common piece of advice on feedback frequency is some version of "give more of it." That advice is correct in spirit and wrong in practice. More feedback delivered carelessly produces worse outcomes than less feedback delivered well. The teams that get this right are not running more meetings. They are running structured cadence with three distinct rhythms, one for each performance state on the team.

The struggling rhythm is weekly, in-the-moment, and embedded in the 1-on-1. Ten to fifteen minutes of specific feedback on the work that happened in the last seven days, plus a clear ask for what changes by next week. The point is real-time course correction, not retroactive autopsy. Struggling employees who get this cadence either improve quickly (the goal) or surface a structural issue that needs a different intervention (also useful information).

The steady rhythm is biweekly to monthly, developmental, and forward-looking. Less about "what happened last week" and more about "what is the next stretch you should be reaching for." Steady performers do not need correction. They need challenge. Without the challenge cadence, they plateau, and you find out they were unhappy when they leave.

The strong rhythm is monthly, ad-hoc, and disproportionately about strategic context. Your strongest performers can usually course-correct themselves on tactics. What they need from you is the bigger map: where the team is going, what trade-offs are being made above their head, where they should be building skill for the next role. Strong performers who do not get this leave for companies that give it to them.

The Math, Made Visible

For a typical team of five (one struggling, three steady, one strong), the math works out to roughly 2.5 to 3.5 hours of focused feedback time per week, depending on tenure and work complexity. That is 7 to 9 percent of a 40-hour work week. It is also the input that compounds the most in your management leverage, because every hour spent here removes downstream hours spent firefighting the consequences of feedback that did not happen.

Compare that to the annual review alternative: roughly 4 hours per direct report per year (the DDI Global Leadership Forecast estimate of total review-cycle time, including prep, the meeting itself, calibration, and follow-up documentation). For a team of five, that is 20 hours per year. The annual-review approach uses dramatically less time and produces dramatically less change. Gallup's engagement research has consistently found that only 14 percent of employees say their annual review inspires them to improve. The other 86 percent are time both sides will never get back.

Three Mistakes That Inflate the Number

When the calculator output crosses 6 hours per week, before you blame the math, check whether one of these patterns is happening.

  1. Your span is too wide. Nine or ten direct reports is past what most leadership research recommends. The right move is to push for structural change (a team lead, a split, a re-org), not to absorb feedback time that crowds out everything else.
  2. You have too many struggling reports. If three or more direct reports are below the bar simultaneously, the issue is rarely individual performance. It is usually upstream: bad hiring, bad onboarding, role misalignment, or a team that grew too fast. Fixing each one individually is more expensive than fixing the upstream pattern. See the cluster on coaching an underperforming employee back to meets expectations.
  3. You are over-investing in steady performers and starving the struggling ones. Common pattern: managers find feedback to steady reports easier (less emotional weight), so they spend disproportionate time there. The result is that steady reports get coached when they should be stretched, and struggling reports get hints when they need direct conversation. The calculator shows the inverse should be true.

How to Use This Output This Week

Three concrete moves:

  1. Audit your last four 1-on-1s. For each direct report, ask: how many minutes of the last 1-on-1 were spent on specific feedback on their work? If the answer is zero for any report, you have your starting point.
  2. Pick one struggling or new report and commit to a real weekly cadence with them for the next month. Not a separate meeting. Ten focused minutes inside the existing 1-on-1, on one specific piece of work, with one specific ask. The script library on constructive feedback examples has fifteen specific scripts you can adapt.
  3. Set a quarterly diary reminder to revisit this calculator. Team composition shifts: people get promoted, new hires arrive, performance states change. The right cadence three months from now will not be the right cadence today.

Frequently Asked Questions

How often should I actually be giving feedback?
The honest answer: more often than annual reviews, less often than every single 1-on-1 turning into a feedback session. The cadence depends on the report. Struggling performers need real-time micro-feedback every week (5 to 15 minutes embedded in 1-on-1s, not separate meetings). Steady performers need biweekly or monthly developmental conversations. Strong performers need monthly ad-hoc plus quarterly stretch conversations. The calculator does the math for your team mix.
Why does the calculator weight struggling reports more heavily?
Counterintuitively, struggling employees need more feedback, not less. Most managers do the opposite: they avoid the difficult conversations and over-feedback the people who are already doing well. The result is that struggling reports get a vague signal that something is wrong but no clear data on what to change, and strong reports get coached when they need to be stretched. The calculator surfaces this asymmetry. A team with two struggling reports and three steady ones needs roughly the same total weekly feedback time as a team with five steady ones, because the struggling pair eats half the budget.
Is annual review enough? My company runs them and they seem fine.
Annual reviews are not feedback. They are summaries of feedback that should have happened all year. Research by Marcus Buckingham and Ashley Goodall, published in HBR as "The Performance Management Revolution" (April 2015), showed that companies that rely on annual reviews alone tend to produce flat behavior change and high employee dissatisfaction. Gallup workplace research has found that weekly meaningful contact between manager and direct report is one of the strongest predictors of engagement and performance. If your annual review is the only time feedback happens, you are effectively running a 12-month feedback latency loop.
My team is 9 people. The calculator says I need 6-8 hours/week. That feels insane.
It is signaling something real. Nine direct reports is past the span of control most management research recommends (typical max: 7-8 for individual contributors, 5-6 if you have any people leaders reporting to you). If the math feels unsustainable, the answer is not to skip feedback. It is to reduce span. Either through promotion of a team lead, splitting the team, or pushing back on the org structure. The calculator is telling you that your real problem is span, not feedback discipline. Use the Span of Control calculator below to confirm.
Does this include feedback during 1-on-1s, or in addition to 1-on-1s?
Included. The numbers assume feedback happens embedded in 1-on-1s, not as separate meetings. If you have a weekly 30-minute 1-on-1 and you spend 10 to 15 minutes of it on real-time feedback, the calculator counts that as the feedback time investment. The remaining 15 to 20 minutes is for everything else (career, blockers, relationship). If you currently have no 1-on-1 cadence, see the article on how often to have 1-on-1s linked below.
What if my report does not want feedback? They get defensive every time.
That is a different problem and one of the situations covered in the 15-example feedback library linked below. Defensive employees usually do not need less feedback. They need a different framing of it (specific behavior, not character; forward-looking, not retrospective autopsy; and a genuine pause for their read). If you back off feedback to avoid the defensiveness, you teach them that defensiveness works. Once. Then the cycle compounds.
Does the calculator handle remote teams differently?
Remote teams typically need 10 to 20 percent more feedback time, because the casual signal you absorb in an office (overheard conversations, body language at meetings, hallway questions) is invisible remotely. If your team is fully remote, treat the calculator output as the floor, not the ceiling. The article on remote 1-on-1 meetings linked below covers what specifically changes.
Should I document every feedback conversation?
No, and that is one of the most common over-corrections. Routine in-the-moment feedback should feel like a normal conversation, not the start of a paper trail. The act of documenting casual feedback corrodes trust faster than skipping it. Document when the feedback is on a pattern issue that may eventually need to escalate (coaching plan or PIP). The threshold: if you can imagine yourself referencing this conversation in a difficult conversation three months from now, write it down. If not, do not.

Cadence Is Half. Scripts Are the Other Half.

Knowing how often to give feedback does not help if you do not know what to say. The library covers fifteen specific situations with the bad version and the good version side by side.

Related: Conversation Delay Cost → Related: Span of Control → Related: Performance Review Time →

← All Calculators