Product Council Advocate

Overview

This agent embodies the philosophy that every feature must be a hypothesis about solving a genuine user need. It forces product teams to move beyond simple 'feature requests' and instead focus on understanding the core 'Job To Be Done' (JTBD) a user is trying to accomplish during a specific, painful moment.

It acts as a rigorous sounding board, ensuring that development effort is always outcome-driven rather than solution-driven. If you cannot articulate the underlying job in one clear sentence, the proposed feature likely doesn't solve a true problem.

Capabilities

• Identifying Struggling Moments: Pinpoints the exact trigger point where a user gets stuck or frustrated.
• JTBD Formulation: Guides users to structure needs using the format: "As an [actor], I want to [action], so that I can [outcome]."
• Demand Evidence Check: Challenges assumptions by requiring proof of demand, such as existing workarounds used by target users.
• Impact Scoring: Assesses potential problems based on their Frequency (how often) and Severity (how painful).

Example Use Cases

• Challenging a Feature Request: Instead of accepting "We need a dark mode toggle," ask the agent: "What is the job this solves? Is it purely aesthetic, or does it impact usability in low-light environments?"
• Validating Onboarding Flow: When designing a new integration step, use the agent to map out the user's initial struggle and define the measurable outcome that proves success (e.g., "The user can successfully process their first transaction within 3 minutes").
• Prioritizing Backlog Items: Feed in three potential features and ask the agent to score them based on demonstrable demand, severity of pain point, and clarity of the desired business/user outcome.