The organisation chart arrives before the capability requirement.
Proposed roles and reporting lines can obscure the specific work, experience and proficiency the programme needs.
For Transformation / PMO
Make the workforce assumptions in your programme visible.
Connect milestones to the roles, competencies and timing they require. Give the programme team and HR a shared basis for reviewing the people workstream.
What you need to deliver
You own programme delivery and the dependencies between workstreams. A workforce plan needs to explain who could do the work, when they could start and which decisions are still outstanding.
What gets in the way
The delivery date is fixed. The staffing assumptions are not.
Internal capacity is assumed to be available.
People identified for a workstream may already be committed elsewhere. Release, backfill and transition timing need explicit review.
Workforce dependencies sit outside the programme view.
A development action, a hire and an external assignment have different owners and lead times. An unresolved step can affect the same milestone.
How EVA helps
Connect the workstream to a reviewed staffing option.
Structure the programme requirement.
Use EVA Workforce Planning to compare plan-linked demand or manager forecasts with available capability. Review the interpretation with the people accountable for delivery.
Compare options and constraints.
Review the available capability picture and use matching where appropriate. Keep evidence, availability and release dates attached to each option.
Coordinate the approved next steps.
Scope workflow for decisions, handovers and updates. Confirm ownership and the systems involved before enabling connected actions.
What you can take forward
A workforce workstream with dependencies people can own.
- Proposed requirements linked to the programme's work and timing.
- Staffing options with evidence gaps and release constraints visible.
- Named actions and review points for the programme and HR teams.
Explore the analysis
Analyses for the decisions you own.
Illustrative. Synthetic data.
Manager's Future Demand
Bring managers' future competency needs, timing and vacancy forecasts into one view.
Demand, urgency and scarcity analysis, forecast vacancies and development, movement or hiring options.
EVA Workforce Planning
Inputs and scope
Question: What capability will we need, when, and where might it be hard to find?
Inputs: Manager forecasts and assumptions, with current capability data for bench comparisons.
A manager-led forecast. Timing, population, current-capability inputs and any repeat cycle are agreed separately.
Plan-linked demand and direct manager forecasts provide complementary inputs. The illustrative candidate and mission-brief views do not execute programme approvals.
A decision in practice
A workstream is green on the plan but has no feasible staffing date.
Connect each critical requirement to a potential staffing response, earliest feasible start, unresolved release or development dependency and owner. Discuss the effect of a delayed move before treating the workstream as ready.
Illustrative decision brief, not a customer result or a standard product report.
Measures you can own
Establish a baseline, target and review period. These are evaluation measures, not promised improvements.
- Readiness at each gate
- Critical requirements with a reviewed staffing response and feasible timing.
- Dependency age
- How long release, evidence or approval questions remain unresolved and who can resolve them.
- Milestone impact
- Staffing dates against the programme plan, with changed assumptions made explicit.
A useful first step
Choose one milestone with an unresolved people dependency.
Bring the workstream plan and the populations in scope. Discuss EVA Workforce Planning for a snapshot or agreed recurring analysis, and EVA Full Automated & Approvals Platform for connected approvals and automation. EVA Competency Mapping can establish a missing baseline. Delivery scope is agreed around the programme.
Who to involve
Workstream owners confirm the work. HR and current managers review people options and release. Finance and technology teams confirm cost assumptions and connected-system requirements.
Which milestone is most exposed to a staffing assumption that nobody has yet confirmed?
Explore your decisions