back

PIP, Constructive Criticism & Areas to Improve

Last Updated on August 25, 2026 by Status.net Editorial Team

If you have not yet, start with our complete guide “Performance Reviews: The Complete Guide.” This article is the constructive-feedback and PIP deep-dive that sits beneath it.

The hardest part of a performance review is the part most managers rush. Addressing what is not working takes time, care, and a certain amount of quiet courage. Many managers soften the language until the feedback loses its shape, or they wait until the annual review to raise concerns that should have been named months earlier.

This complete guide covers the full toolkit for the hard half of the performance conversation. You will find how to write constructive feedback that lands well, example phrases for areas of improvement across every competency, how to structure a development plan, when to move toward a formal performance improvement plan, and the language to use for the most sensitive documentation. Read it top to bottom for the full picture, or jump to the section you need right now.

Part 1Constructive Criticism in Performance Reviews

Constructive criticism is feedback that names a real gap and offers a clear path forward. It is honest about what is not working, and it is generous about the possibility of change. The goal is a stronger version of the employee, and every sentence should serve that goal.

Feedback that is only critical often shuts down learning. The employee moves into defense, and the useful information sits on the surface without landing. Feedback that is only positive often produces no change either. The employee walks away feeling good and does the same work the next week. Constructive criticism sits in the middle. It is warm in tone and firm in content.

The SBI Framework: Situation, Behavior, Impact

The single strongest tool for constructive criticism is the Situation-Behavior-Impact framework. It separates what you observed from what you interpreted, and it grounds every piece of feedback in something specific and shared.

Name the situation in one sentence. Describe the behavior in one sentence, using observable action. Share the impact in one sentence, tying the behavior to the team, the customer, or the work. Together, the three parts make the feedback almost impossible to dismiss as unfair.

Template

In [specific situation], you [observable behavior], and the impact was [effect on the team, customer, or work].

Example

In yesterday’s cross-team planning meeting, you interrupted Priya three times while she was walking through the timeline. The impact was that the team missed the details Priya was about to share, and two follow-up messages after the meeting suggested that others noticed as well.

The Feedback Sandwich (and Why It Often Backfires)

Many managers reach for the classic feedback sandwich: a piece of praise, a piece of criticism, another piece of praise. On paper the structure sounds balanced. In practice it often backfires for two reasons.

The first reason is signal. When the pattern is familiar to the employee, they learn to brace for the criticism the moment they hear the opening praise. The praise loses its meaning and the criticism arrives with extra weight.

The second reason is dilution. Softening the criticism between two warm bookends often makes the concern harder to hear clearly. The employee walks away remembering the praise and missing the growth area.

A stronger approach is to keep positive feedback and constructive feedback in separate conversations when possible. When they belong in the same conversation, name the transition clearly. A sentence like “I also want to share one area I would love to see you continue to grow in this year” tells the employee the tone is shifting and invites them to listen with the right attention.

For more, see “30 Examples of Constructive Criticism: Negative Performance Review” and “100 Positive & Constructive Feedback Examples (Performance Review Phrases).”

Part 2Areas for Improvement: Examples by Competency

The most useful area-for-improvement writing names a specific behavior, cites a moment where it showed up, and points to a specific direction for growth. Below is a walk through the most common competency areas, with example phrases you can adapt for each one.

Communication

Communication feedback usually surfaces in three places: written updates that feel unclear, verbal contributions that are quieter than the role requires, or timing that runs behind the team’s cadence.

Examples:

  • Written project updates have sometimes been shared later than stakeholders needed, particularly during the busy Q2 stretch. A predictable weekly cadence would help the team plan around the work.
  • Continues to develop the practice of surfacing ideas in real time during meetings, so they land in the room where the decision is made.
  • Has room to grow in adjusting the level of technical detail for non-technical stakeholders, particularly in the leadership review conversations.
  • Would benefit from writing shorter, sharper written updates. Recent memos have sometimes buried the headline several paragraphs in.
  • Continues to build the confidence to speak up earlier in cross-functional decisions where his perspective is especially valuable.
  • Response time on written updates has occasionally run longer than the team’s working rhythm, particularly during the busiest quarters.
  • Would benefit from setting expectations more clearly at the start of each project, particularly around what stakeholders can expect and when.

Time Management and Prioritization

Time management feedback often surfaces around missed deadlines, over-committed calendars, or difficulty saying no to lower-priority work.

Examples:

  • Cross-functional deadlines have slipped on three initiatives this year. A shared planning routine with the team would help catch the slip before it compounds.
  • Has taken on more projects than the current role can sustain, and would benefit from a more disciplined practice of declining requests that do not align with the team’s priorities.
  • Continues to develop the practice of protecting focused time each week, particularly for the strategic work that requires deeper thinking.
  • Would benefit from setting weekly priorities in writing, so the team has visibility into how work is being sequenced.
  • Has room to grow in flagging blockers earlier, before they slow the broader team’s cadence.
  • Prioritization under quarter-end pressure has been an area of documented concern this year. Continued work with the team on planning practices would help.

Leadership and Influence

