Write a performance review

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.

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.

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