8 Essential 360 Feedback Questions

Beyond “Good Job”: The Feedback That Builds Teams

Many teams do not have a feedback problem. They have a question problem.

The usual 360 feedback form asks broad, harmless things. Is this person a good communicator? Are they collaborative? Do they show leadership? People answer with safe praise, a few soft criticisms, and nothing changes. The manager feels reviewed. The employee feels judged. HR gets a document, not a development plan.

That gets worse in small and midsize companies, where the same manager who approves leave, handles coverage gaps, explains policy changes, and calms frustrated employees is also supposed to coach performance. In that environment, vague feedback is expensive. If someone communicates poorly, you do not just get confusion. You get missed deadlines, overlapping absences, payroll corrections, and avoidable tension across the team.

The good news is that 360 feedback questions can work very well when they focus on observable behavior. A 2016 APA-reviewed meta-analysis found a significant average effect size of d = .41 on performance improvement across feedback interventions, but performance declined in one third of studies when the process was poorly designed or poorly delivered (American Psychological Association meta-analysis). That matches what practitioners see. Good questions create clarity. Bad questions create noise.

The fix is practical. Ask about behavior people can see. Tie feedback to real work. In growing teams, leave management is one of the easiest ways to make abstract competencies concrete because it forces communication, judgment, fairness, follow-through, and system use into the open.

1. Communication and Collaboration Effectiveness

Poor communication rarely shows up as one dramatic failure. It shows up as scattered Slack messages, unclear approval logic, and employees who all heard something different about the same policy.

That is why strong 360 feedback questions in this category should ask about clarity, timing, and channel choice. If a manager announces a leave carryover rule in a single email and never explains it in a team meeting, that matters. If they approve time off but do not explain the coverage impact to the rest of the team, that matters too.

Ask about behavior people can point to

Useful prompts sound like this:

• Clarity in updates: How clearly does this person explain policy or process changes that affect your work?
• Channel judgment: Does this person use the right channel for the message, such as Slack, Teams, email, or a meeting?
• Cross-team coordination: When schedules change, does this person keep the people affected informed in time to adjust?

For managers using a leave platform, add questions tied to workflow. Does the manager explain why a request was approved, delayed, or denied? Do they provide context around overlapping absences or minimum coverage? Do employees understand what action they need to take next?

Ask for one recent example in the open comment field. Without that, “communication” becomes a personality rating.

A useful operating habit is to connect 360 findings to recurring manager conversations. If your managers already run regular check-ins, fold communication feedback into a better one-on-one meeting agenda. That turns “be clearer” into a repeatable behavior, such as reviewing upcoming leave, coverage risks, and policy reminders every month.

One practical trade-off matters here. More open-ended prompts can produce richer feedback, but too many will reduce completion quality. Research summarized by the Center for Creative Leadership recommends surveys with 15-25 questions and a 70% rating-scale to 30% open-ended mix, with a 10-15 minute completion window to reduce abandonment (360 feedback question design guidance). In practice, that means asking fewer communication questions, but making each one sharper.

2. Decision-Making and Strategic Thinking

Some managers look decisive because they answer quickly. That is not the same as making good decisions.

In a team setting, decision quality shows up in ordinary moments. Someone requests leave during a busy week. Two people on the same function ask for the same day off. A policy exception seems reasonable for one employee but creates precedent for everyone else. Those are strategic decisions in miniature.

Questions that expose judgment

Ask respondents whether the person:

• Reviews context before acting: Does this person consider team availability, known conflicts, and business continuity before making a decision?
• Balances fairness and practicality: When trade-offs are difficult, do they explain the reasoning clearly?
• Uses available information: Does this person look at the information in front of them before approving or declining requests?

A generic decision-making question invites generic feedback. A better one names the evidence. “Does this manager review calendar conflicts and team coverage before approving leave?” tells respondents exactly what to evaluate.

That matters because small teams feel every approval decision. One poorly timed absence can trigger last-minute scrambling, resentment, or a customer delay. A manager who looks at the full picture is not being bureaucratic. They are protecting the team.

Use one open prompt here, not five. Ask for a specific example of a strong or weak decision and what impact it had. If several respondents describe the same pattern, you have a coaching issue worth addressing.

