discovering

Clarifying vague project ideas requires gathering context first, then defining goals and scope. You can establish shared understanding by asking focused questions, proposing high-level approaches with trade-offs, and delivering a discovery brief for stakeholder sign-off before implementation.

A discovery brief is a concise document outlining project goals, constraints, recommended directions, and open questions. You need one when project scope is unclear, multiple interpretations exist among stakeholders, or alignment is required before technical work begins.

Defining project scope with unclear requirements involves gathering background context from stakeholders, docs, and code. By presenting 2-3 high-level directions with trade-offs and asking single focused questions, you can crystallize success criteria and finalize scope.

A guided decision flow resolves multiple stakeholder interpretations by asking one focused question at a time and proposing high-level directions with trade-offs. This context-first discovery approach establishes shared understanding and aligns goals before technical implementation.

The best way to gather context for project discovery involves collecting background from code, docs, and stakeholders. This context-first approach establishes a shared understanding, allowing you to define success criteria, propose directions, and deliver a concise brief for sign-off.

Project discovery needs stakeholder sign-off to ensure alignment on goals, constraints, and recommended directions before technical work begins. Delivering a discovery brief formalizes this agreement, preventing scope creep and conflicting interpretations during implementation.