How to have a hard performance conversation with a VP

You have a 1:1 on Friday with a VP you've been holding off having a hard conversation with. The work isn't where it needs to be. You've mentioned it, sideways, two or three times over the last few months — and nothing's shifted. You also know that the way this conversation gets handled has implications beyond just the work — for the team underneath them, for your relationship, and quietly, somewhere in the back of your mind, for the legal posture of the company if this person ends up exiting badly. This is the playbook.

The instinct is to over-prepare the evidence — every example you can remember, every Slack screenshot, every missed milestone. That's important, and most people do too much of it. Three to five well-chosen examples beat fifteen poorly-sequenced ones. The defensible record is not the same as a litigator's exhibit list.

The instinct that gets the conversation wrong, though, is to over-prepare what you're going to say and under-prepare what you actually want by when. A VP-level performance conversation that ends without a specific named change and a specific named date is a Mention. You don't want a Mention here. You want a Conversation, or — if the pattern has been already named — a Boundary.

This piece walks the four phases: before, drafting, in the room, after. It assumes you know The Accountability Dial™ at least roughly. If you don't, read that one first.

Phase 1 · Before — write three things down

Before the 1:1, in a private doc you don't share, write these three things.

1. The pattern, with five concrete instances. Not impressions. Not "I feel like." Five specific events with dates, contexts, and observable behaviors. "In the Q3 roadmap planning on October 4, the customer-impact analysis was not produced — the team had to do it on the fly." That kind of specific. If you cannot get to five concrete instances, you are still at Mention, and the conversation you are about to have is not the one you think it is.

2. The company impact, in numbers where possible. Not your frustration. The cost. "Customer commitments slipped in two of the last four quarters." "Two of the three senior ICs in the group have asked for transfers." "The two largest deals of the quarter required CEO involvement that should not have." If you can't name the impact in second-order terms, the case is weaker than you think.

3. The change you need by when. Complete this sentence: "By [date], I need to see [specific change]. If it doesn't, the next step is [specific next step]." No version of "more reliable." No version of "stronger leadership." Specific. Observable. Datable. If you cannot fill those blanks, you are not ready for the meeting. The clarity on paper is what makes the conversation possible.

These three documents do double duty: they are how you stay specific in the room, and they are the seed of the legal-defensible record. (More on the documentation separation in Legal-defensible 1:1 documentation.)

Phase 2 · Drafting — the opening, in order

The first sixty seconds of the conversation set whether it lands. Draft them out.

The three beats from The Accountability Dial™:

Beat 1 — what I'm seeing. The pattern, with three of your five instances. "I want to talk about the customer-impact analysis on the roadmap. In the last quarter, in three planning cycles — October 4, October 25, November 8 — the analysis came together late or didn't come together at all. I want to surface the pattern directly with you."

No preamble. No "I hate that we have to talk about this." No "you're doing great in a lot of ways but." The other person reads the shape of your opening in the first thirty seconds and calibrates how serious to take it — give them the version that's serious.

Beat 2 — what the impact is. In the company's terms.

"The impact is two things. One: the deals that required custom analysis in the quarter didn't get the support they needed, and we lost margin in two of them. Two: the team underneath you is reading the cycle and treating the analysis as optional. The standard is dropping."

The second-order impact is what most VP-level performance conversations miss. The work matters. The cascade matters more.

Beat 3 — what I want. Specific, datable, observable.

"From here, I need the customer-impact analysis to be in the planning packet by the Friday of each cycle. We have four cycles left in this quarter. I want to use the next four as the read. I'll check in with you on December 13."

The date is the gift. It is the thing that distinguishes a Conversation from a Mention. Most VP-level conversations end without a date and quietly become Mentions. Don't let yours.

Print these three beats. Have them visible during the meeting if you need to. Keep the whole opening under 60 seconds in the room. Anything longer turns Conversation into a defensive monologue.

Phase 3 · In the room — running the conversation

Rule 1 · Don't apologize for the topic. "I really hate that we have to have this conversation" signals to the other person that you don't really mean it. They read your discomfort and treat the conversation with the same weight. Open warm, direct. "I want to talk about something I've been noticing" is plenty of softening.

Rule 2 · Don't fill the silence after Beat 3. This is the hardest moment of the meeting. After you've named the pattern, the impact, and the change you need by when — the next move is theirs. Most people panic in the silence and start adding qualifications. "I just want to make sure we're aligned." "Obviously this isn't a huge deal." Each of those undoes the clarity you just established. Hold it. Let the person respond.

