Performance improvement plan 1 on 1 agenda: objective tracking without the drama

1 on 1 practice

A performance improvement plan 1 on 1 agenda is a weekly, written loop: shared facts, support, and next actions both people can see. Stay on observable work. Keep a permanent history of action items. That record is how you stay fair when emotion rises. This is a management framework, not legal advice. Follow your company HR process.

This is the HR spoke of The High-Performance Team Playbook.

How do you document a PIP 1-on-1 meeting?

Document the meeting as a chronological compliance trail both people can reopen next week, not as a private recap.

  1. Goals set: the objective gap, the standard, and the date the plan started.
  2. Milestones met: what closed this week against those goals, with artifacts.
  3. Obstacles flagged: what blocked progress, and the support you actually offered.
  4. Sign off: both people can see the same rows before you leave. HR can see the history if policy requires it.

If a step is missing, the file is not ready for a later dispute. Fill it in the room, not from memory in month two.

When do you need a PIP 1 on 1, not a normal 1 on 1?

You need a PIP 1 on 1 when the gap is already named in writing, the time window is set, and both people must leave each week knowing if the plan moved.

A normal 1 on 1 can coach, wander, and recover trust slowly. A PIP 1 on 1 cannot wander. Ambiguous talk is how managers later say they were clear and reports say they never heard a plan.

Use this meeting only after you have already given direct feedback, offered support, and still see the same gap. Involve your people partner before you label the process a PIP. Local law and company policy decide what must be in writing.

According to iSilta's 2026 survey of 146 organizations, 78% cite weak 1 on 1s when manager training is late or thin. Weak 1 on 1s during underperformance become he said, she said. According to the same survey, 81% do not measure behavior change after manager training. A PIP without a weekly evidence loop is the same failure at higher stakes.

Objective vs Subjective Feedback Chart

Objective feedback names what happened against an agreed standard. Subjective feedback names how you feel about the person.

PIP 1 on 1s fail when managers mix the two. Subjective lines sound like character attacks. Objective lines can still be hard, and they can be checked.

Objective vs Subjective Feedback Chart
Topic Subjective (avoid in the PIP 1 on 1) Objective (use this instead)
Output You are not hungry enough In the last two sprints you owned 1 of 4 planned tickets. The plan asked for 4.
Quality Your work is sloppy Reviewers requested rework on 3 of 5 pull requests this month for missing tests named in the team bar.
Time You never show up You missed 2 of 3 weekly planning meetings without notice on 4 Mar and 11 Mar.
Collaboration You have a bad attitude in Slack On 8 Mar you replied to a peer request with no next step after 24 hours. The team SLA is a same day ack.
Learning You do not care about growth The plan asked for one pairing session a week. None were booked in the last 14 days.
Support used You refuse help We offered a named buddy and extra review slots. You attended 0 of 3 booked sessions.

If you cannot fill the objective column, you are not ready to run a PIP 1 on 1. Coach first, or get help from HR on how to gather facts without stalking.

What is the weekly performance improvement plan 1 on 1 agenda?

The agenda is a timed script you reuse every week so the meeting is about the plan, not about mood.

Share this agenda before the meeting. Both people can add facts. Neither person surprises the other with a new accusation in the last minute.

Minutes Block What you do What you write
0 to 5 Open the shared history Read last week's actions out loud Done, slipped, or blocked
5 to 15 Facts this week Match work to the written PIP goals One line per goal: met, missed, or not yet due
15 to 25 Support and blockers Ask what got in the way. Offer help you can actually give Support you will provide, with a date
25 to 35 Reset actions Agree next week's work. Keep the list small Owner, outcome, next date
35 to 40 Confirm the record Read the new rows together Both can see the same list before you leave

Forty minutes is enough. If you need ninety minutes every week, the plan is too vague or the relationship is doing work the document should do.

What belongs in the written PIP file?

  1. The gap in objective language, with dates
  2. The standard you are measuring against (already known to the team)
  3. Support you will give (time, pairing, training, scope cuts)
  4. How you will know it worked, by when
  5. How often you will meet, and where the shared list lives
  6. What happens at the end of the window, in the words HR approved

Do not write secret side notes that contradict the shared list. If it matters for the outcome, it belongs where they can read it. Private coaching thoughts about how to stay calm can stay private. Facts cannot.

How shared action history removes emotion from tracking

Emotion shows up when memory is the only record. A permanent, transparent history of action items makes the week about the list.

People in a PIP often hear every sentence as a verdict. Managers often hear every delay as proof. The list is the third party in the room. You point at a row: this closed, this did not. You can still be kind. Kind is not the same as fuzzy.

Rules that keep heat down:

If they dispute a fact, pause. Check the artifact. Update the row if you were wrong. Fairness is how you keep the process defensible and human.

How iSilta holds the PIP loop

iSilta is HR's peace of mind cockpit: an unalterable, shared historical record of Action Points and alignment benchmarks both people can see.

During a PIP, the worst system is a manager Google Doc the report never opens, plus Slack reminders that vanish. iSilta keeps the history in one place: what was asked, who owned it, whether it closed. You open the 1 on 1 on that list. You do not reconstruct the quarter from memory.

Transparency here is not a public scoreboard. It is two people and, when policy requires it, HR looking at the same actions. That is how you remove "I thought we agreed" as the main plot. Managers cannot quietly edit last week's commitments after the meeting.

Use AI only to draft a summary of actions you already confirmed, never to invent incidents or motive. Confirm every line with the person. The model does not sit in the PIP.

What not to do in a PIP 1 on 1

Skip Why
Surprise goals The plan is the contract for the window
Recording without consent and policy Trust and legal risk both rise
Therapy questions about their character Stay on work. Offer EAP or HR if wellbeing is the issue
Promises you cannot keep Support you name becomes part of fairness

Implementation steps

  1. Talk to HR. Confirm you may start a PIP and what must be in writing.
  2. Write goals in the objective column of the feedback chart. Share the draft.
  3. Create the weekly agenda and the shared action list before the first PIP 1 on 1.
  4. Run the timed agenda. End only after both can see the new rows.
  5. Keep iSilta Action Points (or your shared list) as the only tracking surface.
  6. At the end of the window, review the history together with HR, not a vibe.

Frequently asked questions

How do you document a PIP 1-on-1 meeting?

Write four chronological records: goals set, milestones met, obstacles flagged, and sign off. Keep the same shared list both people can see. Do not keep a private diary that contradicts the file.

What is a performance improvement plan 1 on 1 agenda?

It is a repeating weekly meeting structure used during a PIP. You review shared facts, support, and next actions. You do not relitigate feelings from last month.

How often should you meet during a PIP?

Weekly is the default. The plan is the source of truth. The 1 on 1 is where you update it together. Daily status pings add heat without adding evidence.

What is the difference between objective and subjective feedback?

Objective feedback names observable work, dates, and agreed standards. Subjective feedback names impressions, personality, or motive. PIP 1 on 1s should stay on the objective side.

Should HR sit in every PIP 1 on 1?

Follow your company policy. Many teams keep weekly 1 on 1s as manager and report, with HR on the written plan and at start and end reviews. Ask your people partner before you begin.

How does iSilta help with PIP tracking?

iSilta keeps a permanent, shared history of Action Points both people can see. You track what was agreed, what closed, and what slipped, so the story is not only one person's memory.

Related: The High-Performance Team Playbook, How do you manage an underperforming engineer?, Difficult conversations at work: scripts for engineering managers.

Prefer prepared conversations over memory alone? Explore iSilta features or try the product demo.