The summary is the handoff between discovery and execution. If it is vague, the board and delivery work will be vague too.
What a good summary includes
A good summary usually captures:
- the primary target product or workflow surface
- who performs the work
- the parts of the current process people still rely on
- the pain points making replacement worthwhile
- the desired outcome and key constraints
What to challenge before you unlock
Pause and tighten the summary if any of these are still fuzzy:
- the workflow is too broad
- the owner is unclear
- the system of record boundary is missing
- the outcome sounds like a platform rewrite instead of a workflow replacement
When to move forward
Unlock the project only when the summary feels specific enough that another person could understand the work without replaying the whole chat transcript.
Once the summary is right, continue with Create your first project.