Fox & SantiagoTechnology, applied.Call (877) 244-9687

Answer

What happens if the crew does not use the tool?

We build so that does not happen. The crew is interviewed in the Spec, and the adoption design names who uses the tool and when. The Build is tested with that named crew before go-live, 30 days of stabilization after launch fix whatever gets in their way, and Embedded Adoption keeps improving it. You can see the tool's use in your own workspace the whole time.

It starts with the people who use it

Most tools go unused because they were designed somewhere other than where the work happens. We start on the floor. The Workflow Spec includes interviews with the people in the workflow, so the tool is built around how the work actually runs, and the people who use it are the people who asked for it.

The Spec also includes an adoption design. It names who uses the tool and when, so the rollout is planned around real people, not a job title.

Tested with the named crew before go-live

The Build is not finished at a demo. Before go-live it is tested with the named crew, and what gets in their way is fixed before launch. Release means the agreed production environment with the agreed user group, not a test site.

30 days of stabilization, then the next issue

The first 30 days after launch are stabilization, included in the Build. We stay close to the crew and fix whatever slows them down. You can see the tool's use in your own workspace throughout, so nobody has to guess how it is going.

After that, Embedded Adoption keeps going: the next issue on the list, fixed every month, with monitoring, business-hours support and a weekly operator review.

Why we work this way

A tool that works but sits unused fixes nothing. The WERCS case shows it: the tools that got used were the ones that each fixed one daily job. That is why every engagement starts with the crew that will use the tool, and why we keep working with them after launch.

Questions people ask

Who decides what the tool does?

The people who will use it. The Spec interviews the people in the workflow, on the floor, so the tool is built around how the work actually runs.

Does the crew see the tool before it goes live?

Yes. The Build is tested with the named crew before go-live, and what they find gets fixed before launch.

Can we see whether the crew is using it?

Yes. Use of the tool is visible to you in your workspace, from the first day it is live.

What happens after the first 30 days?

Embedded Adoption takes on the next issue every month, with monitoring, support and a weekly operator review.