Master Feedback Suite

A comprehensive skill for creating, delivering, and managing feedback systems — covering 360-degree reviews, peer feedback frameworks, performance review templates, feedback collection surveys, and constructive criticism delivery techniques.

When to Use This Skill

Choose Master Feedback Suite when you need to:

• Design a structured feedback system for your team or organization
• Write performance reviews with balanced, actionable content
• Create 360-degree feedback questionnaires
• Prepare to deliver constructive criticism effectively
• Build feedback collection forms and analyze results

Consider alternatives when:

• You need employee engagement surveys (use an HR analytics skill)
• You're running customer satisfaction surveys (use a CX skill)
• You need real-time feedback widgets for products (use a product analytics skill)

Quick Start

Copy
# Generate a performance review
claude "Write a balanced performance review for a mid-level software engineer who excels technically but needs improvement in cross-team communication. Include specific examples and growth goals."

Copy
# Performance Review — Q4 2024
**Employee**: Alex Chen | **Role**: Software Engineer II
**Reviewer**: [Manager Name] | **Period**: Oct–Dec 2024

## Overall Rating: Meets Expectations (3.5/5)

## Strengths
**Technical Execution** (Exceeds Expectations)
Alex delivered the payment service migration 2 weeks
ahead of schedule with zero production incidents. Code
review approval rate was 94% first-pass, the highest
on the team.

**Problem Solving** (Exceeds Expectations)
Identified and resolved the race condition in the order
processing pipeline that had caused intermittent failures
for 3 months. Root cause analysis was thorough and the
fix was elegant.

## Areas for Growth
**Cross-Team Communication** (Below Expectations)
Three instances this quarter where API changes affected
the frontend team without advance notice:
- Nov 3: Auth token format change broke mobile app
- Nov 18: Rate limit adjustment without stakeholder review
- Dec 5: Deprecation of v1 endpoints with 1-day notice

**Recommendation**: Share RFC documents with affected
teams 5+ business days before implementation. Join
weekly cross-team sync (Tuesdays 10am).

## Goals for Q1 2025
1. Lead one cross-team project as primary coordinator
2. Present at least one tech talk to engineering org
3. Mentor one junior engineer (pair programming weekly)

Core Concepts

Feedback Framework Types

Framework	Purpose	Frequency	Participants
1:1 Feedback	Direct manager-report dialogue	Bi-weekly	Manager + report
Peer Review	Colleague performance input	Quarterly	3-5 selected peers
360-Degree	Multi-source comprehensive view	Annual	Manager + peers + reports + self
Skip-Level	Senior leadership pulse check	Quarterly	Skip-level manager
Real-Time	Immediate behavioral feedback	As needed	Any colleague

360-Degree Feedback Questions

Copy
## Leadership & Influence
1. How effectively does this person communicate
   their ideas and decisions to the team?
   [1-5 scale + open comment]

2. Does this person actively seek input from others
   before making decisions that affect the team?
   [1-5 scale + open comment]

## Technical Competence
3. How would you rate the quality and reliability
   of this person's technical contributions?
   [1-5 scale + open comment]

4. Does this person stay current with relevant
   technologies and share knowledge with the team?
   [1-5 scale + open comment]

## Collaboration
5. How effectively does this person work across
   team boundaries?
   [1-5 scale + open comment]

6. When conflicts arise, does this person handle
   them constructively?
   [1-5 scale + open comment]

## Growth & Development
7. What is this person's greatest strength?
   [Open response]

8. What one thing would most improve this person's
   effectiveness?
   [Open response]

Feedback Delivery Structure

Copy
## The STAR Method for Specific Feedback

**Situation**: Set the scene with context
"During the client demo on November 15th..."

**Task**: What was expected
"...you were responsible for presenting the new
dashboard features..."

**Action**: What they specifically did
"...and you anticipated the client's questions by
preparing a backup slide with performance benchmarks..."

**Result**: The outcome and impact
"...which built their confidence in our solution and
they signed the contract that same week."

## Anti-Patterns to Avoid
❌ "You're a great communicator" (vague, no evidence)
❌ "You always miss deadlines" (absolute, unfair)
❌ "You should be more like Sarah" (comparison)
❌ "Some people think you're difficult" (anonymous hearsay)

Configuration

Parameter	Description	Example
feedback_type	Type of feedback to generate	"performance_review"
rating_scale	Scale for quantitative ratings	5 (1-5 scale)
include_goals	Add development goals section	true
anonymize	Anonymize peer feedback sources	true
output_format	Delivery format	"markdown" / "form"
review_period	Time period under review	"Q4 2024"

Best Practices

1. Collect specific examples throughout the review period — Don't rely on memory to write reviews. Keep a running log of notable achievements, challenges, and feedback-worthy moments as they happen. A review written from a three-month log is dramatically better than one written from a two-day recall.

2. Balance positive and constructive feedback with a 3:1 ratio — Research consistently shows that feedback is best received and acted on when constructive points are surrounded by genuine positive observations. This isn't about sandwiching criticism — it's about providing an accurate, complete picture.

3. Make every piece of feedback actionable — "Needs to improve communication" is useless. "Share RFC documents with the frontend team 5+ days before API changes, and join the Tuesday cross-team sync" is actionable. If you can't describe what better looks like concretely, the feedback isn't ready.

4. Separate feedback frequency from review cycles — Formal reviews should contain zero surprises. If someone learns about a performance issue for the first time in a quarterly review, the manager failed at ongoing feedback. Use 1:1s and real-time feedback for timely course corrections.

5. Calibrate ratings across teams before finalizing — Different managers have different standards. A "3 out of 5" from one manager might equal a "4 out of 5" from another. Calibration sessions where managers compare ratings and discuss standards produce fairer, more consistent reviews across the organization.

Common Issues

Feedback is too vague to act on — "Good job" and "needs improvement" tell the recipient nothing useful. Every feedback point should answer: what specifically happened, what was the impact, and what should continue or change. Train reviewers to use the STAR method (Situation, Task, Action, Result) for every significant feedback item.

Recency bias dominates reviews — Managers disproportionately remember the last 2-3 weeks of a quarter. An employee who performed brilliantly for 10 weeks and had one bad week gets reviewed on the bad week. Combat this by reviewing your running notes for the full period and weighting observations evenly across months.

Feedback systems collect data but don't drive action — Organizations invest in elaborate 360-degree surveys, generate reports, and then file them. Without a structured follow-up process — where feedback themes become development goals with timelines and accountability — the entire exercise is wasted effort. Close the loop by connecting feedback to concrete action plans reviewed in subsequent 1:1s.