The operational version of strategic thinking is simple. Good managers connect individual requests to team consequences. Weak managers treat each request in isolation.

3. Reliability and Accountability

If you want one category that employees notice instantly, it is reliability.

People know who follows through. They know who approves requests on time, keeps records clean, and remembers to update the team calendar. They also know who creates avoidable admin work for everyone else.

Make accountability measurable

This category works best when the questions focus on routine actions:

• Follow-through: Does this person complete agreed actions when they say they will?
• Timeliness: How consistent is this person in responding to requests that affect team planning?
• Accuracy: Can others rely on this person’s records, approvals, and updates being correct?

For managers and office managers, leave management becomes a concrete performance signal. If approvals sit too long, employees chase. If balances are wrong, payroll gets dragged in. If records do not match policy, compliance risk increases.

A useful 360 item might ask, “How reliable is this manager in maintaining accurate leave records and approvals?” Another could ask, “When errors happen, does this person acknowledge them and correct them promptly?”

Reliability is not charisma. It is whether people can plan their work around your actions without building a backup plan.

This category also pairs well with a broader bank of performance review questions when you want to align formal reviews with daily operating behavior. The strongest surveys do not separate “people skills” from “process discipline” because employees experience both at the same time.

One caution. Do not turn accountability into surveillance. Ask about consistency and ownership, not personality. “Can I depend on this person to act on time?” is useful. “Is this person hardworking?” is too vague to coach.

4. Adaptability and Change Management

Every growing company eventually hits the same wall. The spreadsheet that used to work no longer works. The informal rule everyone “just knew” starts breaking. One office adopts the new process and another ignores it.

That is when adaptability stops being a nice trait and becomes an operating requirement.

What to ask when systems change

Ask questions that separate attitude from action:

• Learning speed: How quickly does this person learn and use new tools or processes?
• Response to change: When procedures change, does this person help the transition or slow it down?
• Support needed: What would help this person adopt new systems more confidently?

These are especially useful during system rollouts. If a team moves from manual leave tracking to a dedicated platform, you want to know who embraced the new workflow, who needed more support, and who continued working from the old spreadsheet.

Do not make the mistake of asking only whether someone is “open to change.” Plenty of people say yes and still avoid the new process. Ask instead whether they started using the new approval path, whether they learned calendar syncing, and whether they stopped relying on off-system side agreements.

The software market is moving toward cloud-based, mobile, and AI-supported tools. One market report projects the global 360 Degree Feedback Software Market will grow from USD 1246.03 million in 2026 to USD 2696.38 million by 2035, with continuous feedback cycles seeing a 35% adoption increase from 2022-2024, while poor design contributed to a 19% response-rate drop in 2023 (360-degree feedback software market projection). The lesson for practitioners is not that more feedback is automatically better. It is that frequent feedback only works when the survey is easy to complete and obviously relevant.

A short, concrete change-management section will tell you more than a long, abstract one.

5. Leadership and Team Development

Leadership feedback goes nowhere when the questions stay generic. “Inspires others” sounds important, but it rarely tells a manager what to do next.

A better approach is to ask whether the manager creates the conditions for good work. Do they set expectations clearly? Do they explain trade-offs? Do they build trust when decisions are unpopular?

Development shows up in ordinary conversations

In small teams, leadership often appears in moments like these:

• An employee asks for leave during a critical week.
• A manager spots repeated overtime and raises burnout risk early.
• A team lead explains why coverage matters without making people feel guilty for taking time off.

Those moments reveal whether the manager can connect people, workload, and policy in a way that supports growth rather than just enforcing rules.

Useful prompts include asking whether the manager gives clear feedback, discusses team capacity openly, and helps employees understand how their decisions affect others. If several direct reports say they never know why approvals happen the way they do, that is not only a process issue. It is a leadership issue.

A strong follow-up tool is reviewing examples of effective performance review comments so managers learn how to give development-focused feedback instead of vague praise or unhelpful criticism.

The best managers make standards visible. People do better work when they understand the reason behind the rule.

This category also deserves emotional care. Feedback can discourage people when it lands harder than expected. The APA review noted emotional risks in the feedback process, including findings from Atwater and Brett’s work where recipients felt discouraged and frustrated when feedback was less positive than anticipated, which is one reason carefully balanced survey design matters (APA review of 360 feedback interventions). Leadership questions should surface blind spots without cornering someone into defensiveness.

