Write a performance review

1. Lukas Brenner: Performance Review Summary, Proposed Rating, and Evidence

Proposed Rating: Meets Expectations

#### Goal Performance (3/3 Achieved or Exceeded) 1. Cut carrier onboarding time from 21 days to 10: Achieved and exceeded. Reduced to 9 days through iterative UX improvements in the carrier portal. 2. Launch Dispatch v2 by October: Achieved on schedule. Shipped in October, though operational failures necessitated a rollback (detailed below). 3. Grow carriers using live tracking from 40% to 55%: Achieved and exceeded. Reached 57% via targeted nudges and integration updates.

#### Context on Dispatch v2 Dispatch v2 launched in October and was rolled back after six days due to an influx of 340 support tickets driven by a lack of support enablement.

While this was a significant operational failure, the root cause analysis reveals mitigating context: * Lukas was on approved company leave during the critical final week before launch. * His designated deputy ran the final pre-launch checks and missed the cross-functional operational sign-offs. * Accountability rests with Lukas as the DRI, and he owns the failure to ensure his deputy was fully briefed. However, framing this as a total product failure ignores that the core software functioned as engineered and is successfully slated for a polished relaunch next quarter.

#### Peer and Historical Feedback * Peers: 3 out of 4 peer reviews are strongly positive, specifically praising Lukas’s cross-functional collaboration, responsiveness, and his work on the onboarding and tracking initiatives. * Operations: The Head of Operations provided negative feedback regarding the communications breakdown during the Dispatch v2 launch, which is fair and has been addressed directly with Lukas. * Precedent (Fairness/Calibration): Last year, Senior PM Priya experienced an identical launch rollback due to a support enablement failure. Priya was rated "Meets expectations" with no PIP. Calibrating Lukas lower would establish a double standard for identical failure modes within the same peer group.

---

2. Recommendation on the PIP

Recommendation: Do not place Lukas on a Performance Improvement Plan.

#### Rationale Placing Lukas on a PIP is unwarranted based on performance, precedent, and HR policy: 1. Performance: He delivered 2 out of 3 major company goals significantly ahead of target, and delivered the third on schedule (with subsequent operational failure). 2. HR Policy Conflict: Railyard HR policy dictates that a PIP requires earlier documented feedback regarding specific performance gaps and an established window to improve. Lukas has received zero written feedback this year regarding strategy or product sense. Issuing a PIP now violates internal policy and exposes the company to unnecessary employment risk. 3. Precedent: Priya received a "Meets Expectations" rating for a similar incident last year. Consistency in calibration is vital for team morale.

Instead of a PIP, Lukas will receive structured coaching, an actionable growth plan focusing on cross-functional operational rigor (specifically launch readiness and stakeholder communication), and clear expectations for his strategic output heading into next year.

---

3. Note to Ines On the Evidence

*

To: Ines Okoro, VP Product From: [Your Name], Director of Product Subject: Calibration Pre-Read: Lukas Brenner

Ines,

Thanks for drafting the pre-read. I’ve reviewed the data, HR policies, and peer feedback regarding Lukas ahead of calibration in five days, and I recommend we adjust our approach.

I propose we rate Lukas Meets Expectations and drop the recommendation for a PIP. Here is why:

• Goal Delivery: Lukas hit or exceeded 3 out of 3 core goals this year. He cut onboarding time to 9 days (target was 10) and grew live tracking adoption to 57% (target 55%).
• The Dispatch v2 Incident: While Dispatch v2 was undoubtedly painful, we need to look at the full picture. Lukas shipped on time, but the launch failed operationally due to a lack of support enablement. Crucially, Lukas was on approved leave that week, and his deputy ran the final checks. While Lukas owns the outcome as DRI, a single operational stumble on a shipped product does not invalidate a strong year of output, nor does it make him "not strategic enough."
• Precedent & Calibration: Last year, Priya had a nearly identical support-related rollback. We rated her "Meets Expectations" with no PIP. We must maintain consistent standards across the team.
• HR Compliance: HR policy requires prior documented feedback on specific gaps and a chance to remediate before issuing a PIP. Lukas has zero written feedback this year regarding strategy or product sense—our only documented conversation was a single verbal check-in after the Dispatch launch in November. A PIP would not survive HR scrutiny.

