Bumped into the CEO this morning and his first words to me were, "Knowledge Management!" Seems he played golf yesterday with another CEO who was crowing about how their new Knowledge Management system had positively impacted their bottom line. He wondered out loud to me, if it could help us.

I've been toying with the idea since that conference last spring, but couldn't figure out how to best package it. With the CEO interested, the time to strike is now, so I hurry back to my office to run some what-if scenarios through Entire.

I have a good idea of the resources I'll need, but don't know how the rest of my world will be affected by inserting a new, major project into the mix. Entire enables me to quickly ascertain where the gaps are and provides me the information I need to dynamically see the effects of rescheduling the work load around the Knowledge Management project. Armed with this knowledge, I'm able to determine that we could kick this project off four months from now with minimal impact to the existing workload. My next step is emailing the CEO with a request for a meeting to follow up on HIS suggestion of exploring Knowledge Management.