6. Equity, Inclusion, and Fair Treatment

A 360 process loses credibility fast if employees believe rules are applied differently depending on who asks.

This category matters in every company, but it is especially important when managers control approvals, exceptions, and schedule flexibility. Employees do not need legal expertise to detect unfairness. They notice patterns. One person gets quick answers. Another waits. One exception is treated as reasonable. Another is labeled a problem.

Questions that reveal consistency

Ask directly about treatment, not intention.

• Consistency: Does this manager handle similar requests in a similar way across the team?
• Respect: Do you feel comfortable raising concerns or asking for time off with this person?
• Transparency: When decisions differ, does this person explain the reason clearly?

The strongest open-ended question in this category is simple: “Have you observed any inconsistency in how requests or policies are handled?” That gives people room to flag a pattern without forcing them into legal language.

This is also a good place to compare perception with workflow data. If survey comments suggest uneven treatment, review approval timing, exception handling, and policy application across teams or locations. You are not trying to “catch” someone with the survey. You are trying to verify whether the experience employees describe matches operating reality.

One practical caution. Do not overload this section with abstract inclusion language if your immediate operational risk is fairness in day-to-day management. Start with treatment people can observe. That gives you a defensible basis for coaching and, when needed, corrective action.

7. Technical Competency and System Proficiency

The fastest way to break a good process is to assume everyone can use the system equally well.

That assumption fails all the time. One manager knows how to review overlapping absences, sync calendars, and export data cleanly. Another approves from email, misses context, and never checks the team view. Both think they are “using the platform.”

Before the video, one point matters. Technical competency in 360 feedback should not be limited to IT roles. In HR and operations, system proficiency is part of job performance.

Separate confidence from competence

Ask questions such as:

• Daily use: How comfortably does this person use the tools required for approvals, tracking, or reporting?
• Problem solving: Can this person handle common issues on their own and know when to escalate?
• Feature adoption: Does this person use the platform features that improve visibility for the team?

This is one area where role-specific wording helps. An office manager might be rated on balance tracking and export accuracy. A people manager might be rated on approving requests with full team context. An HR lead might be rated on configuring policies correctly across locations.

The software market is moving toward cloud-based, mobile, and AI-supported tools. A market analysis notes projected growth in the category, with cloud-based solutions and AI-supported analysis shaping how organizations evaluate and use feedback systems (market analysis of 360-degree feedback software). For a smaller employer, the practical takeaway is straightforward. Choose tools people will use, then write 360 feedback questions that test whether they are using the right features well.

A weak question asks whether someone is “tech savvy.” A useful one asks whether they can reliably use the system to make sound decisions.

8. Customer Focus and Service Orientation

In internal operations, “customer” often means employee.

That matters more than many managers realize. When someone asks about leave balance, eligibility, carryover, or scheduling options, they are not just asking for policy information. They are asking the company to help them plan their life. A cold or confusing answer damages trust quickly.

Service shows up in responsiveness and empathy

Ask questions that reflect the experience people have:

• Responsiveness: How quickly and helpfully does this person respond to questions that affect your ability to plan?
• Context in decisions: When requests are approved or denied, does this person explain the decision in a useful way?
• Problem solving: Does this person try to find workable solutions, not just deliver a yes or no?

This category is often where strong administrators stand out. They remind employees about deadlines, answer common questions clearly, and reduce friction before it becomes frustration. Weak service orientation looks different. People get delayed answers, partial explanations, or policy language with no practical guidance.

For teams using leave software, service orientation can also be observed through process design. Do managers reduce back-and-forth by giving enough context in the first response? Do they point employees to the right place to check balances or policy details? Do they spot patterns, such as repeated confusion about one rule, and fix the communication instead of answering the same question repeatedly?

One final note on survey design. Open-ended feedback is useful here, but too much of it can bury the signal. In smaller teams, hybrid question formats often work better because they collect a rating and a short explanation without demanding an essay. That tends to produce feedback people can act on.

360 Feedback: 8 Key Competencies Comparison

