Make it explicit when…

Posted by  Mark Schenk —March 13, 2007
Filed in Collaboration

The following four conditions are cited as factors that communities of practice might consider in deciding whether something should be made explicit:

  • it is relatively stable
  • it has longer lasting value for a larger community
  • it is expected to be retreived relatively frequently
  • it will be maintained and kept up to date
  1. A van Unnik, Shell EP LLD, Benefits of Developing Knowledge Sharing Communities, Abu Dhabi International Conference and Exhibition, 10-13 October, Abu Dhabi, United Arab Emirates, Society of Petroleum Engineers, 2004

Mark Schenk About  Mark Schenk

Mark works globally with senior leadership teams to improve their ability to communicate clearly and memorably. He has been a Director of Anecdote since 2004 and helped the company grow into one of the world’s leading business storytelling consultancies. Connect with Mark on:

2 Responses to “Make it explicit when…”

  1. Dick Cheuk Says:

    One more point is the knowledge should be codifiable.

  2. Mark Says:

    Good point Dick. Its surprising how often tasks are created like ‘write down everything we have learned about project management in this company’. Any tasks like this would also fail several of the other ‘tests’ listed.

Send this to a friend