Posts Tagged career

Guide for career progression – 3Ps process – Part ONE – Overview

I have been wanting to write about this since a long time, however it took a real long time for me to think appropriately and make my mind on what I should post here. Well, finally I have tried to consolidate few thoughts in my mind about this and putting them here for you all to read / think and if you feel, act on them.

The progress of one in his career is as dependent on hard work, luck as you identifying the right opportunity, sensing chances and making your moves at the right time. The more you move up in the corporate chain, the more it makes things competitive and tougher to break.

In my relatively moderate experience and what I have seen around me, I have tried to devise the progression from one level to another into three step process, which if you work upon, and provided you identify opportunity, sense chances and make your moves at the right time, could help you progress in your career.

Now, before I move on the steps and uncover you the secret, I may warn you that this may not be obviously applicable in all possible cases and all possible job types. My little brain has worked only in the IT sector where you have typical organizational hierarchical structure to deal with and most importantly, you are interested in growing yourself up in the corporate ladder at any cost !

 edit  First pledge to me that you will never break this secret to anyone !

       Great ! Thanks for your pledge. I can proceed happily now !

Moving on now to the three step process I mentioned earlier. The process is typically covered over a period of 2-3 years (considering the IT scenario now) so you must have a patience, a will to put shifts & hard work, capability to learn new things / skills as well as unlearn if the time demands you to do so and pray for a little bit of luck along the way.

The three steps of the process are Prepare, Practice & Pass. So henceforth I would call it as a 3Ps process.

I hope to publish a series of about 4 posts (including this) on career progression and how you can use the 3Ps process (Prepare, Practice & Pass) for your benefit.

Till then, enjoy your time on my blog and as usual thanks for visiting the it.


This is a series of FOUR posts on Guide for career progression – 3Ps process.  Other posts on this could be found below.

Part ONE – Overview
Part TWO – Prepare yourself
Part THREE – Practice hard, become a key player
Part FOUR – Pass it on & progress

Tags: , , , , , , ,

My perspective on performance appraisals of a team – the opportunities & judgements

How do you assess the performance of an employee reporting to you at work? What is your basis of assessing him and how do you decide on the grade that you would give him for his performance? This is a typical question and situation faced by IT managers whilst carrying out the performance appraisal for their subordinates. Earlier I wrote here about the way typically the performance appraisals are carried out in most of the organizations.

In this post, I am trying to put the equation through my perspective and how I would judge a resource based on the work he / she does in the organization on a project.

One of the most important aspect of Project Management, in my eyes is,  to create and give equal opportunities for your subordinates to perform and on the basis of the performance, judge them on their results & outcome.

The obvious question you would ask is how on earth you could give equal opportunities to the resources within your team to shine? Well, the answer to this is simple.  Create opportunities and innovative ideas and encourage taking initiatives that would make the workplace a better place and obviously help the projects.

