Feedback Frameworks & Calibration Guide
Practical models, calibration routines, scripts, and a ready-to-use template to make feedback timely, fair, and focused on development.
Welcome — make feedback useful, humane, and consistent
Feedback does two things well when it’s done right: it helps someone understand how their work shows up for others, and it points to practical next steps they can try. This guide collects compact, usable models, a meeting agenda for calibration, sample rating anchors, simple manager scripts, and a development-oriented feedback plan template you can copy and adapt.
Why structured feedback and calibration matter
Unstructured feedback often feels personal, inconsistent, or punitive. Structured frameworks reduce ambiguity, improve fairness, and help people actually change behavior. Calibration aligns shared expectations across managers so similar performance receives similar feedback and ratings, which strengthens trust and engagement.
Short, practical feedback models
SBI — Situation, Behavior, Impact
Use SBI to describe an observable moment and its effect without inferring intent.
- Situation: Where/when the behavior happened (brief).
- Behavior: Specific observable actions (no labels).
- Impact: What changed for the team, customer, or outcome.
Example: “During yesterday’s client call (situation), you interrupted the client several times while they were describing requirements (behavior). That made it harder for us to capture their priorities and left the client feeling unheard (impact).”
Feedforward
Focus on future behavior rather than blaming the past. Invite the recipient to try an alternative and offer support.
Example: “Next time, try pausing for two seconds before responding so the client can finish. I can help by taking notes so you can stay present.”
Calibration meeting agenda (compact, repeatable)
Use this agenda for a 60–90 minute manager calibration session. Adjust timing to team size.
- Set the purpose and norms — remind participants the goal is shared standards, not manager comparison.
- Review a small batch of anonymized examples or summary ratings (3–8 items).
- For each example: share evidence, propose rating, explain rationale, discuss differences.
- Agree on anchors or phrasing where disagreement is common.
- Capture decisions and any follow-up actions (coaching needs, communication, recalibration).
- Close with a short recap: what changed in the rubric or anchors and who owns updates.
Sample rating anchors (behavioral, adaptable)
Anchors help make ratings less subjective. Below are examples for a 5-point scale; customize wording to your role or competency.
- 5 — Consistently exceeds expectations: Regularly produces work that advances team outcomes; proactively helps others; errors are rare and corrected quickly.
- 4 — Meets and sometimes exceeds: Dependable delivery with occasional stretch contributions; requires minimal correction.
- 3 — Meets expectations: Delivers required work reliably but seldom goes beyond; occasional guidance needed.
- 2 — Approaching expectations: Requires repeated guidance; gaps in consistency or quality affecting timelines.
- 1 — Below expectations: Work often missed or low quality; requires sustained coaching and a clear improvement plan.
Manager calibration scripts — phrases that keep things constructive
These short scripts can be used during one-on-one feedback conversations or in calibration discussions.
- Setting context: “I want to share what I observed and the impact so we can find practical next steps.”
- Giving behavior-focused feedback: “When X happened, I noticed Y. That affected Z.”
- Inviting perspective: “What’s your view on that moment? I want to understand any context I missed.”
- Offering feedforward: “One option to try is A. If you want, I’ll check in after B to hear how it went.”
- Handling disagreement in calibration: “Tell me which evidence you’re using. Where do our interpretations differ?”
Development-focused feedback plan (template)
Copy this simple template into a shared doc. Keep plans short, specific, and measurable.
Feedback Plan
- Observed behavior (brief): [Example using SBI]
- Why it matters (impact): [How it affects customers/team/outcomes]
- Desired behavior (concrete): [What different behavior looks like]
- Action steps & supports: [Specific actions, training, peer partner, manager check-ins]
- Success indicators: [What you’ll see that shows progress — observable measures]
- Owner & checkpoints: [Who owns the plan and when to review]
Common pitfalls and how to avoid them
- Using labels instead of behaviors — avoid phrases like “lazy” or “unmotivated.”
- Focusing only on outcomes — include specific behaviors and context so feedback is actionable.
- Calibration as an annual checkbox — calibrate frequently enough that standards stay meaningful.
- Confusing honest feedback with blame — emphasize improvement and support.
- Ignoring the recipient’s voice — invite their perspective and co-create the plan.
Measuring whether your feedback and calibration are working
Pick a few simple signals and check them regularly:
- Perceived fairness in pulse surveys or quick check-ins.
- Consistency of ratings across managers for similar roles or contributions.
- Completion rate and quality of development plans and subsequent improvement.
- Qualitative signs: fewer escalation conversations, clearer career conversations, more people asking for feedback.
Practical next steps
- Try the SBI model in your next feedback conversation; keep the focus on observable behaviors and impact.
- Run a short calibration meeting using the agenda above with a handful of anonymized examples.
- Create and share the development plan template in your team space so actions are visible and owned.
Resources & templates to copy
Use the sample anchors and the feedback plan template above as starting points. Adapt language to your role, culture, and local norms. If you want to make this interactive, consider turning the Feedback Plan into a shared form so plans and progress can be tracked.
Short, behavior-focused feedback and regular calibration create fairer evaluations, clearer development pathways, and more trusting teams.
Discussion
Comments and conversation will live here.