Skip to main content

​
AI Product Manager

​
Overview

The AI Product Manager monitors your venture continuously - tracking PRD health, momentum signals, team performance, and milestone progress across every stage of your journey. Instead of wondering if your venture is progressing, you receive proactive alerts when scores drop, automatic celebrations when you clear gates, and weekly digests showing exactly where you gained ground. This system eliminates silent stalls and ensures every venture moves forward with clear evidence.

​
Step-by-Step Guide

​
Receiving Your Weekly Progress Digest

  1. Automatic delivery every Wednesday - The system sends your digest to your preferred channel (WhatsApp, Slack, or in-app) at 10 AM UTC without requiring any action from you.
  2. Review your score movement - The digest shows your PRD score before and after (e.g., 72 to 78), identifies which dimension improved most (like Vision Clarity), and lists completed milestones from the week.
  3. Check your next action - At the bottom of every digest, you’ll see the specific next step to improve your weakest dimension. This action is derived from your current gate requirements and takes under 30 minutes.
  4. Update your channel preference - Visit your profile settings or use the /supasherpa page to change where you receive communications. The system respects your preference across all automated messages.

​
Understanding Momentum Alerts

  1. Day 7 gentle check-in - If your PRD hasn’t been edited in 7 days, you’ll receive a message on your preferred channel naming your momentum state (like CLOUD_COVER) and offering help to unblock progress.
  2. Day 14 direct nudge - Without response to the Day 7 message, the system sends a more direct nudge both on your preferred channel and in-app, with 2 specific actions you can complete in under 30 minutes to restart momentum.
  3. Day 21 formal review - After 21 days without PRD activity, you receive messages on all channels with explicit options: re-engage with a specific action, schedule a call with your team, or formally pause the venture. This triggers a Product Manager review.
  4. Respond through any channel - Engaging via any channel (message, vault upload, team interaction) resets the stall detection. Only PRD editing inactivity triggers these alerts.

​
Celebrating Milestones

  1. Stage gate clearance - When your PRD clears a gate (like CONVICTION at score 82 with all core dimensions above 60), you receive a celebration message within 60 minutes on all active channels. The message includes the gate cleared, your overall score, the top 2 dimensions that drove the achievement, and what the next stage demands.
  2. Grade improvements - When your PRD grade jumps a full letter (D to C, C to B), you receive a celebration on your preferred channel showing the biggest dimension mover and your next target score.
  3. Confidence thresholds - When your brief confidence score crosses the ready threshold (75 for Fiftyknots track, 80 for AI Acumen track), you get a celebration and the system initiates matchmaking with experts.

​
Sprint Gateway Reviews

  1. Automatic review at sprint boundaries - Every 4-12 weeks (variable based on your track), the system conducts a structured gateway review analyzing your PRD score trajectory, drift events, momentum state, and team health.
  2. Receive the machine recommendation - The review generates one of four recommendations: Continue (you’re on track), Accelerate (exceeding targets), Pivot (struggling on 2+ dimensions), or Stop (persistent below threshold for 3+ cycles). Stop recommendations always escalate to human review before any action.
  3. View the evidence package - The review appears as a structured in-app report, a customer summary on your preferred channel, and a team discussion thread in Slack #v-{shortname}-reviews. Each includes specific metrics that drove the recommendation.
  4. Override process - If you disagree with a Pivot or Stop recommendation, the human review process allows documented overrides with one of four reasons: strategic context, portfolio timing, learning extension, or leadership bet. Overrides are time-limited to one sprint.

​
Responding to Drift Alerts

  1. MAJOR drift detection - When a critical PRD section changes, is removed, or contradicts existing direction, you receive an alert within 4 hours on your preferred channel.
  2. Review the evidence - The alert shows which section changed (identified by hash), the dimension impact with score before/after, and exactly 2 action paths: deliberate pivot or scope drift correction.
  3. MINOR drift handling - Small changes are logged and included in your weekly digest rather than triggering immediate alerts. You can review drift history anytime through the PRD dashboard.
  4. Machine pivot escalation - If the drift triggers a machine PIVOT recommendation at a gateway, the alert is escalated to within 1 hour and includes the full gateway evidence package.

