feature – as lean thinkers, our focus is on problem-solving. the author explains why effectively solving problems depends on our ability to make the right decisions and suggests the lean community plays closer attention to this.
words: flávio battaglia
every day, each of us must make decisions. countless decisions, in fact – ranging from what we are going to have for breakfast to how we should engage with people around us, from what time we should leave to go to the office to how we are going to spend our free time. our daily lives are continuously, significantly, and directly influenced by the choices we make, which is why how we make decisions has always been a topic of great interest to neuroscientists, psychologists, sociologists, etc.
in the business world, too, decisions are expected of people at all levels of an organization, and it is the combination of those decisions that determines whether a company is ultimately successful. do people at the front line flag up problems or do they hide them? do managers strive to improve the system, or do they blame people instead? do senior execs think long-term when coming up with their strategy or do they choose to just focus on making money now?
in the lean world, we often say that people should be given the tools and autonomy they need to make decisions and, therefore, solve problems, but i believe the focus of our attention has traditionally been problem-solving to the detriment of decision-making. yet, without decision-making one can’t be expected to solve problems.
so, why not pay attention to how we make our decisions and see how the lean way of thinking and acting can help us ensure these are the best they can be?
five stages of decision-making
as mentioned above, theories on decision-making abound. it is mostly described as the resulting in the selection of a course of action among several possible options (could be either or irrational). according to herbert alexander simon, decision-making is a reasoning process based on assumptions of , and beliefs of the decision maker. every decision-making process produces a final , which may or may not prompt action.
if we try to look at this cognitive process from a lean perspective and break it into smaller steps, we can say there are five main stages in the decision-making process:
- perception – how good and trained we are to see the reality around us and recognize certain stimuli as problems requiring our attention.
- intention – based on what we perceive, how willing and determined we are to act and do something about a problem.
- evaluation – how i am going to assess the risk and benefit of acting on a certain problem. is it worth acting on it at this stage? do i have what i need to succeed? at this stage, we are trying to weigh up hypotheses.
- action – based on our evaluation, we decide to act (or not) and use the tools at our disposal (in the case of lean, things like daily management, huddles, kaizen or hoshin) to bring our vision to fruition.
- reflection – how good we are at extrapolating lessons from our experience. did our intervention pay off? what did we learn from it? what’s the impact it had on the system?
lean and decision making
the five elements highlighted above describe how decisions are made, the thought process that causes us to see reality one way or the other, to choose a certain course of action, to draw conclusions from something that happens to us. because lean is so tightly connected with the way we think, i believe that it can help us to ensure that our decisions are the right ones.
applied to these five elements, in fact, lean can turn decision-making into a powerful driver of a transformation. its scientific approach provides us with a structured way to make decisions, even when these happen almost subconsciously (which is why it’s so important to make lean second nature, the way people see the world around them).
lean tools and principles make the decision-making process as effective as it can be. how?
when it comes to perception, with lean we learn to see. this means developing our ability to see problems, to separate value-added work from waste. because we get our information directly from the gemba – rather than a report or a presentation – we have a much more accurate understanding of the reality around us, of the problems we experience, on the decisions we are called to make. (this is where it becomes clear that decision-making is a much wider concept than problem-solving – if our perception is off and we focus on the wrong problem, we can be the best problem solvers in the world but that won’t mean much).
as far as intention goes, as lean thinkers we are driven to make daily improvements to provide more value to our customers, serve the best food we can in a restaurant, offer patients the best possible care. this passion for improvement comes from two sources: the motivation i receive and the knowledge i am given. together, these two elements empower me, give me the will – and the means – to act. this way, each problem i observe becomes a trigger that awakens my intention to “do something about it”.
it is one thing to have the right intention, but what about evaluating the problem and the situation around it to understand whether my intervention has the potential to succeed? it is at this stage that we decide to act or not. after all, tackling a problem when we don’t have the knowledge or the support that we need is wasteful. this makes the evaluation phase critical. lean can help us assess the situation, by encouraging us to ask questions such as, “do i have the support i need from leadership?” “are my people with me?” “is this the right time to take this on?” “do i have the tools i need to have an impact on the situation?” “is it worth focusing on this problem or should it be something else?” developing our evaluating capabilities is just important as honing our perception and problem-solving skills.
if we do decide to act, lean provides us with a wide array of tools, techniques and behaviors that can help us attack a problem – from its definition all the way to its resolution. the “action” phase is the problem-solving we typically talk about in the lean community. a3 thinking, kaizen, engaging with cross-functional teams, gemba walks, 5 whys – one could say that everything lean teaches us is ultimately meant to make the problem-solving process smoother and more effective.
finally, we can’t forget the reflection phase. doing hansei is also a decision. too many neglect this critical activity, only to find how big a hindrance this is to our ability to transform organizations. reflecting on the decisions we have made, on the problems we have solved and how we have gone about it, and on the impact that this has had on the overall system means that we will be better equipped to solve future problems of a similar nature. the more problems we solve, and the more we learn from them, the better we will be at solving future problems – it’s the virtuous cycle of lean. without learning and capturing knowledge, there is only so much progress we can make (not sure if i got the meaning of this final sentence).
let’s try to imagine two real-life scenarios to bring these ideas to life. in both cases, a patient in a hospital is given the wrong medication. here’s how a non-lean decision-making process and a lean decision-making process would unfold.
in the first case, a middle manager learns about the incident. he is an old-fashioned guy, working in an old-fashioned environment. as he looks at what happened – indeed, giving the wrong medication is a very common occurrence in hospitals – he immediately shrugs the problem off by saying, “we have so many of these. no one ever died. we always find out in time.” this flawed perception of reality (which leads the manager to believe this is not even an issue) results in a complete lack of intention to do anything about it. the evaluation of the problem convinces the manager that the best course of action is to ensure that news of the incidence doesn’t spread. “we will do something about it next time. we have so much to do already,” he thinks. no problem has been tackled, and there is therefore no learning that can be drawn from the experience. fast forward a few months, another patient is given the wrong medication. this time, however, she develops a rash all over her body and the hospital ends up with a lawsuit on its hands.
in the second case, the manager is a lean thinker. someone tells her about the medication error, which she immediately sees as a problem that the whole team needs to look into. the manager knows this is common problem in hospitals. she had in fact worried that this might happen while visiting the gemba recently – where she remembers wondering how the pharmacists managed to tell medication apart when so many of them came in such similar containers. her experience studying the work at the gemba has changed her perception and immediately alerts her that the medication error is a huge problem. as a lean thinker, her first instinct – or intention – is to solve it. for her evaluation, she goes to gemba and talks to as many people as she can, really trying to grasp the situation and understand whether an intervention can have the desired result. once she determines that this is in fact the case, she decides to act. she forms a small team to analyze the problem in depth and uses a3 thinking to solve the issue once and for all through a simple, but clever system of colored tags and poka-yoke. as the team gathers to reflect on their learning, the success of their kaizen inspires them to share their experience with the rest of the hospital so that other areas can also avoid medication errors. a year later, the hospital records zero instances of medication error for six months in a row (and counting).
why not simply problem solving?
until now, we have discussed how applying lean to the five dimensions of decision-making makes great sense. but the same positive outcomes can be seen if we look at this the other way around: decision-making gives us a much more complete view of our lean transformations than just problem-solving. it forces us to ask ourselves questions that would otherwise remain unanswered – what problems do we pick? why? based on what indicators? why do i decide to go ahead and tackle this problem?
looking at the five key elements of decision-making might just make us better at lean, because it can add a new dimension to our discussions and give us a new way to look at the challenges before us. to those of you who are on a lean journey and feel sometimes stuck, this perspective can help you see things in a different way, find new doors to unlock. decision-making lies behind all the dimensions of a lean transformation, which is why it is so important we look at it and better connect it to our lean transformation efforts.
as we study lean transformations, our focus until now has been almost exclusively on problem solving. while this is of course fundamental (it lies at the heart of lean), problem-solving without solid decision-making goes nowhere. i think we are missing an opportunity by ignoring the role of decision-making in our lean journeys. if we believe that decision-making constantly comes into play in our daily lives, why are we not discussing it more? why don’t we treat it as the transformation driver it is?
flávio battaglia is director of lean institute brasil.