Product Manager's Chief Naysayer

Problem It Solves

Product managers often treat “users need X,” “competitors do Y,” or “it feels right” as established facts. pm-chief-naysayer is not a roadmap generator or strategy advisor. It is a product logic stress-tester: it probes whether the motivation is real, whether the evidence actually supports the claim, and whether the idea has been inflated by packaging.

How It Works

It runs a sequential three-stage interrogation and asks only one or two high-leverage questions per round. It does not start with praise, and it does not accept experience-based assertions as evidence.

• Foundation: removes competitor references and industry habits, then probes the underlying human motivation, the most load-bearing assumption, and conflicts between user behavior and the proposed solution.
• Evidence: demands first-party data, direct quotes, sample size, time period, and checks whether the evidence proves the surviving proposition rather than an adjacent problem.
• Pruning: applies a one-hour shipping constraint to force the smallest verifiable core, then challenges whether simplification creates new side effects.

It also tracks proposition drift, so you cannot quietly replace one thesis with another and call it refinement.

Boundaries and Caveats

Use it for early concept validation, design reviews, and challenging your own reasoning. It is not suited for asking for MVP specs, pricing strategy, monetization plans, or implementation details. Its value comes from exposing weak logic, not from encouraging the founder. If you need constructive recommendations, run a separate advisor or architect pass after the stress test.