Performance Conversation Script — Development-Focused Review

Welcome and purpose

This script helps managers hold a development-focused performance conversation that is candid, respectful, and action-oriented. Use the phrasing as a template—adapt words to your voice, the relationship, and the individual. The goal is to describe observed behavior, co-create a realistic growth plan, and leave with clear commitments and a follow-up rhythm that builds trust.

Script structure (high-level)

1. Opening: state purpose and create psychological safety
2. Data: share specific examples using situation–behavior–impact
3. Employee perspective: invite self-assessment and listening
4. Gap & expectations: clarify the desired behavior and why it matters
5. Development plan: co-create steps, milestones, support, and measures
6. Check for understanding and commitment
7. Follow-up cadence: schedule check-ins and success criteria

Detailed script with sample phrasing

1) Opening: purpose and safety

Start by anchoring the conversation.

"Thanks for meeting with me. I want to have an open conversation focused on your development. My intention is to be candid and constructive—so we can find ways for you to do your best work and for the team to succeed. I’ll speak from what I’ve observed and want to hear your perspective too."

2) Data: specific examples of behavior and impact (use S-B-I)

Describe observable facts—avoid labels or motives. Use Situation–Behavior–Impact (SBI):

"On Tuesday during the client meeting (situation), you interrupted the client twice and redirected the conversation to technical details (behavior). That left the client frustrated and we missed clarifying their main goal (impact)."

When possible, include more than one example and note frequency or pattern without exaggeration.

3) Employee perspective: invite self-assessment

Give space for the employee to explain their view. Listen actively, reflect, and summarize.

"Help me understand what was happening from your point of view. What do you think went well, and where might things have gone differently?"

Use follow-up prompts: "What were you trying to accomplish?" "What made that difficult?" Summarize back: "So what I’m hearing is..."

4) Gap & expectations: clarify desired behavior

State the gap between current behavior and expectations, and explain why closing it matters for the role, team, or customer.

"When conversations go like this, we risk losing clients and making it harder for teammates to contribute. I expect you to let the client finish, ask clarifying questions, and then summarize next steps before diving into technical details."

Be concrete: give an example of the preferred behavior in the same situation.

5) Development plan: learning activities, milestones, and supports

Co-create specific, timebound steps. Use SMART-style detail where possible.

• Goal: "Demonstrate improved client meeting facilitation by letting clients complete their points and summarizing their needs before technical discussion."
• Actions: "Attend a 1-hour facilitation skills workshop by Sept 15; practice with me in two role-plays before client meetings; use a short checklist during meetings (ask, reflect, summarize)."
• Milestones & measures: "In the next 4 client meetings, receive 3 peer or manager observations and show a decrease in interruptions; client follow-up survey shows clearer understanding."
• Support: "I will attend one meeting with you as an observer; HR can enroll you in a course; I’ll provide feedback forms."

Record who owns each action and specific dates.

6) Check for understanding and commitment

Confirm understanding and secure agreement to try the plan.

"Can you summarize what you heard and tell me which of these actions you can commit to? What might get in the way, and how can I help?"

Listen for realistic commitments. If the employee resists, explore barriers rather than insisting—use problem-solving to adapt the plan.

7) Follow-up cadence and success measures

Agree on when and how you will follow up and the criteria for success.

• Short-term check-in: 2 weeks — quick 20-minute progress and obstacle review.
• Medium review: 6 weeks — review milestone progress, observations, and client feedback.
• Success indicators: reduced interruptions in meetings, positive peer/manager observations, clear client outcomes.
• Documentation: summarize the plan in a brief note and share with the employee after the meeting.

Quick script (condensed)

"Thanks—this is a development conversation. I observed X (situation/behavior/impact). What’s your view? Here’s the gap I see and why it matters. Let’s agree on 2–3 concrete steps, who will do what, and when we’ll check back. Can you summarize and commit to the first step?"

Manager prep checklist

• Collect 2–3 specific examples using SBI (situation–behavior–impact).
• Decide the key expectation(s) you want to clarify.
• Prepare suggested development options (coaching, courses, practice, buddy).
• Plan a realistic follow-up schedule and who will support the employee.
• Create a short written summary to share after the meeting.

Coaching tips & common pitfalls

• Keep tone curious and collaborative—state observations, not judgments.
• Avoid labeling ("lazy," "resistant"). Describe behavior and its effect.
• Focus on outcomes: what will success look like for the employee and the team?
• Watch for defensiveness—use reflective listening and invite concrete next steps.
• Limit the conversation to the most important 1–3 development priorities. Too many items reduce follow-through.
• Document commitments immediately and share them to build accountability and reduce memory errors.

Example development-plan template (copyable)

Development Priority: ____________________________

Desired Behavior / Success Criteria: ____________________________

Actions (who / what / by when):

1. ________________________________ (Owner) — By ______
2. ________________________________ (Owner) — By ______
3. ________________________________ (Owner) — By ______

Support & Resources: ____________________________

Check-in Dates: 1) ______ 2) ______

When not to use a development script

If the behavior is a serious safety, ethics, or legal violation, follow your organization's formal investigation and HR process rather than a coaching script. This script is designed for performance development conversations intended to help employees improve.

Use this script as a reusable pattern. Over time, keep the parts that reliably build trust and produce measurable improvement, and adapt the language to fit your team’s culture and the individual’s needs.