Being transparent

Image by Paweł Grzywocz

A tool is only as good as it is being used. We need to examine the way that we use the tools in order to get the maximum benefit out of it

One of the question that needs to be addressed is how transparent we can be. Wikis and blogs are used to record down the knowledge but the information are also restricted with security features like permission control. While this is necessary for some restricted information or strategic planning, the restriction of information sharing prevents the organization from tapping on the full effectiveness of wikis and blogs.

The information sharing strategy should be guided by the goals of using the tools. Whether we just want to retent the knowledge or to encourage innovation with the knowledge.

Innovation

If you want innovation among different teams, you need to open up the information sharing among teams so that people from other teams can improve on what they know. The access should be opened up to the widest group of audiences possible. You might never know anyone can contribute a useful idea. That person might just be the office cleaner.

Knowledge Retention

If you only want knowledge retention, then the access can be limited to the current team. Whoever joining the team will be granted access subsequently. But do bear in mind that information recorded down will be accessible to them and it will not be good to have old scores coming up.

Another added advantage of being transparent is that the quality of work will be higher. Sometimes things are being filtered or hidden from the other parties or higher management and that could be the source of some pending troubles.

Conclusion

The culture of the organization should also be taken in consideration too. As the famous idiom - "Rome is not built in one day". Even though the management decided to adopt full transparency policy, everyone in the team should be prepared in advance.