Succeeding in an organisation

I overheard a group of IT guys talking about their frustrations with how their department ran, why they had to produce documents no one was going to read, how much of a struggle it was to get anything done. What they all had in common was that they were all fairly new to the organisation. I just listened, because I knew that what I wanted to say to them would have fallen on deaf ears, but it could have gone something like this.

I get it. Sometimes it feels like you have to fight the organisation to get it to let you do the job it hired you to do. I felt the same in my earlier days. You think you’re the expert and that the organisation should listen to you. What you need to understand is that you are nobody to the organisation. You are unproven. You haven’t yet demonstrated the value you can bring.

Succeeding in an organisation requires more than just being good at your job. It requires being able to collaborate and cooperate, influence and communicate, lead through inspiration. It requires that you be humble, accept that you don’t know all the intricacies of what is going on, and look for opportunities to learn. Your job, your purpose, is to deliver value to the organisation, not just to manage projects or architect the infrastructure or keep the systems secure.

It is a struggle, and it may not be what you think you are paid to do, but in figuring out that struggle you can not only make your role successful you can also provide additional benefits to the organisation that come from everyone working together to achieve the same aim. And the organisation needs that.