Clarity Engineering / Phase 02

Definethe System

What should exist, and how does it change?
Discuss your project

The purpose

Understand the people, the pressure and the problem before deciding what to make.

A feature request is a starting point for a conversation. We look for the business need behind it.

In practice

What we work through.

  1. 01

    Listen to the people involved

    Agree who the system serves, what it needs to do and what sits outside the scope.

  2. 02

    Make the relationships visible

    Map the journeys, information and dependencies that connect the experience.

  3. 03

    Agree a first useful release

    Set priorities and acceptance criteria so everyone can recognise when the work is ready.

What you leave with

Something the teamcan use.

Typical outputs are agreed around your scope.

  • A system brief
  • A prioritised scope
  • A release plan and acceptance criteria

Your next chapter starts here

Have a goodfeeling about this?

hello@ghostsavvy.com
Let’s talk