Write a performance review

1. Lukas’s review summary and proposed rating

Proposed rating: Meets Expectations, with a significant development area in launch readiness and communication.

Lukas delivered strong results against two of his three goals. He reduced carrier onboarding time from 21 days to 9, beating the 10-day target, and increased carrier adoption of live tracking from 40% to 57%, above the 55% target.

Dispatch v2 launched in October as planned, but the launch was not successful: support had not been briefed, 340 tickets came in during the first week, and the product was rolled back after six days. Lukas was on approved leave the week before launch, and his deputy ran the final checks. That context matters when assessing individual responsibility for the checks, but it does not erase the product team’s launch outcome or the need to clarify Lukas’s ownership of readiness and communication. The relaunch next quarter will be an important opportunity to demonstrate improvement.

Peer feedback is largely positive: three of four peers cited his onboarding work and collaboration. The Head of Operations raised a concern about how Dispatch was communicated. Overall, the evidence supports recognizing Lukas’s substantial delivery while clearly addressing the failed launch. A Meets Expectations rating is also consistent with the precedent of a Senior PM rated Meets Expectations after a similar support-related rollback.

2. Recommendation on a PIP

Do not recommend a PIP at this time. HR policy requires earlier documented feedback on the specific gap and a chance to improve. The record contains no written feedback this year on strategy or product sense, and the only recorded conversation about launch readiness took place in November, after the Dispatch launch. That does not meet the stated prerequisite for a PIP. The current record also does not substantiate the draft’s broader claims that Lukas “lacks product sense” or is “not strategic enough.”

Instead, give Lukas direct, documented feedback now on the Dispatch readiness and communication failures, clarify his responsibilities for the relaunch, and set measurable launch-readiness expectations for that work. Reassess his performance with that evidence. This addresses the issue without bypassing the required feedback process.

3. Note to Ines on the evidence

Ines, I recommend revising the pre-read to distinguish the documented launch failure from the broader judgments about strategy and product sense, for which we have no recorded feedback. We should include the onboarding and tracking results, the rollback and support impact, the Operations feedback, and the approved-leave/deputy context. The November readiness conversation came after the launch, so it does not establish earlier feedback or an opportunity to improve for PIP purposes. Applying the same Meets Expectations rating used in Priya’s similar case would also support consistency.

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.