Upward feedback: how to collect it, with example questions
How to collect upward feedback from employees about their managers: how it differs from 360 feedback, a question bank, a safe launch in hierarchical cultures and turning results into action.
- Written by
- TeamCheck Editorial Team
- Published
- Updated
- Reading time
- 11 min read
- Change language
- العربية
Key takeaways
- Upward feedback asks direct reports to rate observable behaviors of their manager, giving a view of leadership that senior leaders rarely see.
- It differs from 360-degree feedback by coming from one rater group only, which makes it simpler to run but harder to keep anonymous in small teams.
- A clear developmental purpose, a stated anonymity threshold and prepared managers make candid feedback more likely, especially in hierarchical cultures.
- Research suggests managers improve more when they discuss upward feedback with their teams and commit to specific changes.
Upward feedback is feedback that employees give to their manager about how that manager leads them day to day. It is usually collected through a short, confidential questionnaire about observable manager behaviors, such as how clearly they set expectations, how fairly they treat people and how well they support development. The results are combined into a report the manager uses to improve.
Done well, upward feedback gives managers a view they rarely get any other way: what it is actually like to work for them. This guide explains how upward feedback differs from 360-degree feedback, offers a question bank you can adapt, and shows how to introduce it safely in hierarchical workplaces and help managers act on what they hear.
What is upward feedback?
Upward feedback, sometimes called upward appraisal or a manager effectiveness survey, reverses the usual direction of performance conversations. Instead of a manager assessing their team, the team assesses the manager. Direct reports answer the same set of questions about their manager, their answers are grouped so no individual can be identified, and the manager receives a summary of ratings and comments.
The idea rests on a simple observation. Direct reports see parts of a manager's work that senior leaders do not: how meetings are run, how decisions are explained, how mistakes are handled and whether credit is shared. A manager's own manager mostly sees results. The team sees the behavior that produces them.
Research supports the practice when it is followed through. In a study of 238 managers, Smither and colleagues (1995) found that managers whose initial upward ratings were moderate or low improved over the following six months, and the improvement could not be explained by regression to the mean alone. Atwater, Roush and Fischthal (1995) found that followers' ratings of leaders improved after the leaders received upward feedback, and that leaders' self-ratings moved closer to their followers' views.
Upward feedback is useful for:
- Manager development. It shows each manager specific behaviors to keep and to change.
- Leadership programs. Aggregated results show which management skills need attention across a department or level.
- Culture signals. Asking employees for their view of leadership shows that the organization values their voice.
It is less suited to being the only basis for decisions about a manager's pay or promotion, a point covered below.
Upward feedback vs 360-degree feedback
Upward feedback is often confused with 360-degree feedback. They are related but not the same. A 360 collects views from several directions at once: self, manager, peers, direct reports and sometimes other stakeholders. Upward feedback collects views from one direction only: the people who report to the manager.
| Aspect | Upward feedback | 360-degree feedback |
|---|---|---|
| Who gives feedback | Direct reports (sometimes skip-level reports) | Self, manager, peers, direct reports and others |
| Who receives it | People managers only | Anyone, including individual contributors |
| Main focus | How the person manages and leads people | Overall working behavior across relationships |
| Typical length | Short, often 10 to 20 items | Longer, covering several competencies |
| Setup effort | Lower: one rater group, defined by reporting lines | Higher: rater nomination and several groups |
| Common use | Manager development, leadership culture checks | Leadership and individual development |
| Main risk | Small teams make anonymity hard | Rater fatigue and complex reports |
In practice, upward feedback is often a first step. An organization new to multi-rater feedback may start with a focused upward survey for managers, then move to a full 360 once people trust the process. Inside a 360, direct reports are simply one rater group. If you are planning the wider process, the complete guide to 360-degree feedback covers rater groups, cycles and reports in detail.
Upward feedback questions for managers
Good upward feedback questions describe one behavior a direct report can observe. They avoid personality labels ("Is a good leader") and focus on what the manager does. Use a five-point frequency scale, such as "rarely" to "almost always", with a "not able to observe" option.
These questions are examples to adapt, not a validated instrument.
Setting direction and expectations
- My manager explains how our team's work connects to wider goals.
- My manager makes clear what good work looks like before I start a task.
- My manager tells me early when priorities change.
Communication and listening
- My manager listens to my point of view before responding.
- My manager explains the reasons behind decisions that affect me.
- My manager shares information I need to do my work in good time.
Support and removing obstacles
- My manager helps remove obstacles that slow my work.
- My manager is available when I need guidance on something important.
- My manager supports a reasonable balance between workload and available time.
Feedback and development
- My manager gives me specific feedback on what I did well.
- My manager tells me what I could improve in a respectful way.
- My manager talks with me about my development and career goals.
Fairness and trust
- My manager treats team members fairly when assigning work and opportunities.
- My manager gives credit to the people who did the work.
- My manager keeps commitments made to the team.
- I feel able to raise a concern or disagree with my manager without negative consequences.
Open questions
Add two or three open questions so managers understand the reasons behind the numbers:
- What should your manager keep doing?
- What one change would most help you do your best work?
- Is there anything else you would like your manager to know?
For a broader bank that covers peers, self-assessment and other competencies, see these 360 feedback questions.
How to introduce upward feedback safely
The main barrier to upward feedback is rarely the questionnaire. It is whether employees believe it is safe to be honest. Detert and Edmondson (2011) described "implicit voice theories": taken-for-granted beliefs that speaking up to people above you is risky, which lead employees to censor themselves even when nobody has told them to stay silent. In hierarchical workplaces, including many in Saudi Arabia and the wider GCC, respect for seniority can make rating a manager feel uncomfortable or even disrespectful. A careful launch addresses these concerns directly.
Explain the purpose before the first survey
State in writing why you are running upward feedback, who will see the results and how they will be used. A developmental purpose, where results help managers grow and are not tied directly to their pay, usually builds trust faster. Present it as a way to help managers support their teams better, not as a way to judge them.
Set and explain anonymity thresholds
Anonymity is what makes candid upward feedback possible. Agree a minimum number of responses before a manager sees any results, and tell employees what it is. Many organizations use a minimum of three to five responses, but this is common practice rather than a fixed rule. If a team is too small, you can combine it with a related team, report only at a higher level, or postpone the manager's report until the team grows.
Also tell employees that open comments may be shown word for word, so they should avoid details that identify them, such as a specific meeting only they attended.
Prepare managers before results arrive
Managers who know what to expect react better. Before launch, brief them on:
- The purpose and the anonymity rules, including that they must not try to identify who said what.
- What the report will look like and how to read averages and comments.
- How to respond to difficult feedback: pause, look for themes, and ask for help interpreting it.
- What they will be expected to do afterwards, such as sharing themes and one or two actions with the team.
Let senior leaders go first
When senior leaders take part, receive their own feedback and talk openly about what they are changing, other managers and employees see that the process is genuine. This matters more in workplaces where people take cues from the top.
A launch checklist
- Agree the purpose (developmental or evaluative) and write it down.
- Choose 10 to 20 questions and test them with a few employees for clarity, in every language you will use.
- Set the anonymity threshold and decide what happens with small teams.
- Brief managers on the process, the report and their follow-up role.
- Announce the survey to employees, covering purpose, anonymity and timing.
- Keep the survey open for a defined period, for example one to two weeks, and send reminders based on overall response rates, not individuals.
- Release reports only to managers whose teams meet the threshold.
- Schedule follow-up conversations and a date for the next cycle.
Helping managers act on the results
The research is clear that the value of upward feedback depends on what happens after the report. Walker and Smither (1999) followed 252 managers over five years of an upward feedback program. Managers who met with their direct reports to discuss the feedback improved more than those who did not, and managers improved more in years when they discussed the previous year's feedback with their team.
Reading the report
Encourage managers to read the full report before reacting to any single item.
- Look for themes. A pattern across several related items, or a point raised in several comments, matters more than one low score.
- Compare with your own view. If the report includes a self-assessment, gaps between self-ratings and team ratings show likely blind spots and hidden strengths. The Johari window is a simple way to talk about these gaps.
- Note the strengths. Behaviors the team values are worth naming and keeping.
- Treat small differences with caution. A small gap between two items, or between two years, may not reflect real change.
Sharing results with the team
A short team conversation turns a private report into a shared commitment. A manager might:
- Thank the team for taking part.
- Share two or three themes, including at least one strength.
- Name one or two behaviors they will work on and what that will look like.
- Ask the team for ideas, without asking who wrote which comment.
- Agree how they will check progress, for example at a team meeting in three months.
Managers who find this difficult benefit from support from HR or a coach, who can help them prepare and keep the discussion constructive.
Building a focused development plan
Development plans work better when they are short. For each priority, a manager can note the behavior to change, two or three concrete actions and how progress will be noticed. HR can look across reports to see common themes, such as delegation or giving feedback, and plan training where several managers share the same need.
If you run upward feedback inside a broader 360 process, TeamCheck's 360-Degree Feedback offers ready templates for almost all positions, can generate competencies from a job description or map your own, and produces both a management report and individual reports.
Repeating the cycle
One survey is a snapshot. Repeating upward feedback, for example once a year, lets managers see whether the team has noticed change and shows employees that their input leads somewhere. Keep core questions stable so results can be compared over time.
Common mistakes
- Launching without a stated purpose. If employees cannot tell whether results affect a manager's pay, they may soften their answers or not respond.
- Showing results from very small teams. Reporting two or three responses can expose individuals and damage trust in the whole program.
- Using vague questions. Items such as "My manager is a good leader" give managers nothing specific to act on.
- Trying to identify respondents. A manager who asks "Who wrote this?" teaches the team never to be honest again. Make this rule explicit.
- Collecting feedback and doing nothing. If employees see no response, participation and candor usually fall in the next cycle.
- Using upward ratings alone for evaluative decisions. Team ratings reflect perception and can be affected by unpopular but necessary decisions. Combine them with other evidence before they inform pay or promotion.
- Changing the rules midway. Using results collected for development in evaluative decisions breaks the promise made to employees.
Frequently asked questions
Is upward feedback anonymous?
It should be anonymous for direct reports, which is why results are grouped and only shown when enough people respond. Many organizations set a minimum of three to five responses per manager. Employees should know the threshold before they answer, and they should know that comments may be shown word for word, so they can avoid identifying details.
How often should you run upward feedback?
Many organizations run it once a year, which gives managers time to act and teams time to notice change. Some add a short pulse of a few key questions halfway through the year. Running it too often can tire employees, especially if they have not yet seen any response to the previous round.
What should a manager do with negative upward feedback?
Pause before reacting, read the whole report and look for themes rather than single comments. Talk it through with HR or a coach, then share key themes with the team, thank them, and commit to one or two specific changes. Research by Walker and Smither (1999) suggests that discussing feedback with direct reports is linked to greater improvement.
Should upward feedback affect a manager's performance rating?
It is usually safer to start with a developmental purpose, kept separate from pay and promotion, so employees feel able to be candid and managers feel able to learn. If you later use results as one input to evaluation, announce this before the cycle starts and combine it with other evidence, rather than relying on team ratings alone.
What is the difference between upward feedback and a 360 review?
Upward feedback comes only from a manager's direct reports and focuses on how the manager leads people. A 360 review combines views from several groups, usually self, manager, peers and direct reports, and covers wider working behavior. Upward feedback is simpler to run and is often a first step before a full 360 program.
Summary
Upward feedback gives managers a structured view of how they lead, from the people who experience it every day. It works best when the purpose is clear, questions describe observable behaviors, anonymity thresholds are set and kept, and managers are prepared to discuss the results with their teams and act on them. In hierarchical cultures, a careful launch and visible leadership support matter as much as the questionnaire itself. To run upward feedback as part of a wider multi-rater process, explore TeamCheck's 360-Degree Feedback.
References
We cite sources so you can read further. Links open external websites.
- An examination of the effects of an upward feedback program over time (Smither, London, Vasilopoulos, Reilly, Millsap & Salvemini). Personnel Psychology, 1995. doi.org/10.1111/j.1744-6570.1995.tb01744.x (opens in a new tab)
- The influence of upward feedback on self- and follower ratings of leadership (Atwater, Roush & Fischthal). Personnel Psychology, 1995. doi.org/10.1111/j.1744-6570.1995.tb01745.x (opens in a new tab)
- A five-year study of upward feedback: What managers do with their results matters (Walker & Smither). Personnel Psychology, 1999. doi.org/10.1111/j.1744-6570.1999.tb00166.x (opens in a new tab)
- Implicit voice theories: Taken-for-granted rules of self-censorship at work (Detert & Edmondson). Academy of Management Journal, 2011. doi.org/10.5465/amj.2011.61967925 (opens in a new tab)
Written by
TeamCheck Editorial Team
TeamCheck is an HR talent intelligence platform. Articles are researched and written by the TeamCheck editorial team.