Performance Systems and Integration

In the previous lesson, you built a complete delegation operating system — one anchored in the Definition of Done, reinforced by the Accountability Ladder, and sustained through structured check-in rhythms. You now know how to hand off work clearly, foster ownership, and stay connected without micromanaging. But what happens when, despite all of that, someone on your team is consistently falling short? This is where performance management enters the picture, and it is the area where many people managers feel the least prepared. Throughout this unit, you will learn how to structure underperformance conversations that are fair and data-driven, how to set KPIs that actually guide behavior, and how to facilitate a Performance Improvement Plan (PIP) that gives a struggling team member a genuine path forward. These are not punitive tools — they are leadership instruments that, when used well, protect your team's standards while treating every individual with dignity.

Structuring Underperformance Reviews and KPI Setting

Before you can address underperformance, you need to be able to define performance — and that starts with KPIs. A Key Performance Indicator is a measurable value that demonstrates how effectively someone is achieving their core objectives. The problem most managers encounter is not that they lack KPIs, but that their KPIs are either too vague to act on or too numerous to focus on. A direct report who has fifteen KPIs effectively has none, because the sheer volume makes it impossible to prioritize.

Strong KPIs follow the SMART framework, meaning they are Specific, Measurable, Achievable, Relevant, and Time-bound. Consider the difference between "Improve customer satisfaction" and "Increase the team's average customer satisfaction score from 3.8 to 4.2 by the end of Q3." The first is an aspiration; the second is a target you can track, discuss, and coach toward. When setting KPIs with your direct reports, aim for three to five per quarter — enough to cover their most critical responsibilities without diluting focus. Each KPI should connect visibly to a team or organizational goal so the person understands why it matters, not just what it measures.

Once KPIs are in place, underperformance becomes easier to identify and harder to dispute. An underperformance review is not an ambush — it is a structured conversation built on documented evidence. You should prepare by gathering specific data points such as missed targets, quality issues, feedback from stakeholders, and any patterns you have observed over time. The conversation itself should follow a clear arc. Open by stating the purpose directly, something like "I want to talk about the gap I'm seeing between your current results and the targets we set together at the start of the quarter." Then present the evidence without editorializing — share the numbers, the dates, the specific instances. After laying out the facts, invite their perspective with a prompt like "I want to understand what's been getting in the way from your side." This is critical because it separates the behavior from the person and opens the door to problem-solving rather than defensiveness.

To see what this looks like in practice, consider the following exchange between a manager and a direct report whose client response times have consistently fallen below the team standard.

Facilitating Effective Performance Improvement Plans (PIPs)

When underperformance persists despite clear feedback and adjusted expectations, a Performance Improvement Plan becomes necessary. PIPs have a reputation problem — many employees view them as a prelude to termination, and many managers use them that way. But a well-designed PIP is genuinely meant to give someone a structured, time-bound opportunity to close a performance gap with explicit support. Your mindset going in matters enormously. If you approach the PIP as a formality before firing, the person will sense it immediately and disengage. If you approach it as a sincere investment in their success with honest boundaries, you create the best possible conditions for a turnaround.

An effective PIP begins with a clear description of the performance gap — what is expected versus what has been delivered, backed by specific examples and data. From there, it defines the specific, measurable outcomes the person must achieve by the end of the plan period, and these should be SMART goals just like the KPIs you set during regular performance cycles. Equally important is the support and resources section, which outlines what you will provide — whether that is additional training, more frequent check-ins, adjusted workload, or access to a mentor. This element is what distinguishes a PIP from a mere warning: it acknowledges that you, as the manager, have a role in helping the person succeed. The plan also requires a timeline, typically 30, 60, or 90 days depending on the complexity of the role and the severity of the gap. Finally, it must specify the consequences with total clarity — what happens if the person meets the plan's goals and what happens if they do not. This must be stated plainly, such as "If you meet these goals by the end of the 60-day period, you will return to standard performance management. If the goals are not met, we will move forward with a separation discussion."

During the PIP period, your check-in cadence should increase significantly. Weekly or even twice-weekly meetings focused on progress against the plan's goals are appropriate, and you should document every one of them — what was discussed, what progress was noted, and what guidance was given. This documentation protects both you and the employee by creating a transparent record of the effort invested on both sides. In each check-in, be direct about where they stand. Vague encouragement like "You're heading in the right direction" is not helpful if they are actually still falling short. Instead, be precise:

Sign up
Join the 1M+ learners on CodeSignal
Be a part of our community of 1M+ users who develop and demonstrate their skills on CodeSignal