Valuing information tip 1: Show who owns your content
In my post ‘Showing the value of your information’ I wanted to help you to show to people using your information how valuable it is. I asked ‘What is it you can do for people to realise your content is of value, it is useful, reliable, and authoritative?’ and what pitfalls should you avoid.
I want to show you how knowing who owns your content can help people realise how valuable it can be. When I was the BT Intranet manager there was a publishing standard which made it mandatory for all accredited content e.g. news article, company policy to show on every page who the owner was.
The smart part was to also link to the content owner’s contact details in the Directory, which were automatically updated, so you could easily choose the best way to contact the owner to seek further information or clarify anything.
If you don’t show the owner or editor of the content how can anyone feel they can rely on it.
For collaborative content e.g discussion groups, it isn’t so easy to show the owner. However it is possible to show who owns the community and any comments should have an owner that ideally is linked to their contact details. This allows for some communication to continue directly with the owner if more appropriate.
I don’t recommend anonymous postings to blog, micro blogging, or forums. If you have a comment to make you should feel confident that it will be accepted in the right spirit as long as it meets the terms and conditions e.g. no abusive content. The culture of your organisation should encourage sharing of ideas and problems and a mature debate on how to move forward with each one.
Lastly you need to have a good governance framework which covers roles and responsibilities for publishing and managing content. A publishing standard on how you show you own content will help too. Having a template for entering your details helps and a process for reminding when the content needs reviewing is essential.
(Note: Opinions expressed in this article and its replies are the opinions of their respective authors and not those of DZone, Inc.)