Write a performance review

Annual Performance Review Employee: Theo Brandt, Product Manager Manager: Ana Ruiz, Group Product Manager Overall Rating: Meets expectations

Summary Theo, thank you for your hard work and dedication over the past year. You have established yourself as an exceptionally reliable execution partner and a trusted collaborator across Engineering, Design, and Sales. Your squad’s delivery velocity was impressive, shipping 14 features with 12 on time.

However, that high output did not translate into the outcome targets we set for the year: weekly Timeline usage moved from 22% to 23% (goal: 30%), and time to first plan moved from 3.0 days to 2.6 days (goal: 1.0 day).

I want to own my part in this disconnect. In our 1:1s—and specifically when you asked if you were on track in Q3—I focused my feedback on your strong delivery velocity and stakeholder responsiveness rather than holding us both accountable to the lagging core metrics. Because you delivered on the execution behaviors we discussed all year, your rating for this cycle is Meets expectations. Moving forward, we will work together to shift your focus from shipping volume to driving measurable user outcomes.

Strengths * Execution and Delivery: You run a remarkably tight ship. Delivering 14 features (12 on schedule) is a testament to your organizational skills. Your Engineering Lead noted that your specs are clear, you never miss a sprint review, and you consistently keep the team unblocked. * Cross-Functional Collaboration: Your peers genuinely enjoy working with you. Both Design and Engineering highlighted your collaborative nature, and Sales praised your responsiveness in shipping five of their requests this year. You build strong, frictionless relationships across the org.

Areas for Growth * Outcome vs. Output Orientation: While your squad shipped a high volume of features, six of the 14 are currently used by fewer than 2% of teams. Moving forward, shipping a feature cannot be the finish line; we must measure success by adoption and impact on our core product metrics. * Discovery and Validation: In our push to maintain high velocity, we bypassed critical validation steps. As your Design partner noted, we built and shipped several features without sufficient upfront testing to prove user demand. We need to lean harder on discovery before committing engineering resources. * Strategic Prioritization: Five of the features you shipped came directly from Sales requests, including two built for a single customer each. While supporting Sales is important, saying "yes" to bespoke requests diluted your squad’s focus and pulled capacity away from our broader Timeline and onboarding goals. You need to push back on one-off asks that don’t serve our wider user base.

Goals for Next Half (H1) This half, we are shifting our focus from feature velocity to validated impact. In our 1:1s, we will review metric movement and discovery insights rather than just delivery status.

1. Drive Timeline Adoption: Increase the share of teams using Timeline view weekly from 23% to 28%.
2. Accelerate Onboarding: Reduce the time new teams take to build their first plan from 2.6 days to 1.5 days.
3. Establish a Rigorous Discovery Practice: Before any new feature enters sprint planning, partner with Design to validate demand and usability with at least 5 target customers, and define a clear post-launch adoption target. Ensure 80% of shipped work meets its 30-day adoption target.
4. Protect Roadmap Focus: Audit incoming Sales requests against our core H1 goals. Zero features should be built for a single customer unless explicitly approved at the leadership level, ensuring at least 80% of engineering capacity is dedicated to our primary metric drivers.

Annual Performance Review Employee: Theo Brandt, Product Manager Manager: Ana Ruiz, Group Product Manager Review Period: FY Annual Review Overall Rating: Meets Expectations

---

Performance Summary & Overall Rating

Overall Rating: Meets Expectations

Theo has had a productive year characterized by high operational output, exceptional execution rigor, and strong squad leadership. He shipped 14 features—12 of them on time—and built great trust across engineering and sales.

However, our primary product goals were tied to outcome metrics rather than feature velocity: 1. Weekly Timeline View Adoption: Target 30% | Actual: 23% (baseline 22%) 2. Time to First Plan: Target 1.0 day | Actual: 2.6 days (baseline 3.0 days)

While the delivery machine Theo built is top-tier, the strategic impact of what was delivered fell short of our targets. Six of the 14 features shipped are used by fewer than 2% of teams, reflecting an emphasis on shipping volume and ad-hoc requests over high-leverage product discovery.

I also want to acknowledge my own role here: when you asked in Q3 whether you were on track, I pointed to your velocity and said yes, rather than re-anchoring our conversations on our metric shortfalls. Your execution on what was put in front of you was excellent; our focus now must pivot from output to measurable impact.

---

Strengths

• Execution Rigor and Delivery Reliability: Theo is an exceptional delivery PM. Shipping 14 features with an 85% on-time delivery rate is a testament to his clarity and organizational discipline. As his Engineering Lead noted, “Theo keeps the team unblocked, his specs are clear, and he never misses a sprint review.” His squad runs with rhythm and confidence.
• Stakeholder Responsiveness and Partnership: Theo is highly collaborative and service-oriented. Sales commended him as “very responsive,” appreciating that he delivered five key requests to support revenue efforts.
• Squad Morale and Clarity: The squad feels supported and clear on day-to-day priorities. Theo shields the team from ambiguity during delivery sprints.

---

Areas for Growth

