Enterprise Software Rollouts Are Decided at Adoption

The rollout ships on time. The platform passes UAT. The cutover wave goes off without a critical bug. Three months later, the help-desk queue is full of “where did Z go?” tickets, the power users are hoarding tribal knowledge, and the CFO is asking why the projected ROI hasn’t shown up yet.

The technical rollout was the first half. The half nobody scopes is what the people on the floor actually do once the new system replaces the old one. Generic vendor training is supposed to fill that gap, and almost always doesn’t.

What “rollout” actually covers

Three classes, all the same shape on the inside:

• Net-new enterprise software. First ERP, first CRM, first document management system. Nobody has used it before because nobody has had it before.
• Platform migrations. Old system retired, new system live. The DocuShare-to-SharePoint cutovers we write about elsewhere are this shape. The work moves; the people stay.
• Major reconfigurations. Same vendor, new implementation. Tenant customized so heavily that the next person to open it might as well be on a different platform.

In all three, day one is the same: people whose work depends on a system are looking at a system they have not been trained on. The vendor’s training library, if there even is one, doesn’t help.

Why generic vendor training falls short

Vendors record against their reference tenant. Your tenant has custom fields, custom views, custom forms, custom validation rules, role-based UIs the vendor never designed for, and business processes built around your operation. When operators open the help section and find videos showing fields they don’t have, screens they don’t see, and terminology they don’t use, they close the tab.

Vendor training is for evaluators, not operators. It’s effective for the buying decision and unhelpful for daily work. The gap doesn’t get fixed by buying the platform; it gets fixed by recording training against the configured tenant: the one your team actually uses, with your fields and your workflows and your job titles on screen.

The handoff: how we deliver this as one engagement

We have been delivering custom training libraries alongside our engineering work for a while. Recently we paired with our sister studio Seismic Technologies, who specialize in this. The engagement model that works is a clean handoff between two specialists.

Akora hands over the brief. Because we built or migrated the system, we already own the architecture, the customizations, the role-based access model, the workflow specifics, and the cutover timeline. We package those into a brief: the same artifacts that drove the engineering work, plus an audience map by job function. Nothing in that brief is invented for the training scope. It is the engagement documentation we had already produced.

Seismic does the system analysis and the curriculum. They take the brief, walk the configured tenant end-to-end, and design a curriculum that is role-based and workflow-shaped, not feature-shaped. Each module is “how this person does their job on this system,” not “here are the buttons across the top of the screen.” The shape comes out of the audience map: an operator gets the operator’s modules; an admin gets the admin’s; an approver gets a short module on the approval flow they will be looking at on Monday morning.

Seismic returns a production-ready library. SCORM 1.2 and SCORM 2004 (4th Ed) packages ready to upload to the customer’s LMS. Per-language packages where the workforce is multilingual. Captions and transcripts shipped with every module, so the library passes accessibility audit on day one and search-indexes cleanly. Real footage of the customer’s actual configured tenant, not a vendor demo.

The customer engages once. No second procurement, no second statement of work, no integration friction between two vendors. The training library lands in the customer’s LMS the same week the system goes live.

What this has looked like in practice

Recently we delivered a forty-video training library alongside a multi-terabyte platform cutover. Role-based modules covering field operators, admin staff, records managers, and approvers. Each one watching the workflow they actually run, on the configured system they actually use. The customer asked for Microsoft Learn-style production: the polished, narration-led, motion-graphics treatment Microsoft uses for its own product training. That is what Seismic delivered. The library was in the customer’s LMS before the first cutover wave, so the pilot department had access to training at the moment they had access to the new system. (The engineering side of that engagement is its own case study; this is the part that made it stick.)

The pattern works the same for net-new rollouts and major reconfigurations. The only difference is that there is no “old system” to compare to, so the curriculum is shaped purely by what the person needs to be able to do on day one.

Two specialists, one engagement

Akora delivers the engineering. Seismic Technologies delivers the training library. Different work, different specialization, separate brands on purpose. The customer benefits from both, but each side is owned by people who do that work full time. The brief flows between us; the procurement and the SOW remain one document on the customer’s side.

If you are scoping a rollout where the platform side is locked in but the adoption side is the part that’s worrying you, that is exactly the gap this engagement is shaped to close. If your rollout has already shipped and only the adoption gap is what’s stuck, Seismic takes that work directly.