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. Performance Review Summary & Proposed Rating

Employee: Lukas Brenner, Senior Product Manager Manager: Director of Product Proposed Rating: Meets Expectations

#### Executive Summary Lukas delivered significant business impact this year across core logistics workflows, exceeding quantitative targets on two of his three primary annual objectives. While the Q4 rollout of Dispatch v2 suffered an operational failure that required a temporary rollback, Lukas’s broader performance demonstrates high execution capability, strong peer collaboration, and deep workflow understanding. A rating of Meets Expectations accurately reflects his net delivery, aligns with company precedent, and balances his substantial wins against an operational misstep in launch execution.

#### Objective Performance & Evidence

• Objective 1: Reduce Carrier Onboarding Time (Target: 21 days → 10 days)
• Result: Exceeded (Achieved 9 days).
• Evidence: Lukas redesigned the onboarding funnel, eliminating operational bottlenecks and cutting time-to-activate by over 57%. This represents a major strategic unlock for carrier supply growth and demonstrates strong customer and product workflow sense.
• Objective 2: Launch Dispatch v2 by October (Target: Oct Launch)
• Result: Partially Met / Rollback Required.
• Evidence: Dispatch v2 shipped in October but was rolled back after six days due to 340 support tickets resulting from inadequate Support team enablement. Lukas was on approved leave the week immediately preceding the release, having delegated final checks to his deputy. While Lukas owns the ultimate operational readiness of his product, the failure stemmed from delegation and cross-functional go-to-market (GTM) enablement, not defective core product design. Relaunch is on schedule for next quarter.
• Objective 3: Expand Live Tracking Adoption (Target: 40% → 55%)
• Result: Exceeded (Achieved 57%).
• Evidence: Successfully drove adoption among carriers through incremental UX enhancements and behavioral triggers, surpassing the annual target by two percentage points.

#### Competencies & Stakeholder Feedback * Execution & Impact: Delivered 2 out of 3 major company-level OKRs ahead of target. * Collaboration & Peer Regard: 3 out of 4 peer reviews are strongly positive, specifically praising his cross-functional partnership and execution on onboarding. * Operational Readiness & Communication: Negative feedback from the Head of Operations regarding launch communication on Dispatch v2 is valid. Lukas failed to build a resilient operational handoff prior to his leave, revealing an area for growth in GTM risk management. * Product Sense & Strategy: Lukas’s architectural and flow simplifications in carrier onboarding reflect sound product sense. The feedback record contains no documented deficits in strategic ability or product sense throughout the year.

---

2. Recommendation on the PIP

Recommendation: Do NOT place Lukas Brenner on a Performance Improvement Plan (PIP).

#### Rationale: 1. HR Policy Non-Compliance: Company policy explicitly states that a PIP requires prior documented feedback on the specific performance gap and a reasonable opportunity to correct it. There is zero documented feedback on record regarding strategy or product sense. Lukas received only one conversation regarding launch readiness in November. Placing him on a PIP now directly violates established HR procedure and exposes the company to process risk. 2. Disproportionate Action vs. Net Delivery: Lukas exceeded two key company metrics. Placing a high-performing contributor on a PIP over a single operational coordination error—occurring while on approved leave—is disproportionate and demotivating to the broader team. 3. Precedent and Equity: Last year, Priya (Senior PM) experienced a nearly identical launch rollback driven by a support enablement breakdown. Priya received a rating of Meets Expectations and was not placed on a PIP. Subjecting Lukas to a punitive process under matching circumstances creates severe inconsistency across the product organization.

#### Alternative: Targeted 60-Day Operational Readiness Development Plan Rather than a formal HR PIP, Lukas should be placed on a structured, manager-led coaching plan for the Dispatch v2 relaunch: * Key Terms & Measurable Criteria: * GTM & Enablement Sign-Off: Implement a mandatory Launch Readiness Review (LRR) framework with explicit, written operational sign-offs from Customer Support and Operations at least two weeks before launch. * Dispatch v2 Relaunch SLA: Successfully relaunch Dispatch v2 next quarter with fewer than 50 support enablement tickets in the first 14 days post-launch. * Delegation & Redundancy Protocol: Document a standard operating procedure (SOP) for coverage and handover during PM absences.

---

3. Note to Ines Okoro (VP Product)

To: Ines Okoro, VP Product From: Director of Product Subject: Calibration Pre-Read Draft – Lukas Brenner

Hi Ines,

Ahead of calibration on Friday, I want to share some vital context regarding the pre-read draft for Lukas Brenner. I recommend we revise his rating to Meets Expectations and withdraw the recommendation for a PIP, for three reasons:

1. The Objective Data: Lukas exceeded two of his three major annual OKRs: cutting carrier onboarding from 21 days down to 9 (target was 10), and expanding live tracking to 57% (target was 55%). Peer feedback is 75% positive, praising his collaborative delivery. The Dispatch v2 rollback was a serious operational misstep, but the core product is sound and on track to relaunch next quarter.
2. HR Policy & Documentation: HR guidelines require documented feedback on specific performance gaps before initiating a PIP. There is no written record critiquing Lukas’s strategy or product sense, and we have had only one conversation (in November) regarding launch readiness. A PIP would not meet our HR criteria and would be vulnerable to challenge.
3. Internal Precedent: Last year, Priya had a launch rolled back under almost identical support-readiness circumstances. She received Meets Expectations and no PIP. Applying a PIP to Lukas creates an inconsistency in our standard across the team.

Dispatch v2 showed a breakdown in operational handoff and delegation while Lukas was on approved leave, and the Head of Operations’ frustration is justified. However, this is an operational readiness gap, not an absence of product sense.

I propose we update his pre-read to: > "Lukas: Meets Expectations. Exceeded annual targets on onboarding (9 days) and live tracking (57%). Experienced an operational setback on Dispatch v2 due to GTM/support readiness failures during an absence. Relaunching next quarter under a structured launch-readiness plan."

I will manage Lukas through a rigorous 60-day launch-readiness framework for the relaunch, including sign-offs from Ops and Support. Let’s discuss briefly tomorrow so we’re aligned before the calibration deck is locked.

Best, [Director of Product]

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]