I’ne never been that comfortable with the concept of adoption when applied to enterprise tools. More precisely when the point point was “driving adoption”.
Of course adoption is necessary. And, like every necessary thing, businesses can not afford not to drive it. Nothing but pure logic…but it can’t prevent me from feeling its sounds odd. I was slowly getting used to these words when Paula Thornton brought it back to my attention.
Let’s start with the meaning of words.
Driving : giving oneself the means that are necessary to achieve someting and the appropriate indications to pilot actions.
Adoption : action of making something one’s own in a voluntary way. Supposes the benefit, sense and implications are understood.
If both are necessary, I still can’t put them together in the same sentence. The reason is obvious : if adoption implies spontaneity and a choice that’s not made under duress, driving means make people do something unnatural because if it were natural people would adopt without any external intervention. Some may say that driving only means “create a breeded ground” but I don’t think that’s how companies see things : it would mean they don’t have any hold on the result and, as a result, they only try to make their best so things can happen instead of considering they have an obligation to produce results, what is not conceivable for most businesses. So driving adoptions means making people do unnatural things and such an approach explains how things are so difficult, why people don’t adopt or adopt reluctantly.
Is it a dead end ? Not at all. If both adoption and driving are necessary, we have to be cautions not to mistake what has to be driven and the final result.



You can find the "original" french version of this blog here

