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.
Below the bar, need active coaching
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.
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.
- 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.
- 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.
- 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:
- 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.
- 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.
- 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?
Why does the calculator weight struggling reports more heavily?
Is annual review enough? My company runs them and they seem fine.
My team is 9 people. The calculator says I need 6-8 hours/week. That feels insane.
Does this include feedback during 1-on-1s, or in addition to 1-on-1s?
What if my report does not want feedback? They get defensive every time.
Does the calculator handle remote teams differently?
Should I document every feedback conversation?
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 →