mikelally.net

mikelally.net header image 2

Running A Successful Turnaround: An Overview

June 30th, 2010 · No Comments · career, change, customer service, leadership, management, operations, tools

This continues our series on how to run a successful turnaround – or – The Mike Lally Way. Maybe we’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.

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’s start with data.

I want to see the following Key Performance Indicators (KPIs):

Financial KPIs:
Revenue
Operations Costs
Profit
Contribution Margin
DSO. Days Sales Outstanding.

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.

Customer KPIs
Customer Satisfaction – 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.

Employee KPIs
Employee Satisfaction. Monthly. Simple questions. I will share them.

I will also interview everyone. Three simple questions. If the operation is very large where this isn’t feasible, I would push the interview down the chain of command and get summary reporting created.

Process KPIs/Production
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.

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.

The same principles apply to production. Where do we have defects? Where do we require re-work? How long does it take?

Over the next days/weeks, I will dive into each of these elements/KPIs.

Share

Tags:

0 responses so far ↓

  • There are no comments yet...Kick things off by filling out the form below.

Leave a Comment