M is for Motivation

[This post is a continuation of a conversation I had with a good friend and school buddy who graciously set aside one Sunday morning to talk to me about his new role in managing and motivating his team.]

In your new role as a Network Ops Manager, do you have to get hands on? [I ask him]

Yes…very much. Mine is not a pure managerial vertical. I would say 40% managerial 60% technical. A good thing is a couple of them are technically strong.

How do you motivate your team?

Motivation levels vary…it’s up to me to motivate ‘em. The trick is to make ‘em feel that they are not doing redundant stuffs.

Keep giving them some new challenges?

Yes….make sure they are adding values to themselves, being on the cutting-edge… so I need to keep rotating stuff [responsibilities].

Yes.. Very true, which is a plus point in your line of work… they get to work with some good hi-tech stuff.

Yes…basically talk to them and understand what they would like to do, make sure you align their tech verticals accordingly. Some guys would like programming. Some guys would like networking, server setups etc… As their leader, I have to make sure that I manage their expectations well.

In most mid-sized growing companies, that has become the toughest challenge now.

See, redundant stuff would always be there…. you can’t help it but what you could do is they wouldn’t mind doing 40% redundant work if the other 60% is the exciting stuff. And the 40% redundant work, you could try automating stuff to get the redundancy down….that’s an added motivation.

Well.. in the s/w services industry where these companies mainly cater to US clients/projects… the issue is that we don’t get challenging work. New development mostly happens in-house in their own IT wing. All maintenance work goes offshore.

Yeah….good thing in my company is that we don’t do maintenance….we’re still developing on our IP [Intellectual Property]

When u say “could try automating stuff to get redundancy down” what do you mean?

For us it’s mostly scripting, running cron jobs on our server, etc. We automate all these using PERL. So people who are interested in programming also happy.

Got it. But isn’t it like digging your own grave. Once it is automated you don’t need that 40% allocation of a developer.

Don’t worry. We have enough work as it is. My primary objective is to attain a high degree of automation. I would want to free up minds for solid research work, and not waste ‘em on redundant stuffs. We have enough things to do as it is.

Yes. Automating work, Building processes, etc. That’s the way to go. Also, on a technical front, find innovative ways to do what we do better. But i m sure in your arena the challenges are orgasmic.

Yes, very much. Not many companies do stuff that we do.

I can picture it now… 30 odd perverts in your company.

Correction….50 odd perverts

Does anyone in your team not listen to you? Did you ever have to be harsh on anybody?

All that comes with the package…. you need to be diplomatically harsh.

So was that a piece of cake for you? I mean… something u could easily do? Put the point across in a diplomatic way!

Nope. Thought a lot about it and I’ve been observing all these when I was a lead. Incorrigible guys are shown the door.

That brings an interesting question…. What is it that you have seen in your manager that you don’t want to ever be or do? What kind of a manager do you NOT want to be?

Do less bull-shitting hahaaaa

Ha ok… that’s an obvious one but you would have to do some bull-shitting. It’s part of the game.

Hire and fire. You cannot live without it but fire only in extreme cases. You would try to fit in a non-performing guy in another team.

Ok.. Now I have interesting response to that… about firing and hiring. A manager should not or cannot afford to wait too long or act too fast in hiring or firing. You have to do it perfectly. Not making a decision or delaying a decision itself is a bad decision. You’ve got to trust your gut at some point because if you listen carefully, you know if the dude in your team will work out or not

Yes…100% agree. Especially if you have very aggressive schedules, that’s where a technically sound manager would help. He could cushion the impact that a non-performing engineer would generate to a certain extent. That could be your way of evaluating the guy, to see how much of your time you needed to put in.

Yes. True. However, in aggressive schedules u need to have your backup resources planned.

There is an interesting test every manager can try out:

1. Take a blank piece of paper.

2. Take a pen and write “strengths” on one side and “areas of improvement” on the other.

3. Think of any person in your team… anyone.

4. Note down 1 strength and 1 improvement area.

Based on where your move the pen first tells you a lot about what your opinion is about him/her. If the pen moves towards improvement areas first, the next question you should ask yourself is – What is his/her improvement plan? Have you put one in place? What do you think?

Sounds like what we do in our quarterly appraisals.

Yes… but it might be too late by then. It’s a fact that most managers fire people “too slow” because most of us are scared to go down that path.

I know but as I’m involved in a lot technically, I don’t want to do this hastily. I guess that’s all the more reason for going the extra mile of keeping the good guys in the company.

You mean to say… because you are not a full time manager?

Yes.

Ya, but still u have to keep an eye on your team member at all times… the 40% of your time that you are doing true managerial stuff would be enough.

Yes. You can very easily make out if the guy is slipping. I’m not disputing on whether it is required or not. The only constraint is time.

[My time was up. He had to leave.]

Appreciate what you are doing buddy…..really would help lots of budding managers.

Thanks man.

Did this post ignite a thought? Join us and mirror your thoughts on the 13apples facebook fan page.