TechSoft
Playbook menu: Stage 1: Discover

Delivery Playbook · Lifecycle

Stage 1: Discover

Agree the problem, the baseline and the desired outcome before committing to a solution.

Owner: Delivery Manager · Last reviewed: · Next review: 28 April 2027

Goal: Agree the problem, the baseline and the desired outcome.

What happens

  • 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

What you receive

  • Problem statement and success measures
  • Current-state map
  • Risk register
  • Proposed engagement model

Quality checks

  • Problem statement and success measures read back to the client
  • Baseline numbers recorded, not estimated
  • Security, data and compliance screening done

Approved before we move on

The Client Sponsor agrees the problem statement, success measures and next step.

Who is involved

  • Client Sponsor · leads
  • Delivery Manager · leads
  • UX/UI Designer
  • Tech Lead / Architect
  • Software Engineers
  • QA / Test Automation
  • DevOps / Platform
  • CTO
  • Support & Operations

A typical Discover, step by step

  1. 1

    Kickoff

    Introduce everyone's role. Agree how we communicate, our working hours, the AI-use policy and how decisions are made.

  2. 2

    Stakeholder interviews and workshops

    Talk to the Client Sponsor, users and operators. Write down the problem in their words, then say it back to them.

  3. 3

    System and data review

    Inspect existing systems, integrations, data quality, hosting, access and constraints. Read the code if there is existing code.

  4. 4

    Baseline

    Record today's numbers: cycle times, error rates, costs, release frequency, support volume. Without a baseline there is no outcome.

  5. 5

    Risk, security and compliance screening

    Spot sensitive data, regulatory limits and outside dependencies early.

  6. 6

    Playback

    Present the problem statement, baseline, options and our recommended next step to the Client 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?

= milestone agreed with the client

  1. 01

    Discover

    Problem and baseline

  2. 02

    Design

    Architecture and scope

  3. 03

    Build with AI

    Reviewed increments

  4. 04

    Verify

    Gates and acceptance

  5. 05

    Operate & improve

    Monitor and learn

Measure outcomes, learn, and feed the next increment
Each stage ends with a milestone agreed with the client. What we learn in Operate feeds the next round of Discover.

Related