Leadership feedback often surfaces in situations where the employee is expected to shape decisions or guide the team, even without formal authority.

Examples:

  • Has room to grow in stepping into moments when the team would benefit from a clearer voice on the direction, particularly during strategic planning conversations.
  • Continues to build the practice of shaping cross-team decisions early in the conversation, where her perspective can guide the direction.
  • Would benefit from taking a more visible role in mentoring newer team members, where the depth of her experience would be especially valuable.
  • Has demonstrated strong technical leadership. The next area for growth is influence in the broader engineering organization, beyond the immediate team.
  • Continues to develop the confidence to make and defend calls in ambiguous situations with clarity.

Collaboration and Teamwork

Collaboration feedback usually surfaces around the ways someone shows up in shared work: handoffs, communication with peers, and the quality of cross-team partnership.

Examples:

  • Continues to build cross-functional relationships with peer teams. Investing time in these partnerships during quieter periods would strengthen collaboration when the work gets busy.
  • Has room to grow in inviting broader team perspectives into decisions that touch multiple functions.
  • Would benefit from writing clearer handoffs when work moves from her scope into an adjacent team, so downstream partners have the context they need.
  • Continues to develop the practice of giving credit generously across the team, particularly on projects with multiple contributors.
  • Has occasionally been slower to respond to teammates’ requests during busy weeks. A short acknowledgment, even when the full response takes longer, would help the team plan.

Delegation and Ownership

Delegation feedback often surfaces when a strong individual contributor moves into a role that requires distributing work across the team.

Examples:

  • Has historically taken on more of the coordination herself than the role requires. Delegating earlier at every project kickoff would free her for the strategic work only she can do.
  • Continues to develop the practice of naming clear owners for every deliverable, particularly on shared projects.
  • Would benefit from stepping back from operational detail as the team scope has grown, and trusting the team to carry more of the day-to-day work.
  • Has room to grow in coaching direct reports through hard decisions, so they build the judgment they will need at the next level.
  • Continues to build the practice of assigning stretch projects deliberately, particularly to team members who are ready for greater scope.

Decision Making and Judgment

Decision-making feedback usually surfaces around speed of decisions, quality of reasoning, or willingness to make and defend calls under ambiguity.

Examples:

  • Continues to develop the practice of making calls under ambiguity, so decisions move forward with the information available at the time.
  • Would benefit from documenting significant decisions and the reasoning behind them, so the team has a shared record to reference.
  • Has room to grow in surfacing decisions to peers and stakeholders before finalizing them, particularly on cross-functional questions.
  • Continues to build the judgment to distinguish between the two or three decisions that truly matter and the many small choices that can be delegated.
  • Has occasionally revisited decisions after they were already communicated, which has created uncertainty for the team. Committing more firmly to decisions once made would help.

Feedback and Coaching

Feedback about feedback surfaces most often for managers and senior individual contributors who are expected to help others grow.

Examples:

  • Continues to build the practice of giving specific, behavior-anchored feedback that names the exact behavior worth reinforcing.
  • Has room to grow in delivering hard feedback in real time, so concerns land close to the moment they arose.
  • Would benefit from writing feedback comments that are shorter and sharper, with a clearer link between the observation and the recommended change.
  • Continues to develop the practice of inviting feedback from her own team, particularly in 1:1 conversations.
  • Has occasionally softened feedback to the point where the direct report did not clearly hear the concern. More directness in the moment would help.

Written Communication and Documentation

Documentation feedback surfaces around clarity of writing, structure of documents, and consistency of the paper trail.

Examples:

  • Continues to develop the practice of writing shorter, more structured project documents, with the recommendation surfaced clearly at the top.
  • Would benefit from more consistent documentation of key decisions in the team’s shared workspace.
  • Has room to grow in tailoring the level of detail for different audiences, particularly for the leadership readouts.
  • Continues to build the habit of documenting concerns and observations in real time, so the record stays accurate as the year unfolds.
  • Written stakeholder updates have sometimes been longer than they needed to be. Trimming to the headline would help the message land.

Attention to Detail

Attention-to-detail feedback surfaces in errors that reach stakeholders, in polish that could be higher, or in small habits that would prevent rework.

Examples:

  • Continues to develop the practice of a final review pass on every deliverable, particularly on client-facing work.
  • Would benefit from tighter quality checks before handoff, so downstream teams do not need to catch small errors.
  • Has room to grow in the polish of written deliverables, particularly formatting and consistency across the document.
  • Small errors on client-facing materials have surfaced across the year. A pre-send checklist would help.
  • Continues to build the habit of double-checking assumptions in data analysis before sharing conclusions with stakeholders.

Strategic Thinking

Strategic-thinking feedback surfaces when the employee is expected to shape direction or connect the work to broader context.

Examples:

  • Continues to develop the practice of connecting the team’s work to broader company priorities in written communication and stakeholder conversations.
  • Would benefit from articulating the two-year direction for the function more clearly, particularly in the annual planning cycle.
  • Has room to grow in translating strategic ambition into a clear, sequenced operating plan.
  • Continues to build the ability to say no to the wrong work, particularly when the requests come from senior stakeholders.
  • Would benefit from framing decisions in the context of longer-term trade-offs beyond the immediate quarter.
  How to Write a Performance Review: Frameworks, Examples

