What a Kudo review looks like

Sarah had an unusually high-impact quarter for an individual contributor. The Q4 data platform migration — three months of unglamorous infrastructure work that touched 11 internal services — landed without a single production incident. That doesn't happen by accident. It happens because someone held the technical and the human pieces together simultaneously, and Sarah did both.

She finished the quarter as one of the most trusted engineers on the team, which is a different kind of achievement than shipping fast. People came to her first when something was on fire.

---

The migration is the obvious win, but I want to name the less obvious one. Sarah ran informal daily standups for the three dependent teams during crunch weeks — not because she was asked to, but because she saw the communication gap and filled it. That's the kind of judgment that's very hard to hire for.

Her technical writing improved markedly this cycle. The architecture doc she wrote for the new event pipeline is the first piece of internal documentation I've seen engineers actually reference during incidents. She's developed a real ability to write for an anxious reader — someone who needs clarity fast.

One more: she debugged a latency regression in the pipeline under time pressure, correctly ruled out three plausible causes, and found the real one (a batching misconfiguration that had been in place for 18 months). She didn't guess. She reasoned through it.

---

The area I want to push on is stakeholder communication at the director level and above. Sarah is fluent in team-level communication — she's excellent with peers and ICs. But in two cross-functional reviews this quarter, she underplayed our work in ways that created confusion upstream. The platform team's contributions to two roadmap decisions didn't register because Sarah framed them as "infra support" when they were actually blockers being removed.

This is a communication skill, not a technical one. She has the credibility to speak at that level — the question is whether she's willing to claim it. I'd like to see her present in at least two director-level forums in H1 and own the narrative, not support someone else's.

---

In the next cycle, I want Sarah to lead the observability initiative from kickoff to rollout. She's technically ready, and it'll force the stakeholder communication muscle I mentioned above. I'll be in the room for the first two external presentations; after that, she runs them.

Longer term, Sarah is on the path to Staff Engineer — not because she's the loudest voice, but because she's consistent, and consistency compounds. If she stretches into the communication areas this year, I expect to be making that case by Q4.