Lukas is a strong Senior PM who made a costly execution error on one launch while away. I’ve already addressed launch rigor directly with him, and he’s applying those lessons to the Q1 relaunch. I’ll own his operational coaching moving forward, but a PIP is the wrong tool here.

Let’s chat before the meeting locks in.

Best, [Your Name]

1. Lukas’s review summary and proposed rating

Proposed rating: Meets expectations, with a significant launch-readiness gap to address.

Lukas delivered strong results on two of his three annual goals:

• Carrier onboarding: Reduced onboarding time from 21 days to 9 days, exceeding the 10-day target.
• Live tracking adoption: Increased adoption from 40% to 57%, exceeding the 55% target.
• Dispatch v2: Launched in October, meeting the timing target, but was rolled back after six days. This was not a successful, sustained delivery and should not receive full credit simply because it launched on schedule.

Dispatch exposed a serious readiness failure: support was not briefed, and 340 support tickets arrived in the first week. That outcome warrants explicit negative feedback and corrective action. However, the record does not establish how responsibility was divided among Lukas, his deputy, and other launch stakeholders. Lukas was on approved leave the week before launch, and his deputy ran the final checks. His leave is not itself a performance issue; his planning and handoff before leave remain legitimate areas to assess.

Peer feedback is positive from three of four peers, particularly on onboarding and collaboration. The Head of Operations’ criticism of Dispatch communication is relevant and consistent with the launch failure. It should be addressed directly rather than generalized into an unsupported conclusion about Lukas’s overall capabilities.

Review summary: Lukas exceeded the onboarding and live-tracking goals and received broadly positive feedback on collaboration. Dispatch v2 was a material setback: the release was not adequately prepared for support and was rolled back. As a Senior PM, Lukas needs to demonstrate more reliable launch planning, explicit delegation, and cross-functional readiness. We should establish his specific responsibility for the failure and assess improvement through the relaunch.

“Meets expectations” is the most defensible overall rating on the current record. It recognizes substantial results without minimizing Dispatch. It is also consistent with Priya’s rating last year after a similar rollback and support failure. That precedent is not automatically determinative, but a lower rating here would require a documented, material distinction that we do not currently have.

2. PIP recommendation

Do not initiate a PIP now.

HR policy requires earlier documented feedback on the specific gap and an opportunity to improve. There is no written feedback this year about strategy or product sense. The only recorded conversation concerns launch readiness in November, after Dispatch. On the available record, that does not establish both the required prior documentation and a subsequent opportunity to improve.

The proposed PIP therefore lacks the required foundation. “Not strategic enough” and “lacks product sense” are also too broad to serve as actionable performance gaps without concrete examples and defined expectations.

Instead, put a documented, non-PIP development plan in place now:

• Clarify accountability: Review the Dispatch launch plan, handoff, readiness checks, and go/no-go decision with Lukas, his deputy, Operations, and Support. Identify individual and process failures.
• Set observable expectations: For the relaunch, require named owners for every readiness item, documented support briefing and training, escalation and rollback procedures, and explicit cross-functional approval before release.
• Check progress regularly: Hold biweekly check-ins with Lukas and record feedback, completed actions, and any remaining gaps.
• Assess the relaunch: Evaluate readiness execution and post-launch support outcomes against thresholds agreed with Support before launch.

This should be genuine coaching, not a PIP under another name. If Lukas subsequently fails to meet clearly documented expectations after a reasonable opportunity to improve, reassess with HR. Any later PIP must run for 60 days, with measurable success criteria and the support needed to meet them.

3. Note to Ines

Ines — I agree that Dispatch’s readiness failure deserves clear accountability. I recommend Meets expectations and no PIP at this stage.

The pre-read should distinguish established facts from judgments. Lukas exceeded two goals; Dispatch met its launch date but failed as a sustained release. We have evidence of a launch-readiness and communication problem, but not enough to substantiate “not strategic enough” or “lacks product sense.” We also need to clarify Lukas’s handoff responsibilities versus the final checks his deputy owned.