• Shift from Output to Outcomes: High velocity without metric movement does not move Plotwise forward. Five of the shipped features were sales requests (two serving only a single customer), and nearly half the year’s releases see under 2% usage. Theo must practice saying "not now" to low-leverage requests to protect squad capacity for the core metrics we need to move.
• Pre-Build Discovery and Validation: As our product designer noted, “I wish we’d tested more before building; we shipped three things I’m not sure anyone uses.” Theo should partner earlier with design and analytics to de-risk value and usability before committing engineering time. Building prototypes and running customer problem interviews will prevent spending sprint cycles on features that fail to achieve adoption.
• Metric Ownership in Day-to-Day Decisions: Moving forward, every feature spec should define a clear hypothesis, adoption target, and post-launch metric check. Our 1:1s will also reflect this shift—prioritizing metric movement over sprint status.

---

Goals for the Next Half (H1)

1. Drive Timeline Weekly Adoption from 23% to 28% * Success Measure: Rather than building net-new surfaces, focus on instrumenting workflows, user onboarding, and targeted iterations on the current Timeline experience to increase recurring weekly team usage. 2. Reduce New Team Time-to-First-Plan from 2.6 Days to 1.5 Days * Success Measure: Conduct discovery sessions with recently onboarded teams, identify drop-off bottlenecks, and ship validated onboarding improvements with design. 3. Establish a Customer Discovery & Validation Gate * Success Measure: Implement a lightweight validation process for all incoming feature ideas (especially commercial requests). No feature will be queued for full development without documented user validation and an estimated TAM/adoption threshold (>5% of active teams or explicit strategic tier-1 value). 4. Post-Launch Adoption Audits * Success Measure: Conduct 30- and 60-day post-launch usage reviews for all new releases, tracking engagement against targets and sunsetting or iterating on low-performing functionality.

Theo Brandt — Annual Review

Manager: Ana Ruiz, Group PM, Plotwise Overall rating: Below expectations

Theo, you brought reliability, clarity, and strong collaboration to the squad this year. You kept delivery moving and earned positive feedback from Engineering, Design, and Sales. However, the product outcomes we committed to were substantially below target. This rating reflects that gap—not a lack of effort or commitment.

I also owe you an acknowledgment: I did not give you clear feedback about that gap during the year. When you asked in Q3 whether you were on track, I said, “Yes, great velocity.” That answer confused delivery progress with goal progress and gave you the wrong signal. We should have discussed the metrics and changed course together. You should not be hearing this assessment for the first time in an annual review.

Strengths

Reliable execution. Your squad shipped 14 features, 12 on time. Your engineering lead highlighted your clear specs, consistent participation in sprint reviews, and ability to keep the team unblocked. These are important strengths that make the squad more effective.

Strong working relationships. Design described you as great to work with, and Sales praised your responsiveness. You listen to partners and follow through on commitments. That trust is an asset to preserve as you become more selective about what the squad builds.

What to work on

Own outcomes, not just delivery. Your two annual goals were: - Increase weekly Timeline usage from 22% to 30%. Actual usage reached 23%. - Reduce time to first plan from 3.0 days to 1.0 day. Actual time reached 2.6 days.

Both metrics improved, but neither came close to its target. For a PM, successful delivery is a means to improving customer outcomes, not the end measure of success. This substantial shortfall is the primary evidence for the Below expectations rating.

Strengthen prioritization and validation. Six of the 14 shipped features are used by fewer than 2% of teams. Low adoption does not automatically mean a feature lacks value, but it requires us to examine whether the investment was justified. Five features came from Sales requests, including two for individual customers. Those requests may have legitimate business value; they still need an explicit rationale relative to our broader goals.

Design’s feedback that we should have tested more before building reinforces this development area. Before committing engineering time, establish the customer problem, intended audience, evidence of demand, and expected impact. After launch, check whether that impact materialized.

Make tradeoffs visible. Being responsive should not mean accepting every request. Bring partners a clear recommendation: what we should build, what we should decline or defer, and why.

Goals for the next half

1. Improve the two core outcomes. Increase weekly Timeline usage from 23% to 26% and reduce time to first plan from 2.6 days to 2.0 days, using consistent measurement definitions. In the first month, identify the biggest barriers and establish monthly checkpoints toward those targets.

1. Validate before committing. For every substantial roadmap investment, document the problem, target users, supporting evidence, success metric, and opportunity cost. Test the riskiest assumption before building, or explicitly document why an exception is warranted.

1. Close the post-launch learning loop. Review each substantial release within six weeks against its success metric. Audit the six low-adoption features and recommend whether to improve, maintain, or retire each, accounting for customer and business value.

1. Lead outcome-based prioritization. Bring a monthly roadmap recommendation grounded in metric progress and customer evidence, including explicit tradeoffs for stakeholder requests.

My commitment is to make our 1:1s outcome-focused, review these checkpoints with you, and give direct feedback when progress is off track. Your execution strengths provide a solid foundation. The next step is applying that discipline to choosing and validating work that produces measurable customer value.