Business change workforce planning should begin before delivery pressure exposes gaps between functions. A transformation programme can have a clear objective and still lose momentum when finance, HR and project delivery depend on the same small group of people at the same time.
For employers in Ireland, the practical task is to identify the decisions, dependencies and specialist responsibilities that sit behind the change plan. This creates a clearer basis for deciding what existing teams can absorb, where additional capability is needed and how long that support should remain in place.
Start with the outcomes and decisions
Translate the change programme into a short sequence of business outcomes. For each outcome, identify the decision that releases the next stage, the information required and the person with authority to decide.
The Department of the Taoiseach’s guidance on delivering policy is written for public service implementation. It is not a mandatory standard for private employers, but its planning questions are useful: specify the owner and sponsor, sequence the work, assign responsibilities, set realistic timelines and identify the critical path. The same guidance recommends reviewing the people, finance and supporting tools needed at each phase. Read the guidance.
Use these points as prompts rather than as a formula. The required governance and workforce model will depend on the organisation, the programme and any legal or regulatory obligations that apply.
Map the dependencies between functions
Finance, HR and project delivery often work to different calendars and controls. Build one view of the dependencies between them before translating the plan into role requests.
For each workstream, record:
- the output or decision required;
- the accountable owner and the specialist contributors;
- the information or approval needed from another function;
- the date by which that dependency must be resolved;
- the expected period of specialist support; and
- the consequence if the dependency moves.
This exercise can reveal requirements that a simple headcount plan will miss. A finance specialist may be needed around business-case changes, controls or reporting. HR capability may be required for organisation design, role definition, communications or onboarding. Project managers and business analysts may need to coordinate decisions, risks and delivery across several teams.
Confirm the map with the relevant functional leaders. It should reflect the organisation’s actual approval routes and responsibilities, not assumptions based on job titles.
Protect business-as-usual capacity
People assigned to change programmes often retain responsibilities in their usual role. Record that continuing workload when assessing capacity. A named workstream owner is not necessarily available for every review, workshop and decision the plan assigns to them.
For each critical contributor, compare programme demand with their existing commitments over the next eight to twelve weeks. This time horizon is a suggested management practice, not an external standard. Discuss conflicts early and choose an explicit response: move a milestone, reduce scope, backfill routine work or add specialist support.
Keep review and decision capacity visible as well as execution capacity. A programme can produce analysis and documentation faster than authorised owners can review it. Track work awaiting approval, unresolved cross-functional questions and decisions whose timing affects several workstreams.
Define authority, duration and handover
An effective specialist brief describes the work around the role. Set out the objective, expected outputs, decision boundaries, key interfaces, planned duration and review point. State who directs day-to-day work and who accepts or approves the output.
Duration should follow the work rather than a default contract period. Some needs are concentrated around design or mobilisation. Others continue through implementation, adoption and transition into business as usual.
Plan the handover at the start. Identify the internal owner, the records that must be maintained and the point at which knowledge transfer begins. Where the programme changes, review the brief and confirm any extension through the appropriate commercial process.
Choose the engagement model around the requirement
Once the organisation understands the work, authority and duration, it can choose an engagement model that fits the requirement.
Berkley’s Professional Service Engagements support long-tenure specialist teams within client programmes. Contingent Workforce Solutions support specialist contractor deployment. Specialist Placements cover individual requirements across professional services, business operations and technology disciplines.
The engagement name does not replace a clear operating model. Before support begins, confirm scope, reporting lines, access, onboarding, review arrangements and the people responsible for decisions. Our guide to choosing a workforce engagement model provides a wider framework for that discussion.
Bring one joined-up brief to the workforce discussion
Summarise the change outcomes, functional dependencies, current capacity, specialist gaps and next decision date on one page. Use it with finance, HR, project leadership and procurement so that each requirement is assessed in the context of the wider programme.
Berkley’s Business & Technology practice supports specialist capability across enterprise technology and project delivery, while Berkley’s wider Specialist Placements offering includes finance, HR and other business operations disciplines. Speak to our team about your workforce requirements.
