<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>The Indian School of Business Weblog &#187; McK</title>
	<atom:link href="http://isbweblog.com/tag/mck/feed/" rel="self" type="application/rss+xml" />
	<link>http://isbweblog.com</link>
	<description>The ISB Students&#039; Blog</description>
	<lastBuildDate>Fri, 20 Aug 2010 08:09:44 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0</generator>
		<item>
		<title>McKinsey Case preparatory workshop &#124; 22nd November 2008</title>
		<link>http://isbweblog.com/2008/11/25/mckinsey-case-preparatory-workshop-22nd-november-2008/</link>
		<comments>http://isbweblog.com/2008/11/25/mckinsey-case-preparatory-workshop-22nd-november-2008/#comments</comments>
		<pubDate>Tue, 25 Nov 2008 14:03:15 +0000</pubDate>
		<dc:creator>Prashant</dc:creator>
				<category><![CDATA[Club Blogs]]></category>
		<category><![CDATA[Consulting Club]]></category>
		<category><![CDATA[Class of 2009]]></category>
		<category><![CDATA[McK]]></category>

		<guid isPermaLink="false">http://isbweblog.com/?p=872</guid>
		<description><![CDATA[Nigel Andrade, Partner â€“ McKinsey Singapore, flew down to ISB for a session on case preparation with the batch. The key takeaways from this session could be summarized as follows: Basic approach The interview is a conversation not a Q&#38;A Go in with a peer mindset not a job seeker Talking about yourself : focus [...]]]></description>
			<content:encoded><![CDATA[<p>Nigel Andrade, Partner â€“ McKinsey Singapore, flew down to ISB for a session on case preparation with the batch. The key takeaways from this session could be summarized as follows:</p>
<p class="MsoNormal"><strong>Basic approach</strong></p>
<ol type="1">
<li class="MsoNormal"><span>The interview is a conversation not a Q&amp;A</span></li>
<li class="MsoNormal"><span>Go      in with a peer mindset not a job seeker</span></li>
<li class="MsoNormal"><span>Talking      about yourself : focus on what drives you and how does that fit with the      profession / company </span></li>
<li class="MsoNormal"><span>Have      a clear vision: Where do you want to be 5 years down the line? Be honest</span></li>
</ol>
<p class="MsoNormal"><span>Â <strong>What does McKinsey look for?</strong></span></p>
<ol type="1">
<li class="MsoNormal"><span>Problem      solving horse power : Structured thought process and incisivenessÂ <span><span>-<span>Â </span></span></span>(evaluated through CV and case interviews)</span></li>
<li class="MsoNormal"><span>Leadership      : Sight live instancesÂ <span>(evaluated through CV and PI)</span></span></li>
<li class="MsoNormal"><span>Drive      and aspirations: Do you have risk appetite, have you pushed the envelopeÂ <span>(evaluated through CV and PI)</span></span></li>
<li class="MsoNormal"><span>Presence      : Can you hold a conversation with the CEOÂ <span>(evaluated through PI)</span></span></li>
</ol>
<p class="MsoNormal"><em><span>On a three point scale you need to score the max on one of the top 3 above, and 2 on all others.</span></em></p>
<p class="MsoNormal"><span>Â <strong>Case cracking process</strong></span></p>
<p class="MsoNormal"><em><span>Problem definition, Structuring, Solution, Synthesis </span></em></p>
<p>- Â  Â  Â  Â Process      is key not the solution, make the experience worth remembering for the      interviewer<br />
- Â  Â  Â  Â Be      careful of assumptions you make when you believe you are familiar with the      sector</p>
<ul>
<li><strong>Problem      definition<span style="normal;"></span></strong></li>
</ul>
<p><span><span>a)<span>Â Â Â  </span></span></span><span>Goal is to arrive at : What are you solving for ?</span></p>
<p class="MsoNormal"><span><span>b)<span>Â Â  Â B</span></span></span><span>oard level question thinking, CEO Level thinking </span></p>
<p class="MsoNormal"><span><span>c)<span>Â Â Â Â  </span></span></span><span>Opening questions important</span></p>
<p class="MsoNormal"><span><span>d)<span>Â Â Â  </span></span></span><span>Donâ€™t spend too much time here but don&#8217;t rush through this phase too</span></p>
<p class="MsoNormal"><span>Other pointers</span></p>
<p class="MsoNormal"><span><span>a.<span>Â Â Â Â  </span></span></span><span>Be natural and curious </span></p>
<p class="MsoNormal"><span><span>b.<span>Â Â Â Â  </span></span></span><span>Donâ€™t get into why, what, immediately</span></p>
<p class="MsoNormal">Â </p>
<ul>
<li><strong>Structuring</strong></li>
</ul>
<p><span><span>a)<span>Â Â Â  </span></span></span><span>MECE is litmus test, have you got your hands around it?</span></p>
<p class="MsoNormal"><span><span>b)<span>Â Â Â  </span></span></span><span>Structure is about what to look for, and not how you will solve the problem</span></p>
<p class="MsoNormal"><span><span><span><span>c) Â  Â </span></span></span>Try to understand the background of the problem</span></p>
<p class="MsoListParagraph">Other Pointers</p>
<p class="MsoNormal"><span><span>a.<span>Â Â Â Â  </span></span></span><span>Donâ€™t ask a barrage of questions like a check list</span></p>
<p class="MsoNormal"><span><span>b.<span>Â Â Â Â  </span></span></span><span>Donâ€™t fit framework </span></p>
<p class="MsoNormal">Â </p>
<ul>
<li>Â <strong>Solution</strong></li>
</ul>
<p class="MsoNormal"><span><span>a)<span>Â Â Â  </span></span></span><span>Take a systemic view.</span></p>
<p class="MsoNormal"><span><span>b)<span>Â Â Â  </span></span></span><span>Still ask questions while being creative about solving problems </span></p>
<p class="MsoNormal"><span>Other Pointers</span></p>
<p class="MsoNormal"><span><span>a.<span>Â Â Â Â  </span></span></span><span>Creativity matters. Use logic and be pragmatic</span></p>
<p class="MsoNormal"><span><span>b.<span>Â Â Â Â  </span></span></span><span>Donâ€™t be bland</span></p>
<p class="MsoNormal"><span><span>c.<span>Â Â Â Â  </span></span></span><span>Get provocative ideas</span></p>
<p class="MsoNormal"><span>d. Â  Â  Ideal stage to test the boundary condition of the case</span></p>
<p class="MsoNormal">e. Â  Â  Don&#8217;t get lured into giving recommendations too early into the case</p>
<p class="MsoNormal">Â </p>
<ul>
<li><strong>Synthesis is      not summary</strong></li>
</ul>
<p class="MsoNormal"><span><span>a)<span>Â Â Â  </span></span></span><span>Synthesis is not summary</span></p>
<p class="MsoNormal"><span><span>b)<span>Â Â Â  </span></span></span><span>Two step process : Reframe problem, Plausible solution, Trade-offs</span></p>
<p class="MsoNormal">c) Â  Â  Don&#8217;t take a laundry list approach</p>
]]></content:encoded>
			<wfw:commentRss>http://isbweblog.com/2008/11/25/mckinsey-case-preparatory-workshop-22nd-november-2008/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
