How a multi-year MSP approach succeeded in three iterations - why phasing with measurable building blocks works
Client
International technology and consumer electronics group
Role
Program and Supply Chain Manager / Project Leader
A best practice about a multi-year MSP transformation in which we evolved from baseline transparency to a total blended workforce solution. This story complements the original case with the organisational lessons: not only what we did, but why the iterative approach worked and what others can take from it who face a similar scalability question.
A multi-year partnership rarely starts with the final solution. At the start of this collaboration, the end goal - a total blended workforce solution in which permanent and contingent workforce are steered within one strategic framework - wasn't even feasible to make concrete. What was possible: get a first, narrower ambition clear (transparency and control) and shape an approach together that kept future steps open without pinning them down now.
Three iterations spread over four years - MSP 1.0, 2.0 and 3.0 - let the collaboration grow from transactional to strategic. Every version solved the problems the previous one had made visible. And every version built the capacity to deliver the next.
MSP 1.0 (2011) focused on foundation: transparency and control. What did we spend? To whom? Under what conditions? By configuring a Vendor Management System, streamlining processes and building in KPI reporting, a hidden cost structure became visible.
MSP 2.0 (2012-2013) built on quality and cost savings. With a rate card structure, supplier performance management, broker implementation and compliance management, €300,000 structural savings were achieved - not by spending less, but by buying more cleverly.
MSP 3.0 (2014) lifted the collaboration to the strategic level. One framework for all delivery divisions, one strategic partner as single point of contact, integrated approach for permanent and contingent workforce. The relationship went from supplier-client to partnership.
Phase, don't chase perfection. Every version had a sharp and standalone goal. We didn't try to solve everything in MSP 1.0. The success of 1.0 enabled 2.0; the success of 2.0 enabled 3.0.
Build measurability from the first version. KPI reporting and a workable VMS were part of MSP 1.0, not of a later phase. That way we could demonstrate impact from day one and substantiate the business case for the next step.
Stand strong operationally before you go strategic. Only when orders, invoices and KPIs ran predictably did room open for the strategic conversation on total talent. Being a strategic partner is only credible when the operational base runs smoothly.
Stakeholder alignment as a continuous stream of work. Change management, training and relationship management with hiring managers and suppliers were not set up as standalone projects, but as recurring parts of every iteration. What was a training in 1.0 became an improvement session in 2.0 and a strategic session in 3.0.
Directly measurable: €300,000 structural cost savings, higher candidate quality, shorter lead times and higher satisfaction with hiring managers and suppliers. But the real win was in the system effect: one strategic partner instead of many suppliers, one framework for all divisions instead of fragmented approaches, and one strategic dialogue on total workforce instead of isolated hiring decisions.
The client organisation thus gained not only more grip on hiring, but a structurally different way of thinking about talent: permanent versus flexible was no longer determined by contract, but by value and strategic position.
Plan the iterations, not the destination. The end state (total blended workforce) was not concretely designable at the start of MSP 1.0. Through iterations with sharp intermediate goals, the end state could gradually take shape, without committing in year one to a detailed year-four plan.
Make value measurable from day one. An MSP approach only convinces when business impact is visible. So don't start with technology or processes, but with the KPIs against which the collaboration will be judged.
Build strategic trust through operational execution. Becoming a strategic partner only works when the operational base runs smoothly. Start transactional, end strategic.
In short: in a multi-year partnership, the right order matters more than the right end plan. Those who make every phase valuable in itself while building capacity for the next, build results that last.