Technology
Smartsheet adoption and enablement

The part everyone else calls step four. Named, priced and run alongside the build, because adoption added at the end is just training with a better name.
Why you'd want this
A technically fine rollout, a launch email, a lunchtime training session, and then a slow drift back to the spreadsheet everyone already knew. Nobody refused. They just quietly stopped.
Adoption comes down to ownership, rhythm and whether leaders behave as though the new way is the real way, so we run it as its own piece of work alongside the build. If people need a course to use the thing, the design was wrong. We'd rather fix the design.
Where we support
Adoption runs alongside the build.
- Super users, chosen properly. The people each team already asks when they're stuck, given the time and the standing to actually help.
- The operating rhythm. We design the meetings, the reviews and the cadence the tool has to sit inside, because a dashboard nobody looks at on a Tuesday is just a picture.
- Leadership alignment. We get your executive team asking for the report from the new place and declining the old one, which does more for adoption than any communications plan.
How it will benefit you
The difference between people using it and people having heard about it.
- People use it because it's easier than the workaround. Which is the only definition of adoption worth having.
- You stop paying for a tool nobody opens. Licences you aren't using are the most expensive line in any platform.
- You're not reliant on one person. The knowledge sits across a group rather than in the head of the one very good person who currently holds it all together.
Who to talk to at Five
Related articles

Nick Mackeson-Smith
You can do anything, but not everything all at once: how to be smarter with your yes

Loading

