Skip to content

Idea Lab

Idea Lab is the chat-first entry point to product discovery in GrowthOS. Instead of opening a blank document, you describe a problem or opportunity in plain language and refine it with an AI assistant until the shape of a solution is clear.

Behind the chat, Idea Lab is building the raw material for a PRD: the problem statement, target users, constraints, and success criteria. When the conversation has enough substance, you generate a PRD draft that carries this context into PRD Studio.

Idea Lab is meant to be iterative and low-stakes. Nothing is locked until you finalize the PRD, so you can explore several angles on the same idea, discard dead ends, and only commit once the direction feels solid.

  • Start a new idea thread from a one-line problem statement.
  • Ask the assistant clarifying questions about scope, users, or risks.
  • Iterate on the same thread as your understanding of the problem evolves.
  • Generate a first-draft PRD once the conversation has enough detail.
  • Hand the draft to PRD Studio for structured editing and finalization.
  • Starting a brand-new initiative from a rough idea or customer signal.
  • Before committing to any backlog structure or sprint scope.
  • Exploring two or three different framings of the same opportunity before picking one.
  • A signed-in member account with product access.
  • A Planner seat to create or edit an idea thread; Viewer seats can read shared threads only.
  • Sidebar: Product → Idea Lab
  • Direct route: /product/idea-lab
  1. Open Product → Idea Lab (/product/idea-lab).
  2. Start a new idea thread and describe the customer problem and any known constraints.
  3. Iterate with the assistant: clarify scope, target users, and success metrics.
  4. Ask the assistant to challenge weak assumptions before you move on.
  5. Generate a PRD draft once the thread feels complete.
  6. Skim the generated sections for obvious gaps before leaving Idea Lab.
  7. Continue in PRD Studio to review, edit, and finalize.
  • The thread contains a clear problem statement, target users, and a rough success metric.
  • A generated PRD draft exists and roughly matches what you discussed.
  • You feel comfortable handing the draft to PRD Studio without starting over.
  • Be specific about users and non-goals; sharper prompts produce sharper PRDs.
  • Ask the assistant to list risks or open questions before generating the PRD draft.
  • Keep one thread per idea rather than mixing unrelated problems in the same conversation.
  • Generating a PRD too early, before the problem and users are clearly described.
  • Treating the first generated draft as final instead of reviewing it in PRD Studio.
  • Mixing several unrelated ideas into one thread, which confuses the generated PRD scope.