Discovery Workflow
Owner: Delivery lead Status: draft Audience: commercial and delivery teams Related: Engagement Models, Approval Matrix
Purpose
Scope the client problem, identify the owner, define success, and confirm what the first live workflow should be.
Trigger
Run this workflow when a prospect or client has a credible operating problem and Nucleotto needs to decide what the first live workflow should be.
Inputs
- commercial context and buyer goals
- current workflow bottleneck
- systems touched by the workflow
- owner for approvals and success criteria
Standard sequence
- define the operating problem in concrete workflow terms
- identify the owner and the decision path
- map the systems, handoffs, and constraints involved
- define the first visible output that matters
- confirm what a pilot would need to prove
Outputs
- scoped target workflow
- named owner
- success definition
- recommended pilot starting point
QA checks
- scope is tied to one concrete workflow
- success is measurable
- the owner is explicit
- the first visible output is clear enough to judge in a pilot
Failure modes
- treating discovery like a product demo
- leaving ownership vague
- scoping too broadly for the first pilot
- pitching software instead of operating capacity