Delivery Playbook · Lifecycle
Stage 1: Discover
Agree the problem, the baseline and the desired outcome before committing to a solution.
Goal: Agree the problem, the baseline and the desired outcome.
Activities
- Stakeholder interviews and workshops
- Review of existing systems, data and constraints
- Baseline measures (time, cost, error rate, release frequency)
- Initial risk, security and compliance screening
Artifacts
- Problem statement and success measures
- Current-state map
- Risk register
- Proposed engagement model
Exit criteria
Customer sponsor agrees the problem statement, success measures and next step.
Who is involved
- Customer Sponsor · leads
- Engagement Manager · leads
- Delivery Lead
- Business Analyst · leads
- UX/UI Designer
- Tech Lead / Architect
- Software Engineers
- QA / Test Automation
- DevOps / Platform
- Security & Compliance
- AI / Data Engineer
- Support & Operations
A typical Discover, step by step
- 1
Kickoff
Introduce roles, agree communication channels, working hours, the AI-use policy and how decisions are made.
- 2
Stakeholder interviews and workshops
Hear from sponsors, users and operators. Capture the problem in their words, then restate it.
- 3
System and data review
Inspect existing systems, integrations, data quality, hosting, access and constraints. Read the code if there is existing code.
- 4
Baseline
Record today's numbers: cycle times, error rates, costs, release frequency, support volume. Without a baseline there is no outcome.
- 5
Risk, security and compliance screening
Spot sensitive data, regulatory limits and outside dependencies early.
- 6
Playback
Present the problem statement, baseline, options and a recommended next step to the sponsor for agreement.
Questions we always ask
- What outcome would make this engagement a success, and how will we measure it?
- Who uses the system today, and what do they do when it fails?
- What must not break?
- What constraints exist: budget, dates, regulations, technology, people?
- Who can make decisions, and how quickly?
Related
Lifecycle
Stage 2: Design
Define what will be built, how it will be built and how it will be accepted.
Roles
Product and design roles
Business Analyst and UX/UI Designer: turning needs into clear requirements and usable interfaces.
Governance
Metrics and reporting
What we measure, how we report it, and how the numbers lead to decisions.