Before calibration, I’ll verify the launch ownership, the November feedback record, and whether there are material differences from Priya’s case. Unless that produces materially different evidence, we should revise the pre-read accordingly. HR’s PIP prerequisites are not demonstrated in the current record; the appropriate next step is specific documented feedback and a fair opportunity to improve.

1. Lukas’s review summary and proposed rating

Proposed rating: Meets expectations, with a significant launch-readiness gap to address.

Lukas delivered strong results against two measurable goals. Carrier onboarding time fell from 21 days to 9 days, exceeding the 10-day target. Live-tracking adoption increased from 40% to 57%, exceeding the 55% target. Three of four peers gave positive feedback, particularly on his onboarding work and collaboration.

Dispatch v2 was a substantial delivery failure. Although it launched in October, it was rolled back after six days; the launch objective should therefore not be treated as successfully completed. Support had not been briefed, and 340 support tickets arrived in the first week. The Head of Operations’ feedback reinforces the specific concern about launch communication and operational readiness. Relaunch is planned for next quarter, so the intended outcome remains outstanding.

As the responsible Senior PM, Lukas should be assessed on how he established launch-readiness requirements, cross-functional ownership, and delegation. However, the record does not establish which safeguards he put in place or who approved the final launch. He was on approved leave the preceding week, and his deputy ran the final checks. Approved leave is not a performance failure; equally, delegation does not automatically remove accountability for the preparation and handoff. We should establish those facts before assigning Lukas sole responsibility.

The evidence supports a specific execution and communication gap, not the broader conclusions that Lukas is “not strategic enough” or “lacks product sense.” No feedback on those broader concerns was documented this year, and the supplied record contains no concrete examples substantiating them.

On balance, two above-target outcomes, positive collaboration feedback, and one serious but bounded delivery failure support Meets expectations. This is also consistent with Priya’s rating last year after a similar rollback and support failure. That precedent does not dictate Lukas’s rating, but a harsher outcome requires a material, evidenced distinction—not stronger language about the incident.

2. PIP recommendation

Do not initiate a PIP on the current record.

HR requires earlier documented feedback on the specific gap and an opportunity to improve. The record contains one November conversation about launch readiness, after Dispatch, but does not establish that it was documented or that Lukas subsequently had a meaningful opportunity to demonstrate improvement. There is no documented feedback on strategy or product sense. A PIP on those grounds would therefore lack the required foundation.

Instead, put a documented development plan within normal performance management in place now. This is not a disciplinary PIP or a predetermined path to one. Agree with Lukas on:

• Readiness ownership: Before the relaunch go/no-go review, document owners, decision rights, coverage during absences, escalation routes, and rollback criteria.
• Support preparedness: Before launch approval, secure Support and Operations sign-off on training, customer communications, FAQs, and the escalation runbook.
• Launch monitoring: Before relaunch, agree measurable adoption, reliability, and support-volume thresholds with Engineering, Support, and Operations; review results against them after launch.
• Manager support: Provide a readiness template, help resolve cross-functional ownership gaps, and hold regular check-ins through relaunch.

Document the expectations, support provided, and subsequent results. If a specific performance gap persists after clear feedback and a genuine opportunity to improve, reassess with HR. Any later PIP must meet the policy’s 60-day duration and measurable-success-criteria requirements.

3. Note to Ines

Ines—

I recommend changing Lukas’s proposed rating to Meets expectations and removing the PIP recommendation on the current evidence.

We should retain a direct account of Dispatch’s failure: Support was not briefed, 340 tickets arrived in the first week, and the release was rolled back after six days. But “not strategic enough,” “lacks product sense,” and “disaster” should be replaced with specific, attributable observations. The current draft also omits his two above-target results.

Before the pre-read is finalized, I’ll review the launch checklist, handoff and approval record, clarify the November feedback and subsequent improvement opportunity, and give Lukas a chance to respond to the factual account. I’ll also check whether there are material differences from Priya’s case.

If that review produces additional evidence, we should consider it explicitly. Otherwise, the defensible outcome is Meets expectations, clear launch-readiness feedback, and documented follow-through—not a PIP unsupported by our policy.