office-hours

Run a structured product discovery session using six forcing questions to clarify pain, users, workarounds, outcome, MVP, and kill criteria before development begins. This surfaces real user needs and prevents wasted engineering effort.

Forcing questions in product discovery are a structured set of inquiries designed to surface concrete pain points, target users, existing workarounds, expected outcomes, minimal viable tests, and failure conditions. They challenge premises to ensure a proposed feature solves a real problem.

Generate a design document by capturing answers to product validation questions, logging pushback from challenging premises, and outlining implementation approaches. This produces a structured markdown record for team alignment.

Yes, after evaluating a feature idea through the discovery process, a concise summary of the validated product outcomes and recommendations can be posted directly to a Slack channel. This increases visibility for the team and stakeholders.

The best way to challenge product assumptions during ideation is applying a pushback protocol where a CEO or product manager challenges at least two premises. This surfaces evidence or reframes the problem before committing resources to development.

You should define kill criteria for a new MVP during the initial product discovery phase before committing development resources. Establishing failure conditions early ensures you know exactly when to stop pursuing a feature that is not achieving its expected outcomes.