Back to portfolio
Product & OperationsSimulated project
Product Manager portfolio brief
A simulated product & operations exercise for Product Manager. Treat it as realistic practice, not real client or protocol work.
7 deliverables6 tools referenced3 linked interview questions
Objective
Audit one real product flow
Expected deliverables
Product briefPRDPrioritization memoUser journeyAcceptance criteriaLaunch checklistPost-launch review
Recommended workflow
- Audit one real product flow
- Write a problem brief and PRD with failure states
- Define launch criteria, metrics, and what evidence would change the decision
- Review the result against the rubric, then package it as a case study.
Constraints and safety
- Use only public sources or clearly simulated data.
- Never include seed phrases, private keys, or wallet secrets.
- Redact private user, company, security, legal, or compensation information.
- State every assumption you make.
Tools in practice
- Linear or Jira
- Track decisions, dependencies, bugs, and owners connected to product brief and PRD; the ticket is a coordination record, not the work itself.
- Notion
- Draft, review, and maintain product brief and PRD, with owners, source links, and change history.
- Figma
- Develop and review visual work used in product brief and PRD.
- analytics tools
- Measure the role-specific signals behind product brief and PRD and document attribution, time window, and known gaps.
- Dune
- Collect and analyse the evidence used in product brief and PRD, with definitions and reproducible steps.
- customer research tools
- Recruit and record interviews, surveys, and usability sessions, then connect repeated problems to product decisions without treating requests as requirements.
What a strong submission shows
- A wallet or dApp onboarding audit
- A small PRD
- A prioritization memo
- A launch and rollback plan
Weak submission patterns
- Feature lists with no problem definition
- Roadmaps with no trade-offs
- Case studies claiming impact with no measurement basis
Review rubric
- Accuracy of claims and sources
- Relevance to the target role
- Decision quality and trade-offs
- Completeness of the deliverable
- Clarity of communication
- Honest limitations and next steps
Present it as a case study
- Explain the problem, sources, decisions, ownership, constraints, output, review, and what you would change.
- Show the final artifact before the process notes.
- State what you owned and what belonged to other people.
- Label the work as simulated, and keep any real contribution clearly separate.
Interview questions this project helps you answer
How would you prioritize a usability improvement against a security or infrastructure requirement?
What should make a token or protocol feature unready for launch?
Describe a product decision you would reverse after seeing new evidence