Write a performance review

Annual Review: Theo Brandt

Reviewer: Ana Ruiz, Group PM Period: Full year

Summary

Theo, you run a reliable delivery team. Your squad shipped 14 features, 12 on time, and engineering and sales both value working with you. This year's problem is that shipping didn't move the two goals we set. Timeline weekly use went from 22% to 23%, against a target of 30%. Time to first plan dropped from 3.0 days to 2.6, against a target of 1 day. We measured the work by output, and the outcomes didn't follow.

Results Against Goals

Goal 1: Raise weekly Timeline use from 22% to 30%. Result: 23%. Missed by 7 points. Most of the year's shipping was not aimed at this metric, and the adoption plan never got the attention it needed.

Goal 2: Cut time to first plan from 3 days to 1. Result: 2.6 days. Real progress, a 13% improvement, but well short of target. Some of the gain likely came from onboarding changes that were not in the roadmap.

Delivery: 12 of 14 features shipped on time. This is strong and I want to be clear about it.

Adoption of what shipped: Six of the 14 features are used by fewer than 2% of teams. Five of those six came from Sales requests, and two were built for a single customer. Your designer flagged three shipped features that nobody seems to use. I think they're right.

Strengths

• Reliability. You keep the team unblocked and hit sprint reviews. Engineering trusts your planning.
• Clear specs. Engineering's feedback on your specs is consistent and specific.
• Stakeholder responsiveness. Sales knows you take their requests seriously and act on them.
• Communication with the team. The designer describes you as good to work with, which matters in a squad where tradeoffs get hard.

What to Work On

Validate before you build. The designer's point is the most important feedback in this review. Three shipped features have no evident users, and you had the means to check before building them. Before you commit to a feature, define the usage metric it has to move and run a cheap test to check the need. If you can't name the metric, don't build it yet.

Connect requests to goals. Sales requests are valuable, but five of your last shipped features came from one channel, and two were for single customers. Treat a request as a hypothesis about usage, not a commitment. Ask how many teams the request affects and how it connects to goal 1 or goal 2. Say no, or propose a different version, when the answer is weak.

Treat goals as the status report. Shipping on time is a good sign, but it doesn't tell us whether goals are on track. Report the goal metric first in every update, even when the number is bad.

Rating

Below Expectations.

This rating is based on the two goals you were given. Both moved in the right direction, but neither reached its target, and the delivered features did little to move them. Calibration requires written evidence for this rating, and the evidence is above: the goal results, the usage data on shipped features, and the designer's observation about untested builds.

Your delivery and team relationships are real strengths and are not part of the rating decision. The rating reflects impact on the goals. I'm also not ignoring that the gap was harder to see than it should have been. I'll address my part in the next section.

Where I Fell Short

In the Q3 1:1, you asked directly whether you were on track. I said yes and pointed to your velocity. I never looked at whether the goal metrics were moving, and they weren't. That was my failure, not yours. You asked the right question, and I gave you a reassuring answer based on the wrong evidence. If I had given you the real numbers in Q3, you would have had a full quarter to change course. I'm sorry for that. I'll change how I run goal check-ins, starting with the next half.

Goals for the Next Half

1. Timeline weekly use: 23% to 28%. Within the first six weeks, interview 10 teams that tried Timeline and stopped using it, and bring me a written summary of why. Then propose and run one adoption experiment, with a success threshold set before launch. I'll review the findings with you at the six-week mark.

2. Time to first plan: 2.6 days to 1.5 days. Identify the two or three steps in onboarding that take the most time for new teams, and ship changes against those steps. Report the number every two weeks.

3. Usage gate on all new features. Every feature in the roadmap must have a named usage metric and a pre-build validation step, agreed with the designer. Features without both don't enter the build queue. We'll review the first three together.

4. Sales request triage. Set up a simple process with Sales. Requests are scored by how many teams they affect and how they tie to the goals. Single-customer requests need a specific justification or a different solution. I'll help with the first conversation with the Sales lead.

Theo, you have the delivery discipline to do this. What you need is to point that discipline at the outcomes we set out to change. Let's start the first six weeks with the Timeline interviews.

To: Theo Brandt From: Ana Ruiz, Group PM Date: Annual Review Rating: Meets expectations

*

Hi Theo,

It’s time for your annual review. First, I want to acknowledge your hard work and dedication over the past year. You are an exceptionally reliable Product Manager, and your squad’s execution has been rock-solid.

Strengths

Your delivery engine is second to none. As your engineering lead noted, your specs are clear, you keep the team unblocked, and you never miss a sprint review. Shifting 14 features in a year—with 12 delivered strictly on time—is an impressive output that demonstrates strong project management and technical collaboration.

You are also a fantastic cross-functional partner. Sales loves working with you because you are responsive and action-oriented, and our design lead appreciates your steady communication and positive team dynamic. You cultivate a smooth, friction-free environment for your squad, which is a rare and valuable skill.

Areas for Improvement

While your output and velocity are stellar, we need to evolve how we measure success. Our primary focus this past year was on driving core product metrics, and we fell short of our targets: * Timeline View Adoption: Moved only from 22% to 23% (against a target of 30%). * Time to First Plan: Improved marginally from 3.0 days to 2.6 days (against a target of 1.0).

Additionally, six of the 14 features we shipped are currently used by fewer than 2% of teams. Five of these were direct requests from Sales, including two built for single customers.

As a PM, your role isn't just to say "yes" to stakeholders and push code across the finish line; it’s to interrogate the why, protect our roadmap, and obsess over the impact of what we build. Relying too heavily on outbound feature requests without validating their broader utility led us to invest engineering cycles in low-impact work.

I also want to own my part in this: looking back at our 1:1 notes, I praised your high velocity when you asked if you were on track, and I failed to course-correct early enough regarding the stagnant metric goals. Moving forward, we will be much sharper about tying your weekly execution directly to our key results.

Overall Rating

Meets expectations.

Your execution, reliability, and stakeholder management are top-tier. To reach the next level, you need to shift your mindset from output (features shipped on time) to outcomes (metrics moved and customer value realized).

*

Goals for the Next Half

To help bridge that gap, your goals for the next H are focused on strategic impact and validation:

1. Improve Core Activation Metrics: Reduce the time new teams take to build their first plan from 2.6 days to 1.5 days, focusing on self-serve friction reduction rather than custom feature additions.
2. Increase Feature ROI & Validation: Implement a mandatory pre-build discovery and validation process for all major initiatives. Ensure that 100% of shipped features have a defined success metric and achieve at least 15% adoption within 30 days of launch.
3. Stakeholder Alignment Strategy: Partner with Sales leadership to create a structured framework for evaluating custom requests, ensuring we prioritize scalable product improvements over single-customer concessions without sacrificing our partnership.

Thank you for everything you do for Plotwise, Theo. I’m looking forward to supporting you as you tackle these new challenges in the year ahead.

Best, Ana

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.