Adaptability and Flexibility

Adaptability feedback often surfaces when priorities shift mid-project, when a new tool or process replaces a familiar one, or when the pace of change outpaces the employee’s comfort with ambiguity.

Examples:

  • Has room to grow in adjusting quickly when project priorities shift, particularly during the recent reorganization of the roadmap.
  • Continues to develop comfort with ambiguity, especially in the early stages of a project before the plan is fully defined.
  • Would benefit from a more flexible approach to process changes, particularly around the shift to the new reporting tool this quarter.
  • Has occasionally held tightly to the original plan even after new information suggested a change in direction. Building in regular checkpoints to revisit the plan would help.
  • Continues to build the practice of treating setbacks as information to act on, rather than a reason to disengage from the project.

Accountability and Ownership of Mistakes

Accountability feedback surfaces when errors are minimized, attributed to circumstances outside the employee’s control, or left unaddressed until someone else raises them.

Examples:

  • Has room to grow in naming mistakes early, before a stakeholder or teammate has to raise them first.
  • Continues to develop the practice of separating what was within her control from what was not, and owning the piece that was hers.
  • Would benefit from following through on commitments made in meetings, particularly the action items from the weekly sync.
  • Has occasionally attributed missed deadlines to factors outside the role, when part of the delay traced back to planning earlier in the project.
  • Continues to build the habit of closing the loop after a mistake, including what will change so it does not repeat.

Customer Focus and Client Relationships

Customer-focus feedback surfaces most often in client-facing roles, where responsiveness, empathy, and follow-through shape the relationship as much as the work itself.

Examples:

  • Has room to grow in following up with clients within the agreed timeframe, particularly after the initial proposal stage.
  • Continues to develop the practice of asking clarifying questions before proposing a solution, so the client’s actual need is fully understood.
  • Would benefit from setting clearer expectations with clients about timelines, so requests for updates happen less frequently.
  • Has occasionally moved to solve the stated problem without probing for the underlying need, which led to rework on two projects this year.
  • Continues to build rapport with long-term clients through more regular check-ins outside of active projects.

Emotional Intelligence and Self-Awareness

Emotional intelligence feedback often surfaces around how someone reads a room, manages their reaction under pressure, or notices the impact their tone has on others.

Examples:

  • Has room to grow in reading the energy of the room during high-pressure meetings, particularly when tension is building among stakeholders.
  • Continues to develop awareness of how his tone lands in written messages, particularly when timelines are tight.
  • Would benefit from pausing before responding in moments of frustration, so the reaction matches the situation rather than the stress of the week.
  • Has occasionally missed signals that a teammate needed support, particularly during a stretch when the team was under heavy deadline pressure.
  • Continues to build the practice of naming her own reaction in the moment, which has already helped defuse a few tense conversations this year.

Conflict Resolution

Conflict-resolution feedback surfaces around a tendency to avoid disagreement entirely, to escalate too quickly, or to struggle with mediating a dispute between others.

Examples:

  • Has room to grow in raising disagreements directly with the person involved, rather than routing the concern through a manager first.
  • Continues to develop the practice of staying in a difficult conversation long enough to reach a real resolution, rather than ending it early to reduce discomfort.
  • Would benefit from separating the disagreement about the work from any feelings about the person, particularly in the recent product debate.
  • Has occasionally escalated disagreements to leadership before attempting to resolve them directly with the peer involved.
  • Continues to build skill in mediating between two team members with different views, particularly by naming the shared goal before working through the disagreement.

For more, see “700 Examples for Areas to Improve (for Growth and Performance),”
“200 Areas of Improvement Performance Review Examples,”
“28 Essential Areas of Improvement for Employees [Examples],”
and “12 Areas of Improvement Examples for Employees (Key Skills To Develop).”

Part 3Writing About Weaknesses

Writing about a weakness carries an extra layer of care. The word itself is heavier than “growth area” or “area for improvement,” and it lands with more finality. The strongest writing about weaknesses names the pattern honestly while keeping the door open for change.

Two moves make a real difference.

The first move is describing behavior, without reaching for a personality label. “Sam is disorganized” is a label the employee cannot act on. “Sam has missed three cross-team deadlines this year, and the team has absorbed the work each time” is a pattern with a clear next step. The same content, framed the second way, opens the door to a real conversation.

The second move is developmental framing. Verbs matter. “Struggles with,” “fails to,” “is unable to” carry judgment and close the conversation. “Is working on,” “is developing,” “has room to grow in” keep the door open for change. The content stays honest either way, and the second set almost always produces more useful conversations.

