Shape it before selection
The delivery profile, the tranches and the risk concentration are decided before a vendor is in the room. Reversing those decisions later is the expensive part.
Independent field service transformation
Advice and assurance for large field service operations, from practitioners who have sat on every side of the table: supplier, customer and systems integrator.
The problem
Most digital transformations do not deliver what was promised. In field service the failure pattern is specific, and it repeats: a big bang replacement, a single go live carrying every benefit in the business case, and a dispersed workforce asked to change everything at once.
Platform selection gets the attention. Delivery shape decides the outcome.
How we work
We hold working relationships across the major field service platforms and take commission from none of them. That is what makes it possible to shape a delivery before the platform is chosen, and to govern it honestly once it is in flight.
The delivery profile, the tranches and the risk concentration are decided before a vendor is in the room. Reversing those decisions later is the expensive part.
Benefit arrives in increments that each stand on their own, with legacy kept as a bridge rather than switched off on a date.
Independent assurance across the programme, so the picture reaching the board is the same one the field would recognise.
The methodology
Four disciplines, with assurance running through all of them. Value Recognition is the engagement layer: it establishes what value means here before anything is sequenced. The three below it carry the work.
What value means for this organisation, what it is worth, and which objective the programme is actually optimising for.
Sequencing and delivery, in tranches that each stand alone.
Change that lands with a dispersed workforce, not just a launch.
Benefit measured where it shows up, in what engineers do differently.
The assurance spine. It runs across Release, Adoption and Realisation rather than sitting after them, because risk does not wait for a stage gate.
Written in full on first mention as the ThriveFSM Value Operating System (ThriveFSM VOS), then the VOS. Spoken "voss".
The model
Sequencing is weighted across three lenses: benefit unlock, dependency load and adoption load. You set the weighting, because the right answer depends on what you are optimising for. Change the objective, or change the conditions on the ground, and the sequence changes with it.
| Optimise for | What it buys | What it costs |
|---|---|---|
| Payback | The highest benefit tranches move first, so the business case pays back sooner. | More dependency carried early, and a heavier change load on the field up front. |
| Cost | Fewer parallel workstreams and less duplicate running, so total programme cost falls. | A longer road to full benefit, and a longer period of living with legacy. |
| Continuity | Service risk stays lowest throughout, with the field changing in the smallest viable steps. | Slower realisation, and a business case that has to be defended for longer. |
None of these is the right answer in general. The point of holding one model is that the trade off is explicit, and that it can be re-run when the objective or the conditions move.
Services
Where the operation is going, what it has to become, and which capabilities carry the value. Done before procurement, so the requirement reflects the operating model rather than the incumbent.
Vendor-independent evaluation against a delivery shape that has already been decided, with the commercial and risk terms that follow from it.
Tranche design, dependency and adoption load, and independent assurance in flight. The work that keeps a go live from carrying every risk at once.
Change built for lone and dispersed workers, and measurement of benefit where it actually appears rather than at the point of handover.
Products
The VOS began as a way of working. It is turning into a set of products that do the same job continuously, rather than only at the points where we are in the room. Everything under the ThriveFSM banner is about one thing: the evolution and transformation of field service organisations.
The model itself, as a tool. Set the weighting across benefit unlock, dependency load and adoption load, and see the sequence it produces along with the trade off it carries. Re-run it when conditions change instead of rebuilding the plan.
One call for a scheduling engine. Live street works permits, road closures, traffic management and weather, resolved to a site and a time window, so the schedule is built against the condition of the network rather than in spite of it.
Who it is for
Who we are
Not twelve juniors, billed by the month. A bench of people who have run these programmes from the supplier side, the customer side and the integrator side, with tooling that lets a small team carry work that normally needs a large one.
Start a conversation
If any of this sounds like the programme you are holding, it is worth a conversation.
No pitch deck required. Tell us what is in front of you and we will tell you honestly whether we are the right people for it.
hello@thrivefsm.com
ThriveFSM is a trading name of Thri5 Project Consulting Ltd, registered in England and Wales, company number 11188445.
Registered office: Ground Floor Dearing House, 1 Young Street, Broomhall, Sheffield, South Yorkshire, S1 4UP, United Kingdom.
The ThriveFSM Value Operating System and its supporting framework are proprietary to Thri5 Project Consulting Ltd.