Assuming that you have a fixed set of tasks you do as a part of your project and you have a varied experience pattern in the team where some resources are senior (more experienced & some being juniors (relatively less experienced). In this case, most of the times, its observed that more critical work where results are evident and clear, is done by the senior people within the team whilst the junior people are given more of a regular & business as usual tasks such as reporting, housekeeping & less critical work. Probably, in a way, right for the project and right for grooming them to take up more challenging work once they are good hands-on the project.

However, the catch in this is, how long you would keep this situation? In practice, it works, but how long really would you like to keep it as it is? 3 months, 6 months? Well, depending on the manager / team leader they would like to start giving the responsibilities to the junior members sooner rather than later, and give them challenging work so that they could try and prove themselves as being up for the task! In my eyes, the sooner you start is better, probably immediately after you finish the training & into a month on actual project work you give them good responsibilities so that they could grab the opportunities and give you results you need from them.  But again, this is one side of the story !

Second part is, if there is not much routing work that is challenging enough for the teams then what you, as a leader or a manager do? Create chances for the team to show their potential !  .. the obvious question you would ask is HOW?

One of the simplest way to look for chances is to look for opportunities of improvements in your project and try few of the following suggestions to see if you could use them to allocate non-project work to your team members and get results that would benefit the project to either save efforts, save money or save time ! Give them challenges to provide practical and technical solutions to common project problems and situations and judge them on the results they show on this work. The technique of innovation & taking initiative was what I actually tried on my team members and found really useful to understand the potential within the resources and judge them accordingly.   Some of the examples we recently implemented were the knowledge management wiki, our team blog, health check automation, server uptime checker, mailman list for managing incidents and so on. These things really helped the team, the project and in general increased the level of spirit within the team as most of the resources got equal chance to show their potential by doing a definite work package delivery within the appraisal year.

Now moving on to how you judge the resources on their year end performance.

One of the most important thing you should as a project manager is to keep discussing with your resources about the expectations and guide them in their career. I especially dislike the method of “once-a-year” discussion about your work, probably a month before the corporate appraisal cycle ends !  This is absolutely bad practice.  As a project manager, you not only have a responsibility to deliver the quality project, but you also have a responsibility (may be as a parent or caretaker) to nurture the talent within the team and guide your subordinates towards their goals.  Honestly, and unfortunately, not many Project Managers do this in practice.

If you have been discussing the expectations, creating opportunities for the resources to work on, monitor results and measure the outcome of the work regularly enough then it actually builds a level of trust between the manager & subordinate, which really is important in the corporate world.

One example I give to all my colleagues about appraisal is of how a good, excellent & outstanding performer will react when given a simple task “bring me a glass of water”.

Good performer – Joe
If you ask Joe to bring yourself a glass of water. He would go and literally bring you a glass of water as you said.

The people who would do the given job have done a Good job in my eyes. If they do the given task without any issues, without any pitfalls then they have done a Good job, nothing more.

Excellent performer – John
If you ask John to bring yourself a glass of water. He would go and bring you a glass of water, however with it, he would also bring another jar full of water in case you require more after you drink one glass.

You might have noticed how the response of John differs from Joe. Quite simply, he anticipated the customer requirement and took an initiative to address it without the customer asking for it. Bit of happier customer !

The people who do given job excellently would normally have shown good proactive measurements to ensure the given job and related tasks are completed on time and with quality.

Outstanding performer – Josh 
If you ask Josh to bring yourself a glass of water. He would first give you a choice of hot / cold / tap / mineral water and bring you the same. He would also bring an additional stock in case of you needing more once you drink your glass. Whilst you are drinking the water, he would also make arrangements about next time when you might require it and in case he is not around to server you !

Again, you would have noticed how Josh has differed from John in managing customer requirements. When customer puts a requirement for you, you should always go back to customers with options that are possible within the circumstances so you exactly understand what the customer wants and deliver according, exceeding the original expectations.  An even more happier customer here !

The people who, in my eyes, do an outstanding job would not only do the given job to an excellent level, but would go a step further and take proactive measures to make it better next time. They would bring out initiatives, changes to the processes, tasks and drive them to closure.

These people will make significant difference to the project and would be real assets.

 

In the above, I particularly did not comment on the resources who perfo
rm below the Good level and if despite giving opportunities, the resources do not take them and show results, then probably the project is better without them !

Tags: , , , , ,

Top 5 myths related to application support domain

Did you ever notice that in a multi-service oriented IT organization, that delivers new projects / products as well as provides IT support services to customers, more focus is normally given to delivery of products than providing high quality maintenance & support services? Well, if you have, then you are not the only one!

What I have seen at least in the Indian IT companies is the poor comparison given to the professionals working in the IT service support domain than to the professionals working in delivering new functionality to the customers. I suppose the roots of such unfair comparisons are in few myths that are present in the IT area.

  1. Call centre perception – Yeah, most of the people I spoke with did not have any idea when I asked and interviewed them about working in support projects. I asked them ‘What do you think working in support means for you?’ The quickest answer I got back is ‘I think it’s like working in a call centre, you need to be on phone all the time and answer customer queries. I am not interested in becoming a phone operator!’ Well, to a certain extent they are right. If you are providing support services from an off-site based location (Offshore or nearshore locations) then yes it does involve lots of speaking on phone. But if you look the way IT is working, speaking on phone, joining conference calls etc., has become just the way of work.
  2. You do not learn much when you work in support - This is the most common excuse given by professionals (at least young professionals) when they are asked to work on support projects. They feel that working in support does not offer them opportunities to enrich their skills in technical area. I certainly do not agree with this! In my view, working in the support function just gives you an opportunity to view at things differently and gives you a closer and practical look on how projects work on production platform and how a product is used in practice. You get to know the project and products from a close angle and you are always on the edge to keep the software / service working. Imagine how it would be like to have an outage on a banking site!
  3. You do not feel enough challenged while working in support – This is another common myth that makes house in the minds of fellow software professionals. They feel that working in support projects does not offer enough to challenge their intellectual wits. They feel that the work is repetitive and routine and thus they would get bored after some time in working in the project. I certainly do not think so! Ask this question to the people who support the online trading on bank website, or stock market website where even a minute’s outage may mean you lose millions of dollars in business. Is this not a challenge to keep them running?
  4. My professional growth will stagnate – Lots of people whom I interviewed for projects often complained to me that if they join the support project, their growth opportunity will be limited and they would get stereotyped for rest of their career. To the certain extent I agree with later part (i.e., stereotyped) but definitely do not agree with the first argument. The growth of the individual in an IT organization depends on how the person senses opportunity and makes use of it and not on what project he or she works on. After all, you are likely to get a better recognition if you save a bank site from falling over than writing a piece of software!
  5. My value amongst my peers will go down! – This is one of the silliest excuses I have ever come across; indeed I did come across this. The person who was telling me this was saying that he will feel inferior compared to a person working in a delivery and writing Java code. Fuf.. ! I did not have any answer for this, but all I would say is the inferiority is in the mind and depends on confidence of one rather than natural capability.

Interesting enough right? Let me know if you have come across any more myths about professionals saying no to work in support.

As earlier, pasting here a fantastic Dilbert comic strip that gives perfect example of how the world perceives of the Tech / Application support !

dilbert-tech-support

Tags: , , , ,

Performance Appraisals – are they really the reflection of your performance?

If you are a corporate employee you must have undergone the performance appraisals or the end year appraisals and its equally possible that you would have, sometimes, wondered at the outcome of the result ! 

In most (or all) organizations, the performances of the resources are categorized as per something like Excellent, Very good, Good and Needs improvement etc or A+, A, B+, B, C categories that should ideally reflect the performance done by the resource over the year of measurement of the appraisal.

However, what pisses me off is the fact that in most of the organizations they keep silly rules that are nothing to do with the work you do or the project you work on and still could potentially affect your appraisal.  Few of them I think are as follows,

  • Unnecessary points awarded for attendance (come on time and go on time)  -  For God’s sake, we are in a corporate world where the output and outcome of the work matters and not the time someone enters into a building and leaves the building !!!
  • So called corporate trainings – If you would have read my earlier article about trainings, you would probably have guessed that despite the actual training having a little impact on the outcome of the project work or resource efficiency, the simple tick mark of attending the training makes you earn points against your appraisal.
  • Performance levelling across group, organization – According to me this is one of the most bullshit of the rules used in the performance appraisal.  If a person is brilliant in the given environment or scope, there is a likely chance that he is equally brilliant in the bigger environment. The scapegoats of this rule are the people typically working and delivering small scale projects or the projects having less financial or strategic importance to the organization. In an ideal world, the comparison should be done against the actual objective of the project and individual’s contribution to the same, no matter how much money the project is earning to the company.
  • Percentile factor for promotion cases – If there are many proven fantastic team members, if if they actually are excellent, no rule in the world should stop them to earn their own right of having a good appraisal result. However, mostly the management needs to choose only some percentage of top performers to promote and often leaves many of them demoralized !
  • Goals that were set at the start of year – Another pretty useless thing that is part of the annual appraisal process. The goals should always be revised every quarter and should be short term and achievable in the form of proven results.  The misguided and misleading goals that are often set for management also gives a case to cut points off your appraisal.

Finally, the Dilbert comic strip that truly reflects the appraisal process ;-)

dilbert-appraisal1

Tags: , , , , , ,

Corporate training – waste of time?

Do you think the corporate training courses work towards achieving the goal set prior to the training?

Well, in most of the cases I have seen and heard of it does not help !

What I have seen instead is the fact that the training courses and the on the job work does not really go hand in hand.  I have seen that the application support team being training in a Weblogic related development course rather than incident management, or ITIL courses. 

What really frustrates me is that in most of the companies (well I have only seen few myself, but heard a lot though) that the training courses are not fine tuned or aligned with the job profiles of the professionals undergoing training but mostly are the ones that are sold by the vendors and are standard courses.

This does not really gel well in the long term as the person, despite undergoing training, can not do his / her job efficiently and is blamed for the failures.  It does not work that way does it ?

Weirdly, what I have also seen is the corporate companies forcing compulsory training programmes for the associates and link them to their appraisals etc. Well, in a good sense if all goes well and if all ends tie well, this could well be good for the growth and progress of the organization, but as I said earlier, more often than not they do not end up improving either organization or the associate both.

Tags: ,