A Valuable 2-Day Masterclass for Leaders and their Direct Reports –
Getting results applying Agile, Lean & DevOps is common but usually relies on a handful of people who carry most of the weight because they are excited by the new tools and methods. These early adopters act as champions of change and are essential at the start of an IT transformation. For change to persist, innovation to be sustained and continuously improved, everyone needs to be engaged!
This is where effective leadership is crucial. Using hands-on exercises and role play, this workshop will position you to understand and experience the key behaviors needed to effectively lead Agile, Lean IT & DevOps teams through an enterprise transformation.
Currently, most DevOps, Lean IT, and Agile transformations are not led by CIOs. They are often led by the director of operations, chief architect, or director of development. It is good these people have been given the authority and/or responsibility to introduce a significant change in the way work gets done. But there is a potential downside: without the vision, alignment, and commitment a CIO brings to the discussion, these efforts can collapse for many reasons including lack of commitment across the entire IT service delivery value stream, conflicting priorities, entrenched silos within IT, lack of internal coaching and support, and overburden of bottleneck resources (just to name a few).
The success of the transformation begins and all too often ends, based on the degree the CIO and their direct reports actively lead and authentically connects. To lead people effectively, leaders need to understand the “Why,” the “What,” and the “How.” This is a mindset, skill set, and toolset that needs to be learned, practiced, and adjusted based on the culture of the specific organization and the challenges they encounter. Leaders throughout the organization must be able to connect with people at a very real and meaningful level that fosters trust, transparency, respect, and new ways of working across silos. This is tricky stuff for almost everyone and the CIO is the pivotal influencer of how seriously and deeply people will go to make their transformation succeed.
Program Description: The most difficult step to take in a Lean IT transformation (be it agile, DevOps, service management, etc.) is the very first one. Organizations fall into the trap of learning lean concepts and talking about the possibilities, but the initial excitement fades and the transformation never gets off the ground. Lack of alignment to organizational purpose, inability to figure out where to start, and fear of making mistakes all conspire to keep companies from ever getting started in the first place.
This one day workshop, based on the book, The Lean IT Field Guide by Mike Orzen and Tom Paider, will provide participants with an understanding of the foundational elements needed for a successful lean transformation and practical experience identifying and executing the key activities of pre-launch and day zero activities.
The workshop will focus on preparing you to implement a solid foundation of a sustainable lean transformation, not just focus on terms, definitions, and theory without application!
Benefits: In this interactive workshop you will:
· Gain understanding of the core elements of the Lean IT Roadmap and how to apply it to your DevOps/agile/lean transformation
· Identify your organization’s current strengths, challenges, and readiness to begin a Lean IT transformation
· Learn to apply key concepts, methods, and tools critical to successful transformation
· Acquire the skills to plan and launch a lean transformation using a case study simulation
· Reflect on how you will apply these concepts and tools to get started on the right path or to check/adjust in your organization
Who should take this class? Agile, DevOps and Lean IT practitioners of all levels + those responsible for leading real change in IT
Accountability. It’s a word often feared in society for being associated with the blame game – being singled out when things go wrong, even if the reasons are beyond your scope of control. It seems we are always hearing about the importance of creating a culture of accountability.
Unfortunately, when managers and associates hear the term, they often flinch! Expressions such as “We’re holding you accountable” are often seen as code for “You are liable and will be blamed if things do not go as planned!” This is a major problem for any organization that is serious about creating and sustaining a lean transformation.
If we consider the lessons of LEI’s Transformation Model (shown above), we see that the entire foundation rests on the basic thinking and fundamental assumptions (both overt and unseen) that drive current culture. For leaders who wish to transform from a command-and-control culture to a more participative one, a key assumption is that, when treated respectfully, people will align to a common purpose, deeply engage in both doing the work and improving the process, and assume higher levels of accountability.
The image includes employees taking on tasks without being told to do so, showing initiative to improve quality first and efficiency second, and genuinely caring about their customers, team members, organization, and community. This basic assumption that is so central to a lean transformation becomes null and void when accountability is seen as a liability that management assigns, rather than a self-assumed role that people undertake of their own volition.
When there is evidence of intentional avoidance of accountability, it suggests that people don’t trust the intentions of the organization, leadership, or even fellow teammates. They may be avoiding the risk of potential conflict that comes from taking on a task which the outcome is uncertain. This is true problem solving and it can be scary enough without the fear of being blamed if things don’t work out well. It is interesting to note the role that trust plays in all this.
Creating a lean environment is essentially creating a learning environment. In a learning environment, we move away from experts who tell others what to do and towards learners who run experiments (rapid PDCA cycles) to better understand root cause(s) and validate effective countermeasures. Accountability must be self-imposed in order for people to truly grasp the concept, take ownership, and take on appropriate levels of commitment.
But this can only be done when the fear and apprehension most people associate with words such as accountability are openly addressed. When reflecting on your own organization, here are a few questions to consider:
- Do we blame people when things don’t go as planned?
- Do people self-assume accountability or do we assign/delegate accountability?
- In our current culture is there fear, anxiety or hesitation around accountability?
- Do we ask people to be accountable before asking if they are capable?
- Do accountability and authority always go together? When should they?
To learn more about creating a culture of accountability and respect through effective leadership, sign up for Mike Orzen’s pre-summit workshop, Lead with Respect: Practicing Respect for People to Enable Engagement, Teamwork & Accountability, at the 2016 Lean Healthcare Transformation Summit this June. Learn more about Lead with Respect and other Summit workshops on the summit webpage.
Note: this article also appeared in the Lean Enterprise’s Lean Post in February of 2016.
This is Part 4 of Sequences, Behaviors and Integrating Adaptive Lean IT Systems – an updated article originally published in the Lean Management Journal in October 2015.
In the previous blog entry, team huddles and a visual management system were mentioned. These are both examples of work systems designed to encourage the specific behaviors we want to cultivate. There are many work systems that comprise a lean management system including problem solving, daily huddles, leader standard work, training, recognition, visual management, strategy deployment, measurement, and monthly performance reviews, just to name a few.
It is these work systems that impact people’s behavior most significantly by emphasizing and reinforcing those actions we want to see everyday from everyone. Where many organizations get into trouble is in the sequence and timing of how and when to introduce these systems.
SEQUENCE IS CRITICAL
Over the past twenty-four years, I have tried many approaches and witnessed what works and what doesn’t. Here’s the bottom line: each organization has its own culture, history, and work environment, so one size does not fit all. There is no standard deployment sequence or collection of work systems that apply universally. That said; there are some fundamental concepts applicable to all organizations.
1) Start by establishing a clear purpose throughout the organization. This is a prerequisite for success.
2) Acknowledge that the bedrock of lean is learning and that problem solving capability is the skill to cultivate if you are serious about transformation.
3) Strive to balance the two pillars of lean: continuous improvement and respect for people. Don’t make the common mistake of falling in love with tools of continuous improvement and ignoring respect for people.
4) Create a culture of accountability by building work systems that position your people to succeed, to learn, and to grow. This is true respect for people and promotes high levels of teamwork, engagement, accountability, and ultimately performance.
5) Work systems must be designed, built, maintained, and improved by the people doing the actual work. Outside support is fine, but the frontline people must do the work.
ADAPTIVE LEAN IT SYSTEMS
Whether you are considering bringing lean IT to your organization, currently applying it to IT operations, or determined to build a lasting transformation, awareness of the lean IT diamond and the importance of behavior, work systems, and sequence will significantly increase your odds of success.
At the end of the day, Lean IT is all about effectively responding to change by continuously improving adaptive systems. In order to be effective, IT must change its behavior and functional capabilities in response to its environment and the needs of the Business. When IT reshapes systems and technology, the adaptive change is directly relevant to achieving the goals and objectives of the organization.
For IT organizations to evolve and become more responsive to the changing needs of the Business while simultaneously maintaining the stability and security they are held responsible for, IT professionals need to understand and embrace the behaviors, as well as the thinking, of Lean IT.
For additional information on how to mobilize a Lean IT transformation, see The Lean IT Field Guide – A Roadmap for Your Transformation.
This is Part 3 of Sequences, Behaviors and Integrating Adaptive Lean IT Systems – an updated article originally published in the Lean Management Journal in October 2015.
At the end of the day, all change comes down to altering our established patterns of behavior. Anyone who has attempted to make a lifestyle change (such as quitting smoking or eating healthier) can attest to how difficult this is.
It is interesting to note that most transformations tend to focus on training people in the new ways of doing things. We assume that if people know about a new (presumable better) way of doing something, they will automatically adopt it as their regular way of acting. Nothing could be further from the truth. If knowing about a better behavior caused people to change their actions and develop new habits, no one would be overweight, use tobacco products, or run on less than 6 hours of sleep!
We are all creatures of habit and become very comfortable with the way we’ve always done it, even when our routines become outdated, broken, and painfully frustrating. Why? Because it is really difficult to change the behavior of others or even ourselves. This resistance to change is a universal condition that, unless addressed directly and openly, puts all transformation efforts at serious risk.
MAKE/BREAK, CADENCE, & PREDICTABILITY
There are three factors you need to know about to effectively address this issue: make/break, cadence, and predictability. So what does it take to make or break a habit? I have confirmed it requires 40 days of practicing a new behavior before we can even begin to change old habits. At 90 days we have confirmed and strengthened the routine. At 120 days the new habit becomes deeply engrained as a part of our identity (how we see ourselves). At 1,000 days we have mastered the new behavior. Here’s the secret: the days must be consecutive! That’s right – if you miss a day, any day, the next day is Day One and you start counting from the beginning. I have personally used this approach to successfully affect change at both organizational and personal levels and it works.
Why is this approach so effective? People like routine and predictability – we are hard-wired to repeat what has worked before and to be skeptical of anything outside the conventional pattern. Most people drive to work using the same route, walk through a grocery store selecting the same items, watch the same TV programs, and go to bed at the same time – you get the picture. By enforcing a new routine and deliberately changing our behavior, we gradually provide the predictability and structure our human nature innately desires. When the changes make our work better, faster, less stressful, and prove to be more rewarding, that further reinforces the value of the routine and new habits begin to take deeper root.
As new work processes yield better results including more consistent quality, less rework, variability, and overburden, predictability of outcomes increases and we receive yet another dose of reinforcement – increased customer satisfaction!
THE KEY SYSTEM – PROBLEM SOLVING
An example may serve to clarify this approach to creating new habits. Let’s assume you have introduced lean problem solving to your IT group as part of your transformation. People have received training in basic lean concepts including PDCA, A3, and root cause analysis. The assumption is that once people understand lean problem solving, they will use it in their daily work. This rarely happens. In most cases about 10% of your people will be self-starters and try to apply lean practices on their own. The vast majority of people attend the training and think, “That’s interesting…” and then go back to work using their normal ways of getting things done. They quickly fall back to their comfort zone, which excludes the ideas and tools shared in the training workshop.
Applying the make/break, cadence, and predictability concepts, we would include problem solving as an essential element of our daily team huddles and visual management system. On a daily basis, the team would be coached by responding to questions of inquiry designed to foster new ways of applying what was learned during the training on problem solving. The only way people learn lean is by doing lean!
In the final post of this series, we’ll explore the importance of work systems and sequencing to build adaptive Lean IT systems.
This is Part 2 of Sequences, Behaviors and Integrating Adaptive Lean IT Systems – an updated article published in the Lean Management Journal in October 2015.
Today, many companies are actively seeking the benefits of lean IT and are undergoing constant transportation in their IT group. They are often familiar with lean and/or Six Sigma and have had some success with process improvement in other areas of the business such as manufacturing, accounting, and supply chain.
However, the landscape of IT, the complexity and dynamics of technology, the interdependency of its functional silos, and conflicting priorities when working with the Business, all combine to create a perfect storm of distinctive obstacles.
There is a key relationship that exists in all organizations. When understood and appreciated, it can provide clarity and direction to a lean IT transformation.
Let’s look at the components of the lean IT diamond and why it can be so helpful. At the top of the model, we begin with Purpose. A shared purpose is essential to create and drive a common intention, alignment, and commitment. Everyone in the IT organization (as well as the Business) needs to very clear on why we are in business, why we are transforming, and where we are vs. where we need to be.
If this shared understanding is not in place, you can be certain to see different behaviors, erratic degrees of engagement, and the consequential mixed results. Without a widely understood and collective purpose that people can clearly see within the context of their daily work, everyone is left on their own to identify what matters most and determine what they should do (or not do) about it. If you have ever witnessed pockets of improvement (aka islands of lean in a sea of waste), you can be assured there is a lack of understanding around shared purpose.
The next component is People. It may seem obvious that people are a central ingredient in building a highly effective organization. What is not so obvious, or at least publicly acknowledged, is that many work environments are abundant with uncertainty, disengagement, mistrust, apathy, fear, and political gamesmanship. In our first book, Lean IT Enabling and Sustaining Your Lean Transformation, I noted that people are often the only appreciating asset in an organization. When we treat people with respect and create systems and processes that position them for success, we cultivate trust, engagement, teamwork, and high levels of performance. Perhaps the most essential element in a successful transformation is to ensure the initiative is behavior-based. See the next post in this series for a discussion of behavior-based change.
Process represents the work we do to create value for our customers, to collaborate with our partners (the Business, vendors, supply chain, and outside resources), and to ultimately fulfill the mission of our organization. When processes are undefined, unclear, or not consistently followed, the effort required, the time it takes, the quality of the outcomes, and the frustration of staff and customers all become highly unstable and inconsistent.
The final component of the lean IT diamond is Information and Technology. It is useful to think of these two elements as distinct yet highly interdependent. With respect to information, IT is the mechanism that transforms raw data into useful and actionable information. IT, when done well, is the connective nervous system that joins people with actionable information.
Concerning technology, IT is the enabler of the business – capturing, organizing, and storing immense amounts of data, routine tasks, building transactional records, enforcing business process rules, managing secure access, all while providing work process functionality and visibility to all functional areas of the business.
The flow of complete, accurate, timely, and actionable information is a key determinant of the flow of customer value and organizational performance. When IT stops, the Business stops. When IT flows, information flows and the Business is positioned for success (of course it takes more than just great IT).
Updated article which recently appeared in the October 2015 edition of the Lean Management Journal
Transformation is today’s buzzword. It seems everyone in the lean community is talking about transformation. This makes sense given that we’ve spent the past several decades attempting to understand, copy, and adapt the improvement tools of Deming, Ohno, Shingo, and others and getting mixed results. Today we have only a handful of companies we might describe as Lean Enterprises and Toyota remains as the undisputed archetype. So what is transformation and why are so many companies pursuing it? Transformation is often described using words such as radical change, metamorphosis, revolution, and overhaul. Perhaps the most important aspect of a true transformation is that it is irreversible. This is the characteristic of lean transformation that has eluded most organizations. Granted, they have trained their people in the tools and core concepts, experienced process improvements through kaizen, made changes to the physical environment, introduced lean management systems, and have realized measureable results.
TRANSFORMATION IS DIFFICULT TO SUSTAIN – THE PUNISHMENT OF SISYPHUS
But what many organizations discover is that the momentum and energy required to keep their transformation going is being provided by a small group of people (usually the Process Improvement team, a cadre of lean coaches, or a charismatic lean champion). If they stop leading the charge, improvement work and the underlying transformation immediately begin to taper off. It’s as if organizational momentum is a large stone that needs to be constantly pushed up hill – if we stop pushing, it quickly rolls back down! This reminds me of the Greek myth of Sisyphus, who was punished for being deceitful by being forced to carry a huge boulder up a mountain, only to watch it roll back down, for all of eternity. Many organizations seem to be stuff in a similar loop!
LEAN IT IS ESSENTIAL
Delivering value to the customer is a common objective of practically every organization in existence. In order to accomplish this, it is essential to deliver services, products, and information which meets customer-defined quality, at a price they are willing to pay, and at a pace that matches customer demand. With the advent of the Internet, smartphones, and unprecedented access to information, customer expectations of quality, value, variety, convenience, and delivery have been increasing rapidly and there is no end in site. In order to meet customer expectations, today’s business climate is categorically reliant on the flow of information. Modern-day business process improvement, a collection of principles, systems, and tools aimed at creating a culture of continuous process improvement has evolved over the past 100 years or so. Most recently, we have been witnessing an explosion of improvement methodologies in the Information and Technology space. This comes as no surprise given our insatiable need for the information we require to make timely, informed decisions in response to ever-increasing customer expectations.
In the 1980’s, the IT Infrastructure Library (ITIL) emerged as a set of standard practices for IT which focused on aligning IT services with the needs of business (a novel idea at the time). ITIL has gone through several iterations and evolved to include a continuous service improvement component that embraces many of the tenets of lean thinking. Since then, we have seen the further application of lean in IT including Agile/Scrum, Kanban, Continuous Delivery, Lean Startup, DevOps, and Lean/ Agile Project Management.
I refer to this entire body of IT performance improvement as lean IT. Lean IT is the application of lean through to Information, Communication, and Technology. It’s a management system made up of two key pillars: continuous process improvement and respect for people. Lean IT is ultimately a learning system using a structured and disciplined approach to solving problems and pursuing opportunities. Lean IT focuses on engaging IT people to methodically improve IT processes in partnership with the Business to deliver more value to end users and enable the Business to deliver more value to end customers. This includes getting out on a regular basis to better understand the challenges and value equations of end users and see how information and technology are really being used. Lean IT is about engaging people, improving core business processes, and leveraging technology to enable the entire organization to accomplish more, create more, and achieve more with the least effort required.
In the next installment of this post, we’ll explore the Lean IT Diamond and that fact, although transformation is extremely difficult, it is not impossible.
The Tyranny of Bad Data
We’ve all experienced the frustration and pain associated with bad data – either we’re aware that the information obtained from IT systems is inaccurate or incomplete (and the non-value added work that comes with it) or unaware that the information is based on bad data and the cascading impact of taking the wrong course of action due to misinformation. It is incredible that so much is invested on enterprise technology solutions, as little attention is devoted to ensuring high quality data is the sole source of system information. Only a handful of companies have discovered how to exploit the power of lean IT to shorten time to value development cycles, while assuring data integrity.
The ultimate purpose of information and technology is to enable people to perform great work as effectively and efficiently as possible. From a lean IT perspective, we want to leverage technology to empower people to do excellent work with the least amount of required effort. Technology has the capability to gather, store, organize, manipulate, manage, calculate, analyze, summarize, format, and report limitless amounts of data in order to create actionable information. Technology that efficiently delivers bad information only serves to enable waste, delays, and poor results. For our purposes, information needs to possess the following attributes to be deemed actionable: accurate, timely, complete, and accessible.
For a practical example of Lean IT and data management, see the webinar Lean IT: Driving SAP Continual Process Improvement.
When bad data happens to good people
Donald Rumsfeld, former US Secretary of Defense infamously said: “You go to war with the army you have, not the army you might want or wish to have at a later time.” In the same way, we do business with the data quality we have, not the data quality we might want! But what happens when highly effective technology processes inaccurate, incomplete, and out-of-date data; when bad data happens to good people?
Scenario #1 – We know we don’t know…
If people recognize that the information they are receiving is not actionable, they are forced to choose from damaging alternatives like adjusting their course of action based on years of experience, assumptions, and perceived understanding. Some develop rules of thumb based on personal knowledge, while others devise creative workarounds to obtain the information they require when system information is suspect and unreliable.
Unfortunately none of these countermeasures confronts the root cause of the problem, nor guarantees a timely and accurate business outcome. Undocumented workarounds and tribal knowledge of what to do when the system delivers bad information may work in one instance and fail in another, and all of these actions are forms of guessing that are impossible to scale and sustain.
Scenario #2 – We don’t know we don’t know…
When people rely on information from IT systems, assuming accuracy, timeliness, and completeness, and that information is actually compromised, things get much worse. Bad data generates bad information, prompting people to make misinformed decisions, mistakes, oversights, and the creation of more bad data! The compounding impact of bad data and inaction-able information is a frustrating, downward cycle of errors, corrections, rework, and delays that force people to resort to heroic efforts to deliver mediocre results. Customers instantly notice a lack of service, timeliness, and quality. As employees become more aware of data problems, they begin to lose trust in the system and resort to the workarounds described in scenario #1, which may feel better and attain some results, but do not materially improve the situation. In fact, the more exceptions and workarounds to the way work is conducted, the more variability the customer experiences in service levels, quality, and delivery time!
In my next post, we’ll explore How Lean IT addresses the issue of bad data at a level that creates measurable, sustainable change for the better.
Unless your team puts their individual interpretation into lean methods & tools, the transformation simply will not become embedded and quickly fades away. When you look at an old school picture, who is the first person you look for? If you are like most people, it’s you! There is actually part of the brain that lights up when we see an image of ourselves, or an object that sparks our self identify. We feel good when we identify with who we are, especially if we are part of making something better through a challenge – a situation, a relationship, or the unmet needs of another person.
In order for people and teams to take responsibility for the work systems and outcomes of their area, they need to see themselves rooted in the process. This means that their ideas, challenges, hunches, frustrations, and experiences are reflected in the way work processes are improved over time. They have to get their fingerprints on the work processes to care enough to own outcomes. People self-select responsibility for process when they know their opinion matters and what they do and say has a direct influence on how things change.
When workers see their own reflection in the work they do, they identify more deeply and become vested in the outcomes. Any countermeasure aimed at specific problem is a temporary fix at best. The best teams expect that today’s solutions will certainly not last long. When teams understand the fleeting nature of today’s customer demands, they naturally anticipate the need to check for change and adjust work practices as needed. Improving the way work gets done becomes part of doing daily work.
In order to make the right changes, a clear understanding of purpose must be in place. Objective measurements, some of which are under the direct control of the team, are essential here. When those closest to the work align with purpose and own their process, behavior, and the resulting outcomes, they participate and contribute at a heightened level of engagement.
When lean tools (like value stream mapping and A3s) are hoisted onto teams without the opportunity to accept and assume ownership, we disrespectfully dump a load of tools and training on them, and then expect people to connect! This is how the term “accountability” gets such a negative connotation. It’s crazy to hold anyone accountable when they have been given no reason or opportunity to engage in the change. They don’t see themselves in any of it.
Try to see it from their perspective: “I don’t feel my opinion matters, I don’t know whether we are winning or losing, I am not clear on our purpose or how my work contributes towards it.” With that outlook in place, they then consider their manager’s directive, “Hey, get engaged with lean, take ownership, and make improvements!”
What would you think?