Enterprise Software Implementation

Who this is for

16 tasks for rolling out new software across an organisation — an ERP, a CRM, a helpdesk, anything where the hard part isn't installation but adoption. It covers requirements, vendor selection, configuration, data migration, training, go-live, and the support period afterwards.

Most of the risk is human

Enterprise software rarely fails technically. It fails because the people expected to use it weren't consulted, weren't trained, or were given a tool that's worse than their spreadsheet for the specific thing they do all day.

That's why the stakeholder and requirements tasks come first, and why they should involve the people doing the work rather than only the managers describing it. The gap between how a process is documented and how it's actually performed is where implementations die.

Configure for the process you have

The configuration tasks invite a choice: reshape the software to match your process, or reshape the process to match the software. Both are legitimate. Doing neither deliberately — customising heavily while also asking people to change how they work — is what produces expensive systems nobody trusts.

Heavy customisation also becomes a tax on every future upgrade, so be honest about which of your processes are genuinely differentiated and which are just habit.

Train close to go-live, then again after

Training delivered three weeks early is forgotten. Schedule the main sessions near the cutover, and plan a second round a fortnight later, when people have hit real questions and will actually listen.

Timing

Three to six months. Turn on due dates — the parallel-running and support tasks are time-boxed by nature, and slipping them quietly is how a rollout stalls.