, Read Never (WORN) Whats  your

What is your ? , read never…You know those documents written with fervour to communicate an important policy but no one ever reads them, no one has access or no one cares. Why? Perhaps because they can’t be found, they are not presented well, How does your organisation curate information? Do you have a Wiki, a sharepoint library, a directory on a server to store and access files. Outside of a staff handbook, where would the person lowest on your companies ladder find information on your policies. Do you have a policy or process, or even better firmly embedded governance for naming files and where they are stored?

Or…do you have systems, but the office stores their  files in an way, the Finance people, name files in an accounting way and the IT dept are a law unto themselves. Even worse do some individuals have an individual way of storing everything. What happens then when they leave?  I have been there when this happened and finding files or understanding file systems means information is lost. So what do we to do?

charity checkup knowledge strategy  knowledge strategy - WORN 300x217 - Written Once, Read Never (WORN)| Whats your your knowledge strategy

  1. Knowledge maturity. Where are you or your organisation on the information development scale? What do we have now and where is it? Is it out of date, does it use different naming styles, is it in different locations, is some of it some hard copy, is it in closed or open access points, can be accessed via mobile tech. So we must obtain this understanding and be honest about the situation, then we can gauge realistic targets and expectations about knowledge .
  2. Which System? With our new awareness, we ought to probably detail some sort of system to get a procedure and approach set up where one may not presently exist. Use of Sharepoint web-based systems,  naming of files and folders, having a Knowledge Wiki for policy, even a properly indexed hard copy of all organisation policy. Knowledge must be curated and collated but access should be self-service, items found easily, named simply and so on
  3. . We buy in, because without it nothing will change. Certainly it will be harder to get resources allocated to make change.  However we don’t just buy in, we a commitment for teams to discuss and talk about, at all levels, the .
  4. Scope. Firstly Identify your team to focus on knowledge , it can be small but it must be focussed so as not to be put on a back burner; second identify the scope for your knowledge policy.  Any policy to be used s simplicity, clarity and realistic/achievable objectives; finally identify the documentation you already have for validity, currency and usability. All else can go to an archive directory.
  5. Benefits. To make your hard work pay off, you and your team should be communicating to everyone tough out the organisation why knowledge is important. Of course there is GDPR, but also communication, transformation, professionalism and the simple matter of finding things quickly and quietly.
  6. Hard work. Knowledge can be separate, a central plank or partner of a strategy is often hard work; especially where an organisation has grown organically and file naming or organisation alone is something done in an ad hoc way. There will be duplication and complication so it will be a tough task to review and change. It may take some time.
  7.  Essential strategy No document should be  Read Never (WORN) in your , it’s why you strategy.

Why not get in touch and find out how we can help you with your .

 

Leave a Reply - Your Opinions Matter

%d bloggers like this: