​
Weekly Product Review Process

​
Overview

A recurring meeting to review product progress, prioritisation, and key decisions. This is the heartbeat of product management. Frequency: Weekly Duration: 60 minutes Owner: Chief Product Officer Attendees:
  • Chief Product Officer (facilitator)
  • CTO (or Engineering Lead)
  • UX Designer
  • Product team members
Optional:
  • CMO (for go-to-market discussion)
  • CEO (for strategic alignment)

​
Agenda (60 minutes)

​
1. Metrics Review (10 minutes)

Review:
  • North Star Metric trend
  • Key product metrics (activation, engagement, retention)
  • Success metrics for recently shipped features
  • Any alerts or concerning trends
Questions:
  • What’s working well?
  • What needs attention?
  • Any surprises in the data?
Artifacts:
  • Product metrics dashboard
  • Success criteria tracking

​
2. In-Flight Features Status (15 minutes)

For each active feature:
  • Current status (on track, at risk, blocked)
  • Progress since last week
  • Blockers or dependencies
  • ETA changes
Focus on:
  • Features launching this sprint
  • Features in testing/QA
  • Critical path items
Outcomes:
  • Identify blockers to escalate
  • Adjust timelines if needed
  • Reallocate resources if necessary

​
3. Customer Feedback & Insights (10 minutes)

Review:
  • Top customer requests this week
  • Support ticket trends
  • User research insights
  • Sales/CSM feedback
Questions:
  • Are we seeing patterns?
  • Any urgent issues to address?
  • Any opportunities we’re missing?
Sources:
  • Support ticket system
  • Customer interview notes
  • Sales team input
  • Usage analytics

​
4. Prioritization & Roadmap Updates (15 minutes)

Activities:
  • Review new feature requests and opportunities
  • Score using RICE framework
  • Update roadmap based on new information
  • Discuss any strategic shifts
Questions:
  • Should anything move up in priority?
  • Should we defer or cancel anything?
  • Do we have capacity for new work?
Artifacts:
  • RICE scoring spreadsheet
  • Product roadmap
  • Feature backlog

​
5. Decisions & Action Items (5 minutes)

Document:
  • Key decisions made
  • Action items with owners
  • Follow-ups needed
  • Next week’s focus areas
Outcomes:
  • Clear decision log
  • Accountability for actions
  • Alignment on priorities

​
6. Questions & Discussion (5 minutes)

Open floor for:
  • Cross-functional questions
  • Strategic concerns
  • Process improvements
  • Team needs

​
Pre-Meeting Preparation

​
CPO Prep (30 minutes before)

  • Review metrics dashboard
  • Check feature status updates
  • Review customer feedback from last week
  • Prepare discussion topics
  • Update agenda with specific items

​
Team Prep (Optional)

  • Have status updates ready
  • Prepare any questions or blockers
  • Review customer feedback in your area

​
Meeting Outputs

​
Decision Log

Document in: /processes/decision-log.md Format: 
Date: [YYYY-MM-DD]
Decision: [What was decided]
Rationale: [Why]
Owner: [Who is responsible]

​
Action Items

Track in project management system Format: 
- [ ] [Action item]
  - Owner: [Name]
  - Due: [Date]
  - Status: [In progress | Blocked | Done]

​
Roadmap Updates

Update: /roadmaps/[current-quarter]-roadmap.md Changes to:
  • Feature priorities
  • Timeline adjustments
  • New additions or deferrals

​
Best Practices

​
DO

  • Start and end on time - Respect everyone’s calendar
  • Come prepared - Review materials beforehand
  • Focus on decisions - Not just status updates
  • Document outcomes - Decisions and action items
  • Be data-driven - Use metrics to inform discussions
  • Stay strategic - Don’t get lost in implementation details

​
DON’T

  • Don’t skip metrics - Data keeps us honest
  • Don’t defer hard decisions - Address issues head-on
  • Don’t let it become a status report - Use async updates for status
  • Don’t ignore customer feedback - Their voice drives priorities
  • Don’t go over time - If more time needed, schedule separately

​
Communication

​
Post-Meeting

Within 24 hours, CPO sends:
  • Meeting notes - Key decisions and action items
  • Roadmap updates - If any changes made
  • Follow-ups - Any additional context needed

​
Distribution

  • Product team (required)
  • Engineering leads (required)
  • Leadership team (summary)
  • Broader org (quarterly highlights)

​
Continuous Improvement

​
Monthly Review

  • Is this meeting effective?
  • Are we making good decisions?
  • Should we adjust format or agenda?
  • Are the right people attending?

​
Feedback

Team members can suggest improvements:
  • More/less time on certain topics
  • Different meeting format
  • Additional attendees
  • Better preparation materials
  • Monthly roadmap planning: /processes/roadmap-planning.md
  • Quarterly OKR review: /processes/okr-review.md
  • Feature launch checklist: /templates/launch-checklist.md
  • Prioritization framework: /frameworks/prioritisation.md