Leadership 360 Toolkit & Calibration Process

Purpose & what this toolkit contains

This toolkit helps you run a fair, development-focused Leadership 360: a validated survey, guidance for anonymized reporting, facilitator notes and scripts for development conversations, a calibration meeting agenda and protocol to align ratings, and a prioritized development planning template leaders can use after their debrief. Use the pieces together or pick the parts you need.

What you’ll find here

• Survey structure and sample questions, grouped by competency with rating anchors
• Reporting rules that protect anonymity while surfacing patterns and priorities
• Facilitation notes and a short script for one-on-one development debriefs
• A calibration meeting agenda, step-by-step protocol, and a simple rubric to align ratings
• A prioritized development planning template and a worked example
• Quick timeline, common pitfalls, and practical tips to reduce bias

How to use this toolkit

1. Customize the survey questions to match your competency model and organizational language.
2. Run the survey using anonymous collection (see Reporting rules).
3. Generate the aggregated report and hold one-on-one debriefs with leaders.
4. Use the calibration meeting to check for systemic bias, align interpretation, and ensure fairness across roles or business units.
5. Agree on prioritized development goals and capture them in the planning template.

Survey structure & sample questions

Prefer a short, competency-based instrument: 25–40 items across 6–8 competencies is typically high-value and higher-response friendly. Use behavioral statements rather than personality descriptions.

Rating scale and behavioral anchors

Recommended scale: 1—5 (1 = Needs development, 3 = Meets expectations, 5 = Role model). Anchor the scale with brief behavior descriptions when possible.

Competency groups and sample items

• Leading Others
  • Sets clear expectations and follows up so people know when work is done well.
  • Holds people accountable with fairness and clarity.
• Communication
  • Explains decisions and reasoning in ways that are understandable and timely.
  • Listens actively and responds constructively to concerns.
• Collaboration & Influence
  • Builds useful cross-team relationships and brings people together to solve problems.
  • Persuades others with evidence and respect rather than authority alone.
• Developing People
  • Coaches team members to improve performance and builds growth opportunities.
  • Provides useful feedback that leads to change.
• Strategic & Decision Making
  • Balances short-term delivery with longer-term priorities and trade-offs.
  • Makes timely decisions using relevant information and input from the team.
• Execution & Results
  • Delivers on commitments and helps the team focus on the highest-value work.
  • Removes obstacles that prevent progress.

Reporting: aggregation, anonymity, and layout

Reports should show patterns and priorities rather than exposing individual respondents. Use these rules:

• Aggregate scores by rater group (self, direct reports, peers, managers, other). Show means, sample sizes, and confidence notes.
• Only display free-text comments when at least three respondents exist in that rater group for that leader, or after de-identification has been verified.
• Include a simple visual summary — e.g., radar chart of competency means, a small table of percentile comparisons, and a short narrative of key patterns (strengths, development areas, surprises).
• Flag low-response areas where interpretation should be cautious (for example, < 5 total respondents).
• Provide suggested interpretation notes for facilitators: focus on recurring themes across groups rather than single high/low scores.

Facilitation notes for development debriefs (one-on-one)

Goal: help the leader interpret feedback, choose 1–3 prioritized development priorities, and commit to next steps.

Before the meeting

• Review the full report and highlight consistent patterns across rater groups.
• Prepare open questions and a short set of examples to illustrate observations.

During the meeting — 45 minutes recommended

• Open with intent: "This is about development, not performance decisions."
• Ask the leader: "What patterns stand out to you? What surprises you?"
• Explore strengths briefly, then focus on 1–3 development priorities anchored in evidence from the report.
• Co-create a first draft of the development plan using the template below.

Sample phrasing: "I notice your direct reports rated you lower on 'Coaching' than peers did. Can you tell me about a recent example where you coached someone?"

Calibration meeting: agenda & protocol

Use calibration when multiple raters or units are involved, or when scores may affect role comparisons. Keep calibration focused on fairness and shared interpretation, not on forcing identical numeric scores.

Suggested 90-minute agenda

1. Welcome, purpose, and confidentiality reminders (5 minutes)
2. Review scoring rubric and behavioral anchors (10 minutes)
3. Discuss selected anonymized reports (45 minutes) — pick examples that illustrate potential misalignment or surprising differences
4. Agree adjustments or interpretation principles (20 minutes)
5. Capture actions and next steps (10 minutes)

Calibration protocol

• Use a short scoring rubric: 1 = observable behavior below expectations, 3 = consistent expected behavior, 5 = role model/consistently exceeds expectations.
• When groups show systematic differences (e.g., all managers score lower than peers), discuss root causes (different standards, context, or framing) before adjusting.
• Document any changes to thresholds or interpretation rules so they’re applied consistently across leaders.

Prioritized development planning template (use this during debrief)

Capture no more than three priorities. Make each goal SMART and include measures, support, and check-ins.

Example (short): Goal: Improve coaching conversations so direct reports report more frequent, useful feedback. Why: Direct reports rated 'Developing People' 2.8 vs peers 3.6. Success indicator: 80% of direct reports say they received actionable feedback within 6 weeks. Activities: 1:1 practice sessions with coach, peer-observed coaching, targeted reading. Check-ins: manager and coach weekly for 8 weeks.

Quick timeline (example)

• Week 0: Launch / rater selection
• Weeks 1–2: Survey open
• Week 3: Close survey, generate report
• Week 4: One-on-one debriefs
• Week 5: Calibration meeting
• Weeks 5–12: Development actions and regular check-ins

Tips to reduce bias and improve fairness

• Use behaviorally specific items rather than general adjectives.
• Require a minimum number of respondents before publishing subgroup comments.
• Encourage raters to focus on observable behavior and recent examples.
• Calibrate raters on the same rubric and review a few anonymized examples together.
• Separate development conversations from compensation or promotion decisions.

Common mistakes to avoid

• Running a 360 without follow-up development support.
• Overloading the instrument with too many items; longer surveys reduce response quality.
• Exposing identifiable comments — this harms trust.
• Using 360 data alone for high-stakes decisions without context and calibration.

Platform and capability notes

This static toolkit is ready to be converted into interactive artifacts to improve data quality and follow-through. Practical next capabilities to implement:

• Convert the survey to an interactive form so respondents complete the exact structured questions and responses are stored for analysis (platform interactive forms).
• Save responses via the platform submission capability and store them for trend analysis and auditability.
• Package the survey, reporting templates, calibration agenda, and planning template into an acquireable toolkit that teams can copy and tailor for their context.

Next steps & recommended readings

• Start with a pilot group to refine wording and response thresholds.
• Run one calibration meeting after the pilot and adjust reporting rules as needed.
• Provide short facilitator training so debriefs focus on development not defensiveness.