Thursday, August 25, 2016
Does your ECM system have a story title like, “Doc Repo” or “Approval Center”, or is it called by its vendor name? Even a generic name is better than the vendor’s name. A unique name gives the solution an identity. This identity could help expand the solution to other areas of the company. Some companies adopt an IT pet name for their systems and solutions, but many others just call their HR system, “PeopleSoft”, or their ERM system, “AllScripts”, etc. These names just promote the vendor, not the unique solution.
Second, You’ll need to “balance the flexibility required for innovation with the routinization needed for ongoing operations.” (Tushman and O’Reilly 1996). You can’t create a completely new story which makes no sense or is too obtuse. The purpose of the system name and stories is to bring disparate, silo oriented, groups together with a common understanding of the solution.
A narrative needs to be transformative: “Transformational innovation requires offering or doing something fundamentally different; a metamorphosis most organizations don’t excel at. Such innovation is disruptive because it introduces products and services that change the business landscape by providing a dramatically different value proposition. And championing transformational innovation involves going to war with all the elements inside an organization that benefit from the status quo.” (Stephen Denning)
There’s always a beginning, middle, and end of stories. The ECM solution is the middle of an ongoing story. It doesn’t end, it just morphs into another solution and narrative, like Star Wars.