Insights

The Cost of Starting Too Late: HCM Project Leadership

September 16, 2026

The Cost of Starting Too Late: HCM Project Leadership

When should you bring in a project manager?

THE DIRECT ANSWER

Bring in specialised HCM or payroll project management expertise before you sign a vendor contract, not after. A generalist PM and a specialist payroll/WFM PM are not interchangeable – knowing where these projects typically go wrong is what protects your budget, timeline and outcome before commitments are locked in.

Why timing changes the outcome

There is a familiar sequence in HR and payroll technology projects. The organisation agrees that change is needed, develops a business case, selects a platform, negotiates a contract and announces a target date. Only then does someone ask who will manage the project.

At that point, the project manager is not stepping into a blank canvas. They are inheriting a budget, scope, timeline and set of supplier commitments that may already be difficult to deliver. The decisions with the greatest influence on the outcome have often been made before the person accountable for delivery has entered the room.

If you are considering a Human Capital Management (HCM), payroll or workforce management implementation, the question is not whether you will eventually need project leadership. It is whether you can afford to make the early decisions without it.

The ready trap

Delaying the appointment of a project manager until the project has commenced is something we see often. Until a platform has been selected and the scope approved, leadership often regard the work as exploration rather than a project that needs to be managed. Formal project management during the budgetary and scoping phases historically has been viewed by organisations as premature or like an avoidable cost.

In reality, this is the stage when delivery risk is being created. Early estimates become approved budgets. Indicative dates become public commitments. Vendor assumptions become contractual obligations. Business teams agree to contribute resources without a clear view of the time or capability required.

When these assumptions are not tested by a project manager with implementation experience, they do not disappear. They travel into the project and become constraints the delivery team must manage.

This is established project practice

The case for early involvement is not unique to payroll or HCM. The Project Management Institute has described the value of a strategic front end to the project lifecycle and the risk of asking project managers to deliver solutions, dates and budgets they had little or no role in developing. It identifies business case preparation, financial analysis and evaluation of solution options as areas where project management expertise can add value before formal delivery begins.

The same principle is visible in HCM implementation practice. In a published Workday transition case study, a utilities organisation engaged experienced project management and subject matter expertise while it was still finalising its request for proposal and selecting an implementation vendor. That early involvement helped shape and negotiate the statement of work, clarify responsibilities and address risks before they became delivery issues.

The message is consistent: involving delivery expertise early is not extra administration. It is how organisations make better commitments from day one, which ultimately leads to more favourable and improved post go live successful outcomes.

Specialised HCM/payroll expertise, not generalist project management

This is not simply project management one-o-one. It is specialised HCM, payroll or workforce management (WFM) project management, and that difference is the key one.

Knowing the critical stages of a project and, more importantly, where they tend to go wrong, is something an experienced payroll or WFM project manager brings over and above a project manager without that specialist skillset. Award interpretation, pay run cut-offs, parallel testing, data migration risk and the operational reality of a live payroll calendar are specific to this domain. A generalist PM can run a disciplined process; a specialist payroll/WFM PM knows which parts of that process carry the greatest risk of failure, and why.

What waiting costs

The business case understates the real effort. The benefits of a new platform are usually easy to describe. The work required to realise those benefits is harder to quantify. Data cleansing, integrations, award interpretation, testing, change management, training and operational backfill can be underestimated or excluded. The result is a business case built on a number that was never truly achievable.

The contract embeds assumptions that favour delivery simplicity. A vendor statement of work is not the same as a complete client delivery plan. If testing cycles, data ownership, integrations, change control and acceptance criteria are unclear before signature, those gaps can become delays, variations or disputes later.

Resourcing is promised rather than planned. The phrase ‘the team can absorb it’ is often accepted without testing what it means. Payroll and HR subject matter experts still have a day job, and the greatest project demand often coincides with critical operational periods. Without early capacity planning, the organisation discovers the conflict only when decisions, testing or data preparation begin to slip.

Governance is added after it is needed. Decision rights, escalation paths, reporting cadence and scope controls should exist before pressure builds. When governance is improvised after the first disagreement, the project is already spending time and trust that could have been protected.

What early project leadership changes

An experienced project manager or client-side delivery partner brings an implementation lens to decisions while they are still inexpensive to change. They can pressure-test the business case, assess whether the timeline reflects the actual work, identify internal capability gaps and establish the governance needed to resolve issues quickly.

They also strengthen vendor selection and contracting. Commercial and legal review remains essential, but delivery review asks different questions: Who owns the data? How many test cycles are included? What is the process for defects and change requests? Which integrations sit inside or outside scope? What must the client provide, and when? What assumptions could affect cost or schedule?

Early involvement does not require a large project office or a lengthy engagement. The value comes from applying the right expertise at a small number of high-impact moments: business case development, procurement, scope definition, contract review, resource planning and governance design.

Five questions to ask before signing

Has the proposed timeline been tested against payroll cycles, peak periods and the availability of key subject matter experts?
Does the budget include the internal effort required for data, testing, change, training and operational backfill?
Are vendor and client responsibilities clear enough that each deliverable has an accountable owner?
Does the statement of work define testing cycles, acceptance criteria, change control and what happens when assumptions prove incorrect?
Is there a governance structure with clear decision rights and escalation paths from day one?

Frequently asked questions

When should you bring in a project manager for an HCM or payroll implementation?

Before the vendor contract is signed, ideally while the business case is being built, vendors are being evaluated and scope is being defined. This is when the budget, timeline and vendor commitments are still open to change.

What happens if we wait until closer to go-live to add project leadership?

The budget, contract terms and timeline are already fixed. A project manager can still improve delivery from that point, but many of the strongest levers for protecting cost, scope and timeline have already been used.

Does early involvement mean setting up a large project office?

No. Early value comes from applying the right expertise at a small number of high-impact moments: business case development, procurement, scope definition, contract review, resource planning and governance design.

What does a delivery-focused contract review check that commercial or legal review might miss?

Data ownership, the number of test cycles included, the process for defects and change requests, which integrations sit inside or outside scope, what the client must provide and when, and any assumptions that could affect cost or schedule.

Why does this need to be a specialist project manager rather than a generalist?

Because knowing where HCM and payroll projects typically go wrong – award interpretation, pay run cut-offs, parallel testing, data migration, is a specific skillset. An experienced payroll or WFM project manager brings this over and above a generalist PM without that background.

What is the better question to ask instead of ‘when do we need a project manager’?

Ask, ‘What decisions are we about to make that would benefit from delivery expertise?’ If you are building a business case, evaluating vendors, negotiating a statement of work or setting an implementation date, the answer is now.

Next steps

Planning an HCM, payroll or workforce management change? We provide independent advisory, client-side specialised HCM and payroll project management, program governance and quality assurance, from early planning through to go-live and optimisation. Practical involvement early is what protects the budget, timeline and outcome you’re working towards. Start the conversation with our team today, before your project starts.