<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by @sreejath on Medium]]></title>
        <description><![CDATA[Stories by @sreejath on Medium]]></description>
        <link>https://medium.com/@sreejath?source=rss-b7c1a20e187b------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*zLDSoR2OLBFtwKNl.jpeg</url>
            <title>Stories by @sreejath on Medium</title>
            <link>https://medium.com/@sreejath?source=rss-b7c1a20e187b------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sun, 22 Nov 2026 00:47:15 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@sreejath/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[“Has it stopped raining?”]]></title>
            <link>https://medium.com/pragmatic-fanatic/has-it-stopped-raining-5a5f488d93c9?source=rss-b7c1a20e187b------2</link>
            <guid isPermaLink="false">https://medium.com/p/5a5f488d93c9</guid>
            <category><![CDATA[rapport-building]]></category>
            <category><![CDATA[small-talk-is-big-again]]></category>
            <category><![CDATA[rapport]]></category>
            <category><![CDATA[smalltalk]]></category>
            <category><![CDATA[interview]]></category>
            <dc:creator><![CDATA[@sreejath]]></dc:creator>
            <pubDate>Sun, 29 Dec 2019 16:26:55 GMT</pubDate>
            <atom:updated>2019-12-29T16:37:40.385Z</atom:updated>
            <content:encoded><![CDATA[<blockquote>How not knowing how to answer this question cost me a plum assignment…<br>… and how you can avoid making the same mistake</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*0bvNLkBRckacwM0IJJEUUQ.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/@jackofallstreets?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Jack Finnigan</a> on <a href="https://unsplash.com/search/photos/rain?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><p>Not very long ago, I was approached about a very interesting role. It was that of a Scrum Master with a growth path to eventually becoming the Agile CoE lead. The organization was mature in terms of non-Agile delivery, but new to Agile.</p><p>I looked up the organization and the key people and was impressed with what I saw. The organization was fast growing, had a forward thinking leadership that was unafraid to take calculated risks and was extremely result focused. They had done their due diligence before deciding to pivot to agile and had a realistic understanding of what to expect both in terms of benefits and challenges.</p><p>What they needed was someone that could help them adopt Agile at a sustainable pace, help set up a CoE that would eventually become a CoP that would govern all project delivery within the organization. Based on the description, it looked like a role that I wanted to execute and I was excited about it from the get go.</p><p>The initial telephonic conversations went really well and were followed by a series of in person interviews. The final interview was with the VP that my potential manager was reporting to. By this time, everything was going well and the unspoken understanding was that the opportunity was mine to lose.</p><p>On the big day, the weather was a little unsettled. So I started early and arrived well in time. Right on time, the VP came down and introduced herself. As we were walking towards the elevators, she looked across at me and asked:</p><p><strong><em>“Has it stopped raining?”</em></strong></p><p>“Er, yes.., yes it has.”</p><p>“Oh good, because when I drove in this morning, it was raining heavily. Could hardly see three cars out front.”</p><p>“Oh, ok.”</p><p>“I feel very low energy in this kind of weather.”</p><p>“Ah, ok.”</p><p>All this while, my mind was already on the interview and I was thinking about some of the specific proposals I had prepared to address the challenges that were brought up in earlier discussions. I had kept this as a surprise addition to my answers to questions that I was reasonably confident would come up during our conversation. So, I was paying only peripheral attention to what I then thought was a desultory chat to occupy the time.</p><p>By this time, the elevator door opened, we entered and rode up to her floor in silence and went into the interview room. Over the course of the next hour, we had what I thought was a very engaging discussion about how I can help them address their challenges. While she seemed impressed by the specific proposals I had prepared, I thought I sensed a measure of reservation. However, since everything else seemed to be going well, I put it down to my nerves.</p><p>All in all, when I left the building, I was quietly confident that I had given it my best shot. And based on the feedback I had received from earlier interviews, I rated my chances of landing the role as very high.</p><p>So, imagine my surprise when I got an email in a few days saying that they have decided not to offer me the role. And to my chagrin, I saw the same role advertised on a job board, which meant that they did not go with someone else that they thought was better, rather they rejected me. The feedback I got from HR was pretty much boilerplate — your qualifications were impressive, but we decided to go in a different direction etc.</p><p>Throughout the interview process, my primary point of contact was the hiring manager (my could’ve been boss, had everything worked out). We had great rapport and were already connected on LinkedIn. After thinking it over, I sent him a note saying that regardless of the outcome, I enjoyed the opportunity to discuss the opportunity and appreciated the time and effort he spent with me. At the tail end, I asked him for his honest feedback about what went wrong.</p><p>He replied to me saying that they were all agreed that I had the skills and experience necessary to execute the role. And they were impressed with the research I had done and the proposals I presented. However, this role required establishing rapport with and influencing senior leadership. And the VP was not convinced I had the necessary soft skills to do this.</p><p>This puzzled me for a second, as I thought my conversation with her went quite well. It was only much later, that the realization hit me.</p><p><em>I had fluffed the most important question in the interview process. <br>The very first question:<br></em><strong><em>“Has it stopped raining?”</em></strong></p><p>While I was focused on my preparations for the hard skills portion of the interview, I was neglecting the soft skills portion. The small talk at the beginning of the interview was not really small.</p><p>This was a crushing disappointment and a lesson I was unlikely to forget in a hurry. While I had done extensive research on various aspects of a job interview, small talk was an area that I had not really paid attention to. I set out forthwith to address this, while the memory of the failure still stung. And when I started looking, the amount of material available on this aspect was really mind blowing.</p><p>I spent the next few weeks reading up on everything I could get my hands on about small talk in the context of a job interview. And below, I have distilled my findings and my personal opinions on this topic, with the hope that you, my reader, would find it useful.</p><h4><strong>1. Be prepared:</strong></h4><p>While this might seem like an oxymoron, it helps to be prepared. But how do you prepare for small talk?One option is to have a few safe and effective topics in your mind.<br>Here are a few topics you might want to consider.</p><p><strong><em>The Weather : </em></strong>Cliched as it might seem, there is a good reason why weather is a good topic for an ice breaker. It’s neutral, it invites comment without committing the other person to a long conversation, it allows you to judge the mood of the person you are talking to without getting personal and it can provide a segue into any number of topics. So this is a reliable stand by topic as an ice breaker. If possible segue from this to…</p><p><strong><em>The Interviewer</em></strong><em>:</em> Everyone loves to talk about themselves and their hobbies. If you know who you will be speaking to, glean as much information as you can about your interviewer and use this to narrow down on topics that you might have a common interest in. If you don’t know ahead of time, then have some topics that are likely to interest a generic person who will be interviewing you. One such topic could be…</p><p><strong><em>The Organization</em>: </strong>The next logical topic for conversation is the organization you are interviewing with. Has something interesting happened in their market? Have they made any interesting moves? It’s a little tricky to work this into an initial introduction, but if an opening presents itself, definitely something to talk about. As a side benefit this also highlights your interest in the organization and the role. A nice segue from this would be…</p><p><strong><em>The Surroundings</em></strong>: Saw something interesting in the lobby? Something you saw on the way you drove in? All legitimate topics. Remember, the idea is to lubricate the social interaction so that the transition to the hard skills part is seamless and pleasant. The specific topic itself is only of peripheral importance. <br>And if you really, really cannot think of anything else, there is always…</p><p><strong><em>Current Affairs/Sports: </em></strong>It might seem counter intuitive to spend time reading up on the news on the day of a big interview. After all, shouldn’t you be better off brushing up on the key skills portion or making sure you have covered all the “hooks” (more on this in another article) in your resume? However, the news can provide rich fodder for small talk, provided you…</p><h4><strong><em>2. Avoid controversial topics</em></strong></h4><p>There are certain topics (politics and religion being two of them) that are best left outside of the work setting. Not only should you avoid bringing them up, but you should also tactfully deflect the conversation if the interviewer brings it up, like it happened to me once.</p><p>However, quite often, by trying to be agreeable, people <em>pretend </em>to agree, but really you should…</p><h4><strong>3. Be genuine</strong></h4><p>The purpose of small talk is to establish rapport. And nothing robs a situation of rapport like insincerity. So, if your interviewer is a ballet fan and you think Arabesque is a type of coffee, please don’t pretend to love ballet. You might manage to fool the interviewer for now, especially if you have done some upfront research. But, remember, if things go well, you could be working this person for years. How long can you keep up the charade? I would leave it to you to imagine the impact on your credibility, when they realize you were just pretending to be interested in something to score points with them. The best thing to do would be to acknowledge the interviewer’s interest, admit (in a self deprecating manner) your lack of knowledge on the subject, and if it seems appropriate, gracefully pivot to another topic.</p><p>One way to be be genuine is to…</p><h4><strong>4. Be curious</strong></h4><p>Quite often, we are so wrapped up in our own thoughts and nervous about the interview, that we set aside our natural curiosity. This is a shame, as we could discover literally dozens of things to make small talk about if only we pay attention. It could be some thing as simple as asking follow up questions to the comments made as part of saying hello. If the interviewer says they had a busy morning, perhaps you might want to follow up and ask if they are working on something new and exciting. This demonstrates both an interest in the interviewer as a person and interest in what is going on within the organization.<br>Additionally, while engaging in small talk, you should always…</p><h4><strong>5. </strong>Ready to take initiative if needed</h4><p>Occasionally, you might meet someone that doesn’t initiate any small talk at all. What should you do? Skip the whole small talk routine? Not necessarily. It could be that they are introverted and not good at small talk, or it could be a test to see if you are capable of initiating small talk yourself. In either case, you should at least make an attempt to initiate small talk. At best, this could allow a normally reclusive person to open up and make your interaction more positive, at worst, you observe the basic etiquette and establish that the person is not interested in making small talk. In either case you would be better off than if you had just kept quiet and let the silence build.</p><p>However, while engaging in small talk, you should always…</p><h4><strong>6. </strong>Read the cues</h4><p>While engaging with the interviewer, you should pay attention to their cues, both verbal and non-verbal indicating their level of interest in pursuing a topic or with the small talk in general. Perhaps the interviewer is uncomfortable answering a question you posed, perhaps you get the sense that they want to move on to the hard skills portion of the interview, or they really want to spend more time getting to know you better. <br>Based on your reading of the cues, you should …</p><h4>7. Maintain the flow</h4><p>The purpose of small talk is to provide initial lubrication to the interaction between two people who do not know each other well (or even, at all). And one of the key features of a good interaction is how the conversation flows. Abrupt changes in direction, conversational dead ends are things you must keep an eye out for and strive to avoid as much as is possible. <br>And to be able to do that, and do that seemingly effortlessly, the one thing you must do is to…</p><h4>8. Practice</h4><p>As the saying goes: <em>“Practice makes perfect.”<br></em>And while I almost certainly will not become “perfect” at small talk, a little bit of practice has improved my competence in indulging in small talk to an astonishing (for me) degree. And the good thing is that the opportunities are always there in front of us. Right from the person who is serving you at the coffee shop to casual acquaintances you meet at a social function, you get to practice making small talk multiple times a day. So use each opportunity you get and see what a difference it makes to your skills.</p><h4><strong>Conclusion</strong></h4><p>Establishing rapport in a short period of time is critical in making a positive impression during a job interview. The ability to indulge in small talk is a key skill that makes this possible. Fortunately, making small talk is a skill that can be easily learnt and polished with some amount of preparation and practice. So, next time someone asks you “Has it stopped raining?”, you know how to answer! :-)</p><h4>Bonus</h4><p>One topic that I stumbled upon while researching small talk was “Coded Conversations”. For me, this cleared up that one nagging question I had after spending two years in the UK. Why do British people speak so much about the weather. If you had the same question, then, well, wonder no more, the answer is in the page linked to below:</p><p><a href="http://www.bbc.com/future/story/20151214-why-do-brits-talk-about-the-weather-so-much">Why do Brits talk so much about the weather</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5a5f488d93c9" width="1" height="1" alt=""><hr><p><a href="https://medium.com/pragmatic-fanatic/has-it-stopped-raining-5a5f488d93c9">“Has it stopped raining?”</a> was originally published in <a href="https://medium.com/pragmatic-fanatic">Pragmatic Fanatic</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Project Manager vs Scrum Master]]></title>
            <link>https://medium.com/pragmatic-fanatic/project-manager-vs-scrum-master-8e05075c0a39?source=rss-b7c1a20e187b------2</link>
            <guid isPermaLink="false">https://medium.com/p/8e05075c0a39</guid>
            <category><![CDATA[scrum]]></category>
            <category><![CDATA[project-manager]]></category>
            <category><![CDATA[project-management]]></category>
            <category><![CDATA[scrum-master]]></category>
            <category><![CDATA[agile]]></category>
            <dc:creator><![CDATA[@sreejath]]></dc:creator>
            <pubDate>Sun, 29 Sep 2019 14:55:46 GMT</pubDate>
            <atom:updated>2019-09-29T14:55:46.696Z</atom:updated>
            <content:encoded><![CDATA[<p>The difference: in one sentence</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/0*HbRLzfNNaHURrewa" /></figure><p>One day, I was discussing Agile and Scrum with a group of colleagues, when one person asked me:</p><p><strong>“What is the key difference between a Scrum Master and a Project Manager?”</strong></p><p>I spoke about the servant leadership and facilitation aspects of the Scrum Master role and contrasted this with the more command and control role of a Project Manager.</p><p>While they seemed satisfied, I got this nagging feeling that there is something more fundamental that I was missing.</p><p>It was only later that it came to me. While the above aspects are important, the key difference between a Scrum Master and Project Manager is the lens through which they look at every decision they make related to the project.</p><p><strong>Every time a decision needs to be made, the project manager asks: “How will this affect my plan?” whereas the Scrum Master asks: “How will this affect my product?” <br></strong>The Project Manager will strive to make decisions that will keep maintain the integrity of the existing plan, while the Scrum Master will look to maximize the value delivered to the client regardless of what the original plan was.</p><p>The Project Manager will look for predictability and control, while the Scrum Master will look for opportunities to maximize value even if it means modifications to original plan.</p><p>This does not mean, of course that either role is better or worse, just that the roles (and the delivery models used) should be matched to the needs of the project and stakeholder expectations.</p><p>If you need a very clearly defined scope with low probability of change delivered on a specific date and with a specific budget, plan based delivery led by a good Project Manager increases the probability that the project will be successful.</p><p>However, if your product exists in a dynamic space where the stakeholder expectations evolve during the course of the project and the focus is on maximizing value delivered, an Agile project led by a competent Scrum Master is more likely to offer the required flexibility.</p><p>How has been your experience with Plan based/Agile projects in terms of predictability and flexibility? Please share your thoughts in comments below.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8e05075c0a39" width="1" height="1" alt=""><hr><p><a href="https://medium.com/pragmatic-fanatic/project-manager-vs-scrum-master-8e05075c0a39">Project Manager vs Scrum Master</a> was originally published in <a href="https://medium.com/pragmatic-fanatic">Pragmatic Fanatic</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Why “Tell me about the most…” gets you bad hires]]></title>
            <link>https://medium.com/pragmatic-fanatic/why-tell-me-about-the-most-gets-you-bad-hires-24be96379f21?source=rss-b7c1a20e187b------2</link>
            <guid isPermaLink="false">https://medium.com/p/24be96379f21</guid>
            <category><![CDATA[recruiting]]></category>
            <category><![CDATA[handle-job-interviews]]></category>
            <category><![CDATA[hiring]]></category>
            <category><![CDATA[jobs]]></category>
            <dc:creator><![CDATA[@sreejath]]></dc:creator>
            <pubDate>Sun, 13 Nov 2016 05:28:05 GMT</pubDate>
            <atom:updated>2016-11-13T05:28:05.618Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*eVTsHqSKt4Y881T2mlftFQ.jpeg" /></figure><p>One comment I received for <a href="https://medium.com/@sreejath/don-t-interview-your-next-hire-801239e23a10#.pgigxsrr9">my earlier article </a>on why you shouldn’t interview your next hire(<a href="https://www.linkedin.com/pulse/dont-interview-your-next-hire-sreejath-sreeraman">originally published on LinkedIn</a>), was that there is a far quicker and simpler way to identify a potential good hire. They were referring to the <em>“Tell me about the most …” </em>question.</p><p>This is a commonly used interview approach, but just in case this is new to you, here is how it is supposed to work:</p><p>You ask the candidate to tell you about the most complex, biggest, toughest, <em>&lt;insert adjective of your choice here&gt; </em>role they have executed. Once you get an overview, you drill down into each aspect of the role until you get a sense of how much the person has really contributed.</p><figure><a href="http://bit.ly/2g16MXK"><img alt="" src="https://cdn-images-1.medium.com/max/232/1*CIF_blyDhxQSQhkL_1ZREg.png" /></a><figcaption><a href="http://bit.ly/2g16MXK">Don’t Interview Your Next Hire</a></figcaption></figure><p>In theory, this is a much quicker way to identify a good candidate because you don’t have to go through all the trouble of setting up a real life scenario, and it gets you better information than standard technical/behavioral/scenario based questions.</p><p>While this approach seems good <strong><em>in theory</em></strong>, it doesn’t hold up quite that well in actual practice. Here’s why:</p><p>First and foremost, there is the <strong>information asymmetry </strong>problem. When you ask a candidate to describe a project <strong><em>they </em></strong>have worked on, by definition, they have more information about the role than you do or can hope to gain during the course of an hour by merely asking questions. This affects your ability to assess their contributions objectively as the information you can glean from the interview is less complete and of a lower quality than what you could obtain by watching them actually execute their role.</p><p>Secondly, this question has now become a staple, and most serious candidates prepare for this. While this in itself is not bad, the problem is that many people cannot resist the temptation to <em>cross the line and embellish their achievements </em>and pass off others’ achievements as their own. And while you can trip up the occasional under-prepared candidate with follow up questions, it is very difficult, if not impossible to identify a well prepared candidate, who is making things up.</p><p>Last, but certainly not the least, even if the candidate is truthful and/or you are confident in your abilities to assess someone using this method, what you get out of this process is their version of how they performed in a past role. However, what you are looking to assess is how they can help you in your present (and future) circumstances. And while past performance can be a valuable input, it is not as predictive as having them solve real world problems for you in your environment.</p><p>Have you ever tried interviewing anyone where you asked them to “Tell me about the …” How was your experience? <br>How about having someone execute real world tasks? If you have tried both, have you noticed any tangible difference between the two? Is one better/worse than the other, in your opinion?</p><p>Please share your thoughts in the comments.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=24be96379f21" width="1" height="1" alt=""><hr><p><a href="https://medium.com/pragmatic-fanatic/why-tell-me-about-the-most-gets-you-bad-hires-24be96379f21">Why “Tell me about the most…” gets you bad hires</a> was originally published in <a href="https://medium.com/pragmatic-fanatic">Pragmatic Fanatic</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Interesting light at dusk last week]]></title>
            <link>https://medium.com/@sreejath/interesting-light-at-dusk-last-week-a2cd14ae9747?source=rss-b7c1a20e187b------2</link>
            <guid isPermaLink="false">https://medium.com/p/a2cd14ae9747</guid>
            <category><![CDATA[nofilter]]></category>
            <category><![CDATA[missisauga]]></category>
            <category><![CDATA[no-edits]]></category>
            <dc:creator><![CDATA[@sreejath]]></dc:creator>
            <pubDate>Sat, 03 Sep 2016 03:24:20 GMT</pubDate>
            <atom:updated>2016-09-03T03:24:20.302Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*VzL2JpGw_d6yD_fLVaHd8g.jpeg" /><figcaption>Mississauga Skyline</figcaption></figure><p>Interesting light at dusk last week</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a2cd14ae9747" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Don’t Interview Your Next Hire]]></title>
            <link>https://medium.com/pragmatic-fanatic/don-t-interview-your-next-hire-801239e23a10?source=rss-b7c1a20e187b------2</link>
            <guid isPermaLink="false">https://medium.com/p/801239e23a10</guid>
            <category><![CDATA[talent-acquisition]]></category>
            <category><![CDATA[interviewing]]></category>
            <dc:creator><![CDATA[@sreejath]]></dc:creator>
            <pubDate>Sun, 11 Oct 2015 16:13:31 GMT</pubDate>
            <atom:updated>2016-11-12T11:12:01.770Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/698/1*QTF-oZOTid87HkQZPlT4lg.png" /></figure><p><em>This article was originally published on </em><a href="https://www.linkedin.com/pulse/dont-interview-your-next-hire-sreejath-sreeraman"><em>LinkedIn</em></a></p><p><strong>So you have a position that you need to fill…</strong></p><p>You have looked for suitable people within your organization, tapped contacts for referrals, advertised on job boards and have winnowed the resulting avalanche of profiles down to a handful of people that you think might be able to execute the role you have.</p><p><strong>What do you do next?</strong><br>If you are like most hiring managers, you interview the shortlisted people and make your decision based on how each person performs during the interview.</p><p><strong>Here is the problem with this approach…<br></strong>Barring a few exceptions (direct selling comes to mind), there is a very weak correlation between performing well in an interview and performing well on the job. Taking programming as an example, there are many first class programmers stuck in roles well below their potential, simply because they do not interview well. And there are multitudes of mediocre programmers who are hired largely on the basis of their interviewing skills, who then proceed to muck up on the job and give their PMs grey hairs and ulcers.</p><p><strong>So, how do we get around this problem?<br></strong>Do not interview your next hire. At least, not in the classic question-answer format. Instead, when you bring them in, pair them up with someone that is executing a similar role (preferably in the same/closely related team) and have them solve a real world problem or execute a set of tasks they would need to do, if they are hired. You can observe/participate if you’d like, or even conduct this if this person will be working in your team. If you do this, you can figure out pretty quickly if this person is a good fit for the role.</p><p><strong>But this takes too much time….<br></strong>Not really…<br>Sure, evaluating someone by having them perform real world tasks requires that you be prepared to invest more time upfront. However, the quality of the information you get is significantly better that what you can reasonably expect to obtain from merely talking to a person. This would help you in making better hiring decisions. Also, have you thought about the amount of time you would have to spend cleaning up the damage wreaked by a poor hire, and the time you will have to spend replacing them (with another potential poor hire)?</p><p>Also, if a candidate is obviously not suited for the role, then you will figure this out quite early on in the process. If you establish a routine to gracefully end the process as quickly as is possible when you decide that the candidate is an obvious misfit for the role, the initial time commitment across multiple candidates (good and bad)might be about the same as that for a conventional interview process. In fact, if you plan to screen more than four people, the aggregate time you spend choosing the right candidate might even be less than the time you will spend talking to them.</p><p><strong>This won’t work for the role I have open…<br></strong>One objection I often hear is: “But, how about roles with responsibilities that don’t fit well into this format?” It is true that not all job functions for all jobs can be adapted to this format. However, most jobs, especially in IT have significant components that fit into this format.<br>So, let us say you are hiring a Project Manager. You can give them a baseline project plan, the current status (presumably of a project in trouble) and a set of constraints and ask them to put together a recovery plan. You can then ask them to sell this to a “Steering Committee”. You can set up a meeting with the classic “Difficult Stakeholder” and observe them operate under pressure. The list can go on, but you get the idea.</p><p>Does the above require more forethought, effort and commitment from your part? It sure does. But, will it help you zero in on the best available candidate? I think it does, and I believe that once you try it out, you will agree.</p><p>I am always looking for ways to improve how I identify, screen and select top talent. So, please share your thoughts in comments below.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=801239e23a10" width="1" height="1" alt=""><hr><p><a href="https://medium.com/pragmatic-fanatic/don-t-interview-your-next-hire-801239e23a10">Don’t Interview Your Next Hire</a> was originally published in <a href="https://medium.com/pragmatic-fanatic">Pragmatic Fanatic</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Microsoft Abolishes Stack Ranking]]></title>
            <link>https://medium.com/@sreejath/microsoft-abolishes-stack-ranking-608a1f89c6ae?source=rss-b7c1a20e187b------2</link>
            <guid isPermaLink="false">https://medium.com/p/608a1f89c6ae</guid>
            <dc:creator><![CDATA[@sreejath]]></dc:creator>
            <pubDate>Tue, 17 Dec 2013 04:24:42 GMT</pubDate>
            <atom:updated>2013-12-18T06:10:39.141Z</atom:updated>
            <content:encoded><![CDATA[<h4>How does this affect you?</h4><p>A couple of days ago, <a href="http://j.mp/1fuAIni">Microsoft announced </a>that they are eliminating the stack ranking method used to rate employees. For those not familiar with the term, <a href="http://j.mp/I51ROI">Stack Ranking</a> is an Employee Evaluation and Rating tool designed by Jack Welch at GE. Also called “Forced Ranking”, it compels the supervisor to rate all their resources in a stack. Once this done, the bottom 10% are marked as Low Performers and (based on the circumstances) are required to undergo performance improvement measures or leave.</p><p>While Jack credits this tool with improving the efficiency at GE dramatically, it has several glaring shortcomings which are widely known. But despite this, many professionally run, large organizations have been using this evaluation method, for the want of a better alternative to manage performance evaluation for large groups of people.</p><p>Microsoft is abandoning this system because in their experience, the stack ranking method “leads to employees focusing on competing with each other, rather than competing with other companies.” In fact in August 2012, Vanity Fair published a <a href="http://j.mp/17aB2Tb">stinging critique</a> in which it detailed how this method has harmed Microsoft.</p><p>While details about the new performance evaluation tool are sketchy at best, an internal memo, published by the Seattle Times, explains that the new approach will have three elements: Greater emphasis on teamwork and collaboration; better and more frequent feedback to employees about performance; and most importantly, elimination of the bell curve.</p><p>One thing is certain. If MS can put an alternative in place that works, then the other companies should take a long hard look at that model and see if there are elements that make sense to them.</p><p>What are your thoughts on Stack ranking as a performance evaluation tool? Have you used/seen any other structured performance evaluation tools in your career that you think are better?</p><p>Please share your thoughts in the comments.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=608a1f89c6ae" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>