Proof of Adoption (Part 2)

Got a bunch of DMs about Tuesday’s PoA (Proof of Adoption) post that– somewhat inexplicably– weren’t about peanut butter cups. Enough of them, in fact, that I now feel obliged to pop some persistent myths.

First…

Software adoption in the enterprise does not come from senior management support.

It doesn’t come from a great comms plan.

Or better training.

Correlation vs. causation yo!

Also…if you’re a vendor, there is nothing “lucky” about landing mandate-happy executive partners because you’re also landing a deeply resentful user population. Think five-year-olds right before nap time.

Software adoption that sticks– the sustainable, scalable kind– is almost entirely driven by early adopters who LOVE(!) the experience so much that they want to use all their social capital to lower their colleagues’ resistance to change.

Think of it this way:

Your product is– hopefully– an ice cream cone– say… Haagen Daz Pistachio or Ben & Jerry’s Chunky Monkey with all the large chunks of bitter dark chocolate dug out and thrown into the trash– where they belong.

Your client’s early adopters are the five-year-olds willing– nay, excited(!) to share a lick or two of their cone (the fools).

That’s super important because no one responds well to mandates. But… and this is the key… they do love what their friends love… and usually… because their friends love it.

Social engineering for good yo!

–

If you’re still confused: #DarkChocolateIsSatan #HillNumberTwo