A living view of the path I’m taking into Product — what I’ve completed, where I am now, and the work I’m choosing next. I’m trying to build the transition the same way I want to build products: evidence first, useful moves, real feedback, and constant iteration.
Learn how software gets built so Product decisions can stay grounded in technical reality.
Strengthen the language, accountability, and decision-making principles behind effective Product teams.
Move beyond “I built something” and explain the problem, tradeoffs, decisions, and outcomes behind the work.
I’m actively researching a day-of group context handoff problem: when one person carries the plan, context, and “what’s next?” decisions for everyone else.
Only after the problem survives discovery: map the journey, choose the critical moment, and prototype the lightest experience worth testing.
Turn the case study into proof that feedback changes the product, not just a polished mockup.
Translate the work into clear stories that show discovery, prioritization, technical fluency, stakeholder alignment, and outcomes.
Use the portfolio, network, applications, and interview reps to move into a role with meaningful Product ownership.
The destination is bigger than one company or one job title: become the kind of Product leader who understands users, aligns teams, makes smart tradeoffs, and ships technology people genuinely care about.
Side quest complete
The roadmap is just one little corner of the site. Head back to the side-quest hub to see what else gets unlocked over time.
