This is a post originally from Soapbox, written by Colin Whitney and loved the subject so much we’ve posted it here as well.

I hate it. I hate that statement. I drives me batty…

Ok, Point taken. That’s not your job. And there’s proof because it’s not in your job description. Great. We’re all clear. There’re clear boundaries, and we’ve all got our marching orders, right?

Wrong. Don’t believe me? Then you won’t like the rest of this post…

Still reading? Ahh you’ve given me a chance! Thanks! It’s taken me a long time to put my finger on this one. For a couple of reasons. First, I’m pretty sure my own personal dislike of the statement “Ya, but that’s not my job” translates to: “You want me to do my work, and that other person’s job – I’m already busy, and you’re just asking me to do more.” Let me try here…

What happens when the work changes and your job description doesn’t?

The problem is the the world changes, and so does the work. Constantly. For example: Whose job description reads: “Make sure we stay on top of emerging competition and technology, while responding to shifting consumer behaviours” at Blockbuster?

Why should you even care?

Internally at any company, a statement like this is fertile ground for conflict. Because what it really says is this: “Do it yourself,” or “I don’t care,” or “What I’m doing is far more important.” Externally, it says the exact same thing… to customers. They don’t care if it’s your job or not. In their mind you are the company, and you just pissed them off.

So, what then? I’m to do everyone’s job?

Nope. It’s not about who’s job is what. It’s about caring outside your cube. It’s about looking at the whole rather then just your piece in it. It’s all about asking: “How can I help?” If the front desk is empty and a client walks in… and all you do is stare at them as if they’ve intruded or annoyingly interrupted your day, then your company fails. Not just you.

Read the rest of this entry on Soapbox