Example phrases for writing about weaknesses:

  • Sam is working on the pattern of missed cross-team deadlines that has surfaced across three quarters this year. Progress in Q4 has been meaningful, and continued focus on shared planning practices should help.
  • Priya continues to develop her comfort with delegation. She has historically taken on more of the coordination work than the role requires, particularly on high-stakes projects.
  • Michael has room to grow in giving direct feedback to peers in real time. His written feedback is thoughtful; the next area for growth is verbal feedback during shared work.
  • Diego is building his practice of protecting focused time each week. The busy stretches of the year have sometimes eroded the deeper strategic work only he can do.
  • Yuki is working on her presentation skills in larger meetings. Her ideas are strong in written form and small-group settings, and the next area is bringing the same clarity to larger audiences.
  • James is developing his practice of surfacing decisions earlier to stakeholders. Recent projects have been influenced by decisions made faster than the team could absorb.

Related: “200 Examples of Weaknesses for Self-Performance Reviews.”

Part 4Self-Assessments: Writing About Your Own Areas to Improve

Many performance cycles ask employees to write a self-assessment before the manager writes theirs, and the section on weaknesses or areas to improve is often the hardest paragraph to draft. Write too little and it can read as unaware. Write too much and it can read as self-defeating. A well-written self-assessment finds the middle ground: honest, specific, and connected to a plan already in motion.

A few practices make the difference:

  • Choose one or two real growth areas rather than listing every possible flaw. A long list dilutes the ones that matter most.
  • Anchor each growth area in a specific project or moment, the same way a manager would use the SBI framework.
  • Name what is already being done about it. A weakness paired with an active plan reads as self-awareness rather than as a confession.
  • Avoid false modesty. Downplaying real strengths to appear humble makes the weaknesses section harder to trust, since the reader senses the self-rating is not calibrated.
  • Avoid minimizing language for a pattern that has come up more than once. If a manager has already raised it, naming it directly in the self-assessment builds credibility rather than risk.

Example phrases for a self-assessment:

  • One area I am actively working on is delegating earlier in a project. On the Q3 launch, I held onto coordination tasks longer than I needed to, and I have started assigning owners at kickoff instead of midway through.
  • My written updates have occasionally run long, and I know that has made it harder for stakeholders to find the headline quickly. I have started using a one-line summary at the top of every update, and early feedback has been positive.
  • I want to keep developing my comfort with speaking up in larger meetings. My instinct is to share ideas in writing afterward, and I am working on bringing that same clarity into the room in real time.
  • I recognize that I sometimes move to solve a problem before fully understanding the underlying need. I am building the habit of asking one more clarifying question before proposing next steps.

Part 5Development Plans and Areas of Growth

A development plan turns a growth area into a plan the employee can actually execute. Where the review says “what,” the development plan says “how.”

The strongest development plans have four components. A clear growth area, named specifically. A learning method that fits the growth area, whether coaching, training, mentorship, or a stretch assignment. An application context where the new skill will be practiced in real work. A check-in cadence that keeps the plan alive across the cycle.

Growth rarely happens through individual effort alone. A strong development plan also names what the manager will do, whether providing coaching, creating stretch opportunities, or offering feedback on a defined rhythm.

Example development plan phrases:

  • To support Sarah’s growth in strategic communication, the development plan includes executive coaching every four weeks, a short course on structured writing in Q1, and the assignment of the annual strategy memo as a stretch project, with check-ins every six weeks.
  • To support Michael’s continued growth in delegation, the plan includes weekly 1:1s focused specifically on workload, a co-authored planning routine with the team, and monthly check-ins with a senior peer who has already made the same transition.
  • To support Priya’s development in cross-functional influence, the plan includes a formal partnership assignment with the peer leader in product, participation in the quarterly planning process, and quarterly feedback from three cross-functional partners.
  • To support Diego’s continued growth in written communication with leadership, the plan includes a short writing course in Q1, biweekly feedback on his written stakeholder updates, and a shadow assignment on the executive board prep for the mid-year review.
  • To support Yuki’s development in presentation skills, the plan includes a company-wide presentation on the analytics function in Q2, coaching support from the head of design, and monthly practice sessions with a peer group.

Template

To support [employee]’s growth in [specific area], the development plan includes [learning method 1], [learning method 2], and [learning method 3], with check-ins every [interval].

Example

To support Maya’s growth in delegation, the development plan includes executive coaching, a short leadership course, and a stretch assignment leading our cross-functional planning, with check-ins every six weeks.

For more, see “2 Detailed Examples of Professional Development Plans,”
“2 Templates and Examples: Individual Development Plan,”
and “6 Plan Examples – Development Areas for Employees.”

Part 6Performance Improvement Plans (PIPs)

A performance improvement plan is a written document that names specific concerns, defines the changes required, and lays out a defined timeline for improvement. It is one of the most serious tools in the performance conversation, and one of the most easily misused.

A PIP is appropriate when three conditions are true. First, the concerns are clear and have been raised in prior conversations. Second, the concerns have persisted despite feedback and support. Third, the manager and HR agree that formal documentation and a defined timeline are warranted.

A PIP is generally not appropriate in a few scenarios. It should not be used as a surprise consequence for feedback the employee has never received before. It should not be used as a substitute for a difficult conversation that should have happened months earlier. It should not be used as a way to manage someone toward the door without giving them a fair chance to recover. A well-run PIP either produces a real change in performance or leads to a respectful, documented transition. Both outcomes are legitimate; a PIP designed to fail is not.

