feedback session examples

Standard Operating Procedure: Structured Performance and Project Review Protocols

Document Control

• Document ID: SOP-HR-PRO-00[__]
• Version: 1.[__]
• Effective Date: [YYYY-MM-DD]
• Review Cycle: Annual

1. Purpose & Scope

This document defines the systemic approach for conducting high-impact evaluative discussions. It is applicable to all departments within [Company Name] to ensure consistency, psychological safety, and actionable outcomes during review cycles.

2. Prerequisites

• Documentation: Access to [Performance Management System/Project Log].
• Materials: Pre-filled [Review Template/Scorecard] for the subject.
• Environment: A private, neutral space (physical or virtual) free from interruptions.
• Data: Quantitative metrics or specific behavioral examples from the period of [Start Date] to [End Date].

3. Roles & Responsibilities (RACI)

4. Step-by-Step Procedure

Phase 1: Preparation and Calibration

• Schedule session at least [__] days in advance via [Calendar Platform].
• Review the [Subject Name]’s self-assessment against organizational KPIs.
• Gather 3-5 specific examples of [Success/Growth/Challenge] to ground the discussion in reality.

Phase 2: The Opening and Alignment

• Establish the purpose of the meeting: [__________].
• Create a "safe container" by stating: "The goal of this session is to align on performance and identify blockers."
• Invite the subject to share their perspective on the period first.

Phase 3: Evidence-Based Dialogue

• Present the first example: "I noticed [Specific Behavior/Output] on [Date/Project]. How do you view that outcome?"
• Use the SBI model: Situation, Behavior, Impact.
• Pause for active listening; allow the subject to process and respond.

Phase 4: Action Planning and Closing

• Define the "Next Steps" clearly: [__________].
• Document the agreed-upon growth goals in [System Name].
• Confirm understanding: "What are the primary takeaways from our conversation today?"

5. Quality Assurance, Pro-Tips, and Common Pitfalls

• Quality Assurance: All summaries must be logged in [System Name] within [__] hours of the session.
• Pro-Tip: Use "I" statements (e.g., "I observed...") rather than "You" statements to reduce defensiveness.
• Common Pitfall: Recency Bias. Ensure you are evaluating the entire review period, not just the last two weeks.
• Common Pitfall: Avoiding the "Hard Truth." If performance is below standard, be direct and explicit about the gap.

6. FAQs

Q: What if the subject disagrees with my assessment? A: Acknowledge their perspective and document the disagreement in the record. If the discrepancy is material, schedule a follow-up meeting with [Department Manager/HR] to mediate.

Q: How do I handle emotional responses during the session? A: Pause the conversation. Allow the individual space to compose themselves. Validate their feelings without necessarily changing the assessment, then resume when the subject is ready.

Q: How often should these sessions be held? A: For standard operations, [Frequency, e.g., Quarterly] is the minimum. Critical projects require sessions at the [Beginning/Midpoint/Conclusion].