<?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>mikelally.net &#187; operations</title>
	<atom:link href="http://mikelally.net/blog/category/operations/feed/" rel="self" type="application/rss+xml" />
	<link>http://mikelally.net/blog</link>
	<description></description>
	<lastBuildDate>Sat, 19 May 2012 11:59:16 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
		<item>
		<title>Running A Successful Turnaround: Final Thoughts</title>
		<link>http://mikelally.net/blog/running-a-successful-turnaround-final-thoughts/</link>
		<comments>http://mikelally.net/blog/running-a-successful-turnaround-final-thoughts/#comments</comments>
		<pubDate>Thu, 12 Aug 2010 11:29:34 +0000</pubDate>
		<dc:creator>mikelally</dc:creator>
				<category><![CDATA[change]]></category>
		<category><![CDATA[operations]]></category>
		<category><![CDATA[tools]]></category>
		<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[finance]]></category>
		<category><![CDATA[leadership]]></category>
		<category><![CDATA[management]]></category>
		<category><![CDATA[running a successful turnaround]]></category>
		<category><![CDATA[sales]]></category>
		<category><![CDATA[systems]]></category>

		<guid isPermaLink="false">http://mikelally.net/blog/?p=695</guid>
		<description><![CDATA[I have been working on a series of posts detailing my thoughts on how I would fix or turn around a business operation. We&#8217;ve talked about financials, how to get a handle on your customers and understanding youremployees in an effort to get them more engaged, and finally, we talked about processes. When you walk into a situation [...]]]></description>
			<content:encoded><![CDATA[<div name="googleone_share_1" style="position:relative;z-index:5;float: right; margin-left: 10px;"><g:plusone size="tall" count="1" href="http://mikelally.net/blog/running-a-successful-turnaround-final-thoughts/"></g:plusone></div><div class="tweetmeme_button" style="float: right; margin-left: 10px;">
			<a href="http://api.tweetmeme.com/share?url=http%3A%2F%2Fmikelally.net%2Fblog%2Frunning-a-successful-turnaround-final-thoughts%2F"><br />
				<img src="http://api.tweetmeme.com/imagebutton.gif?url=http%3A%2F%2Fmikelally.net%2Fblog%2Frunning-a-successful-turnaround-final-thoughts%2F&amp;source=mikelally&amp;style=normal&amp;b=2" height="61" width="50" /><br />
			</a>
		</div>
<p>I have been working on a <a href="http://mikelally.net/tag/running-a-successful-turnaround/">series of posts</a> detailing my thoughts on how I would fix or turn around a business operation. We&#8217;ve talked about <a href="http://mikelally.net/?p=467">financials</a>, how to get a handle on your <a href="http://mikelally.net/?p=636">customers</a> and understanding your<a href="http://mikelally.net/blog/?p=638">employees</a> in an effort to get them more engaged, and finally, we talked about processes.</p>
<p>When you walk into a situation that requires immediate improvements, you have to start the triage process almost immediately. Michael Watkins will tell you to wait 30 days of your first 90 days. I&#8217;m not sure I have ever been afforded that kind of time. <img src='http://mikelally.net/blog/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
<p>I like to get my hands around data quickly. If the data I want isn&#8217;t currently being collected, the first step is to begin the process of pulling it together. This is always coupled by what the military folks are calling HUMINT. Human Intelligence. Talk to everyone. Make sure you are getting the raw feed so to speak. Make sure it isn&#8217;t filtered by management.</p>
<p>You need both facts and data and the human take on things. You can make data support your assumptions. By the way, try not to have assumptions. Try to begin with an open mind. Let the stories unfold.</p>
<p>I like the term &#8220;Key Performance Indicators&#8221; or KPIs. I want to see</p>
<p><strong>Financial KPIs:</strong><br />
Revenue<br />
Operations Costs<br />
Profit<br />
Contribution Margin<br />
DSO. Days Sales Outstanding.</p>
<p>I also would want to see the standard balance sheet/cash flow reports. But I am trying to take this from a purely operational point of view. You may not have access to the big picture. You can only control your own environment.</p>
<p>I want to see financials reported by customer. I want to see them reported by team. You will gain knowledge from those two views. We want to know our most profitable customers (not necessarily the customers bringing in the most revenue). I want to know who is COSTING us money. Because we may want to fire them. Gently, of course.</p>
<p><strong>Customer KPIs</strong></p>
<p>I know. I originally said 6 questions. Its 7. Those questions are:</p>
<p>1. Courtesy of the Whomever You Interact With Most Frequently (support person, billing, customer service, field service, delivery person, sales person, account manager, CEO)</p>
<p>2. Skills and Knowledge of Whomever You Interact With Most Frequently</p>
<p>3. Quality of the Resolution</p>
<p>4. Timeliness of the Resolution</p>
<p>5. Overall Experience</p>
<p>6. Additional Feedback – open ended feedback</p>
<p>7. Net Promoter Score. “Would you refer us to someone else?”</p>
<p>Day 1 &#8211; every customer gets these questions. Then quarterly. Sometimes monthly. Track results.</p>
<p><strong>Employee KPIs</strong><br />
Two sets of feedback here. Sit down with everyone. One on one. Ask them 3 questions:</p>
<ol>
<li>What are we doing well?</li>
<li>What are we doing poorly?</li>
<li>If you could fix one thing right now, what would it be?</li>
</ol>
<p>When you have a good percentage of the people interviewed. Start listing action plans on things we are going to fix. FOLLOW THROUGH. Seriously, if you don&#8217;t follow through, just stop reading. Go play Farmville.</p>
<p>The second piece is more formal &#8211; quantitative. Employee Satisfaction Surveys. Everyone can groan now. Again&#8230;short and simple. 5 questions and a section for feedback. NOT ANONYMOUS. I hate anonymous.</p>
<p>1. In the past seven days, have I received recognition or praise for doing good work?<br />
2. Are my coworkers committed to doing quality work?<br />
3. Do I have a best friend at work?<br />
4. In the past 6 months, has someone at work talked to me about my progress?<br />
5. This past year, have I had the opportunities at work to learn and grow?</p>
<p><strong>Process KPIs/Production</strong></p>
<p>You have to roll up your sleeves and understand what is happening in your operation. Your KPIs will vary here &#8211; each team will have a different set of productivity measurements. Sales will have contacts converting to leads and leads converting to sales. Support will have first call closure (number of times a customer has to re-contact you on the same issue). Every unit should be tracking their local version of the company focused numbers: Revenue, Profit, Contribution Margin, ESat, CSat, DSO.</p>
<p>I just watched a show that follows the New York Jets (football) around through Training Camp. The first episode starts out with the head coach, Rex Ryan, listing the teams goals for the season. WIN MORE GAMES THAN ANYONE ELSE. The defense&#8217;s goals for the year: WIN MORE GAMES THAN ANYONE ELSE. The special team&#8217;s goals for the season: you guessed it. I love the singular KPI. The One Number.</p>
<p>Another handy tool I forgot to mention in the process post is a <a href="http://www.mindtools.com/pages/article/newTMC_05.htm">SWOT analysis</a>. You may even want to bring in someone from the outside to facilitate this activity. I&#8217;ve found that bias can certainly creep in. You can steer the analysis to support your theories. Facts and data people. Facts and data.</p>
<p>I hope you have enjoyed this series of posts. It has been very interesting for me to go through this exercise. I am sure I will have reason to edit and modify as time marches on. Please discuss in the comments. Ask questions! I will be happy to take a shot at answering.</p>
<h2  class="related_post_title">If you liked this post, try these...</h2><ul class="related_post"><li><a href="http://mikelally.net/blog/case-study/" title="Case Study">Case Study</a></li><li><a href="http://mikelally.net/blog/running-a-successful-turnaround-process-improvements/" title="Running A Successful Turnaround: Process Improvements">Running A Successful Turnaround: Process Improvements</a></li><li><a href="http://mikelally.net/blog/running-a-successful-turnaround-the-employee-view/" title="Running a Successful Turnaround: The Employee View">Running a Successful Turnaround: The Employee View</a></li></ul>]]></content:encoded>
			<wfw:commentRss>http://mikelally.net/blog/running-a-successful-turnaround-final-thoughts/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Running A Successful Turnaround: Process Improvements</title>
		<link>http://mikelally.net/blog/running-a-successful-turnaround-process-improvements/</link>
		<comments>http://mikelally.net/blog/running-a-successful-turnaround-process-improvements/#comments</comments>
		<pubDate>Sun, 01 Aug 2010 12:25:13 +0000</pubDate>
		<dc:creator>mikelally</dc:creator>
				<category><![CDATA[change]]></category>
		<category><![CDATA[management]]></category>
		<category><![CDATA[operations]]></category>
		<category><![CDATA[tools]]></category>
		<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[running a successful turnaround]]></category>

		<guid isPermaLink="false">http://mikelally.net/blog/?p=685</guid>
		<description><![CDATA[I have been working on a series of posts detailing my thoughts on how I would fix or turn around a business operation. I would take a stab at a scenario an MBA candidate/intern threw at me. So far we have talked about financials, how to get a handle on your customers and understanding your employees [...]]]></description>
			<content:encoded><![CDATA[<div name="googleone_share_1" style="position:relative;z-index:5;float: right; margin-left: 10px;"><g:plusone size="tall" count="1" href="http://mikelally.net/blog/running-a-successful-turnaround-process-improvements/"></g:plusone></div><div class="tweetmeme_button" style="float: right; margin-left: 10px;">
			<a href="http://api.tweetmeme.com/share?url=http%3A%2F%2Fmikelally.net%2Fblog%2Frunning-a-successful-turnaround-process-improvements%2F"><br />
				<img src="http://api.tweetmeme.com/imagebutton.gif?url=http%3A%2F%2Fmikelally.net%2Fblog%2Frunning-a-successful-turnaround-process-improvements%2F&amp;source=mikelally&amp;style=normal&amp;b=2" height="61" width="50" /><br />
			</a>
		</div>
<p>I have been working on a <a href="../tag/running-a-successful-turnaround/">series of posts</a> detailing my thoughts on how I would fix or turn around a business  operation. I would take a stab at a scenario an MBA candidate/intern  threw at me. So far we have talked about <a href="../?p=467">financials</a>, how to get a handle on your <a href="../?p=636">customers</a> and understanding your <a href="http://mikelally.net/blog/?p=638">employees</a> in an effort to get them more engaged.</p>
<p>Today we will talk about processes. Specifically understanding your processes and then applying continuous improvement to those processes. For those just joining, our hypothetical situation is a manufacturing operation that is in need of being turned around.My background is service operations. I have spent a lot of time in call centers in the financial services, telecom, and BPO industries. I&#8217;ve run customer service, technical support, inbound and out sales operations &#8211; you name it, I have the t-shirt.</p>
<p>Along the way, I picked up a very large helping of quality process management. I&#8217;ve gone through an ISO certification (and passed). I&#8217;ve been through a New York State Governor&#8217;s Award application process (it&#8217;s the state level Malcom Baldridge and we came in second). I&#8217;ve embraced and almost implemented COPC standards (call center six sigma).</p>
<p>I want to know how long it takes us to  produce the widgets. I want to know how long it takes to ship the  widgets. And I want to understand how long it takes us to support the  customers buying our widgets. The current quality fad is Lean. Fine. Whatever. It goes back to Drucker. Total Quality Management. Six Sigma. ISO. All essentially the same stuff. All result in a quality framework. We can get what we need without spending thousands upon thousands of dollars on a &#8220;quality initiative.&#8221;</p>
<p>Coming from the land of technical support &#8211; any time someone was  working on ANYTHING, they needed to be in a support ticket. Assigned to a  customer. With the clock running. The same principles apply to production. Where do we have defects? Where do we require re-work? How long does it take?</p>
<p>I want to see rolled up reporting,  daily, weekly, monthly, etc. How many tickets, top 10 issues, AGING of  tickets. The same principles apply to production. Where do we have defects? Where do we require re-work? How long does it take?</p>
<p>The big tool here is doing <a href="http://www.mindtools.com/pages/article/newTMC_80.htm">root cause analysis</a>. And, really, that is what this whole series is about. Figuring out why your business is struggling and setting it on a better path. RCA is actually very simple, but you have to be honest and authentic. You have to eliminate assumptions. Assume nothing! And the best thing about RCA is that you can do it without doing math.</p>
<p>A great tool for identifying root cause is the <a href="http://www.isixsigma.com/index.php?option=com_k2&amp;view=item&amp;id=1308:&amp;Itemid=49">5 Whys</a>. Get  yourself a <a href="http://www.isixsigma.com/index.php?option=com_k2&amp;view=item&amp;id=1416&amp;Itemid=1&amp;Itemid=1">fishbone diagram</a>. (there are templates for word and excel off that link.) And start working through each situation. Do it in groups. And I don&#8217;t mean groups of managers. Again &#8211; USE YOUR TEAM(s). Don&#8217;t do this around a big conference table with your managers. Go to the floor. Talk to the people DOING the work. Better yet, get a cross-functional team going. You will be amazed at what 3 people from different business units come up with.</p>
<p>You may have to do some <a href="http://www.mindtools.com/brainstm.html">brainstorming</a>. Don&#8217;t roll your eyes at me! It works. Sometimes you have to help people shake the cobwebs off. Sometimes you have to help them make the transition from step by step process thinking to stepping back to a broader view. Get yourself a whiteboard and start drawing the <a href="http://www.mindtools.com/pages/article/newISS_01.htm">mindma</a>p of the brainstorming session. You will quickly get to <a href="http://www.mindtools.com/pages/article/newTMC_03.htm">cause and effect</a> relationships.</p>
<p>So there you go. Get your non-manager people together. Give them some tools. And let them have at it. Don&#8217;t be afraid to use your fancy watch and do some simple time studies. If it takes you 20 minutes to enter an order while the customer is on the phone &#8211; you have a problem. If your widget making machine is down for an hour out of every 8 hour shift you probably have a problem. (I can&#8217;t say for sure, maybe that is normal.)</p>
<p>Next time, I will wrap this series up with some final thoughts. I hope this is proving beneficial. Please leave a comment or tweet this out into the internets!</p>
<h2  class="related_post_title">If you liked this post, try these...</h2><ul class="related_post"><li><a href="http://mikelally.net/blog/running-a-successful-turnaround-final-thoughts/" title="Running A Successful Turnaround: Final Thoughts">Running A Successful Turnaround: Final Thoughts</a></li><li><a href="http://mikelally.net/blog/running-a-successful-turnaround-the-employee-view/" title="Running a Successful Turnaround: The Employee View">Running a Successful Turnaround: The Employee View</a></li><li><a href="http://mikelally.net/blog/running-a-successful-turnaround-the-customer-view/" title="Running a Successful Turnaround: The Customer View">Running a Successful Turnaround: The Customer View</a></li></ul>]]></content:encoded>
			<wfw:commentRss>http://mikelally.net/blog/running-a-successful-turnaround-process-improvements/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Running a Successful Turnaround: The Employee View</title>
		<link>http://mikelally.net/blog/running-a-successful-turnaround-the-employee-view/</link>
		<comments>http://mikelally.net/blog/running-a-successful-turnaround-the-employee-view/#comments</comments>
		<pubDate>Sun, 25 Jul 2010 20:05:50 +0000</pubDate>
		<dc:creator>mikelally</dc:creator>
				<category><![CDATA[change]]></category>
		<category><![CDATA[leadership]]></category>
		<category><![CDATA[management]]></category>
		<category><![CDATA[operations]]></category>
		<category><![CDATA[tools]]></category>
		<category><![CDATA[genchi genbutsu]]></category>
		<category><![CDATA[running a successful turnaround]]></category>
		<category><![CDATA[Tom Peters]]></category>

		<guid isPermaLink="false">http://mikelally.net/blog/?p=638</guid>
		<description><![CDATA[I have been working on a series of posts detailing my thoughts on how I would fix or turn around a business operation. I would take a stab at a scenario an MBA candidate/intern threw at me. So far we have talked about financials and how to get a handle on your customers. Its all about [...]]]></description>
			<content:encoded><![CDATA[<div name="googleone_share_1" style="position:relative;z-index:5;float: right; margin-left: 10px;"><g:plusone size="tall" count="1" href="http://mikelally.net/blog/running-a-successful-turnaround-the-employee-view/"></g:plusone></div><div class="tweetmeme_button" style="float: right; margin-left: 10px;">
			<a href="http://api.tweetmeme.com/share?url=http%3A%2F%2Fmikelally.net%2Fblog%2Frunning-a-successful-turnaround-the-employee-view%2F"><br />
				<img src="http://api.tweetmeme.com/imagebutton.gif?url=http%3A%2F%2Fmikelally.net%2Fblog%2Frunning-a-successful-turnaround-the-employee-view%2F&amp;source=mikelally&amp;style=normal&amp;b=2" height="61" width="50" /><br />
			</a>
		</div>
<p>I have been working on a <a href="http://mikelally.net/blog/tag/running-a-successful-turnaround/">series of posts</a> detailing my thoughts on how I would fix or turn around a business operation. I would take a stab at a scenario an MBA candidate/intern threw at me. So far we have talked about <a href="http://mikelally.net/blog/?p=467">financials</a> and how to get a handle on your <a href="http://mikelally.net/blog/?p=636">customers</a>.</p>
<p>Its all about ENGAGEMENT. TP is a huge fan of employee engagement. Go figure &#8211; so am I. An engaged employee is a productive one. I read an article recently (can&#8217;t find it) that said U.S. working population is 26% engaged, 55% not engaged and 19% actively disengaged. in your 40 person shop, 20+ could care. 8 of your people are actively trying to screw you up. Are you listening now?</p>
<p>Oh&#8230;and those 8&#8230;they aren&#8217;t who you think.</p>
<p>I like a two phased approach coupled with a very strong helping of genchi genbutsu or MBWA (Management By Walking Around). Get yourself seen. Have breakfast with people. Have lunch. Fruit roll ups. Just do it. Then, the first step is to sit down with everyone and just talk. The second stage is to do a formal employee satisfaction survey. Depending on the size of the team, you may not get a chance to sit with everyone. But you can devote 30 minutes to each interview.</p>
<p>I love <a href="http://www.grassrootsleadership.com/">Capt. D. Mike Abrashoff (ret.)</a>, who wrote an EXCELLENT book on leadership -<a href="http://www.amazon.com/dp/0446529117/ref=nosim/?tag=grassrootslea-20&amp;link">It&#8217;s Your Ship</a>. (This is a great book for new leaders by the way.) Mike lays out a very simple plan in this book that has served me RIDICULOUSLY well over the years.</p>
<p>3 questions.</p>
<ol>
<li>What are we doing well?</li>
<li>What are we doing poorly?</li>
<li>If you could fix one thing right now, what would it be?</li>
</ol>
<p>Short and simple. The best part about this process is that once you have a decent sample size, you will know the top issues facing your team and you will have some pretty good ideas on how to fix them.</p>
<p>From a process perspective it is pretty easy. Gather everyone together and tell them you are going to meet with them individually. It is a great opportunity to introduce yourself to them and put them at ease. You don&#8217;t want to just start randomly calling people into your office. (Although &#8211; that tactic has its merits.)</p>
<p>From the long term approach &#8211; start conducting Employee Satisfaction Surveys. A long time ago I referred to a great set of questions that really get at Employee Engagement &#8211; the 1<a href="http://mikelally.net/blog/?p=145">2 Questions That Matter</a>:</p>
<p>In hindsight, twelve questions seems like a bit much. Some of them are a bit redundant. Here are a solid 5 to get you started:</p>
<p>4. In the past seven days, have I received recognition or praise for doing good work?<br />
9. Are my coworkers committed to doing quality work?<br />
10. Do I have a best friend at work?<br />
11. In the past 6 months, has someone at work talked to me about my progress?<br />
12. This past year, have I had the opportunities at work to learn and grow?</p>
<p>Number 10 stays because there is a lot of research on the benefits of having a best friend at work.</p>
<p>5 questions and then leave room for feedback. And I hate anonymous surveys. They are pointless. Guess what though&#8230;if people aren&#8217;t comfortable filling our your employee survey and attaching their name &#8211; YOU HAVE A PROBLEM.</p>
<p>You are not going to get all your answers the first time you do one. But that is ok because you&#8217;re already doing the 3 Question meetings. Do the E-Sat quarterly. You could do them monthly if you like but quarterly has worked for me. You have to be consistent. The WORST thing you can do is drop this survey on your people and then not do another one. Actually, the worst thing you can do is conduct the survey and not follow up on the results.</p>
<p>You have to be very clear in communicating your intent. That is: you want to make things BETTER. Make YOURSELF accountable to action items created out of the survey. And do it publicly. You have to share the findings. You have to share the actions you plan to take to correct problem areas. You must be c-o-n-s-i-s-t-e-n-t. You must be patient. It takes a bit of time to build trust.</p>
<p>You could deploy this survey using the 5-scale or the 3-scale. In a 5-scale, you can look at Strongly Disagree-Disagree-Neutral-Agree-Disagree. Only the top two boxes matter. That is why I can say go with a 3-scale:<br />
Disagree-Sometimes-Agree. And then only count the &#8220;agrees&#8221;. Just seems simplier and eliminates ambiguity.</p>
<p>Our next installment will talk about Processes and continuous improvement.</p>
<h2  class="related_post_title">If you liked this post, try these...</h2><ul class="related_post"><li><a href="http://mikelally.net/blog/running-a-successful-turnaround-final-thoughts/" title="Running A Successful Turnaround: Final Thoughts">Running A Successful Turnaround: Final Thoughts</a></li><li><a href="http://mikelally.net/blog/running-a-successful-turnaround-process-improvements/" title="Running A Successful Turnaround: Process Improvements">Running A Successful Turnaround: Process Improvements</a></li><li><a href="http://mikelally.net/blog/running-a-successful-turnaround-the-customer-view/" title="Running a Successful Turnaround: The Customer View">Running a Successful Turnaround: The Customer View</a></li></ul>]]></content:encoded>
			<wfw:commentRss>http://mikelally.net/blog/running-a-successful-turnaround-the-employee-view/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Running a Successful Turnaround: The Customer View</title>
		<link>http://mikelally.net/blog/running-a-successful-turnaround-the-customer-view/</link>
		<comments>http://mikelally.net/blog/running-a-successful-turnaround-the-customer-view/#comments</comments>
		<pubDate>Sat, 17 Jul 2010 08:39:47 +0000</pubDate>
		<dc:creator>mikelally</dc:creator>
				<category><![CDATA[change]]></category>
		<category><![CDATA[customer service]]></category>
		<category><![CDATA[leadership]]></category>
		<category><![CDATA[management]]></category>
		<category><![CDATA[operations]]></category>
		<category><![CDATA[running a successful turnaround]]></category>
		<category><![CDATA[skills]]></category>
		<category><![CDATA[tools]]></category>

		<guid isPermaLink="false">http://mikelally.net/blog/?p=636</guid>
		<description><![CDATA[Last week, I started as series of posts detailing my thoughts on how I would fix or turn around a business operation. Inspired by a promising MBA student that is doing an internship with us, I thought I would take a stab at a scenario she threw at me. Last week-ish we talked about financials. [...]]]></description>
			<content:encoded><![CDATA[<div name="googleone_share_1" style="position:relative;z-index:5;float: right; margin-left: 10px;"><g:plusone size="tall" count="1" href="http://mikelally.net/blog/running-a-successful-turnaround-the-customer-view/"></g:plusone></div><div class="tweetmeme_button" style="float: right; margin-left: 10px;">
			<a href="http://api.tweetmeme.com/share?url=http%3A%2F%2Fmikelally.net%2Fblog%2Frunning-a-successful-turnaround-the-customer-view%2F"><br />
				<img src="http://api.tweetmeme.com/imagebutton.gif?url=http%3A%2F%2Fmikelally.net%2Fblog%2Frunning-a-successful-turnaround-the-customer-view%2F&amp;source=mikelally&amp;style=normal&amp;b=2" height="61" width="50" /><br />
			</a>
		</div>
<p>Last week, I started as <a href="http://mikelally.net/blog/tag/running-a-successful-turnaround/">series of posts</a> detailing my thoughts on how I would fix or turn around a  business operation. Inspired by a promising MBA student that is doing an  internship with us, I thought I would take a stab at a scenario she  threw at me. Last week-ish we talked about <a href="http://mikelally.net/blog/?p=467">financials</a>.</p>
<p>This week, let&#8217;s talk about getting a handle on your customers &#8211; specifically their level of satisfaction. A few years ago I linked and commented on a <a href="http://mikelally.net/blog/?p=139">great approach</a> to customer satisfaction (csat). The original article talked about the 5 csat questions you will ever need but it was service operation focused. I think the questions are still very relevant and can be used in almost any business.</p>
<p>It is really 5 questions and a 6th which asks for verbal feedback. I also throw in another question &#8211; a net promoter score question. So really&#8230;.7 questions. Here they are (in order of importance):</p>
<p>1. Courtesy of the Whomever You Interact With Most Frequently (support person, billing, customer service, field service, delivery person, sales person, account manager, CEO) &#8211; Your customer deserves and and expects to be treated in a courteous/professional manner. If you are scoring poorly here you need to make sure you have communicated the absolute importance of service and satisfied customers to your team. You may also need to specifically train customer service and customer experience skills.</p>
<p>2. Skills and Knowledge of Whomever You Interact With Most Frequently &#8211; While a courteous employee is nice, it won&#8217;t make a bit of difference if they can&#8217;t solve the customer&#8217;s issue. Your customers want confidence in the employee&#8217;s skills and knowledge to resolve the issue at hand. This is the best way to measure your team&#8217;s skill and knowledge level. Weaknesses here go back to the hiring and training process.</p>
<p>3. Quality of the Resolution &#8211; Again, courteous and knowledgeable employees are really nice to have, but they need to be actually addressing customer needs/questions/issues. Customers calling back for the same reasons over and over again is a customer that is going to churn on you.</p>
<p>4. Timeliness of the Resolution &#8211; Time is money! Fix your customer&#8217;s problem the first time they call. Two things happen if you don&#8217;t: you drive up your total cost per incident and you irritate your customer&#8217;s&#8230;see churn above. This is a process problem. Break it down step by step. No step is too small. Trouble lies in the handoffs.</p>
<p>5. Overall Experience &#8211; This is really the weighted average of the first 4. Keep in mind that customers will weigh each of the above differently. If you have a low score (bottom two boxes out of 5), CALL THAT CUSTOMER AND BEG THEM TO HELP YOU UNDERSTAND WHAT YOU CAN DO BETTER!</p>
<p>6. Additional Feedback &#8211; always, always, always allow your customer to give you open ended feedback. Let them vent. Not only will they tell you what is wrong (and right if you are lucky) they will tell you how to FIX IT.</p>
<p>Additionally, I have become a fan of the net promoter score. Net  Promoter basically asks one simple question &#8211; &#8220;Would you refer us to  someone else?&#8221; You take all the people that say yes and subtract all the  people that say no and you end up with your score. It makes for a great  measurable. And it is easy to create goals from it. If you&#8217;re NPS is 55  &#8211; set a goal to increase it to 60.</p>
<p>Ask these questions to your customers as soon as you get into your turnaround. Then do it quarterly. Track and compare results. If you have a lot of customers, you can outsource this task. If you have a manageable number of customers, keep it in house. If you have a handful of customers, you should be doing this yourself, on the phone or in person.</p>
<p>Each of the top 5 questions should get a scale of 1-5. 1 being completely off the rails broken and 5 being Superbowl win. I would label the boxes specific to each question. For example: Courtesy of the person would be a scale of Christian Bale/Mel Gibson to Miss Manners. Or you could let HR rule the world and do a scale of 1 to 5. If you do 1 to 10, then top two boxes are good. I like 1 -3 &#8211; easier to get through and eliminates ambiguity.</p>
<p>Ideally, every customer gets some kind of sponsor. Positive responses should get a follow up of thanks. Negative responses should get a follow up to work through the issues. It doesn&#8217;t even have to be an &#8220;executive&#8221; sponsor. In fact, you could kill two birds with one stone here&#8230;.you can find out which of your employees are engaged too. (See next week&#8217;s installment.)</p>
<h2  class="related_post_title">If you liked this post, try these...</h2><ul class="related_post"><li><a href="http://mikelally.net/blog/running-a-successful-turnaround-final-thoughts/" title="Running A Successful Turnaround: Final Thoughts">Running A Successful Turnaround: Final Thoughts</a></li><li><a href="http://mikelally.net/blog/running-a-successful-turnaround-process-improvements/" title="Running A Successful Turnaround: Process Improvements">Running A Successful Turnaround: Process Improvements</a></li><li><a href="http://mikelally.net/blog/running-a-successful-turnaround-the-employee-view/" title="Running a Successful Turnaround: The Employee View">Running a Successful Turnaround: The Employee View</a></li></ul>]]></content:encoded>
			<wfw:commentRss>http://mikelally.net/blog/running-a-successful-turnaround-the-customer-view/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Running a Succesful Turnaround: The Financials</title>
		<link>http://mikelally.net/blog/running-a-succesful-turnaround-the-financials/</link>
		<comments>http://mikelally.net/blog/running-a-succesful-turnaround-the-financials/#comments</comments>
		<pubDate>Fri, 09 Jul 2010 01:45:56 +0000</pubDate>
		<dc:creator>mikelally</dc:creator>
				<category><![CDATA[accounting]]></category>
		<category><![CDATA[change]]></category>
		<category><![CDATA[leadership]]></category>
		<category><![CDATA[management]]></category>
		<category><![CDATA[operations]]></category>
		<category><![CDATA[tools]]></category>
		<category><![CDATA[finance]]></category>
		<category><![CDATA[running a successful turnaround]]></category>

		<guid isPermaLink="false">http://mikelally.net/blog/?p=467</guid>
		<description><![CDATA[Last week, I started as series of posts detailing my thoughts on how I would fix or turn around a business operation. Inspired by a promising MBA student that is doing an internship with us, I thought I would take a stab at a scenario she threw at me. This week, let&#8217;s talk about financials. [...]]]></description>
			<content:encoded><![CDATA[<div name="googleone_share_1" style="position:relative;z-index:5;float: right; margin-left: 10px;"><g:plusone size="tall" count="1" href="http://mikelally.net/blog/running-a-succesful-turnaround-the-financials/"></g:plusone></div><div class="tweetmeme_button" style="float: right; margin-left: 10px;">
			<a href="http://api.tweetmeme.com/share?url=http%3A%2F%2Fmikelally.net%2Fblog%2Frunning-a-succesful-turnaround-the-financials%2F"><br />
				<img src="http://api.tweetmeme.com/imagebutton.gif?url=http%3A%2F%2Fmikelally.net%2Fblog%2Frunning-a-succesful-turnaround-the-financials%2F&amp;source=mikelally&amp;style=normal&amp;b=2" height="61" width="50" /><br />
			</a>
		</div>
<p>Last week, I started as <a href="http://mikelally.net/blog/running-a-succ…nd-an-overview/">series of posts</a> detailing my thoughts on how I would fix or turn around a business operation. Inspired by a promising MBA student that is doing an internship with us, I thought I would take a stab at a scenario she threw at me.</p>
<p>This week, let&#8217;s talk about financials. I am taking an operational view. Maybe a business unit, maybe a small company. In some scenarios, you may not get access to the financials. I like to focus on a few areas:</p>
<ul>
<li>Revenue</li>
<li>Operating Costs</li>
<li>Profit</li>
<li>Contribution margin</li>
<li>Days Sales Outstanding (DSO)</li>
</ul>
<p>Ultimately, I want to understand profitability by customer. I want to know who my most profitable customers are and I want to know who is killing me. Down the road, we will make decisions. Sometimes, customers need to get fired. Crazy. I know. But why would you do business with someone that is costing you money? Charge them more or get rid of them. Unless they are &#8220;strategic&#8221; &#8211; i.e. bringing you HORDES of profitable customers.</p>
<p>I don&#8217;t think anyone can be running pure COST CENTERS any more. Every unit should be finding a way to become a profit center. Either way, cost or profit center, you have to understand where the money is going. Detailed operating costs. I promise you there is waste. Find it. Create a bonus plan that rewards people for finding new ways of doing things. Make it so that it comes directly to you and not through a chain of command. Don&#8217;t let a middle manager feel threatened and stomp down a great idea.</p>
<p>Contribution Margin is a KPI I also like to examine. Simply put, it is total product price less its variable costs. This really gets at the profitability by customer KPI. You can break this number down many different ways. By customer. By product. By team. It helps drill down into potential trouble spots.</p>
<p>Then, there is DSO. This one has always amazed me. I have been in several operations where payments from customers have lapsed to 90+ days. 120+ days. How is that possible? It happens. One goal is to start closing the gap on DSO. If your standard terms are net 30. Your cash flow is being affected. Plus the conversation required with your customer is worth it for a couple of reasons. First, it is a good to talk to your customers. Second, if they are really late, maybe they have a business problem you might be able to fix.</p>
<p>What is costing us money? Where are we profitable? These are the two big questions that I seek answers to in a turnaround situation. Next steps are to figure out ways to align costs and customers better. Can you charge customers more for the products/services delivered? Can you cut costs? Are there process inefficiencies (more on that later)?</p>
<p>I avoided the obvious cash flow and balance sheet pieces. There are plenty of better places to get that information. I am taking an operational &#8211; line management &#8211; view. My goal is to show how I would pull apart an operation, dissect it, and then build it back up for greatness.</p>
<p>Next time, we will talk about the Employee Side KPIs. (I will try to do better on timing. This was a holiday week for me. Things got a little nutty.)</p>
<h2  class="related_post_title">If you liked this post, try these...</h2><ul class="related_post"><li><a href="http://mikelally.net/blog/running-a-successful-turnaround-final-thoughts/" title="Running A Successful Turnaround: Final Thoughts">Running A Successful Turnaround: Final Thoughts</a></li><li><a href="http://mikelally.net/blog/case-study/" title="Case Study">Case Study</a></li><li><a href="http://mikelally.net/blog/running-a-successful-turnaround-process-improvements/" title="Running A Successful Turnaround: Process Improvements">Running A Successful Turnaround: Process Improvements</a></li></ul>]]></content:encoded>
			<wfw:commentRss>http://mikelally.net/blog/running-a-succesful-turnaround-the-financials/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>Running A Successful Turnaround: An Overview</title>
		<link>http://mikelally.net/blog/running-a-successful-turnaround-an-overview/</link>
		<comments>http://mikelally.net/blog/running-a-successful-turnaround-an-overview/#comments</comments>
		<pubDate>Wed, 30 Jun 2010 10:01:53 +0000</pubDate>
		<dc:creator>mikelally</dc:creator>
				<category><![CDATA[career]]></category>
		<category><![CDATA[change]]></category>
		<category><![CDATA[customer service]]></category>
		<category><![CDATA[leadership]]></category>
		<category><![CDATA[management]]></category>
		<category><![CDATA[operations]]></category>
		<category><![CDATA[tools]]></category>
		<category><![CDATA[running a successful turnaround]]></category>

		<guid isPermaLink="false">http://mikelally.net/blog/?p=322</guid>
		<description><![CDATA[This continues our series on how to run a successful turnaround &#8211; or &#8211; The Mike Lally Way. Maybe we&#8217;ll just call this RAST. Running A Successful Turnaround. The Mike Lally Way is just way too lame. Today, I will take a holistic, high-level view and in future posts, I will look at each element [...]]]></description>
			<content:encoded><![CDATA[<div name="googleone_share_1" style="position:relative;z-index:5;float: right; margin-left: 10px;"><g:plusone size="tall" count="1" href="http://mikelally.net/blog/running-a-successful-turnaround-an-overview/"></g:plusone></div><div class="tweetmeme_button" style="float: right; margin-left: 10px;">
			<a href="http://api.tweetmeme.com/share?url=http%3A%2F%2Fmikelally.net%2Fblog%2Frunning-a-successful-turnaround-an-overview%2F"><br />
				<img src="http://api.tweetmeme.com/imagebutton.gif?url=http%3A%2F%2Fmikelally.net%2Fblog%2Frunning-a-successful-turnaround-an-overview%2F&amp;source=mikelally&amp;style=normal&amp;b=2" height="61" width="50" /><br />
			</a>
		</div>
<p>This continues our series on how to run a successful turnaround &#8211; or &#8211; The Mike Lally Way. Maybe we&#8217;ll just call this RAST. Running A Successful Turnaround. The Mike Lally Way is just way too lame. Today, I will take a holistic, high-level view and in future posts, I will look at each element in more detail.</p>
<p>Walking into any turnaround situation, I immediately set out to acquire data supported by human information (or intel). You cannot just look at data on a page. A) the data will lie to you. It will beguile you. It will tell you that you are smarter than you think. B) You need to get out in front of your people anyway. Let&#8217;s start with data.</p>
<p>I want to see the following Key Performance Indicators (KPIs):</p>
<p><strong>Financial KPIs:</strong><br />
Revenue<br />
Operations Costs<br />
Profit<br />
Contribution Margin<br />
DSO. Days Sales Outstanding.</p>
<p>I want these numbers broken out by customer and/or by team. Definitely by customer. I want to know our most profitable customers (not necessarily the customers bringing in the most revenue). I want to know who is COSTING us money.</p>
<p><strong>Customer KPIs</strong><br />
Customer Satisfaction &#8211; every main customer contact (assuming we have one) gets a very short 5+1 questions survey. The plus 1 question is the Net Promoter question. Then we start doing this quarterly, same questions. We track results.</p>
<p><strong>Employee KPIs</strong><br />
Employee Satisfaction. Monthly. Simple questions. I will share them.</p>
<p>I will also interview everyone. Three simple questions. If the operation is very large where this isn&#8217;t feasible, I would push the interview down the chain of command and get summary reporting created.</p>
<p><strong>Process KPIs/Production</strong><br />
Simple time studies will do. I want to know how long it takes us to produce the widgets. I want to know how long it takes to ship the widgets. And I want to understand how long it takes us to support the customers buying our widgets.</p>
<p>I come from the land of technical support. Any time someone was working on ANYTHING, they needed to be in a support ticket. Assigned to a customer. With the clock running. I want to see rolled up reporting, daily, weekly, monthly, etc. How many tickets, top 10 issues, AGING of tickets.</p>
<p>The same principles apply to production. Where do we have defects? Where do we require re-work? How long does it take?</p>
<p>Over the next days/weeks, I will dive into each of these elements/KPIs.</p>
<h2  class="related_post_title">If you liked this post, try these...</h2><ul class="related_post"><li><a href="http://mikelally.net/blog/running-a-successful-turnaround-final-thoughts/" title="Running A Successful Turnaround: Final Thoughts">Running A Successful Turnaround: Final Thoughts</a></li><li><a href="http://mikelally.net/blog/running-a-successful-turnaround-process-improvements/" title="Running A Successful Turnaround: Process Improvements">Running A Successful Turnaround: Process Improvements</a></li><li><a href="http://mikelally.net/blog/running-a-successful-turnaround-the-employee-view/" title="Running a Successful Turnaround: The Employee View">Running a Successful Turnaround: The Employee View</a></li></ul>]]></content:encoded>
			<wfw:commentRss>http://mikelally.net/blog/running-a-successful-turnaround-an-overview/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Case Study</title>
		<link>http://mikelally.net/blog/case-study/</link>
		<comments>http://mikelally.net/blog/case-study/#comments</comments>
		<pubDate>Sun, 27 Jun 2010 13:07:58 +0000</pubDate>
		<dc:creator>mikelally</dc:creator>
				<category><![CDATA[change]]></category>
		<category><![CDATA[finance]]></category>
		<category><![CDATA[leadership]]></category>
		<category><![CDATA[management]]></category>
		<category><![CDATA[operations]]></category>
		<category><![CDATA[sales]]></category>
		<category><![CDATA[tools]]></category>
		<category><![CDATA[running a successful turnaround]]></category>
		<category><![CDATA[skills]]></category>

		<guid isPermaLink="false">http://mikelally.net/blog/?p=314</guid>
		<description><![CDATA[We have an intern working with us. She is getting her MBA. She still has that new car smell on her. By that I mean &#8211; she hasn&#8217;t become bitter and jaded. She is still full of the possibility that most business problems are easy to fix. If only we applied ourselves. She&#8217;s taken to [...]]]></description>
			<content:encoded><![CDATA[<div name="googleone_share_1" style="position:relative;z-index:5;float: right; margin-left: 10px;"><g:plusone size="tall" count="1" href="http://mikelally.net/blog/case-study/"></g:plusone></div><div class="tweetmeme_button" style="float: right; margin-left: 10px;">
			<a href="http://api.tweetmeme.com/share?url=http%3A%2F%2Fmikelally.net%2Fblog%2Fcase-study%2F"><br />
				<img src="http://api.tweetmeme.com/imagebutton.gif?url=http%3A%2F%2Fmikelally.net%2Fblog%2Fcase-study%2F&amp;source=mikelally&amp;style=normal&amp;b=2" height="61" width="50" /><br />
			</a>
		</div>
<p>We have an intern working with us. She is getting her MBA. She still has that new car smell on her. By that I mean &#8211; she hasn&#8217;t become bitter and jaded. She is still full of the possibility that most business problems are easy to fix. If only we applied ourselves. She&#8217;s taken to quizzing me. The classic battle of education versus experience.</p>
<p>She challenged me the other day with a problem they had studied. I thought it would make for interesting reading. The problem was a struggling manufacturing operation. The problem is pitched as one of production. But I will give the ending away. It really is a quality problem.</p>
<p>So &#8211; over the next few posts, I will lay out the Mike Lally Method. <img src='http://mikelally.net/blog/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' />  We will talk operations, sales, a little finance, and HR (shudder) with a good dose of management and leadership thrown in.</p>
<h2  class="related_post_title">If you liked this post, try these...</h2><ul class="related_post"><li><a href="http://mikelally.net/blog/running-a-successful-turnaround-final-thoughts/" title="Running A Successful Turnaround: Final Thoughts">Running A Successful Turnaround: Final Thoughts</a></li><li><a href="http://mikelally.net/blog/running-a-successful-turnaround-the-customer-view/" title="Running a Successful Turnaround: The Customer View">Running a Successful Turnaround: The Customer View</a></li><li><a href="http://mikelally.net/blog/running-a-successful-turnaround-process-improvements/" title="Running A Successful Turnaround: Process Improvements">Running A Successful Turnaround: Process Improvements</a></li></ul>]]></content:encoded>
			<wfw:commentRss>http://mikelally.net/blog/case-study/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

