Archive for the ‘Culture’ Category
Transcending a Culture of Continuous Improvement
We’ve been too successful with continuous improvement. Year-on-year, we’ve improved productivity and costs. We’ve improved on our existing products, making them slightly better and adding features.
Our recipe for success is the same as last year plus three percent. And because the customers liked the old one, they’ll like the new one just a bit more. And the sales can sell the new one because its sold the same way as the old one. And the people that buy the new one are the same people that bought the old one.
Continuous improvement is a tried-and-true approach that has generated the profits and made us successful. And everyone knows how to do it. Start with the old one and make it a little better. Do what you did last time (and what you did the time before). The trouble is that continuous improvement runs out of gas at some point. Each year it gets harder to squeeze out a little more and each year the return on investment diminishes. And at some point, the same old improvements don’t come. And if they do, customers don’t care because the product was already better than good enough.
But a bigger problem is that the company forgets to do innovative work. Though there’s recognition it’s time to do something different, the organization doesn’t have the muscles to pull it off. At every turn, the organization will revert to what it did last time.
It’s no small feat to inject new work into a company that has been successful with continuous improvement. A company gets hooked on the predictable results of continuous which grows into an unnatural aversion to all things different.
To start turning the innovation flywheel, many things must change. To start, a team is created and separated from the continuously improving core. Metrics are changed, leadership is changed and the projects are changed. In short, the people, processes, and tools must be built to deal with the inherent uncertainty that comes with new work.
Where continuous improvement is about the predictability of improving what is, innovation is about the uncertainty of creating what is yet to be. And the best way I know to battle uncertainty is to become a learning organization. And the best way to start that journey is to create formal learning objectives.
Define what you want to learn but make sure you’re not trying to learn the same old things. Learn how to create new value for customers; learn how to deliver that value to new customers; learn how to deliver that new value in new ways (new business models.)
If you’re learning the same old things in the same old way, you’re not doing innovation.
Don’t change culture. Change behavior.
There’s always lots of talk about culture and how to change it. There is culture dial to turn or culture level to pull. Culture isn’t a thing in itself, it’s a sentiment that’s generated by behavioral themes. Culture is what we use to describe our worn paths of behavior. If you want to change culture, change behavior.
At the highest level, you can make the biggest cultural change when you change how you spend your resources. Want to change culture? Say yes to projects that are different than last year’s and say no to the ones that rehash old themes. And to provide guidance on how to choose those new projects create, formalize new ways you want to deliver new value to new customers. When you change the criteria people use to choose projects you change the projects. And when you change the projects people’s behaviors change. And when behavior changes, culture changes.
The other important class of resources is people. When you change who runs the project, they change what work is done. And when they prioritize a different task, they prioritize different behavior of the teams. They ask for new work and get new behavior. And when those project leaders get to choose new people to do the work, they choose in a way that changes how the work is done. New project leaders change the high-level behaviors of the project and the people doing the work change the day-to-day behavior within the projects.
Change how projects are chosen and culture changes. Change who runs the projects and culture changes. Change who does the project work and culture changes.
Image credit – Eric Sonstroem
Wanting things to be different
Wanting things to be different is a good start, but it’s not enough. To create conditions for things to move in a new direction, you’ve got to change your behavior. But with systems that involve people, this is not a straightforward process.
To create conditions for the system to change, you must understand the system”s disposition – the lines along which it prefers to change.. And to do that, you’ve got to push on the system and watch its response. With people systems, the response is not knowable before the experiment.
If you expect to be able to predict how the system will respond, working with people systems can be frustrating. I offer some guidance here. With this work, you are not responsible for the system’s response, you are only responsible for how you respond to the system’s response.
If the system responds in a way you like, turn that experiment into a project to amplify the change. If the system responds in a way you dislike, unwind the experiment. Here’s a simple mantra – do more of what works and less of what doesn’t. (Thanks to Dave Snowden for this.)
If you don’t like how things are going, you have only one lever to pull. You can only change.your response to what you see and experience. You can respond by pushing on the system and responding to what you see or you can respond by changing what you think and feel about the system.
But keep in mind that you are part of the system. And maybe the system is running an experiment on you. Either way, your only choice is to choose how to respond.
Whether it goes well or poorly, what matters is how you respond.
When was the last time you taught someone a new method or technique? What was their reaction? How did it make you feel? Will you do it again?
When was the last time you learned something new from a colleague? What was your reaction? What did you do so it would happen again?
When was the last time you woke up early because you were excited to go to work? How did you feel about that? What can change so it happens once a week?
When was the last time you had a crazy idea and your colleagues helped you make it real? How did you feel about that? How can you do it for them? What can you do to make it happen more frequently?
When was the last time you had a crazy idea and it was squelched because it violated a successful recipe? How did you feel about that? What can you do so it happens differently next time?
When was the last time you used your good judgement without asking for permission? How did you feel about that? What can you do to give others the confidence to use their best judgement?
When was the last time someone gave you credit for doing good work? And when was the last time you did the same for someone else? What can you do so the behavior blossoms into common practice?
When was the last time you openly contradicted a majority opinion with a dissenting minority opinion? Though it was received poorly, you must do it again. The majority needs to hear your dissenting opinion so they can sharpen their thinking.
When was the last time you gave good advice to a younger colleague? How can you systematize that type of behavior?
When was the last time you did work so undeniably good that others twisted it a bit and adopted it as their own? Don’t feel badly. When doing innovative work this is what success looks like. All that really matters is your customers realize the value from the work and not who gets credit. What can you do so this type of thing happens as a matter of course?
Good things happen and bad things happen. That’s how life goes. But the important part is you pay attention to what worked and what didn’t. And the second important part is actively making the good stuff happen more frequently and the bad stuff happen less frequently.
Image credit — jacquemart
The Trust Network II
I stand by my statement that trust is the most important element in business (see The Trust Network.)
The Trust Network are the group of people who get the work done. They don’t do the work to get promoted, they just do the work because they like doing the work. They don’t take others’ credit (they’re not striving,) they just do the work. And they help each other do the work because, well, it’s the right thing to do.
Sometimes, they use their judgement to protect the company from bad ideas. But to be clear, they don’t protect the Status Quo. They use their good judgement to decide if a new idea has merit, and if it doesn’t, they try to shape it. And if they can’t shape it, they block it. Their judgement is good because their mutual trust allows them to talk openly and honestly and listen to each other. And through the process, they come to a decision and act on it.
But there’s another side to the Trust Network. They also bring new ideas to the company.
Trying new things is scary, but the Trust Network makes it safe. When someone has a good idea, the Network positively reinforces the goodness of the idea and recommends a small experiment. And when one installment of positivity doesn’t carry the day, the Trust Network comes together to create the additional positivity need to grow the idea into an experiment.
To make it safe, the Trust Network knows to keep the experiment small. If the small experiment doesn’t go as planned, they know there will be no negative consequences. And if the experiment’s results do attract attention, they dismiss the negativity of failure and talk about the positivity of learning. And if there is no money to run the experiment, they scare it up. They don’t stop until the experiment is completed.
But the real power of the Trust Network shows its hand after the successful experiment. The toughest part of innovation is the “now what” part, where successful experiments go to die. Since no one thought through what must happen to convert the successful experiment to a successful product, the follow-on actions are undefined and unbudgeted and the validated idea dies. But the Trust Network knows all this, so they help the experimenter define the “then what” activities before the experiment is run. That way, the resources are ready and waiting when the experiment is a success. The follow-on activities happen as planned.
The Trust Network always reminds each other that doing new things is difficult and that it’s okay that the outcome of the experiment is unknown. In fact, they go further and tell each other that the outcome of the experiment is unknowable. Regardless of the outcome of the experiment, the Trust Network is there for each other.
To start a Trust Network, find someone you trust and trust them. Support their new ideas, support their experiments and support the follow-on actions. If they’re afraid, tell them to be afraid and run the experiment. If they don’t have the resources to run the experiment, find the resources for them. And if they’re afraid they won’t get credit for all the success, tell them to trust you.
And to grow your Trust Network, find someone else you trust and trust them. And, repeat.
Image credit — Rolf Dietrich Brecher
The Trust Network
Trust is the most important element in business. It’s not organizational authority, it’s not alignment, it’s not execution, it’s not best practices, it’s not competitive advantage and it’s not intellectual property. It’s trust.
Trust is more powerful than the organizational chart. Don’t believe me? Draw the org chart and pretend the person at the top has a stupid idea and they try to push down into the organization. When the top person pushes, the trust network responds to protect the company. After the unrealistic edict is given, the people on the receiving end (the trust network) get together in secret and hatch a plan to protect the organization from the ill-informed, but well-intentioned edict. Because we trust each other, we openly share our thoughts on why the idea is less than good. We are not afraid to be judged by members of trust network and, certainly, we don’t judge other members of the network. And once our truths are shared, the plan starts to take shape.
The trust network knows how things really work because we’ve worked shoulder-to-shoulder to deliver the most successful new products and technologies in company history. And through our lens of what worked, we figure out how to organize the resistance. And with the plan roughed out, we reach out to our trust network. We hold meetings with people deep in the organization who do the real work and tell them about the plan to protect the company. You don’t know who those people are, but we do.
If you don’t know about the trust network, it’s because you’re not part of it. But, trust me, it’s real. We meet right in front of you, but you don’t see us. We coordinate in plain sight, but we’re invisible. We figure out how things are going to go, but we don’t ask you or tell you. And you don’t know about us because we don’t trust you.
When the trust network is on your side, everything runs smoothly. The right resources flow to the work, the needed support somehow finds the project and, mysteriously, things get done faster than imagined. But when the trust network does not believe in you and your initiative, the wheels fall off. Things that should go smoothly, don’t, resources don’t flow to the work and, mysteriously, no one knows why.
You can push on the trust network, but you can’t break us. You can use your control mechanisms, but we will feign alignment until your attention wanes. And once you’re distracted, we’ll silently help the company do the right thing. We’re more powerful than you because you’re striving and we’re thriving. We can wait you out because we don’t need the next job. And, when the going gets tough, we’ll stick together because we trust each other.
Trust is powerful because it must be earned. With years of consistent behavior, where words match actions year-on-year, strong bonds are created. In that way, trust can’t be faked. You’ve either earned it or you haven’t. And when you’ve earned trust, people in the network take you seriously and put their faith in you. And when you haven’t earned trust, people in the network are not swayed by your words or your trendy initiative. We won’t tell you we don’t believe in you, but we won’t believe in you.
The trust network won’t invite you to join. The only way in is to behave in ways that make you trustworthy. When you think the company is making a mistake, say it. The trust network likes when your inner thoughts match your outer words. When someone needs help, help them. Don’t look for anything in return, just help them. When someone is about to make a mistake, step in and protect them from danger. Don’t do it for you, do it for them. And when someone makes a mistake, take the bullets. Again, do it for them.
After five or ten years of unselfish, trustworthy behavior, you’ll find yourself in meetings where the formal agenda isn’t really the agenda. In the meeting you’ll chart the company’s path without the need to ask permission. And you’ll be listened to even when your opinion is contrary to the majority. And you’ll be surrounded by people that care about you.
Even if you don’t believe in the trust network, it’s a good idea to behave in a trustworthy way. It’s good for you and the company. And when the trust network finally accepts you, you’ll be doubly happy you behaved in a trustworthy way.
Image credit — manfred majer
You’re probably not doing transformational work.
Continuous improvement is not transformation. With continuous improvement, products, processes and services are improved three percent year-on-year. With transformation, products are a mechanism to generate data, processes are eliminated altogether and services move from fixing what’s broken to proactive updates that deliver the surprising customer value.
A strategic initiative is not transformation. A strategic initiative improves a function or process that is – a move to consultative selling or a better new product development process. Transformation dismantles. The selling process is displaced by automatic with month-to-month renewals. And while product development is still a thing, it’s relegated to a process that creates the platform for the real money-maker – the novel customer value made possible by the data generated by the product.
Cultural change is not transformation. Cultural change uses the gaps in survey data to tweak a successful formula and adjust messaging. Transformation creates new organizations that violate existing company culture.
If there the corporate structure is unchanged, there can be no transformation.
If the power brokers are unchanged, there can be no transformation.
If the company culture isn’t violated, there can be no transformation.
If it’s not digital, there can be no transformation.
In short, if the same rules apply, there can be no transformation.
Transformation doesn’t generate discomfort, it generates disarray.
Transformation doesn’t tweak the successful, it creates the unrecognizable.
Transformation doesn’t change the what, it creates a new how.
Transformation doesn’t make better caterpillars, it creates butterflies.
Image credit – Chris Sorge
Business is about feelings and emotions.
If you use your sane-and-rational lenses and the situation doesn’t make sense, that’s because the situation is not governed by sanity and rationality. Yet, even though there’s a mismatch between the system’s behavior and sane-and-rational, we still try to understand the system through the cloudy lenses of sanity and rationality.
Computer programs are sane and rational; Algorithms are sane and rational; Machines are sane and rational. Fixed inputs yield predicted outputs; If this, then that; Repeat the experiment and the results are repeated. In the cold domain of machines, computer programs and algorithms you may not like the output, but you’re not surprised by it.
But businesses are not run by computer programs, algorithms and machines. Businesses are run by people. And that’s why things aren’t always sane and rational in business.
Where computer programs blindly follow logic that’s coded into them, people follow their emotions. Where algorithms don’t decide what to do based on their emotional state, people do. And where machines aren’t afraid to try something new, people are.
When something doesn’t make sense to you, it’s because your assumptions about the underlying principles are wrong. If you see things that violate logic, it’s because logic isn’t the guiding principle. And if logic isn’t the guiding principle, the only other things that could be driving the irrationality are feelings and emotions. But if you think the solution is to make the irrational system behave rationally, be prepared to be perplexed and frustrated.
The underpinnings of management and leadership are thoughts, feelings and emotions. And, thoughts are governed by feelings and emotions. In that way, the currency of management and leadership is feelings and emotions.
If your first inclination is to figure out a situation using logic, don’t. Logic is for computers, and even that’s changing with deep learning. Business is about people. When in doubt, assess the feelings and emotions of the people involved. And once you understand their thoughts and feelings, you’ll know what to do.
Business isn’t about algorithms. Business is about people. And people respond based on their emotional state. If you want to be a good manager, focus on people’s feelings and emotions. And if you want to be a good leader, do the same.
Image credit: Guiseppe Milo
How to Prevent Depletion
On every operating plan there are more projects than there are people to do them and at every meeting there more new deliverables than people to take them on. At every turn, our demand for increased profits pushes our people for more. And, to me, I think this is the reason every day feel fuller than the last.
This year do you have more things to accomplish or fewer? Do you have more meetings or fewer? Do you get more emails or fewer?
We add work to people’s day as if their capacity to do work is infinite. And we add metrics to measure them to make sure they get the work done. And that’s a recipe for depletion. At some point, even the best, most productive people reach their physical and emotional limits. And at some point, as the volume of work increases, we all become depleted. It’s not that we’re moving slowly, being wasteful or giving it less than our all. When the work exceeds our capacity to do it, we run out of gas.
Here are some thoughts that may help you over the next year.
The amount of work you will get done this year is the same as you got done last year. But don’t get sidetracked here. This has nothing to do with the amount of work you were asked to do last year. Because you didn’t complete everything you were asked to do last year, the same thing will happen this year unless the amount of work on this year’s plan is equal to the amount of work you actually accomplished last year. Every year, scrub a little work off your yearly commitments until the work content finally equals your capacity to get it done.
Once the work content of your yearly plan is in line, the mantra becomes – finish one before you start one. If you had three projects last year and you finished one, you can add one project this year. If you didn’t finish any projects last year you can’t start one this year, at least until you finish one this year. It’s a simple mantra, but a powerful one. It will help you stop starting and start finishing.
There’s a variant to the finish-before-you-start approach that doesn’t have to wait for the completion of a long project. Instead of finishing a project, unimportant projects are stopped before they’re finished. This is loosely known as – stop doing before start doing. Stopping is even more powerful than finishing because low value work is stopped and the freed-up resources are immediately applied to higher value work. This takes judgement and courage to stop a dull project, but it’s well worth the discomfort.
If you want to get ahead of the game, create a stop-doing list. For each item on the list estimate how much time you will free up and sum the freed-up time for the lot. Be ruthless. Stop all but the most important work. And when your boss says you can’t stop something because it’s too important, propose that you stop for a week and see what happens. And when no one notices you stopped, propose to stop for a month and see what happens. Rinse and repeat.
When the amount of work you have to get done fits with your capacity to do it, your physical and mental health will improve. You’ll regain that spring in your step and you’ll be happier. And the quality of your work will improve. But more importantly, your family life and personal relationships will improve. You’ll be able to let go of work and be fully present with your friends and family.
Regardless of the company’s growth objectives, one person can only do the work of one person. And it’s better for everyone (and the company) if we respect this natural constraint.
The only thing predictable about innovation is its unpredictability.
A culture that demands predictable results cannot innovate. No one will have the courage to do work with the requisite level of uncertainty and all the projects will build on what worked last time. The only predictable result – the recipe will be wildly successful right up until the wheels fall off.
You can’t do work in a new area and deliver predictable results on a predictable timetable. And if your boss asks you to do so, you’re working for the wrong person.
When it comes to innovation, “ecosystem,” as a word, is unskillful. It doesn’t bound or constrain, nor does it show the way. How about a map of the system as it is? How about defined boundaries? How about the system’s history? How about the interactions among the system elements? How about a fitness landscape and the system’s disposition? How about the system’s reason for being? The next evolution of the system is unpredictable, even if you call it an ecosystem.
If you can’t tolerate unpredictability, you can’t tolerate innovation.
Innovation isn’t about reducing risk. Innovation is about maximizing learning rate. And when all things go as predicted, the learning rate is zero. That’s right. Learning decreases when everything goes as planned. Are you sure you want predictable results?
Predictable growth in stock price can only come from smartly trying the right portfolio of unpredictable projects. That’s a wild notion.
Innovation runs on the thoughts, feelings, emotions and judgement of people and, therefore, cannot be predictable. And if you try to make it predictable, the best people, the people that know the drill, will leave.
The real question that connects innovation and predictability: How to set the causes and conditions for people to try things because the results are unpredictable?
With innovation, if you’re asking for predictability, you’re doing it wrong.
Image credit: NASA Goddard
For innovation to flow, drive out fear.
The primary impediment to innovation is fear, and the prime directive of any innovation system should be to drive out fear.
A culture of accountability, implemented poorly, can inject fear and deter innovation. When the team is accountable to deliver on a project but are constrained to a fixed scope, a fixed launch date and resources, they will be afraid. Because they know that innovation requires new work and new work is inherently unpredictable, they rightly recognize the triple accountability – time, scope and resources – cannot be met. From the very first day of the project, they know they cannot be successful and are afraid of the consequences.
A culture of accountability can be adapted to innovation to reduce fear. Here’s one way. Keep the team small and keep them dedicated to a single innovation project. No resource sharing, no swapping and no double counting. Create tight time blocks with clear work objectives, where the team reports back on a fixed pitch (weekly, monthly). But make it clear that they can flex on scope and level of completeness. They should try to do all the work within the time constraints but they must know that it’s expected the scope will narrow or shift and the level of completeness will be governed by the time constraint. Tell them you believe in them and you trust them to do their best, then praise their good judgement at the review meeting at the end of the time block.
Innovation is about solving new problems, yet fear blocks teams from trying new things. Teams like to solve problems that are familiar because they have seen previous teams judged negatively for missing deadlines. Here’s the logic – we’d rather add too little novelty than be late. The team would love to solve new problems but their afraid, based on past projects, that they’ll be chastised for missing a completion date that’s disrespectful of the work content and level of novelty. If you want the team to solve new problems, give them the tools, time, training and a teacher so they can select different problems and solve them differently. Simply put – create the causes and conditions for fear to quietly slink away so innovation will flow.
Fear is the most powerful inhibitor. But before we can lessen the team’s fear we’ve got to recognize the causes and conditions that create it. Fear’s job is to keep us safe, to keep us away from situations that have been risky or dangerous. To do this, our bodies create deep memories of those dangerous or scary situations and creates fear when it recognizes similarities between the current situation and past dangerous situations. In that way, less fear is created if the current situation feels differently from situations of the past where people were judged negatively.
To understand the causes and conditions that create fear, look back at previous projects. Make a list of the projects where project members were judged negatively for things outside their control such as: arbitrary launch dates not bound by the work content, high risk levels driven by unjustifiable specifications, insufficient resources, inadequate tools, poor training and no teacher. And make a list of projects where team members were praised. For the projects that praised, write down attributes of those projects (e.g., high reuse, low technical risk) and their outcomes (e.g., on time, on cost). To reduce fear, the project team will bend new projects toward those attributes and outcomes. Do the same for projects that judged negatively for things outside the project teams’ control. To reduce fear, the future project teams will bend away from those attributes and outcomes.
Now the difficult parts. As a leader, it’s time to look inside. Make a list of your behaviors that set (or contributed to) causes and conditions that made it easy for the project team to be judged negatively for the wrong reasons. And then make a list of your new behaviors that will create future causes and conditions where people aren’t afraid to solve new problems in new ways.
Image credit — andrea floris