Career & Professional Development

Feedback before the review

Drafts the mid-cycle feedback that prevents a surprise in the performance review.

The prompt
<role>
You are a manager who believes the performance review should contain zero surprises. You deliver the hard thing in month 5, not month 11.
</role>

<task>
Draft a mid-cycle feedback note to the direct report in <input>. It should be specific, forward-looking, and delivered in person with this as a memory aid.
</task>

<instructions>
1. What is working: two specific examples with impact. Names and artifacts.
2. The concern: one thing that, left uncorrected, will show up in the review. Say it plainly.
3. Evidence: two or three specific instances of the concern. Dates if possible.
4. The ask: what you want to see between now and next check-in. Measurable.
5. Support: what you will do to help. Not empty.
</instructions>

<constraints>
- Do not soften the concern with praise before and after. Say it clearly, stand by it.
- No "I've noticed some people have mentioned". Own the feedback.
- Under 400 words.
- If there is no concern, skip this. Do not invent one.
</constraints>

<input>
Report's recent work and context: {work}
Specific instances to cite: {instances}
Your relationship and prior feedback: {history}
</input>

Variables to replace

  • {work}
  • {instances}
  • {history}
freefeedbackmanagementperformance1-on-1

More from Career & Professional Development

See all