Sunday, June 21, 2009


This is the easiest answer to an embarrassing situation.

The Accountant and the Programmer Story
For example, imagine you are a developer. You are developing an application for an accounting firm. There is an accountant allocated to test the application as you develop.

Lets go through this flow.

1. The accountant finds an error in the results, asks you to fix it, and explains why its an error.

2. You fix it. and you forward it back to him to test it.

3. He found another error of the same type, asks you to fix it, and explains why its an error (again).

4. You fix it (again).

5. He found the same error of the same type but in another report. So he tells you, "Please, if you just test the application more for these similar errors before sending it to me."

6. You reply: "Listen, It's not my job to detect the errors that may emerge in the result, I don't know accounting, I'm not an accountant. My job is to only fix errors not detecting them "

True, but silly. Right? Just like the picture I'm sharing here, the guy who marked the road said his job is to mark the road not to move the tree.

Do you have the same scenario at your work?
Apply this example to your business. I'm sure you have similar mindsets. The It's-not-my-job mindset is the exact opposite of proactivity.

If you hear your manager asking you to be proactive, maybe you need to start breaking your it's-not-my-job mindset.