OK, enough of the teasers and the overviews. I know that you all want to know the answer to the original question: How do we win with mobile enterprise content management (ECM) – get the benefits while controlling the downside, i.e. the risks and costs?
This post is all about Consideration 1 of the Six Considerations: How Should We Address Our Current State Of Mobile DM Chaos?
First, do a – focused, quick – Current State Assessment for mobile and ECM. Assess the standard things you look at in an ECM Current State Assessment. Look at your processes and the people, technologies, and content that are associated with them. There’s a rock solid methodology for doing this. (Just email me, and I’ll send you the instructions on how to do it.)
But you should also assess and document the important mobile issues:
- What’s the division of labor between IT and users at your organization? Does centralized IT control and manage mobile including the choice of devices, or is it a Lord of the Flies situation, or is it a mix, something in between?
- What are the types of users and user scenarios (on this slide the document with the little people you see addresses that)?
- What devices are folks using, like smart phones, Blackberries, iPads, and so on?
- What are the ECM and mobile capabilities that folks are using?
- What’s the architecture, configurations, and security like?
You can get pretty sophisticated in how you document all this in your Current State Assessment, but all you may really need is a big spreadsheet.
When you do the Current State Assessment, you’ll see uncontrolled diversity of all those variables, failed enterprise synching, and what might be called system of engagement problems. (Note that “systems of engagement” is a useful jargon term to distinguish the collaborative and social technologies from the older “systems of record” that most of us in ECM are familiar with.)
For basic mobile ECM health, these variables all need to be managed at the enterprise level. This is a necessary condition for the success of any future mobile ECM projects. The Current State information will be used as you develop your Future State and Roadmap.
Stay tuned. Next time, Consideration Number Two: How Should We Start Adding Mobility to DM?