office-hours

To validate a startup idea, you run a structured discovery session that surfaces demand signals and captures premises using a one-question-at-a-time flow. This process applies design-thinking to test your assumptions and produces a formal design doc for next steps.

A design doc is a formal plan capturing your Problem Statement, Demand Evidence, Target User, and Success Criteria. You need one during early-stage ideation or hackathons to evaluate if an idea is worth building and to align teammates or investors.

You structure brainstorming by applying six forcing questions covering demand reality, status quo, narrowest wedge, and future-fit. This one-question-at-a-time flow with stop-and-reflect cadence ensures rapid iteration and validates the core premise of your idea.

Yes, structured discovery works for hackathon projects by using Builder mode to quickly evaluate ideas. It guides you through design-thinking prompts to identify target users and success criteria, outputting a concrete design doc to guide your build.

The best way to document problem statements is through an automated design doc generated from a structured discovery session. It captures demand evidence and target users by systematically questioning your assumptions and drafting a formal plan.