The Four-Part PIP Structure

The strongest PIPs follow a clear structure.

Part 1: Specific concerns. Name each concern with a specific behavior, evidence, and dates. Vague language weakens the entire document.

  All Job Interview Types & Formats: The Complete Guide

Part 2: Expected behavior. Name the specific, measurable behavior the employee needs to demonstrate. The bar should be clear enough that both the employee and the manager could evaluate it fairly.

Part 3: Timeline. Define the length of the PIP, usually 30, 60, or 90 days, with check-in dates named specifically.

Part 4: Consequences. Name the consequences if the expected behavior is not sustained by the end of the PIP period.

Template

Performance Improvement Plan for [employee], [role], [start date] to [end date].

Concerns being addressed: [Concern 1, with specific behavior, evidence, and dates]. [Concern 2, with specific behavior, evidence, and dates].

Expectations for improvement: Over the next [time period], [employee] is expected to [specific behavior 1] and [specific behavior 2], measured through [signal].

Timeline: This PIP runs from [start date] to [end date], with check-in conversations scheduled for [date 1], [date 2], and [date 3].

Support provided: [Weekly 1:1s with the manager, coaching resources, training, or any other support].

Consequences: If the expected behaviors are not sustained by [end date], next steps may include [formal review of the role or other consequence].

Example

Performance Improvement Plan for Sam Rivera, Product Analyst, September 1 to October 31.

Concerns being addressed: Three cross-functional deadlines were missed during Q2 and Q3, specifically the Q2 launch retrospective (due June 14, delivered June 28), the August reporting cycle (due August 4, delivered August 19), and the September pricing analysis (due September 8, delivered September 22). These delays created downstream impact for both the analytics team and the product team. The concerns were raised in the June 20 and August 25 1:1 conversations, documented in the shared notes.

Expectations for improvement: Over the next 60 days, Sam is expected to deliver every committed milestone on the agreed-upon date, and to flag any anticipated delays at least three business days in advance. Progress will be tracked through the shared project tool and reviewed in each check-in.

Timeline: This PIP runs from September 1 to October 31, with check-in conversations scheduled for September 15, October 1, and October 20.

Support provided: Weekly 1:1s focused specifically on workload and planning. A short course on workload management, completed by September 20. Access to a peer mentor for weekly planning support.

Consequences: If the expected behaviors are not sustained by October 31, next steps may include a formal review of the role.

Documentation Considerations

PIPs carry real legal weight. Every claim in the document should be supported by specific evidence and dates. Every check-in should be documented in writing, with a copy shared with the employee. Every conversation should be scheduled through the same channels used for other performance conversations.

Work closely with HR throughout the process. A short conversation with HR before drafting can save significant rework later, and it protects both the manager and the employee if the process moves toward more difficult decisions.

When Coaching Is Enough (and When a PIP Is Needed)

Many performance gaps respond well to coaching before a formal PIP becomes necessary. Coaching works well for a first-time gap, for a pattern the employee has not yet been told about clearly, or for a skill that is genuinely still developing. A PIP becomes the right tool when the pattern has already been named, more than once, and it has continued anyway.

A few questions help clarify which tool fits the situation:

  • Has this concern already been raised directly with the employee, in a documented conversation? If not, coaching and a clear conversation usually come first.
  • Has the employee had a real chance to change the behavior, with support, before now? A PIP without a prior fair chance often reads as punitive rather than developmental.
  • Is the concern about a skill that can be built with practice, or a mismatch between the role and the employee’s current capabilities? The answer shapes whether a PIP or a broader conversation about role fit is the more honest next step.
  • Would the team or the business absorb real risk if the pattern continues for another quarter without formal documentation? If so, moving to a PIP sooner is often the fairer choice for everyone involved.

What Happens When a PIP Ends

A PIP should end with a clear, documented decision, not an ambiguous fade into the next review cycle. There are generally three outcomes.

  • Successful completion. The employee sustained the expected behavior through the full timeline. Document the outcome clearly, close the PIP formally, and continue reinforcing the improvement with specific recognition. A successful PIP deserves to be acknowledged, not quietly filed away.
  • Partial improvement. Some progress occurred, but not enough to fully close the concern. Some organizations extend the timeline with a revised set of expectations. This should be a deliberate decision made with HR, not a default when the manager feels uncertain about the next step.
  • No meaningful improvement. The expected behavior did not materialize despite support and a fair runway. This typically leads to the consequence named in the original PIP document, whether that is a role change, a formal review, or a separation process managed with HR.

For more, see “How to Write a Performance Improvement Plan (PIP).”

Part 7Unsatisfactory Performance Letters

An unsatisfactory performance letter is a formal document, usually paired with or following a PIP, that names sustained performance concerns and often signals the beginning of a formal review process. It carries even more documentation weight than a standard PIP.

The letter is used in a small number of scenarios. Most often, it accompanies the conclusion of a failed PIP, documenting the ongoing concerns. Sometimes it precedes a PIP when the concerns are serious enough to warrant formal documentation immediately. In some organizations, it accompanies a termination decision.

