Start with the user problem, not the feature list.
Example: reframed a retention effort from “add more content” to climate-aware timing guidance, which materially improved repeat usage.
About
Product manager by day, furniture builder by night.
Quick Snapshot
- Role Focus
- Product Management, AI-enabled products, platform reliability
- Experience
- 0→1 and scale-stage product teams
- Strengths
- Strategy, prioritization, and execution under ambiguity
- Current
- Product Manager at Indeed
I work on product teams where clarity, shipping rhythm, and good judgment matter more than shiny roadmaps. I care about reducing complexity, closing feedback loops, and building things people actually use.
Outside of software, I build furniture and tinker in the shop. Wood has a way of exposing bad assumptions fast, which is a useful habit to bring back into product work.
This site is where I keep notes, project writeups, and experiments across software and woodworking.
Operating Principles
Reduce risk in slices, then scale what works.
Example: replaced high-risk rewrite plans with phased migrations and clear checkpoints, restoring release confidence while shipping roadmap work.
Make decisions legible across functions.
Example: used concise decision memos and explicit tradeoff framing to align design, engineering, and leadership on scope and sequencing.
Measure outcomes, then document the learning.
Example: paired launches with activation and retention targets, then published post-launch readouts to improve future prioritization.