Your move
List every production gap
Make access, data, errors, deployment, evidence, support, and ownership visible work.
Compare the prototype with the real journey and expose the missing work. Group gaps by user experience, data, access, failure handling, security, deployment, observability, support, and ownership.
Do this now
Three moves, in order.
- Walk every journey state against the product as it exists now.
- Record the evidence that a capability works or the gap that blocks it.
- Prioritize by consequence and dependency, not by how interesting the code is.
Build the artifact
Production gap list
Copy these fields into a note, document, or sheet you already use.
Journey state
Where the user is
Current evidence
What works today and how you know
Gap
Missing behavior, control, or owner
Consequence
What happens if it stays missing
Dependency
What must exist first
Give AI the bounded job
Prompt from your artifact—not from vibes.
Audit this prototype against the journey and evidence I provide. Create a production-gap list. Do not infer that a feature works because code or a UI exists; require a demonstration or test receipt.
Before you use it
The work leaves your hands only when:
- Every gap maps to a user state or operating need.
- Existing capabilities have evidence.
- Security, data, support, and recovery are included.