The structure of an unsatisfactory performance letter usually includes:

  1. A clear statement that performance is being classified as unsatisfactory, with the specific classification the company uses.
  2. A summary of the concerns that led to the classification, with specific behaviors, evidence, and dates.
  3. A reference to prior performance conversations and any prior formal documentation, including PIPs.
  4. A description of the support provided during the review period.
  5. A clear statement of the next steps and any formal consequences.
  6. A place for the employee to acknowledge receipt of the letter.

Example unsatisfactory performance letter language:

This letter is to inform you that your performance during the review period from [start date] to [end date] has been classified as unsatisfactory in relation to the responsibilities of your role as [role].

The specific concerns include sustained gaps in [specific area 1], documented in the [date] and [date] performance conversations, and [specific area 2], documented in the [date] performance improvement plan.

These concerns have persisted through the review period, despite the support provided, which included weekly 1:1s with your manager, coaching resources, and the training program completed in [month].

Given the sustained pattern, the next steps include [formal review of the role, or other formal consequence], scheduled for [date].

Please sign and return this letter to acknowledge receipt. This acknowledgment does not indicate agreement with the classification, only receipt of the letter itself.

 

Work closely with HR on the exact language of any unsatisfactory performance letter. The words carry legal weight and should be reviewed carefully before delivery.

For more, see “5 Examples: Unsatisfactory Performance Letter to Employee.”

Part 8How Employees Should Respond to Constructive Feedback

Receiving feedback well is a skill of its own, and often an under-taught one. The strongest response has three moves: listening carefully, asking clarifying questions, and taking time to process before deciding how to act.

The first move is to listen without immediately defending. Feedback that lands hard often produces the instinct to explain, correct, or push back in the moment. That instinct usually shuts down the conversation and misses information the manager was trying to share. A short, steady acknowledgment gives the manager room to keep going.

The second move is to ask clarifying questions. A single well-shaped question can turn vague feedback into feedback the employee can actually act on. Ask for specific examples. Ask what a stronger version of the behavior would look like. Ask what success would look like in three months.

The third move is to take time. If the feedback is significant, saying “Thank you for sharing this. I would like to sit with it for a few days and come back with my response” is a signal of mature judgment. Managers almost always respect a thoughtful reply more than an immediate defense.

Example phrases employees can use in response to constructive feedback:

  • Thank you for sharing this. Can you help me understand a specific moment when you saw the pattern show up?
  • I appreciate the honesty. What would a stronger version of that behavior look like in practice?
  • That is helpful to hear. Would you be open to walking me through the situation you mentioned so I can understand it more fully?
  • I want to take a few days to sit with this and come back with a real plan. Would it work to reconnect on Thursday?
  • Thank you. This is not entirely what I expected to hear, and I want to make sure I understand it fully before I respond. Can you share what you would like to see change in the next month?
  • I hear the concern about [specific area]. I have been aware of that as a growth area and would love to talk about the plan I have been building around it.
  • I want to acknowledge what you shared. My experience of that situation was different in some ways, and I would love to walk through it together so we can see the fuller picture.
  • Thank you for the specific example. It helps me see the pattern more clearly, and I have a few ideas for how I would approach it differently going forward.

For more, see “50 Example Phrases for Employees Responding to Feedback.”

Part 9How to Give Constructive Feedback (Manager Skills)

Giving constructive feedback well is one of the most important skills a manager builds across a career. The strongest managers make feedback a steady, low-stakes practice, so the harder conversations arrive against a foundation of trust.

The conversation itself usually has a clear shape. Open with the specific situation. Describe the behavior you observed. Share the impact it had. Invite the employee to respond and share their perspective. Discuss what a stronger version of the behavior would look like. Close with a clear next step and a check-in date.

Timing matters as much as structure. Feedback delivered too late in a project loses its usefulness. Feedback delivered in front of others can feel like humiliation, no matter how carefully worded. Feedback delivered when the manager is tired or frustrated often lands harder than intended. The strongest managers deliver feedback close to the moment it happened, in a private setting, when they have the calm to speak with care.

Following up is often the missing piece. A single conversation rarely produces a change on its own. A brief written recap of what was discussed, a scheduled follow-up check-in, and a willingness to notice the change when it happens all help the feedback take root.

Example conversation openings for managers:

  • I want to share some feedback from Tuesday’s planning meeting. Is now a good moment, or would later this afternoon work better?
  • I noticed a pattern I want to raise with you, and I would rather talk through it now than wait for our next 1:1. Do you have 15 minutes?
  • I have been thinking about the way the Q3 launch went, and I want to share both what worked and one area I think we can strengthen together.
  • There is something I want to name from yesterday’s cross-functional meeting. Can I share it with you?
  • I want to give you some feedback that I have been sitting with for a few days. It is meant to be constructive, and I want to talk through it together.
  • Before we get into the agenda for today, I want to share a piece of feedback about the client conversation yesterday. Would that work?