​
Common Questions

Q: How does the system know if my venture is stalling?
The system tracks multiple signals: PRD edits (7/14/21 day thresholds), momentum score (below 30 is STALLED), customer engagement across all channels, and team activity. A venture only triggers stall alerts if the PRD goes untouched AND no other engagement occurs. If you’re messaging your team or uploading to the vault, you’re not stalled even if the PRD isn’t edited. Q: What happens if I disagree with a gateway review recommendation?
Stop recommendations always go to human review before any action - they’re never automated. For Pivot recommendations, you can request a human override with one of four documented reasons (strategic context, portfolio timing, learning extension, leadership bet). The override is time-limited to one sprint, after which the next gateway re-evaluates with fresh evidence. Q: Can I change where I receive these messages?
Yes. Visit your profile settings or the /supasherpa page to set your preferred channel (WhatsApp, Slack, or in-app). The system respects this preference for weekly digests, stall nudges, and most alerts. Gate clearances and Accelerate recommendations broadcast to all channels because they’re celebration-worthy. You cannot set multiple external channels as preferred - pick one. Q: Why did I get a celebration for clearing a gate but not for my score improving from 74 to 76?
The system celebrates full letter grade improvements (D to C, C to B) and stage gate clearances, but not incremental score gains within the same grade. A 2-point gain from C+ (74) to C+ (76) is progress but doesn’t cross a meaningful threshold. The weekly digest always shows score movement, but celebrations are reserved for gates and full letter jumps. Q: What if my team is causing delays but I’m working hard on my PRD?
The system monitors team health separately from your venture momentum. If your team’s average response time exceeds 24 hours for 3 consecutive days, a team health digest goes to Slack #v-{shortname}-team. Individual drag (2+ missed deadlines, 48+ hour response times) triggers private DMs to that person, not public channels. If team health drops below 40 (CRITICAL), the Product Manager is alerted within 2 hours for team composition review.

​
Troubleshooting

Issue: I responded to the Day 7 stall nudge but received a Day 14 nudge anyway
Solution: The system only resets stall detection if you edit the PRD or engage through trackable channels (messaging, vault uploads, team interactions). Replying to the nudge message itself doesn’t count as venture activity. Open your PRD and make any edit, even a small one, to signal active work. Issue: My weekly digest says my score improved but I don’t see it in the PRD dashboard
Solution: Digests are generated Wednesday mornings based on the previous week’s activity. The PRD dashboard may show real-time data that includes changes after the digest was sent. If the discrepancy persists beyond 24 hours, check that you’re viewing the correct venture (if you have multiple) and that no MAJOR drift events rolled back a score gain. Issue: I received a MAJOR drift alert but I didn’t change anything
Solution: MAJOR drift can trigger from three sources: you edited a critical section, a team member edited it, or a system auto-population conflicted with existing content. Check the drift alert for the specific section identified. If a team member made the change, coordinate with them. If it was auto-population, you have two paths: accept the change as a deliberate pivot or correct it as scope drift. Issue: The gateway review recommended Pivot but I believe we’re on the right track
Solution: Gateway reviews generate machine recommendations based on quantitative signals (PRD scores, momentum, team health). If you disagree, request human review through the in-app gateway review report. Document your reasoning with one of the four override categories. The override is time-limited to one sprint, giving you focused time to prove the thesis or adjust course. Living PRD - The AI Product Manager tracks your PRD health continuously, but you control the content. Visit /prddashboard to edit sections, view scoring breakdowns by dimension, and see version history. Every edit triggers re-scoring within minutes, which feeds into your weekly digest and gateway reviews. SupaSherpa Chat - While the AI Product Manager sends proactive alerts and digests, SupaSherpa Chat (/supasherpa) lets you ask questions anytime. Use it to clarify why a dimension score dropped, get tactical advice between digests, or understand what a gateway review recommendation means for your next steps. Journey Dashboard - The AI Product Manager monitors your position within the ICP-specific journey. Visit /journeydashboard to see your stage, sub-stage, and task completion status. Gateway reviews reference this journey progress when making Continue/Accelerate/Pivot/Stop recommendations, so understanding your journey context helps you interpret Product Manager signals.