Skip to content

Update Checklist - Product

Update Cadence

Monthly Review - First Monday of each month, or when significant product changes occur.

Pre-Update Checklist

Before You Start

  • [ ] Review customer feedback from past month
  • [ ] Check analytics on product usage
  • [ ] Review competitive landscape changes
  • [ ] Gather feedback from beta users (Section 05)

Update Process

1. Vision & Value Proposition (vision.md, value-proposition.md)

  • [ ] Still accurate given market feedback?
  • [ ] Any shifts in target audience or use cases?
  • [ ] Update last_updated if changed
  • [ ] Note: Major changes require updating Section 03 (Branding)

2. MVP Specifications (mvp-specifications.md)

  • [ ] Any features added/removed based on feedback?
  • [ ] Technical feasibility confirmed with engineering?
  • [ ] Timeline still realistic?
  • [ ] Update priority levels based on customer requests
  • [ ] Check dependencies between features

3. Technical Architecture (technical-architecture.md)

  • [ ] Still supports MVP requirements?
  • [ ] Any new technical constraints or opportunities?
  • [ ] Security requirements up to date?
  • [ ] Scalability assumptions validated?

4. Cloud Credits Strategy (cloud-credits-strategy.md)

  • [ ] Partner discussions progressing?
  • [ ] Credit amounts still optimal ($200 sweet spot)?
  • [ ] Integration timelines on track?
  • [ ] Legal terms with cloud providers progressing?

What to Check

  • [ ] All documents have current last_updated (within 30 days)
  • [ ] No contradictions between documents
  • [ ] MVP timeline aligns with GTM plan (Section 04)
  • [ ] Technical constraints documented

Key Metrics to Review

  • [ ] Feature adoption rates (from analytics)
  • [ ] Customer satisfaction scores
  • [ ] Time-to-value metrics
  • [ ] Technical debt accumulation
  • 00-Command-Center: Include product milestones in sprint priorities
  • 02-Market: Ensure competitive analysis reflects current positioning
  • 03-Branding: Sync messaging if value prop changes
  • 04-Marketing: Align MVP features with launch plan
  • 05-Beta: Review beta user feedback for product insights
  • 08-Operations: Technical architecture impacts deployment

Red Flags

⚠️ If you notice: - MVP scope expanding beyond 6-week timeline - Technical architecture can't support requirements - Value proposition not resonating with beta users - Cloud credits strategy blocked by legal issues

Time Budget

Monthly review: 2-3 hours Quick sync: 30 minutes (if no major changes)

Last Updated: YYYY-MM-DD Next Review: First Monday of next month