Write a performance review

Annual Review: Theo Brandt

Reviewer: Ana Ruiz, Group PM Overall rating: Meets expectations

---

Summary

Theo, this year you showed that you can run a squad that ships reliably. That matters, and the people you work with notice it. But the two outcomes we set for the year mostly didn't move, and closing that gap is the most important thing for your next half.

Before the details, I need to own something. In our Q3 1:1, you asked whether you were on track for your goals. I told you yes and pointed to your velocity. That was wrong. The goal metrics weren't moving, and I didn't raise it. You asked the right question at the right time, and you deserved a straight answer that could have changed how you spent Q4. Some of the gap you'll read about below is on me. I've changed how I'll run our 1:1s so it doesn't happen again (see Goals).

Results against goals

Neither goal was met. Time to first plan improved by about 13%, which is real progress but short of the target. Timeline usage was essentially flat.

Strengths

Delivery and execution. Your squad shipped 14 features, 12 of them on time. That's a strong record and a hard one to sustain.

Clarity and keeping the team moving. Your engineering lead said: "Theo keeps the team unblocked, his specs are clear, and he never misses a sprint review." Clear specs and reliable rituals are the base of a healthy squad, and you've built that.

Collaboration and responsiveness. Your designer called you "great to work with." Sales described you as "very responsive." People trust you to follow through, and that trust is an asset you can now point in a more deliberate direction.

What to work on

1. Connect what you build to the outcomes you own. Six of the 14 features are used by fewer than 2% of teams. Delivery was strong, but much of it went to work that didn't move Timeline adoption or onboarding speed. The question to ask before each piece of work is: which of my goal metrics will this move, and how will I know?

2. Validate before building. Your designer said: "I wish we'd tested more before building; we shipped three things I'm not sure anyone uses." Lightweight testing, such as prototypes, customer interviews, or fake-door tests, would let you put your execution strength behind ideas that are more likely to land.

3. Prioritize stakeholder requests against goals. Five features came from Sales requests, and two of those served a single customer each. Being responsive to Sales is good. Saying yes by default isn't. I'd like you to weigh requests openly against your goals and be comfortable saying "not now, and here's why." I'll back you in those conversations.

4. Track your outcome metrics yourself. Don't rely on me to flag when a metric is off. Know where your numbers are every month. If they aren't moving, raise it early, even when delivery looks great.

Rating rationale

The rating is Meets expectations. Your execution, delivery record, and collaboration are strong. Your outcome results fell well short of target, which would normally weigh more heavily on the rating. I've also taken into account that I gave you inaccurate feedback in Q3, when there was still time to change course. The rating reflects both your real strengths and the need to turn them into results.

Goals for the next half

These are proposed targets. Let's finalize them together in our next 1:1.

1. Timeline weekly usage: 23% → 27%. Start with discovery: find out why teams aren't using Timeline before deciding what to build.
2. Time to first plan: 2.6 → 1.5 days. Build on the progress you've made by finding and removing the biggest drop-off points in onboarding.
3. Validate before building. Every feature over a small size threshold should have a written hypothesis, a success metric, and some form of user validation before development starts. Review usage 30 days after launch.
4. Review the six low-usage features. Recommend for each whether to improve it, leave it, or retire it, so we reduce maintenance load and learn from what didn't land.
5. A clear intake process for stakeholder requests. Share it with Sales so they understand how their asks are weighed against squad goals.

My commitment to you: starting now, the first item in every monthly 1:1 will be your goal metrics, before delivery or stakeholder updates. If something is off track, you'll hear it from me clearly and early.

I'm glad you're on the team, Theo. You've proven you can deliver. Now let's make sure what you deliver moves the needle.

— Ana

---

Note for you, Ana: I'd suggest raising the Q3 feedback in person before Theo reads this, so the written acknowledgment doesn't come as a surprise. If calibration pushes toward Below expectations because of the missed goals, the Q3 note is the key context to bring up there.

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.