Make-It-Stick Guide.

Confirm, a while after adoption, that the technology is actually used as intended and delivering the benefit you bought it for, and fix, retrain, or drop it if not.

After adoption, and periodically.

Confirm it is used and helping

Are people using it as intended, for the real work?

Is it actually making the work better, faster, cleaner, more reliable?

If not, why? Name the real blocker: too hard, not trained, does not fit the workflow, missing a feature

Fix, retrain, or cut losses

If it is a training gap: retrain and support. If it is a fit or setup problem: adjust the configuration or the workflow

If the tool genuinely does not serve the work: be willing to stop paying for it. Protecting a bad purchase because it was expensive is how the loss grows

Where a tool problem keeps recurring, put it in your Problem and Idea Log so it gets worked properly

A tool is worth only what it is used for. The honest test is not whether you bought it but whether the work is genuinely better because of it. Where it is, protect the adoption; where it is not, fix the cause or move on without sentiment.

Your answers stay in your browser on this page and are never sent anywhere. Use Save or print to keep your copy.

Back to Get the Right Technology in Place, or start over from the welcome page.