Knowledge work...
Thinking about doing, is different than doing...
In college, I had one of the best jobs...at the dining commons, I was the "pot and pan washer."
My job was incredible! When I arrived to work in the evening, the cooks had already left for the day (no one was adding to my stacks). There were three sinks: Wash, Rinse, Disinfect. On the left, a huge pile of dirty pots and pans. Spread around the kitchen were hooks and shelves to store the clean pans.
I worked until the left of the sink was clear, and all the pans were stored. This was NOT knowlege work.
Fast forward in time to 2004.
When I'm in the office, I receive new e-mails throughout the day. I am usually working on an article or two at any given time. I also have travel arrangements to make. Throw in all kinds of personal issues to handle (dentist appointments to make, car repairs to schedule, etc).
This is knowledge work.
Knowledge work is different than industrial work. A knowledge worker has to "decide" what to do, while an industrial worker has a set outline of what to do.
Most folks I work with have some version of both of these going at any given time. Our specialty is in creating "punch lists" for people who have to think about their work, but don't have time to re-think about what they've thought about before.
For example, we encourage people to process e-mail before doing it. Instead of reading all the (
http://davidco.com/pdfs/tt_email.pdf]e-mail ), closing the "unimportant ones" and only doing the urgent ones, (
http://davidco.com/pdfs/tt_workflow_chart.pdf )PROCESS them all. This way, it's not necessary to go back into a "semi-processed" in-basket and re-think what you've already thought about.
Here's some info re: the father of the principle of Knowledge Management:
http://home.att.net/~nickols/chronicle.htm