How we workA four-stage method you can read at every step
A method is only worth anything if, at any moment, you can answer three questions: where the project stands, what has been decided and what is waiting on you. The sequence below applies equally to a consulting engagement, a software build or a brand overhaul, with different deliverables but the same demand for visibility.
The four stages of a project
-
Understand
We meet the people affected by the subject, not only those who commissioned it: leadership, but also the teams who live with the problem every day. We go through the existing documents, figures and tools.
-
Design
We compare several possible answers, including the one that involves doing less, or using a tool you already have. Each option is weighed by cost, timing, risk and what it asks of your teams.
-
Build
Work moves in short batches. Each batch ends in something observable: a clickable prototype, a testable version, a finished asset, a recommendation ready to apply.
-
Improve
Once the deliverable is in service, we watch how it is really used: what gets used, what gets worked around, what raises questions. The indicators set during scoping are reviewed with you.
What we commit toWhat stays the same from one project to the next
Decisions are written down and dated. Disagreements are voiced before they are settled. Communication is direct, with no intermediary between you and the work. When your project spans several areas of expertise, you keep a single point of contact, responsible for the whole, and continuous follow-up from one stage to the next.
Go furtherPutting the method into practice
Let’s bring your projects to lifeYour next project starts here.
Want to know how this sequence would play out on your project? Describe it to us.