Reaching the Next Level

When a new programmer starts writing code, s/he requires detailed specifications and clear requirements. The understanding is on a level "I need to get this piece of code working". There's not very much thought given on what happens outside this routine or how things are connected.

On the next level, the coder understands that the piece of code s/he's writing is a piece of a larger system. This system exists for some purpose, but the purpose isn't necessarily clear for the person. But generally s/he understands the system is important for the company and probably generates financial benefits (i.e. is sold).

Reaching the next level is already quite challenging. At this point the developer starts to think about the customers' business. How do the customers make their money? (...that can be then invested. Maybe in software. Maybe even on the solution you are developing...) And when you understand how the customers make money, you understand their priorities and needs. What is important for them and critical for their business.

There might be intermediate levels between the ones I mentioned, but I think this covers the basic steps. I'd encourage all developers to try to advance on these steps. The higher you are, the better you can fill your customers' needs and thus the more valuable you become. I'm not saying that code writing is easy. I'm simply saying that being able to write code AND understand the business is a tad harder and rare. Development on this path starts from understanding the user. 

(Sometimes the decision maker for software purchase is not the same as the user. Users might be only influencers in a complex network. But let's leave this out of scope for now. )

Understanding the Whole

When a company is in the middle of an organizational change, it is sometimes difficult to understand your/others roles and the expectations. It's easy to stay with the comfortable old routines and do what you have always done. After all, you know what to do, you have done the same thing plenty of times before.

But here's the catch: what if things around you have changed? Things you know how to do might not deliver the value anymore the same way they used to. Or it can even be that the activity you keep on doing is creating a major pain for someone else in the organization.

Unfortunately I can't think of a good example where organs of living organisms were scrambled, but with organizations this can happen. And then it doesn't really work out well if the lungs still think they are fingers and forget to breath. It might have severe consequences even though they are still able to type like they used to. Like in the good old times.

Break the old habits! If you have been assigned to a new role, check what's really expected from you. Are you a muscle cell doing some heavy lifting or should you be concentrated on thinking about the future like the rest of the brain cells? How does your work affect the whole?