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.

Annual Review: Theo Brandt

Prepared by: Ana Ruiz, Group PM Overall rating: Meets expectations

Theo, I want this review to be direct, because you deserve a clear picture. I also need to own a mistake of mine, which I cover below.

Results against your goals

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

Strengths

Delivery and team health. Your squad shipped 14 features, 12 on time. Your engineering lead says you keep the team unblocked, write clear specs, and never miss a sprint review. That reliability is hard to build, and the team trusts you.

Collaboration. Your designer called you "great to work with." Sales called you "very responsive." You treat partners as partners, and that is a real asset.

Responsiveness to stakeholders. You moved quickly on requests and kept people informed.

What to work on

1. Connecting what you ship to the outcomes you own. Your goals were about Timeline adoption and onboarding speed. Most of the year's output didn't aim at either. Six of the 14 shipped features are used by fewer than 2% of teams. Five of those six were Sales requests, and two of those were built for a single customer each. Responsiveness is a strength, but here it substituted for prioritization. Saying yes to five Sales asks used capacity that could have gone toward your goals.

2. Validating before building. Your designer said, "I wish we'd tested more before building; we shipped three things I'm not sure anyone uses." I agree. Moving fast on unvalidated work produces output, not impact. Fewer, better-tested bets would serve you and the team better.

3. Using data to drive decisions. Our 1:1s focused on delivery and stakeholder updates, not on whether your metrics were moving. Part of your job is to look at usage numbers regularly and change course when they don't move. I'd like you to make that a habit.

Where I fell short

In your Q3 1:1 you asked whether you were on track for your goals. I told you yes, citing great velocity. That wasn't accurate. Velocity was great, but the goal metrics weren't moving, and I never raised it. You asked the right question and got a misleading answer. I should have flagged this months earlier, when you had time to change course. Some of this outcome is on me, and it's a main reason I'm rating you Meets rather than Below expectations.

Rating rationale

Meets expectations reflects strong execution and collaboration, weighed against two missed outcome goals and a significant share of shipped work with minimal adoption. Without the missing mid-year feedback, I'd have had a harder conversation with you about the lower end of this rating. I don't see evidence for Exceeds, and I think the evidence supports Meets rather than Below, given partial progress on onboarding and the feedback gap on my side. To be clear, this is a solid-but-not-yet-sufficient year on outcomes, and the next half needs to show a shift.

Goals for the next half

1. Onboarding: Reduce time to first plan from 2.6 days to 1.8 days. Identify the two or three biggest drop-off points in the first-plan flow within the first month, and bring me a proposal for addressing them.
2. Timeline adoption: Raise weekly Timeline usage from 23% to 27%. Start with research into why teams who try Timeline don't return, and share findings with me by the end of month one.
3. Validation before build: Every feature above a small-effort threshold needs a written success metric and some evidence of demand (user tests, prototype feedback, or data) before engineering starts. Requests from a single customer need a case for broader value.
4. Post-launch review: Check usage of each shipped feature 60 days after launch and report the results to me. If something is underperforming, tell me what you'll do about it.
5. Sales partnership: Work with Sales on a lightweight way to evaluate requests so that "yes" is reserved for asks tied to our goals or to broad demand, and "not now" comes with a clear reason.

How we'll work together

We'll spend the first part of every 1:1 on your goal metrics, not just delivery. I'll tell you plainly where you stand each quarter, including when the news is uncomfortable. If you disagree with anything here, I want to hear it. I'd also like to hear what support would help most.

You've built a team that executes well and trusts you. The next step is pointing that capability at the metrics that matter. I'm confident you can do it.

Ana

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.