How we work

Map it. Explain it. Do it. Prove it.

Four steps, the same on every engagement, whichever offerings you choose. The first conversation is free.

Four steps, start to after go-live

  1. 01

    Map it

    Discovery, scope and SOW.

    What we do
    A free 30-minute discovery consultation, then we map what is changing, who it affects and when it goes live, and recommend the offerings that fit.
    What you get
    A Statement of Work setting out the deliverables, review rounds, hosting, data handling, rollout approach and schedule. Production starts only after it is signed.
    What we need from your team
    A sponsor and a process owner for the discovery call, and whatever already exists: the rollout plan, SOPs, screens or site photos.
  2. 02

    Explain it

    Scripts, storyboards, films.

    What we do
    We write the scripts, storyboard the message and make the films, with a realistic presenter, animated, or both.
    What you get
    Approved scripts and storyboards, then the finished films in the styles and languages agreed in the SOW.
    What we need from your team
    The key messages from your sponsor, one reviewer per round, and consent from any leader shown as a presenter.
  3. 03

    Do it

    Build, review, pilot.

    What we do
    We build the hands-on practice in a recreated version of your screens or site, on synthetic data, never your live system.
    What you get
    A working Practice, Preview or Simulate build, two structured review rounds and a pilot with a test group.
    What we need from your team
    SOPs and the new system’s screens or a test environment, an IT contact for hosting and sign-in, reviewers and a test group.
  4. 04

    Prove it

    Rollout, readiness, after go-live.

    What we do
    We roll out the way you choose: all sites at once, a pilot site first, or in waves, and support you through go-live and after.
    What you get
    The readiness heat map by site and job, the roster and access codes set up, and updates for new hires and every revision.
    What we need from your team
    The roster, site leads who use the heat map in their huddles, and one contact for changes after go-live.

The kinds of change we help with

Present and Animate explain the change; Practice, Preview and Simulate let people do the new work before go-live.

ERP implementations

System migrations, redesigned workflows, cross-functional impacts and go-live readiness, including acquisitions moving onto one system.

Typical audiences: Operations, finance, supply chain, IT, leadership

Master data management

Data ownership, governance, golden records, system dependencies, interfaces, standards and process changes.

Typical audiences: Data teams, IT, operations, finance, leadership

AI and automation rollouts

New assistants, automated workflows, changed responsibilities and what adoption looks like day to day.

Typical audiences: Leadership, operations, customer service, IT, company-wide teams

Warehouse and operations

New picking, routing, scanning, production and inventory workflows, on the floor and on the device.

Typical audiences: Warehouse teams, operations, supply chain, supervisors

Supply chain transformation

Planning, procurement, inventory, logistics, fulfillment and network changes.

Typical audiences: Supply chain, procurement, operations, finance, leadership

Change and executive communications

What is changing, why it matters, when it happens and what people need to do, from town halls to steering committees.

Typical audiences: Executives, sponsors, managers, company-wide teams

Which hands-on build fits?

QuestionPracticeCoached practicePreviewOld way, new waySimulateDigital twin
Best whenPeople are learning a new system taskThe old way is being replaced: a green screen, an older ERP, spreadsheets, paper or an acquired companyThe work happens on a floor with devices
What employees doDo the task in the new system with a coachDo the task the old way and the new way, side by sideWalk a 3D twin of the site and follow the SOP on the device
ExampleRaise a purchase requisition in ACME OneMove an order desk from the old way to ACME One, or an acquired company onto yoursCount stock on a handheld in an ACME distribution center
Add-ons—Translate (look-up view) · Change Map (admin view)Drill: an outage, a mock recall and more

Every Practice, Preview and Simulate build comes with the same readiness heat map: who is ready, by site and job, before go-live and after.

Before we build

Key considerations

What we agree with you before we build, so the trainer fits your IT, your people and your rollout.

Hosting and sign-in

We host your trainer on a private link, and employees sign in with their employee number, so there are no new passwords. If your IT team prefers, we deliver a self-contained package for your intranet or learning system instead, and results stay in your systems. Single sign-on can be scoped in the SOW.

Data, privacy and AI

Built on synthetic data in a recreated version of your screens, never connected to your live system. Leaders see results by site and role, groups under five people are merged, and names are visible only to the admins you choose. The dashboard answers plain questions with built-in logic; if you connect your own AI service, it only ever receives an anonymous summary.

Your team's involvement

  • Process owner or subject-matter expert: walks us through the real task, shares SOPs and screens, answers questions during design and build.
  • IT contact: hosting, sign-in and a security review.
  • Site leads: the roster, the test group, and using the dashboard in site huddles.
  • Reviewers: two structured review rounds and final sign-off.

Rollout

You choose: all sites at once, a pilot site first, or in waves. We agree on it in the SOW and set up the roster, access codes, site posters and dashboard to match.

Devices and languages

Practice and Preview run in a current browser on a laptop or desktop; Simulate needs a desktop browser with 3D graphics, or a recent tablet. The leadership dashboard works on any device. Language versions and accessibility needs are scoped up front.

What we need from you

Your SOPs and the new system's screens or a test environment. Preview also needs today's screens and steps; Simulate needs floor plans, photos or a walkthrough of the site and the devices your teams use.

All of this is written into your Statement of Work.