Example feedback statements using SBI:

  • In yesterday’s planning meeting, you cut in three times while Priya was walking through the timeline. The impact was that the team missed the details Priya was about to share, and two people mentioned it to me afterward.
  • During the Q2 launch, the written project updates ran later than the team’s working rhythm, and stakeholders reached out twice looking for status. The impact was that the group lost some confidence in the delivery timeline.
  • In the last two client escalations, the response time on the internal notification thread was longer than the incident protocol calls for. The impact was that the support team could not begin their part of the work as quickly as usual.
  • During the Thursday design review, you shared strong technical feedback in writing after the meeting, though it did not come up in the conversation itself. The impact was that the group made decisions without the input that would have shaped them.
  • In the last two 1:1 conversations, we agreed on next steps that did not appear in the written recap. The impact is that we sometimes arrive at the next 1:1 with different understandings of what was decided.
  The Complete Guide to Manager Performance Reviews

Preparing to Deliver Feedback

The conversation itself usually goes better because of what happens before it, not just during it. A short round of preparation makes the difference between feedback that lands with clarity and feedback that unravels in the moment.

  • Gather two or three specific examples in advance. A single anecdote can feel like an overreaction; a documented pattern feels like an observation worth discussing.
  • Decide the one change you most want to see, in concrete terms. If you cannot describe the desired outcome clearly, the employee will have a hard time acting on it.
  • Check your own emotional state before starting the conversation. Feedback delivered while frustrated tends to carry more edge than intended.
  • Choose a private setting and a moment when neither of you is rushing to another meeting. Feedback squeezed into the last five minutes of a call rarely gets the attention it deserves.
  • Anticipate how the employee might respond, including the possibility of surprise, disagreement, or a defensive reaction, and plan how you will respond to each.

Handling Emotional Reactions During the Conversation

Even well-prepared, well-delivered feedback sometimes produces a strong emotional reaction. Tears, frustration, or a defensive shutdown do not necessarily mean the feedback was delivered poorly. They often mean the feedback mattered.

  • Pause and let the reaction happen. Rushing to fill the silence or over-explain often makes the moment feel more uncomfortable for both people.
  • Acknowledge the emotion directly. A simple “I can see this is landing hard, and I want to make sure we get through it together” often helps the employee regain their footing.
  • Offer a short break if the reaction is strong. Stepping away for a few minutes and returning to finish the conversation often produces a far better outcome than pushing through.
  • Return to the specific facts once the emotion has settled, rather than abandoning the substance of the feedback to smooth things over.
  • Follow up in writing afterward, and check in again within a day or two. A strong reaction in the room does not need to define the relationship going forward.

For more, see “How to Give Effective Feedback (and Avoid Mistakes).”

Part 10Adapting Constructive Feedback for Remote and Hybrid Teams

Feedback that would land clearly in a hallway conversation can lose its warmth by the time it travels through a screen or a chat message. Remote and hybrid teams need a few adjustments to keep constructive feedback effective.

  • Keep anything beyond a small, quick note off of chat tools. A written message in Slack or Teams strips out tone, and a significant piece of feedback delivered that way often lands harder than intended.
  • Turn cameras on for feedback conversations when possible. Tone and body language carry a large share of the message, and a phone call or a camera-off video call removes much of that signal.
  • Give a little more notice before scheduling a feedback conversation over video than you would for an in-person chat. A meeting invite with a vague title can create anxiety before the conversation even starts; a short line like “I want to talk through the Q3 project together” sets a calmer tone.
  • Build in slightly longer pauses during the conversation. Video calls compress natural conversational rhythm, and a pause that would feel normal in person can feel like dead air on a call.
  • Send the written recap even more reliably than you would for an in-person conversation. Remote employees do not get the informal follow-up hallway moments that often reinforce or clarify feedback delivered face to face.
  • Account for time zones when scheduling both the conversation and the follow-up check-in, so an employee is not receiving significant feedback right before logging off for the day.

Part 11Making Feedback a Continuous, Year-Round Practice

Feedback that only happens at review time arrives late and carries too much weight for a single conversation to hold. The strongest managers spread feedback across the year in small, regular moments, so nothing has the chance to build into a surprise.

  • Use weekly or biweekly 1:1s as the primary channel for ongoing feedback, rather than saving observations for a quarterly or annual review.
  • Write a short note to yourself right after a moment worth flagging, even if the conversation happens later. Details fade quickly, and a note taken within the day keeps the feedback specific.
  • Tie a short check-in to any active development plan, so growth areas get revisited on a defined rhythm instead of resurfacing only when a formal review is due.
  • Watch for “feedback debt,” the pattern of noticing something worth raising and letting it slide because the moment feels inconvenient. Feedback debt compounds, and it often surfaces all at once at review time, which feels unfair to the employee.
  • Balance the rhythm with recognition. A steady practice of naming what is working, alongside what needs to grow, keeps the relationship from feeling like a running list of problems.

Frequently Asked Questions

What is the difference between constructive feedback and a performance improvement plan?

