We need to measure what we do - that's what we agreed on in part 1. What do we need to measure? Let's assume we're introducing a small state of the art 2.zeroey employee-portal in a not not small company.
The company does already run an intranet, it's almost ten years old. People are used to it, they always complain but there's nothing special about it.
What can be improved?
- With the new solution, it's easier to create content, so editors can work faster.
- They have a better flow in their work, so they make less mistakes.
- The new portal offers a better navigation, so people should find content easier.
- Tags are introduced, so that should also increase findability.
- Search is improved.
- Some basic content features have been introduced, so now it is possible to create slideshows, embed videos, audios and other media - that improves the user experience and saves the editors worktime.
- Basic statistics are part of the tool (tracking the backend and the frontend).
- Wiki functionalities allow fast editing for a bigger and not so skilled audience - that saves training, editor time and user time and reduces errors.
- Blog functionalities introduce new possibilities and enhance communication.
- RSS is used for feeds - in the portal, in blogs, wikis, the other way round; they optimize the use and reuse of content.
- Comments are introduced and are a simple feedback tool for users.
- Tags, clouds, categories in the fronted are just some next generation tools in the frontend, they enhance and train the employee's media literacy.
These are just words... They have to be transformed into measurable numbers, the numbers have to be interpretable so that they relate to values, and finally the complete package has to be transformed somewhere into money.
The desired improvements have to be transformed into trackable metrics: What are the indicators, can they be found in the cms/portal?
The metrics need to be clustered into rememorable topics, and they need a visualisation: create charts, get sample data, build words and their stories.
Finally, an obvious connection between the indicators, their behaviour and the financial development of the project has to be made visible.
Visualization: Key Values based on easily trackable indicators.
But step by step.
- In the current project, four main values could be identified: Effiency, Satisfaction, Quality, Impact. Each of these values is based on several metrics, these metrics can be combined to several graphs that indicate trends and development.
- This leads to a balanced-scorecard-like environment, where small changes on a basic level are aggregated to effects on a visible level, on a level that can be communicated on a senior management level: You don't have to say "We are having less usercomments than last month", but you can say "Our portal is loosing on impact"; you don't have to talk about painful cms editor-tools, but you can talk about efficience in the work of editors or about increasing or decreasing cost per content or cost per user.
- Changes on the value level finally have to be translated into financial dynamics: where do changes in the techy metrics in the underground make you loose money, where do they make you win some?
Relations and data are quite complex by now, but it is really important to keep the dynamic parts really simple and related to as little data sources as possible - preferrably only one: Everything that comes out of the portal can be measured in the portal; everything else should have to be defined only once.
This is what we will cover in the next part.
Part 1: ROI - social media metrics based on investments in the future
Related articles by Zemanta
- Social Media Basic Literacy Skills In the Nonprofit Workplace
- Wikis Still Slow to Catch on Internally, Externally
- New Project to Help Explain Social Media
- ROI Smoke and Mirrors - social media metrics based on investments in the future
- Exchange4Media and Blogworks.in present "India Social Media Survey, Brands and Corporates" Edition 1, December 2008