Chains…

There’s a way things are supposed to work. I’m supposed to know what my people are working on. My boss is supposed to know what I’m working on. And so forth and so on until somewhere in the stratosphere one person knows more or less all of the major projects that are running. For the record, “major” projects don’t include informing the building every time someone makes an adjustment to a slide set or when they need to buy a hundred dollars of toner for the printer. The chain of command exists for a couple of reasons and one of those is to make sure information flows smoothly both upwards and downwards. I’m more than happy to report my progress and issues to my boss, who can then report it to his boss, and upwards ad infinitum. What I’m not going to to is generate a completely new class of report that skips several steps in this process. It duplicates effort and basically makes any semblance of structure pointless at best.

We’ve gotten so concerned and wrapped around ourselves doing things because we can, that no one at any level has called a pause to assess whether we should. What a Charlie Foxtrot. Scott Adams would be proud.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s