Rule 3 · Read for ownership. This is the only thing that matters about how they respond. The response will be one of two shapes.

Ownership shape: "You're right, here's what's going on, here's what I'm going to do." Specifics. Acknowledgement of the pattern. A concrete proposal for the change. If you see this shape — even imperfectly — the Conversation is working. Confirm the cadence, the check-in date, and the form of the next read. End the meeting.

Non-ownership shape: explanation of why each instance was actually justified, externalization to other functions or to a tough quarter, vague "I'll work on it" without a named change. If you see this shape, you are no longer at Conversation. You are at Boundary, and the right move in the room is to shift the language explicitly.

A Boundary, in the room, sounds like:

"I hear what you're saying. Here's where I am. I need to see [specific change] by [date]. If the pattern hasn't shifted by then, we'll need to have a different kind of conversation about whether this is the right shape of the role for you."

That is the conversation people don't want to have. It is also the one that's been earned by everything that came before — the unspoken Mentions, the avoided Conversations, the months of pattern.

Phase 4 · After — the documentation that holds

Within an hour of the meeting, send the recap. Two to four sentences. Slack or email — whatever your operating norm is.

"Thanks for the conversation today. We talked about the customer-impact analysis pattern, and agreed on it being in the planning packet by Friday of each cycle for the next four cycles. Check-in on December 13."

That is the record. It is also the act that makes the conversation real to the other person — they got a recap — rather than something they can later remember as casual.

What to capture. The conversation initiated. The pattern named. The change requested. The agreed-upon cadence. The follow-up date.

What not to capture. The exact words spoken. Your private thinking about how it went. The employee's emotional reaction. Anything from your prep doc.

The principle is what happened, not what was said and felt while it was happening. That distinction is what makes a record defensible if it ever needs to be — and ordinary if it never does.

This is also why the prep work above stays in a separate, private doc. Mixing prep notes with the record is one of the most common mistakes managers make. The prep is your thinking. The record is the company's. They should never live in the same place. (Detailed treatment here →)

When to escalate to formal action — and when not to

A Performance Improvement Plan after a single Conversation that didn't fully land is too early. A PIP after a Boundary commitment that wasn't kept is the right time. Use The Dial as the gate: Conversation → Boundary → Limit.

The Boundary is where you ask for a specific, observable change with a date and name the consequence if it doesn't happen. The Limit is the moment you stop carrying the growth for them — the downstream consequences (PIP, reassignment, separation) are formal events that may follow it, handled with HR's process alongside.

If you are tempted to skip Boundary and go straight to a formal action, you are acting from frustration, not from the methodology. The action will read that way to the employee, to HR, and — if it ever comes to it — to a jury. The methodology protects the company by being clean, not by being aggressive.

What "good" looks like at the 30-day mark

By the end of 30 days from the Conversation (or 60 from a Boundary), the read is binary. Either the agreed change is happening, or it isn't. The biggest sin you can commit at this point is to let the check-in slide because things "seem better." If they are, say so explicitly — affirmation is what locks in the new pattern. If they aren't, name it explicitly — staying silent is how you end up at month six with no progress and no escalation path, in a posture that is both bad for the company and bad for the employee.

The clean version of this work — clear Mention, clear Conversation, clear Boundary, clear Limit, clean documentation — is the version that's good for everyone involved. It's faster, it's kinder, it's more legally defensible, and it leads to either a real performance change or an honest mutual exit. The slow version, the avoided version, the Mention-for-six-months version, is the version that ends in resentment, surprise, and exposure.

The methodology is what protects all of it.

How Ren makes this easier

Ren reads the context from your Slack and Teams threads, helps you locate where the pattern actually sits on The Accountability Dial™ (most VP-level conversations are misclassified by a stage), drafts the three-beat opening in your voice, prompts you to send the recap right after, and captures the legal-defensible what happened layer automatically.

The drafts and prep stay between you and Ren — Tier 1, never visible to HR or the leadership team. Only the outcomes — did the conversation happen, did it resolve, what was the agreed change — roll up as the Tier 2 layer that becomes the company's record.

This is the workflow Ren was built for. Take the three-minute product tour to see it draft a VP-level Conversation in real time, or talk with us about a deployment for your leadership team.