Case study / Staffing Solutions
Eleven contractors, and no definition of done.
Capacity that had been contracted as individual monthly headcount was re-scoped into three bounded work packages and one dedicated pod — so that programme completion became a reportable figure, and the knowledge held by three individuals became documentation before any of them left.
- 5 weeks→8 days
- ramp to productive contribution
- 3 → 0
- single-person system dependencies
- 11 → 4
- separate engagements to manage
Situation
The context
Eleven contractors had been engaged individually across an eighteen-month grid-data programme, each on a rolling monthly basis. Three held knowledge of business-critical components that existed nowhere else, replacement ramp was averaging five weeks, and the programme could not state what proportion of its scope was complete.
Every individual engagement was performing. The programme still could not say how much of it was done.
The first task was not to replace anybody. It was to determine which parts of the work were genuinely deliverables with an edge, and which were continuing capacity — because those are two different things and both had been bought the same way.
Intervention
The intervention
The work was separated into what had an edge and what did not. Three bounded packages were scoped, priced and moved to Aevis delivery accountability; the continuing capacity became one dedicated pod with cross-cover written into its composition.
Shape
Deliverables separated from continuing capacity
Packages
Scope, acceptance criteria and price agreed before start
Dedicated pod
Standing capacity with cross-cover by design
Knowledge capture
Documentation as an acceptance condition
Delivery path
The dependencies were closed before anybody left.
Knowledge capture was sequenced first rather than treated as an exit activity, because the point at which somebody resigns is the point at which it can no longer be negotiated.
Weeks 01–03
Assess
Mapped the work against the four engagement shapes, identified which parts had a definable edge, and located the single-person dependencies.
Decision gateEngagement shapes agreed with the alternatives pricedWeeks 04–07
Package
Scoped and priced three work packages with acceptance criteria, and defined the pod’s composition, cross-cover and review points.
Decision gatePackage scope and pod composition approvedWeeks 06–14
Capture
Made documentation of the three critical components an acceptance condition on the first package, so it happened while the individuals concerned were still engaged.
Decision gateCritical-component documentation acceptedOngoing
Run and review
Delivered the packages against acceptance, ran the pod against agreed review points, and reported programme completion against accepted scope.
Decision gatePackage acceptance and periodic pod review
Operating shift
Nothing changed about the people. Everything changed about the contract.
The same individuals largely continued. What moved was where delivery risk sat and what the programme could state about itself. These are the practical shifts the case study is designed to make visible.
FromHeadcount by the month
→ToDeliverables with an edge
Three parts of the work turned out to have acceptance criteria, and pricing them that way moved delivery risk to the supplier.
FromProgress reported as effort
→ToCompletion reported as scope
Accepted packages gave the programme a denominator, which is what it had been missing rather than a reporting tool.
FromKnowledge in three people
→ToKnowledge in documentation
Capture was an acceptance condition on paid work, not an end-of-contract courtesy that competes with a handover deadline.
FromEleven engagements
→ToFour commercial relationships
Renewal, review and escalation became four conversations rather than eleven, without reducing the capacity available.
Evidence record
A result with its provenance attached.
The published story keeps the result, the supporting artefact and its limit together.
- 5 weeks→8 days
- ramp to productive contribution
- 3 → 0
- single-person system dependencies
- 11 → 4
- separate engagements to manage
Evidence attached
- Engagement-shape assessment with alternatives priced
- Work-package scope and acceptance criteria
- Critical-component documentation, accepted
- Pod composition, cross-cover and review record
Capabilities involved
- Work-package-based staffing
- Dedicated teams
- Technical screening and sourcing
- Onboarding and knowledge transfer
- Continuity and replacement cover
- Delivery governance
- Nature of the work
- No AI involved. Assisted matching was not used on this engagement; the existing individuals were retained rather than so
- Baseline
- Eleven individually contracted engagements, an average replacement ramp of five weeks, and three components whose operating knowledge existed in one person each.
- Data sources
- The client’s programme records, engagement contracts and onboarding logs, together with the assessment produced in the first phase.
- Human-control point
- Package scope and acceptance criteria were approved by the client’s programme director, who also accepted each package. Pod composition and review outcomes were agreed at the same forum.
- Technology used
- None specific to the result. The change was to the engagement structure and to where documentation was held.
- Measured result
- Ramp to productive contribution fell from five weeks to eight days as documentation accrued; the three single-person dependencies were closed; eleven engagements became four.
- Evaluation period
- The fourteen-week restructuring, plus two subsequent package cycles.
How to read these figures
Bring your context
Buying people by the month for work that has an edge?
Tell us what has to be true at the end and by when. The answer usually decides how it should be contracted, and it is often not how it is contracted now. We will be precise about which experience transfers.
- Response
- One working day, Monday to Friday