01Frame
Name the decision before opening the dataset.
We establish what someone needs to decide, what they know today and what prevents them from acting.
A decision worth solving for.THE FLODATA METHOD
Walk the problem.
Then build.
The first conversation starts with a blocked decision. The technology choice comes after we understand the work.
Bring us a problemFive steps.
One working relationship.
Try the Data Readiness Check ↗02Walk
The brief is a starting point. The work tells us more.
We inspect actual records and follow the workflow with the people responsible for it. The diagnostic exposes missing information and practical constraints.
[CONFIRM: paid diagnostic]03Shape
Build only what the decision needs.
We recommend an approach that fits the problem, including reusing existing systems or reducing the scope.
A scope that earns its place.04Build
Choose the tools after the problem is understood.
We engineer the required data flows and interfaces. Bespoke development runs through every service.
The engineering follows the evidence.05Stay
Keep the system useful as the work changes.
We monitor what is running and extend it as operational needs develop. Support commitments are agreed explicitly.
[CONFIRM: support hours and response commitment]01 / 05
WHAT TO BRING
A problem is enough.
Tell us the decision you need to make and where the information sits. A redacted example of the current workflow can help once we agree how to share it.
You do not need a technology specification. The Walk is where we examine the data and agree what is worth building.
Start with a private self-assessment ↗A GOOD PLACE TO START