Organizing Information

A few days ago, some of the senior leaders within our team got together to set out some "standards" for how we capture and manage information in our organization.  Specifically, we decided to share information more effectively by storing the files and information we create for various consulting opportunities in a file structure that will make it easier to find and use information.  Rather than each person creating and managing their own filing structure and guiding others to information, we're trying an agreed, standardized file structure based on a "taxonomy" we pulled together over a few hours.

This effort raised some interesting questions.  First, we needed to redefine the goal.  Why were we creating a standard set of folders?  Everyone agreed that finding information is valuable, and should be easier.  But was speed the main goal, or was context important?  If so, what context was valuable?  WIthout everyone agreeing on the goal for the data organization, it would be hard to agree on the remaining questions.

Then we needed to think about how to organize the data.  By function, by client, by timeframe, by methodology phase, by deliverable?  Depending on your perspective of the data, any one of these could be an important and valuable first cut at the data.   

Then, we needed to split some hairs or have better definition.  For example, we create PowerPoint presentations for webinars, conference and other speaking engagements and for client sales presentations.  We had formerly divided this into two folders, one specifically for client sales presentations, and every other type of outside presentation.  Was that still appropriate, or should we simply have a "presentations" folder with subfolders based on the audience or purpose?

In some cases, we need meta-data about the documents, deliverables, plans and so forth.  If I include a project plan that we used to manage a project for a client, but I don't include the facts about that client and what made that project plan specific to that client, it's possible someone else will use that plan but not understand the constraints under which it was written.  Creating a structure to help people find information is not enough - that information needs context so that it can be re-used properly.

As we work with this new structure I'll post some things we learn about its use.

Comments

[Priscilla Palmer]

You have been tagged for The Personal Development List. (See my site for details), I would love it if you would participate.

[futhermet]

I thought this was a great post, and made some comments elsewhere.

http://futhermet.wordpress.com/2007/08/28/km-and-organizing-information/

I think the KM literature doesn't include enough of these real world, what-folder-should-we-put-that-in, discussions and I found it reassuring that I'm not the only one who's sat in meetings like this. The classification issue is a sticky one, and I look forward to hearing more about your efforts here.

Thanks a lot.

[Hello]

hi
[url=http://www.wowpower-leveling.com]world of warcraft Powerleveling
[/url]. wowpower-leveling.com is an Expert Online
[url=http://www.wowpower-leveling.com]world of warcraft Power leveling[/url]
[url=http://www.wowpower-leveling.com]wow Powerleveling
[/url] Site, dedicated in providing customers with fun in the professional service of
[url=http://www.wowpower-leveling.com]wow Power leveling
[/url]. Excellent Service, Super wow power leveling.
[url=http://www.needrsgold.com]runescape gold[/url]
[url=http://www.needrsgold.com]rs gold[/url]
[url=http://www.needrsgold.com]rs2 gold[/url]
[url=http://www.needrsgold.com]runescape money[/url]

[Nike Shox Turmoil]

He'll get an extra spring in his step in the Nike Shox Turmoil (3.5y-7y) Boys' Running Shoe, offering him the best in cushioning and durability.Mesh upper with flexible midfoot strapping system for snug fitNike Shox system at heel for impact protection with cushioned PU forefoot for responsive rideFull-length rubber outsole for traction and durability

[Carlos Rozo]

I agree with the goal-setting as an important step. As part of my work on the KM field, I found that talking about taxonomies with the "non-initiated" was a conversation killer. That is why I decided to create a simple way for an individual to manage a taxonomy with their information, and came up with http://thotz.net right now is a Beta, but we plan to expand it to organizations to address this specific problem. I'd also appreciate your feedback if you have some.