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.

Theo,

You bring strong execution and partnership to the team. The engineering lead called out that you keep work unblocked, write clear specs, and consistently show up for sprint reviews. Your squad shipped 14 features, with 12 delivered on time, and Sales described you as very responsive. Those are meaningful strengths.

Overall rating: Below expectations

This rating reflects the gap between the outcomes we set and the outcomes delivered. Timeline weekly use increased from 22% to 23%, against a goal of 30%. Time to first plan improved from 3.0 days to 2.6, against a goal of 1 day. Delivery was strong, but the intended customer outcomes moved only modestly.

There is also a signal to examine in the shipped work: six of the 14 features are used by fewer than 2% of teams. Five were Sales requests, including two for a single customer each. Low usage does not automatically mean a feature was the wrong investment—some work serves a specific strategic need—but we need clearer evidence and rationale for those choices. Your designer also wished we had tested more before building, and questioned whether three shipped items were useful. Taken together, this points to an opportunity to strengthen discovery, prioritization, and post-launch learning—not simply to ship more.

I also need to own a miss on my part. In our Q3 1:1, you asked whether you were on track, and I told you yes based on velocity. I should have discussed the goal metrics and the gap then. I didn’t, and that deprived you of a timely chance to adjust. I’m sorry. Going forward, I’ll make our 1:1s include progress against outcomes, not just delivery and stakeholder updates.

What to work on

• Start with the user problem and intended outcome; use research and testing to check the problem and proposed solution before committing to build.
• Balance stakeholder responsiveness with product judgment. For Sales requests, make the target customer, broader strategic value, and trade-offs explicit.
• Define success measures before launch, then review adoption and learn from the results. Treat low usage as a prompt to investigate, not as a verdict by itself.

Goals for the next half

1. Raise Timeline weekly use from 23% to 26% by the end of the half. Identify the biggest adoption barriers and review usage trends regularly.
2. Reduce time to first plan from 2.6 days to 2.0 days. Instrument the activation journey, find the main points of friction, and prioritize improvements against them.
3. For each substantial feature bet, document the target user, problem evidence, expected outcome, and success measure before development. Validate larger bets with target teams before building, and review adoption after launch so we can iterate or change course.

I believe your execution strengths give you a solid base for this next step: making sure the team’s delivery translates into measurable customer value.