# Analysis: Listen first

The most expensive mistake in any project is building the wrong thing well. So we start by listening.

## Obvious questions first

Who uses this? What should they be able to do? What’s broken today? What does success look like in a year? We ask the obvious questions because the obvious answers are often missing.

## Context, not just requirements

A feature list tells us what you want. Understanding your business, your users and your constraints tells us what you need. They’re not always the same thing.

## What you get

- A clear picture of goals, users and constraints
- An honest look at what exists today
- Risks and opportunities, named early
- A shared basis for every decision that follows

## Sometimes the answer is smaller

Sometimes the analysis shows you need less than you thought. We’ll tell you. That’s a good day, not a lost sale.