Why do the same mistakes repeat when lessons-learned sessions are held?

Because lessons are usually recorded as events rather than patterns. An event invites agreement and fades; a pattern can be named in a steering meeting, watched for through its early signal, and interrupted while interruption is still cheap.

Which pattern should a programme in trouble address first?

The decision-rights pattern, because it feeds the others. Data questions, testing trade-offs, and readiness calls all stall or drift when nobody holds clear authority to decide them.

How can a team tell a pattern is running before it does damage?

By its early signal: workshops ending with options, cleansing questions without owners, test plans that assume first-time passes, or training planned as a single event. Each signal is visible weeks before its cost arrives.

Is delaying a go-live ever the right call?

Yes, when the readiness evidence says so and the criteria were agreed in advance. A short planned delay is a governance decision; a date kept against the evidence transfers the cost to employees, support teams, and trust in the system.

HCM Implementation Mistakes

The failure patterns that repeat in HCM implementations — undefined scope, compressed testing, thin change — and how to break each one before design hardens it.

Adoption Metrics That Matter
Communication Planning for Go-Live
What Happens During an HCM Implementation?
HCM Implementation Cost

Site navigation

Karim Chaouki — AML and ADP Workforce Now Implementation Consultant

Senior Implementation Consultant. AML compliance, ADP Workforce Now HCM, payroll systems. PMP Certified. Bilingual EN/FR. Toronto, Canada.

About Karim Chaouki
Blog — AML & HCM Implementation Insights
AML Compliance Consulting
ADP Workforce Now Implementation US/CAN
Payroll Systems PM
Bilingual Implementation Manager