Constructive feedback is the ongoing practice of naming behaviors that could be stronger and pointing toward growth. It can happen in a 1:1, in a written comment, or in the flow of a project. A performance improvement plan is a formal document that names specific concerns, sets defined expectations, and lays out a timeline for improvement. A PIP is a much more serious step, and it usually follows a period of constructive feedback that has already been raised in prior conversations.

How long should a PIP be?

Most PIPs run 30, 60, or 90 days. The length should match the complexity of the changes required. A behavioral change may be observable within 30 days. A change in project execution or delivery pattern usually takes 60 to 90 days to demonstrate meaningfully. Work with HR on the right timeline for your situation.

Should I tell the team that an employee is on a PIP?

Generally no. A PIP is a confidential document between the employee, the manager, and HR. Sharing it with the broader team breaks trust with the employee, creates workplace anxiety for others, and can create legal exposure for the company. The one exception is when specific responsibilities need to be temporarily redistributed while the PIP is in progress, and even then, the redistribution should be framed as an operational change without disclosing the PIP itself.

Can an employee refuse to sign a PIP?

Signing a PIP is usually an acknowledgment that the employee has received the document, and does not indicate agreement with the content. Most companies ask the employee to sign to confirm they received the document. If an employee declines to sign, the manager can note the refusal in the record. Work with HR on the specific practice at your company.

How do I address a pattern of concern with an employee who has been receiving positive feedback for years?

Slowly, and with care. Employees who have received consistent positive feedback often experience a sudden shift as unfair or arbitrary. The strongest approach is to start with a private conversation that names the pattern you have been noticing, invite the employee to share their view, and agree on a short-term plan to address the concern. Save the more formal moves for later, if the pattern continues after the initial conversation.

How do I write about a weakness without discouraging the employee?

Describe behavior, use developmental verbs, and pair every concern with a clear path forward. Words like “is working on,” “is developing,” “has room to grow in” keep the door open for change. Words like “struggles with,” “fails to,” “is unable to” close it. The same honest content, framed developmentally, produces conversations that lead to growth.

What if the employee disagrees with the feedback?

Disagreement is not necessarily a bad sign. Sometimes the employee is right, and the manager’s picture of the situation is incomplete. Sometimes the disagreement itself reveals a gap in the employee’s self-awareness. The most useful move is to invite the employee to share specific evidence for their view, weigh it honestly against the pattern you have observed, and update either the feedback or the plan based on what you learn.

Can constructive feedback be shared in writing?

Yes for smaller feedback, no for larger concerns. Small, quick observations often land well in writing, particularly when the culture is written-first. Larger concerns almost always deserve a real conversation first, followed by a written recap. A significant piece of feedback delivered only in writing often lands harder than the writer intended.

What is the difference between coaching and a performance improvement plan?

Coaching is an ongoing, informal investment in helping someone build a skill, and it usually happens without a written document attached. A PIP is a formal, time-bound document with named consequences, used after coaching and feedback have already been tried and the concern has continued. Most performance gaps should start with coaching. A PIP becomes the right tool when the pattern persists despite that support.

How do I write about my own weaknesses in a self-evaluation?

Pick one or two real growth areas rather than a long list, anchor each one in a specific project, and name the plan already underway to address it. A self-assessment that pairs an honest weakness with active steps toward improvement reads as self-aware, while one that lists flaws without a plan can read as unfinished.

How does giving feedback change for remote or hybrid employees?

Feedback for remote employees needs a little more intention. Keep anything significant off of chat tools, use video with cameras on when possible, give more notice before the conversation, and send a written recap afterward, since remote employees do not get the informal hallway follow-up that often reinforces in-person feedback.

What happens if an employee successfully completes a PIP?

Document the outcome clearly and close the PIP formally, rather than letting it fade without a decision. Continue reinforcing the improvement with specific recognition over the following months, since sustained change often needs continued encouragement to stick.

What happens if an employee does not improve during a PIP?

This typically leads to the consequence named in the original PIP document, which may include a formal review of the role or a separation process. Work closely with HR at this stage, since the documentation from the entire PIP period will matter significantly for whatever comes next.

How often should managers give feedback throughout the year?

In most cases, weekly or biweekly 1:1s work well as the primary channel for ongoing feedback, supplemented by a note in the moment whenever something specific is worth flagging. Saving all feedback for a quarterly or annual review often lets small concerns build into larger surprises.

What should I do if an employee becomes emotional during a feedback conversation?

Pause and let the reaction happen rather than rushing to fill the silence. Acknowledge the emotion directly, offer a short break if needed, and return to the specific facts once things have settled. A strong emotional reaction in the room does not need to define the relationship going forward, especially if you follow up with care in the days after.

Conclusion

The harder half of the performance conversation asks more of both managers and employees. It calls for specificity, care, and the willingness to name what is not working without diminishing the person doing the work.

When you are ready to go deeper, return to our complete guide “Performance Reviews: The Complete Guide” for the full system. For the largest phrase library across every competency, see “2000+ Performance Review Phrases: The Complete List.”

The best constructive feedback is honest enough to matter, specific enough to act on, and warm enough to be received.

Posted in: Complete Guides