Item Implementation complexity Resource requirements Expected outcomes Ideal use cases Key advantages Communication and Collaboration Effectiveness Low to Medium: survey and observation-based Moderate: feedback collection, multiple channels Clearer messaging, higher policy adoption, fewer misunderstandings Evaluating manager communications, rollout messaging, cross-team coordination Improves transparency and identifies communication gaps Decision-Making and Strategic Thinking Medium to High: requires case examples and data review Moderate: access to historical data, decision records Better approval quality, fewer coverage gaps, improved compliance Approvals balancing coverage, leadership assessment, strategic staffing Enhances long-term planning and risk mitigation Reliability and Accountability Medium: metrics integration and consistency checks High: continuous tracking, system logs, audit support Consistent approvals, accurate records, audit readiness Compliance-sensitive roles, payroll accuracy, audit preparation Increases trust and reduces compliance risk Adaptability and Change Management Medium: behavioral measures and adoption tracking Moderate: training, adoption metrics, surveys Faster adoption, identifies champions and resistors System rollouts, phased multi-location implementations Predicts implementation success and informs training Leadership and Team Development Medium: multi-rater feedback and outcome correlation Moderate: 360 feedback, turnover and performance data Improved retention, better coverage planning, stronger teams Manager development, succession planning, coaching programs Builds capacity, reduces burnout, improves delegation Equity, Inclusion, and Fair Treatment Medium to High: sensitive measurement and pattern analysis High: confidential surveys, demographic and audit data Fairer policy application, lower legal risk, higher psychological safety Diversity initiatives, compliance reviews, distributed teams Detects bias and ensures consistent treatment Technical Competency and System Proficiency Low to Medium: skills assessments and usage metrics Moderate: training resources, usage tracking, certifications Higher platform adoption, internal super-users, fewer support requests Technology rollouts, identifying trainers, reducing consultant reliance Boosts adoption and enables peer-led support Customer Focus and Service Orientation Low to Medium: service metrics and satisfaction feedback Moderate: satisfaction surveys, ticket and response tracking Better employee experience, fewer HR tickets, proactive service HR support roles, managers handling employee inquiries Improves satisfaction and encourages proactive problem solving

From Questions to Action Turning Feedback into Growth

The value of 360 feedback questions does not come from the form itself. It comes from what managers, HR, and team leads do next.

Start small. Do not turn every comment into a development project. Choose one or two themes per person. If a manager scores well on reliability but poorly on communication, that is enough to work on. If an office manager is strong on service orientation but inconsistent on system use, focus there first.

Write the development plan in plain language. “Improve communication” is not a plan. “Explain approval decisions with coverage context and send policy reminders before deadlines” is. “Be more accountable” is not a plan. “Respond to leave requests within the team standard and correct record errors promptly” is.

Then create a check-in point. A 360 review without follow-up is just a well-formatted opinion. A short manager check-in, a one-on-one discussion, or a practical workflow review is usually enough. The point is not to revisit every comment. The point is to see whether behavior changed.

That is where operational systems help. In a small or midsize company, people do not have time to manage performance in one place and day-to-day admin in another. When leave approvals, balances, overlap visibility, and policy reminders all live in the same workflow, you can connect feedback themes to real behavior. A manager who was unclear about policy can use automated nudges and consistent documentation. A leader who made uneven decisions can review team context before acting. A team lead with reliability issues can use a shared workflow instead of memory and inbox search.

Keep the emotional side in mind too. Feedback can improve performance, but only when the process feels fair, specific, and development-oriented. If employees think the survey is punitive or vague, they either disengage or become defensive. Clear purpose matters. Anonymity matters. Focus matters.

This is why many organizations use 360 feedback for leadership development rather than discipline. According to the Center for Creative Leadership, 86% of organizations use 360-degree feedback primarily for leadership development (Center for Creative Leadership summary). That is the right lens. Use feedback to build awareness, strengthen judgment, and make better day-to-day management visible.

When the questions are concrete, the conversation improves. When the conversation improves, teams work better.

Redstone HR helps growing teams turn feedback into consistent action. If your 360 feedback questions reveal problems with approvals, policy communication, team coverage, or record accuracy, Redstone HR gives managers the context and automation to fix them in the flow of work. You can centralize PTO and sick leave, sync approved time off to shared calendars, maintain audit-ready records, and give employees fast answers through the AI Policy Assistant, all without relying on spreadsheets or manual follow-up.