Back to roadmaps
Mixed

Product & Operations roadmap

People targeting product & operations roles such as Product Manager, Product Operations, Technical Writer.

This is a lane-level planning guide, not a role-specific curriculum or a guaranteed path to a job. Starting point: You can start with audits and checklists before owning shipped features.

Milestones

  1. Stage 1 of 5

    Learn product, wallet, and transaction fundamentals

    Learning focus

    Proof artifact

    Flow notes

    Review criteria

    The flow notes should be reviewable by someone else: it names its assumptions, matches the stated task, and could stand as a small piece of evidence on its own.

    Done when: You can produce the flow notes without step-by-step guidance and could explain the decisions behind it.
  2. Stage 2 of 5

    Audit one Web3 user journey

    Learning focus

    Proof artifact

    Journey audit

    Review criteria

    The journey audit should be reviewable by someone else: it names its assumptions, matches the stated task, and could stand as a small piece of evidence on its own.

    Done when: You can produce the journey audit without step-by-step guidance and could explain the decisions behind it.
  3. Stage 3 of 5

    Write a small PRD and prioritization rationale

    Learning focus

    Proof artifact

    PRD

    Review criteria

    The prd should be reviewable by someone else: it names its assumptions, matches the stated task, and could stand as a small piece of evidence on its own.

    Done when: You can produce the prd without step-by-step guidance and could explain the decisions behind it.
  4. Stage 4 of 5

    Build a launch checklist or feedback taxonomy

    Learning focus

    Proof artifact

    Ops system

    Review criteria

    The ops system should be reviewable by someone else: it names its assumptions, matches the stated task, and could stand as a small piece of evidence on its own.

    Done when: You can produce the ops system without step-by-step guidance and could explain the decisions behind it.
  5. Stage 5 of 5

    Apply with a case-study-led portfolio

    Learning focus

    Proof artifact

    Case study

    Review criteria

    The case study should be reviewable by someone else: it names its assumptions, matches the stated task, and could stand as a small piece of evidence on its own.

    Done when: You can produce the case study without step-by-step guidance and could explain the decisions behind it.

Decision point after each milestone

After each milestone, check whether the output matches a role's proof standards on its role guide. If it does not, revisit the milestone before moving on; if a nearby role fits your evidence better, compare it before continuing.

Related roles in this lane

Turn milestones into evidence