Usable with a quick edit10 of 12 checks passed
The review is complete, well-structured, and directly usable; only minor wording tweaks might be needed, and no evidence re-checking is required.
Output
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
| Goal | Target | Result |
|---|---|---|
| Weekly Timeline view usage | 22% → 30% | 22% → 23% |
| Time for new teams to build first plan | 3 days → 1 day | 3.0 → 2.6 days |
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.
- Timeline weekly usage: 23% → 27%. Start with discovery: find out why teams aren't using Timeline before deciding what to build.
- 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.
- 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.
- 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.
- 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.
Grades and run details
Decision model 88 · LLM judge 11 of 13 checks
Decision model checks
- passUses the supplied evidence correctly64%
- passAddresses the actual decision75%
- partialRespects explicit constraints21%
- failIdentifies material uncertainty30%
- passAvoids unsupported claims40%
- passProduces the required deliverable80%
- passOwns the manager's part100%
- passSets next goals as outcomes, with support96%
- passClear and direct, with care100%
- passJudges outcomes, not activity95%
- passNames gaps you could see97%
- passWeighs the whole period89%
Run
- Run
- #1
- Time to output
- 28 s
- Submitted
- 5 Oct 2026