Write a performance review

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

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.

Theo Brandt — Annual Review

Ana Ruiz, Group PM, Plotwise

Overall rating: Below expectations

Theo, you brought strong execution discipline, clear communication, and dependable partnership to the team this year. However, our two primary goals were to increase weekly Timeline use and shorten the time new teams take to build their first plan. We made only modest progress on both:

• Weekly Timeline use: increased from 22% to 23%, against a goal of 30%.
• Time to first plan: decreased from 3.0 days to 2.6 days, against a goal of 1 day.

Those results are the basis for this rating. Your squad shipped 14 features, 12 on time, but delivery volume and timeliness did not translate into the customer outcomes we committed to achieve. Six of those features are used by fewer than 2% of teams. Low adoption does not automatically make a feature unsuccessful, but it does require us to establish what value it created and whether it justified the investment.

I also owe you an acknowledgment of my part in this. In Q3, you explicitly asked whether you were on track, and I told you yes, citing great velocity. That was misleading: I should have distinguished delivery performance from progress against your goals. Our 1:1s focused too heavily on delivery and stakeholder updates, and I did not address the stalled metrics. You should not be hearing this assessment for the first time in an annual review. That management failure is mine; it does not erase the outcome gap, but it matters to how we understand the year and move forward.

Strengths

Reliable execution and engineering partnership. You keep the team unblocked and provide clear specs. The engineering lead specifically highlighted both, along with your consistent participation in sprint reviews. Shipping 12 of 14 features on time reflects real delivery discipline.

Strong collaboration and responsiveness. Design describes you as great to work with, and Sales values your responsiveness. You create productive working relationships and follow through on commitments. Those strengths are important foundations for effective product leadership.

What to work on

Shift from managing delivery to managing outcomes. The roadmap needs a clearer connection to Timeline adoption and first-plan speed. For each meaningful investment, define the customer problem, expected metric movement, and how we will assess success after launch. When the metrics are not moving, bring that into our discussions early and recommend a change in approach.

Validate demand before committing engineering capacity. Design’s concern that we should have tested more, together with the low usage of several shipped features, points to a need for stronger discovery. Use prototypes, customer conversations, and lightweight experiments to test the riskiest assumptions before building.

Make prioritization trade-offs explicit. Five shipped features were Sales requests, including two for individual customers. Those requests may have legitimate business value, but responsiveness alone is not a sufficient reason to prioritize them. Assess their customer reach, strategic or commercial value, cost, and opportunity cost—and make clear when an exception is worth taking.

Goals for the next half

1. Increase weekly Timeline use from 23% to 27%. Identify the main adoption barriers, test proposed solutions, and prioritize the interventions with the strongest evidence.
2. Reduce time to first plan from 2.6 days to 1.8 days. Diagnose where new teams stall and measure whether each onboarding improvement reduces that friction.
3. Strengthen investment decisions. For every substantial roadmap item, document the problem, supporting evidence, intended outcome, and success measure before committing to build. Review results within six weeks of launch and decide whether to iterate, expand, or stop.

We will confirm metric definitions and tracking at the start of the half, then review progress monthly. I will give you explicit feedback on whether you are on track, help resolve prioritization conflicts, and avoid treating velocity as a substitute for impact.

You have a strong execution foundation. The next step is to apply that strength to fewer, better-supported bets that measurably improve customers’ experience.