Career Bloom

Your source for authentic and practical career advice

  • In my last post, Product Manager, or Product Experience Manager, I described the disparate features and experiences that got broken in SiteZ and made the case that product management team should be responsible for overall product experience. In the final post of this series, I will present my views on how product management team should manage experience so that such issues can be minimized or avoided. Note that I am not talking about creating initial product experience or its next version, which is a topic of itself. I will focus only on managing the product as it goes through incremental changes.

    There are 3 questions that must be answered by product management team at all times (and should be asked periodically):

    1. Are we seeing all the activities we should be seeing?
    2. Are we processing all the activities we see?
    3. Are we making good decisions based on our processing outcomes? (more…)
  • Someone asked me this recently:

    You have 2 options: Work with a good boss, but the work is some boring stuff, or work on some interesting project, but the boss is not good. Which one would you choose?

    My mind jumped to all the boss-work combinations possible, see the picture.

    If I make this a generic question, it is really a multiple choice question:

    Which is the best option for you to choose?

    1. Bad Work and Bad Boss
    2. Bad Work and Good Boss
    3. Good Work and Bad Boss
    4. Good Work and Good Boss

    The questioner was asking which one to choose between 2 and 3, so let’s talk about this first. While there is a scale of goodness, let’s assume black-and-white situation for simplicity – things are either good or bad!

     

    Good work makes life at work interesting, it grows your career, and overall makes you happy. So of course you would want to choose good work.

    Good boss gives you opportunities to grow, guides you in your career quest, and removes roadblocks in your work thus making you effective. So of course you would want to choose good boss.

    If you have to prioritize between them, it is not easy. My answer was to choose good boss (option 2 above). Here are the reasons I gave:

    1. You can turn boring work into work that helps your career (esp. when you have a good boss), but it is very hard to turn a bad boss into a good one.
    2. Your career depends much more on quality of boss than quality of work. This is because career depends on factors other than quality of work. For example, even if you work on a boring project, your good boss can give you opportunities to present your work to your VP, thereby giving much needed visibility.

    This also reminded me one of the hindi couplets from my textbook:

    गुरु गोबिन्द दोऊ खड़े, काको लागूँ पाय।

    बलिहारी गुरु आपने, जिन गोबिन्द दियो बताय।।

    (Teacher and God, both are standing – whose feet should I touch first?

    I bow to thee, O teacher! Who made me understand God)

    While the analogy is crude, it is worth saying: a good boss is like a teacher, a guide – he/she will help you know and understand the work, the career, the workplace. Good work is great, but not enough.

    So what about options 1 and 4? They seem obvious – 1 is strict no-no, and 4 is worth grabbing with both hands. However, it is important to keep in mind that there is no single, or correct, definition of ‘good work’ or ‘good boss’. Work good for one may be painful to another, and boss great for one may be bad for others. So if the definitions are clear, the question becomes more complicated, and even moot. Before answering this multiple-choice question, it is important to spend time on following questions:

    1. What kind of work will be good work for me at this stage of my career?
    2. What kind of boss will be good boss for me at this stage of my career?

    These are not easy questions to answer because they rely on your current career stage, career goals, and your self-awareness, but they are very important to answer if the original question is to be answered.

    What is your take on this? If you are given a choice between good boss and good work, which one will you choose?


     

  • In my last post Experiencing the product, or productizing the experience?, I talked about my experience with SiteZ and how their overall experience left much to be desired even though the core product was good enough. In this post, I will try to analyze things that went wrong which shouldn’t have.

    Here are 5 things that went wrong for SiteZ if I look from a customer’s perspective:

    1. They misled the user about the time it takes to register.
    2. They didn’t allow the user to abort the registration attempt gracefully (which left the email address behind and created rest of the mess).
    3. They were not forthcoming about who is sending me these spam emails (the email address was hidden with a display name that was the advertiser’s).
    4. They exposed a feature to me (unsubscribe) which didn’t work
    5. They didn’t give me an easy way to delete my account – emails bounced, UI didn’t have a button to delete, etc. (more…)
  • About 6 months back, I saw a print advertisement from a well-known job portal (I will call it SiteZ): “Free webinar and live chat with well-known Mr. X”. When I visited their site, they helpfully informed me that I need to be a registered user of their site (which meant I had to be someone looking for a job, which I was not), but it would take only 30 seconds to register. I didn’t mind giving 30 sec and a few bits of personal information to attend this webinar so I proceeded with registration. It took me about 2-3 minutes before I realized that this is going to take quite some time – they wanted all kinds of details about my profile, what kind of job I was looking for, what I had been doing so far in my career, etc.; simply uploading my resume didn’t SiteZ. So I abandoned my effort and tried to find a way of deleting this account I had just created. (more…)

  • When I received the following mail in my Inbox, I was excited:


    Dear Alumni,

    We are glad to announce the elections of new members of the Executive Committee of IIT Delhi Alumni Association for the year 2013. It has been noticed that there is a very thin attendance in the AGM chaired by the Director IITD and Chairman IITDAA owing to the election process and cultural programme, which is not only embarrassing but also not in the interest of the Association. To improve attendance at the AGM, the program will start at 5:00 P.M. Voting will be from 5:00-6:30 p.m. Only

     …

    -Election of Executive Committee members (During AGM)                                                    27th April 2013

    (Full text at the end of this post)

    After coming back to India in Feb 2012 to start my second innings of life, getting associated with IITD Alumni Association (IITDAA) has been on top of my mind. And being part of the executive committee is one of the best ways of getting connected and make some impact. (more…)

  • This post is a follow-up to my earlier post Creating Resumes that Work where I shared some tactics for creating purposeful resume.

    I review a large number of resumes every week – they come through ‘Get Resume Review’ section of our website (now closed), from Sunstone students, and from family and friends. I share my perspectives on resume creation with all of them and review a number of iterations of their drafts. However, it seems that telling ‘what to do’ is not enough. This post is an attempt to capture some of the important ‘what not to do’ when creating resume. There are 3 ways people lose focus on right things and end up with mediocre resumes.

    The ‘Why’ Pitfall: Focusing on showcasing your talent, and not on getting an interview call

    It is very common to find resumes full of great accomplishments, awards, experiences, buzzwords, which don’t create a compelling story for the reader. This happens because these people create resume to showcase themselves. However, this is not why a resume needs to be created. Single-most important purpose of a resume is to get you an interview call. In an interview, you will get more opportunities to showcase yourself. Eulogizing yourself is rarely the most effective means to awe the resume reader and make them curious enough to call you for an interview. Connecting to reader’s needs and wishes and connecting to their belief and values is the best way to make the reader curious.

    The ‘What’ Pitfall: Focusing on activities, and not on results

    This is most common pitfall people fall into, and many templates and samples you will find on the web perpetrate this. Frankly, no one cares about what all things you did in your prior roles. What they care about is what you accomplished for the company (or client or someone else), and how big and hard was the accomplishment. This is because activities tend to be domain-specific (what you do in a semiconductor industry to achieve growth is very different than what you need to do in an internet company for example), while results (when written like specific and measurable business outcomes) tend to be domain-agnostic (20% growth or customer sat of 4/5 mean the same in different industries). So the resume is better understood if it is written focusing on outcomes or results, than when focusing on activities.

    The ‘Who’ Pitfall: Focusing on what is important to you, and not what is important for reader

    Many resumes tend to focus on activities and accomplishments they hold dear to their heart. However, it is important to understand who you are making the resume for, and what is important to them. Many people find it hard to do, for 2 reasons:

    1. They may not know what is important for the reader, because they haven’t thought much about the reader
    2. Focusing on reader may mean dropping a few details that you hold dear, which many people find hard to accept.

    For example, if the reader is likely to look for ‘creative problem solving’ as a key skill, burying it deep inside the details and instead highlighting your team management skills doesn’t help your reader, and diminishes your chances of achieving your objective. It is important to research your reader (read job description, company profile, talk to someone in the company, etc.), and then re-prioritize your resume content by putting yourself in reader’s shoes.

    To avoid these pitfalls, it is critical to keep a keen eye on 3 areas:

    1. Purpose
    2. Results
    3. Reader

    In subsequent posts, I will present a few suggestions on how to take a resume that suffers from one or more of these pitfalls and fix them. I am also interested in hearing about what pitfalls you have come across.

    Photo Credit: freedigitalphotos.net

  • It is not easy to change your domain when changing jobs. A domain change may mean moving from a functional domain to another (say Banking to Real Estate, or semiconductors to internet) or moving from one discipline to another within the same functional domain (Developer to Product Manager, Support Engineer to Sales Person, etc.). In either of these cases, you expose yourself to a changed environment, where many of your prior experiences are rendered useless, and you are required to learn new domain very quickly. Hence, many of such changes might not work as expected.

    So why do people go for such domain changes? There are many reasons, most have something to do with your career choice. Here are a few:

    1. New domain is hot and happening, existing domain is boring and stagnant
    2. New domain offers role that old domain can’t offer, and you want that role
    3. You can perform very well in the new domain since your expertise of old domain can be leveraged.
    4. Long term career can be better developed in the new domain than in the old

    Whatever the reason for change might be, it is very important to proceed with caution and a good plan. We have posted a document Changing Domains that presents 5 steps that should be followed when changing domains – this mitigates the risk of failure, and prepares you for success.

    Photo Credit: freedigitalphotos.net

  • An effective resume presents you in an impactful way and compels the reader to invite you to an interview. It also acts as a marketing brochure for the product YOU and presents the value you offer to a prospective ‘buyer’ (employer). Therefore, it is very important to construct this document carefully and provide right information that conveys your value in the best possible manner. Quality and presentation of a resume impacts the # of interview calls you will get when you are looking for a job. It also impacts how the interviewer will perceive you – a well-written resume creates a positive bias in interviewer’s mind towards you and helps you a lot. Hence it is important to pay utmost attention to your resume and create it with good principles in mind. There are 3 things that need to be focused on:

    1. Context of the reader: There are different types of readers who read a resume and each has a unique goal and characteristic that must be factored in when creating a resume
    2. Principles of good resume writing: There are some key principles to create a good resume and they must be adhered to
    3. Creating a domain-independent resume: This is useful all the time, but becomes critical when you wish to change your domain (say banking to real estate, or semiconductor to internet).

    We have posted a document Creating Purposeful Resumes that presents this in more detail and will help you create resumes that work. You can also send your resume to us if you want to get resume review.

  • Recently, I had an opportunity to meet many test engineers from a large IT services company. These were 0-5 years experienced engineers. Here are a few comments I heard multiple times:

    I am in performance testing and I don’t know about manual testing

    I only write automation scripts (execution and reporting is done by other roles) so I don’t know about how the system performed in final results

    I was at loss for words at times. I know that IT services companies need to drive down their costs (since they find it too hard to move up the value chain of IT projects) and slicing job roles is one way of doing this. But it was first time for me to talk to people who worked in such fine slices of roles.

    Writing scripts, but not knowing about how the system performed? Calling yourself tester and not knowing manual testing? What kind of workforce are we creating? Where is the well-rounded test engineer who is supposed to be the customer advocate in the engineering team? Where is the omniscient test engineer who is supposed to be the go-to person even for the dev team regarding all the functionality of the system?

    To be clear, this is not only test team within an engineering team. Similar role slicing is happening within development, project management and other teams. This reduces cost in the same way assembly lines reduced cost of production in manufacturing sector – put all the intelligence in the line (process design) and reduce the dependency on the quality of personnel (or as Henry Ford is alleged to have said “Why is it every time I ask for a pair of hands, they come with a brain attached?”). Resources become eminently replaceable, don’t require training, and hence wages can be reduced.

    I pity those who get slotted in these slices of roles and think they are making a career by sticking to a well-known company. They don’t realize that they have stopped learning, that too so early in their career. At least in 0-5 years of a career, the goal must be to try out as many career opportunities as you can, learning a lot on the way, before taking a role which puts you in a silo (read climbing the wrong hill for a great analogy from computer science).

    I also pity the companies – it is very hard to take this bunch of employees and develop them into next set of leaders and managers. While I am sure many companies are trying to give their employees enough knowledge through training, interactions etc., there is really no substitute to on-the-job learning. While this approach to software delivery is laudable from cost cutting perspective, it can’t build long term success.

    If you are in one of these roles, reflect on your career path carefully: you may be hurting your career growth much more than you think. If you are not sure, ask yourself 3 questions:

    1. Have I learned new skills (other than maybe new domain because of new project) over last 3-6 months?
    2. Do I understand a lot about various aspects of the software I am working on?
    3. Do I know enough about the work being done by those who depend on my work, as well as whose work I depend on?

     

     

  • In a previous post 3 bad reasons to change job, I presented 3 reasons which people usually give when changing jobs, but which are really bad reasons to do so. Subsequently, I was asked what are good reasons to change jobs, and hence this post.

    A job is a promise of fair exchange between you and your organization – you promise to deliver results for the organization, and the organization promises to provide you with financial incentives in exchange. Both sides believe they get a fair deal in this bargain (which is true for any fair-market exchange). This exchange takes place through your manager, who representative organization to you, and you to the organization.

    In addition to financial incentive, you can also get non-financial ones, like learning new skills, visiting new places, meeting new people etc. which you might value a lot. In a stable state, organization gets great results delivered through you, and you get great financial and non-financial gains from the organization. Higher the alignment of non-financial gains to your career goals, higher the value you assign to these gains. Of course, this assumes that you have defined your career goals to some level of detail; if you haven’t, then you have a bigger problem to worry about!

    Manager plays a crucial role in this exchange. Organization relies on the manager to quantify the value being created by you through your results delivery (through the often dreaded performance appraisal process). You rely on the manager to derive your financial and non-financial gains from the organization. So manager is an important piece in this exchange and can strongly influence the outcome for each party.

    Given this market-style definition of a job, let me present 3 good reasons to change job. However, please note that it may not always be clear that you are encountering one or more of these. So it is always a good idea to do a simple check from time to time by asking yourself this question: Am I having fun at work, and am I looking forward to another day at work? When answers consistently come negative, it is time to investigate more.

    You give much more than you receive

    This means that your financial and non-financial gains are much less compared to what you give to the organization. This is an unfair exchange and you are losing, so you must cut your losses and move on. It is also important to keep an eye on each of the gains (financial and non-financial) even when overall gains seem fine:

    1. Very low financial gains, high non-financial gains – When your non-financial gains are high, they may compensate for your financial shortfalls. It is important to see if your financial goals are being met. If not, it is time to move on. However, if the financial stability is ensured (though your bank balance might not be growing as much as your friend’s), non-financial gains is great to have and this is a good situation to be in. Typically this situation is encountered in early phases of the career.
    2. Very low non-financial gains, high financial gains – It is important to keep an eye on the extent of non-financial gains, since they build your stock value and make you more valuable for the next company and years to come. If the non-financial component is very less, you should consider changing job even when the financial gains seem to compensate for the non-financial shortfall. An example is when you are asked to do highly repetitive/mundane work (though critical for the company) which doesn’t give you any learning but the salary is good. Keep doing it for years, and your career will get irreparable damage though your bank balance will be fine. Typically, this is encountered in middle phase of the career.

    You give much less than you receive

    This means that your financial gains are much more than what you give to the organization (since organizations don’t typically look at your non-financial gains when comparing the fair exchange value). This may sound like a contrarian advice to change the job in this situation, because it is great to get paid much more than what you offer in value. However, staying in such a situation for long makes you complacent, and vulnerable to changing market dynamics (since organization is getting much less value for its money, it is much more likely to react to get rid of you). For example, you may be a highly-paid senior employee in a company that does cutting edge technology work and your expertise is highly desirable for the company, but your salary has grown so much over the years that it hurts the company (and you may be paid much more than your peers in other industries). This will happen in niche industries where talent is scarce and deep expertise is required. This is also reached when you become too senior in the company but there is no space to grow beyond your current level.

    Your manager is not your well-wisher

    As mentioned above, manager is a crucial link in the exchange between you and the organization. When the manager doesn’t have your best interests at their heart, you are not in a place where your career can succeed, and you must change your job. There have been many cases (read my earlier post ‘Is your manager killing your career aspiration‘ to see one of the ways manager can be problematic) of managers adversely impacting a career, and when you encounter such a manager, you must change your job.

    A note on ‘change the job’ advice is in order: this doesn’t always translate into changing the company. Depending on the kind of issue you find yourself facing, sometimes it could mean moving to a new part of the organization, or taking a new role. Change is the operative word here: something must be different in the new state, and a new company is just one (though the most common) dimension that can be changed when changing a job.

    Image: FreeDigitalPhotos.net