I build the bridge between the people who write the code and the people who need it to work.
Part translator, part planner, part nag-with-a-spreadsheet. I turn fuzzy asks into roadmaps engineering can build from — and turn engineering tradeoffs into decisions anyone can make confidently.
A program manager who sits between teams doesn't have one job — she has three, all at once.
Turn a fuzzy ask from leadership or a client into a spec an engineer can actually build from — no guessing, no scope creep mid-sprint.
Turn a technical tradeoff into a decision a non-technical stakeholder can make confidently — without dumbing it down or sitting through a deck.
Run the unglamorous cadence — planning, standups, risk logs, retros — that turns "we should build that" into something that's actually live.
A quick look at the kind of fuzzy-to-shipped problems I like living in.
Less "skills list," more "what's actually open in my browser on a Tuesday."
A few tiny games that borrow from the day job: timing, translation, and surviving a chaotic sprint.
Click "Lay plank" when the marker hits the green zone. Three misses and you start over — get all 8 planks down to cross.
Match every vague ask to the spec it actually needs. Find all 6 pairs in as few moves as you can.
Survive a chaotic product cycle: catch the good stuff (features, clear specs, boba) and dodge scope creep & prod bugs. Ship at 100 velocity before morale hits zero.
Short, practical write-ups on the PM craft. More coming soon.