HOW TO: Limit WIP #7: Understand Your Customers

In this series, we’ve been discussing the psychology of your work, the sized of tasks, how we complete certain types of tasks, and who / what might interrupt us.Perhaps it’s time to understand the consumers of our tasks: our customers. When we do something, even if it is simply relaxing, there is a potential beneficiary of that task.We do things. Those things we loosely call “work”. “Work” has a “work product”. “Work products” should have some value for somebody. That somebody is the customer.Customers can include:

• those paying money for the work (the traditional customer)

• our bosses (corporate hierarchy)

• colleagues, coworkers, partners (corporate culture)

• regulators or agents of an authority (bureaucracy)

• family (family)

• friends and neighbors (society)

• ourselves (ourselves)

And there are likely other customers and subdivisions of these customers.If you are doing things that have no value to anyone … why are you doing them?To limit our WIP, we need to make sure we are doing the right thing.But even if we know it's the right task, are we doing the thing right? To learn this, we must ask ourselves:

• What does our customer want?

• What is the highest value they can get from my work?

• Do I have time to give them that value?

• How much value can I get done in the time I have?

• Will that level of value be sufficient?

We often find ourselves saying “no” to that last question, but continuing to do the work anyway.When we know our work is going to be of insufficient quality, we tend to become aggravated. We feel annoyance at the task, at those who asked us to do the task, an ourselves for getting stuck in a situation like this. This annoyance increases the chance that our work product will be of low quality – making the work even more insufficient.If we didn’t want to do a good job, this would not be a problem.Since we do, there are five quick actions we should take when we understand we have a customer:

• Be clear about what they want – Yes, this sounds obvious, but how many times have you had to rework something because of a simple initial lack of understanding?

• Be clear about what is on your plate – No, sorry Miss Customer, you are not the only thing I am doing right now. I wish you were, but life doesn’t work like that. Here’s what I can realistically do.

• Get their feedback early and often – How soon can you show them an interim product? How quickly can you compare expected and actual progress? Earlier feedback = earlier delivery.

• Understand minimum and optimal deliverables – Minimum and optimum deliverables give you a range of success to shoot for. If you are always aiming for the high point, you will usually underdeliver.

• Work is a relationship – All work is a relationship between the person doing the work and the person receiving it. Communication (again as early as possible) helps both cement the relationship and ensure an appreciated delivery.

It's simple, if we don't know who it is for, we don't know what we are doing. If we don't know what we are doing, how can we limit our work-in-progress?

Customer Alert System: Element #13 of the Kanban

In 2006, my first kanban based project involved setting up a Personal Kanban for a team of 12 developers. Since we were just starting out with kanban, we had no idea what to expect. I did know a few key things though.1. I wanted the customer to have real-time information about what was going on2. I wanted no more status meetings3. I wanted no impedance whatsoever between my development team and the customerSo, we did the following:We set up a kanban in Groove 2.0 (a collaborative platform developed by Ray Ozzie) and shared that with our client. This meant that our client could see our kanban any time they wanted.I gave my client full access to all my developers. In other words, anyone from their side could contact anyone from my side any time they wanted. They were on our chat rooms, they had our Skype addresses, they had our phone numbers. Any time the client wanted access to anyone or anything at Gray Hill Solutions, they could have it.I allowed the clients to come to our daily stand-up meetings and fully participate. They directly participated in the selection of work, the phasing, and its constitution.The upshot of this was that the customer has, through the kanban, a real-time warning system that we may be doing something that required discussion. The fear - of both my developers and the client - was that this would create endless discussions and nothing would get done.The opposite happened.The client understood where we were and what we were doing. They could look at the product any time they wanted. They could see the kanban. They attended the 15 minute meetings so they knew of any challenges we were facing.Additional conversations were rarely necessary - because everyone already knew.The kanban itself gave the client and the team such a high fidelity of information, all we ever needed to talk about was real changes in the backlog or design decisions. In other words, all we had to talk about was value.

Customers, Respect & Value: Lean Muppets Post 9

Respect is a fundamental value in Lean

Profit in business comes from repeat customers;customers that boast about your product and service,and that bring friends with them.~ W. Edwards Deming

Everyone has been in this position before.  You’re doing business with someone – your only goal is to give them money for their services – and they make the simplest request onerous. In this case, the customer has ordered a bowl of soup and it is, apparently, defective.  We can feel his dread of calling support when he notices the fly. He knows frustration is just around the corner.

But, he’s not getting value for money and he calls Grover over. Grover goes through several emotional phases before confronting the problem.

Avoidance – Grover puts him off. “Just a moment sir,” and “Not now sir.”Misdiagnosis – The customer tells Grover there is a fly in his soup. He’s been around soup enough and knows full well the scope and extent of the problem. Grover however, then goes through a set checklist of problem solving provided to him on his first day in customer support. First, the checklist tells him to look under the soup. The customer tells him it’s not under, but rather it is in the soup. Grover returns to his checklist and looks next to the soup. Again, the customer clearly tells him the fly is in the soup.Disbelief and Blame – “I will look in  the soup now, for this supposed fly.” Grover first insinuates that the customer is wrong, and then looks “on” the soup.At this point the customer loses his cookies and lays into Grover, to the point that the two almost come to blows.Admission – In the heat of this exchange, Grover asks, “Why did you order fly soup!?” It turns out that the system (his restaurant) specially serves bowls of fly soup. What was a feature for the restaurant is a defect in the eyes of the customer.Complete Communication Breakdown – To placate the customer, Grover then goes to get another bowl of soup. He returns and offers, “I think you will be very happy with this.” When the customer asks what it is, he replies “Cream of Mosquito.”While we could certainly  talk about failure demand, like we did in back in post two when Ernie painted Bert’s portrait, here we’ll talk about respect.Customers who have a choice will not continue to deal with companies that do not respect them. If you are in a business where you are lucky enough to enjoy a monopoly or near-monopoly you can treat your customers poorly or even regularly insult them. But if they have a choice, you may want to think twice.In general, people do not feel respected if they feel “processed.” So checklists, forms, and formalities do not set a stage for repeat customers.But let’s take Deming’s quote one level further. In business, you get profit from repeat customers. But our customers are not always people buying services from us. If our spouse asks us to take out the garbage, they become our “customer” for that task. (If you don’t believe me, dump the garbage on the floor and tell me if your spouse doesn’t act like Grover’s customer).Each day we engage in myriad transactions. Some of them are economic, but most are social. Consistently disrespecting people will eventually erode our social capital and leave us with no friends and distrusted by all. If we respect others, then we will have friends that boast about our product (ourselves) and bring more friends with them.

~

This is ninth in a series of Lean Muppet Posts. For a list of Lean Muppet posts and an explanation of why we did this, look here -> Lean Muppets Introduction