TechSoft
Playbook menu: Stage 2: Design

Delivery Playbook · Lifecycle

Stage 2: Design

Define what will be built, how it will be built and how it will be accepted.

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

Goal: Define what will be built, how, and how it will be accepted.

What happens

  • Architecture and integration design, with recorded decisions
  • Prioritized backlog with acceptance criteria
  • Prototype and usability check where users are involved
  • Test strategy, release plan and AI-use plan

What you receive

  • Architecture and ADRs
  • Backlog and roadmap
  • Prototypes and design specs
  • Test and release strategy
  • Security and data-handling plan

Quality checks

  • Architecture reviewed by the Tech Lead; key decisions recorded
  • Every story has testable acceptance criteria
  • Test, release and AI-use plan agreed

Approved before we move on

Architecture, scope for the first release and acceptance criteria approved by client and Tech Lead.

Who is involved

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

A typical Design, step by step

  1. 1

    Shape the solution

    Turn the problem statement into options and choose the smallest solution that achieves the outcome.

  2. 2

    Architecture and integration design

    Define components, data model, integrations, hosting and non-functional requirements. Record key decisions as ADRs.

  3. 3

    Backlog and acceptance criteria

    Break the scope into stories that each deliver value on their own. Each has testable acceptance criteria.

  4. 4

    Prototype and test with users

    Where users are involved, make clickable prototypes and test them before building.

  5. 5

    Test, release and AI-use plan

    Agree how the work will be tested and released, and which AI tools may be used on which parts.

  6. 6

    Approval

    Client and Tech Lead approve architecture, first-release scope and acceptance criteria.

= 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