The smallest sensible fix
How a fix runs, from first call to support.
Understand enough to change things safely. Build only what earns its place. Check the result before doing more.
- 01
Show us the problem
A 30-minute screen-share beats a 30-page brief. Walk us through the real process, including its workarounds and awkward edges.
- 02
Follow the work
We trace where information starts, who touches it, which decisions matter, what goes wrong and what a good finish looks like.
- 03
Agree the measure
Together we agree what to measure, such as handling time, turnaround, errors, chasing, reporting delay, reliance on one person or days to get paid.
- 04
Choose the smallest fix
A form, a changed hand-off or a feature you already have may be enough. Where software is worth it, we define one clear job to build first.
- 05
Check it works
We test it on real work and compare the result with the agreed measure before doing anything more.
- 06
Host and support it
We can run, monitor and maintain what we build. You get documented dependencies, data you can export and a person to contact.
Check before doing more
Agree what better means before building.
A Faff Score can point to a likely problem. It can't prove a business case. For paid work, we look at the workflow and how it runs today, and the proposal sets out the measure we'll use.
Sometimes the right answer is not to build. A changed form, clearer owner, better template or feature you already pay for can be the smallest sensible solution.
What changes the figureNumber of systemsAPI availabilityData qualityException volumeSecurity requirementsInterface complexity