On Being Well Rested
All business processes are powered by people. Even with all our automation and standardization, nothing moves without people. And people are powered by language. Language is important.
“Fix that so we don’t make any more mistakes.” Snarl words. “Figure out what we do well, and let’s do more of that.” Purr words. Which are more powerful?
“Wonderful work.” Purr words. “Wonderful, more customer complaints.” Snarl words. The same word is both, but it’s clear to all which is which. One is empowering, the other demotivating. Which is better for business?
Subtle usage makes a difference, intonation makes a difference, and tone makes a difference. It’s not just words that matter, but how they’re delivered also matters. Words can build or words can dismantle, and so can delivery.
We know people drive everything. And we know words influence people. Yet we don’t use words in ways that respects their gravity.
It takes care to use the right words in the right ways, and it takes thoughtfulness. But with today’s race pace, it’s tough to be well rested which makes it tough to use care and forethought. Well rested shouldn’t be a luxury and shouldn’t be scoffed at. In an instant the wrong words at the wrong time can be catastrophic. Trouble is the value of being well rested cannot be quantified on the balance sheet.
People power processes and words power people, and the right words at the right time can make all the difference. But it takes thoughtful, enlightened people to deliver them. And for that, they should be well rested.
The Illusion of Control
When things don’t go as planned, you have a choice – look outside or look inside. Looking outside is about control and looking inside is about lack of control.
When you look outside, what you’re saying is the universe didn’t behave per the plan, and you’re going to teach it a lesson. You’re going to tighten the screws until it does what you want; you’re going to add personal energy (probably all your energy) to lock things down; you’re going to control what must be controlled so the universe follows your plan.
The look outside approach can work, for a while. You can put your fingers and toes in all the holes; you can make sure everyone does their job; and you can be the master scheduler for the universe, but only for a while because the universe has limitless energy and you don’t. And while your control-the-world strategy looks like it’s working, it’s not – not even in the short term. The universe is playing you – it’s sucking your energy while you tread water. The universe isn’t stupid – it knows you can’t last. But at its core, the universe likes to teach; and when you fight it head-to-head, it wants to teach you about opportunity cost. While you spend all your energy wresting it to a draw, it prevents you from moving forward. It wants you to learn you have finite energy and to be thoughtful about how you spend it.
When you look inside, what you’re saying is the universe didn’t behave per the plan, and didn’t think it would. You’re going to learn from the universe and work with it; you’re going to surf the wave of the universe’s energy and carve a cross product with its momentum; you’re going to adjust your plan because you have a lack of control over the universe and most other things.
The look inside approach is effective in the long term because it works with the natural trade winds of the universe. Sailing downwind takes far less energy than tacking into the teeth of the cosmic winds, and it’s faster. This is the lesson the universe wants you to learn. But it’s not that easy. The universe constantly tests you. It changes wind direction without our consent and watches. Will you look outside or inside? Will you tack into the wind or change course and throw a huge bow wave as you go?
The toughest part isn’t the wind; it’s the other sailors. They’ve been trained over the years to tack quickly and tack often, to sail directly toward the destination regardless of the wind, even if they must grab the oars and break their backs into the wind. For those sailors, a course change is a sign of weakness – real sailors battle the wind; real sailors stay the course even if the great circle route is faster.
Thing is, plans never happen as planned, and yours is no different. Yes, control things that can be controlled, but remember – the uncontrollable can’t be controlled just because you want them to be. The universe has been around a long time and knows the ropes. It knows you don’t have control over it; it knows you only have control over how you respond to it.
When you work hand-in-hand with the universe, it rewards you, though it does so obliquely. So if your winds suddenly change and you have to sail away from your grand destination, don’t despair – that’s the universe rewarding good behavior. Double the watch and scan the horizon for the uncharted island with far more treasure than you thought possible. The universe calls that karma.
Image courtesy of YachtPals.com
Seeking Comfort in Discomfort
There’s a natural desire to create comfort because, well, it’s comfortable. The parents of comfort are sameness and familiarity. To be comfortable we naturally seek out familiarity, and since we’re most familiar with what we did last time, we naturally want to repeat the past. Because we’re familiar with it and because the familiarity makes us comfortable, there’s natural gravitational pull toward the past. Same goes for sameness – it’s comfortable so we seek it out. That’s why there’s so much momentum around what we did last time – familiarity and sameness create comfort and comfort feels comfortable.
And there’s a second level of intellectual inertia created by our desire for comfort. Yes, the parents are the same – sameness and familiarity – but this level of comfort is about comfort with what we have. Whatever success we’ve had, we want to hold onto it so we can feel comfortable. It’s the success we know, it’s what we’re familiar with, and we want sameness around success.
Level one is about comfort around our behavior and level two is about comfort around outcomes of our behavior. We do what we did last time because we know how to do it and we extrapolate – because we did it well last time we’ll do it well this time. We do what we did last time because it worked and we extrapolate – because it worked last time it will work well again. And when the past is repeated, we’ll be comfortable.
This is a fine way to go if things are static – when the rules of the past are the same in the future. But the wheels fall off when things are dynamic – extrapolation doesn’t work when the rules change,and surely we live in dynamic times. If there’s one thing we should be uncomfortable with it’s seeking comfort in familiarity and sameness.
Just as comfort fosters sameness, discomfort drives disruption.
No doubt the future’s rules will be different, and discomfort will be the forcing function. Discomfort with the status quo will propel upstarts to innovate and break rules. For them familiarity and sameness are uncomfortable, and since they too are human, they will seek out comfort. But they will find it in unfamiliarity and difference. They will be comfortable when they disrupt the game, dethrone the leaders, and coronate themselves.
Whether you’re the leader or the start-up, increase your level of discomfort. The leader can create pockets of discomfort (financed by comfort-based success) to break the rules on their own terms and obsolete their best stuff on their own timeline. And the already uncomfortable start-up can add more to harden itself for the tough times ahead.
Maximizing comfort does not maximize business success. There is little learning without discomfort and there is no adaptation without it. If you’re feeling comfortable, that’s the telltale sign you shouldn’t.
It’s All Connected
There’s a natural tendency to simplify, to reduce, to narrow. In the name of problem solving, it’s narrow the scope, break it into small bites, and don’t worry about the subtle complexities. And for a lot of situations that works. But after years of fixing things one bite at a time, there are fewer and fewer situations that fit the divide and conquer approach. (Actually, they’re still there, but their return on investment is super low.) And after years of serial discretization, what are left are situations that cannot be broken up, that cut across interfaces, that make up a continuum. What are left are big problems and big situations that have huge payoff if solved, but are interconnected.
Whether it’s cross-discipline, cross-organization, cross-cultural, or cross-best practice, the fundamental of these big kahunas is they cross interfaces. And that’s why they’ve never been attacked, and that’s why they’ve never been solved. But with payoffs so big, it’s time to take on connectedness.
For me, the most severe example of connectedness is woven around the product. To commercialize a product there are countless business process that cut across almost every interface. Here are a few: innovation, technology development, product development, robustness testing, product documentation, manufacturing engineering, marketing, sales, and service. Each of these processes is led by one organization and cuts across many; each cut across expertise-specialization interfaces; each requires information and knowledge from the other; and each new product development project must cooperate with all the others. They cannot be separated or broken into bits. Change one with intent and change the others with unintended consequences. No doubt – they’re connected.
Green thinking is much overdue, but with it comes connectedness squared. With pre-green product commercialization, the product flowed to the end user and that was about it. But with environmental movement there’s a whole new return path of interconnected business processes. Green thinking has turned the product life cycle into the circle of life – the product leaves, it lives it’s life, and it always comes back home.
And with this return path of connectedness, how the product goes together in manufacturing must be defined in conjunction with how it will be disassembled and recycled. Stress analysis must be coordinated with packaging design, regulations of banned substances, and material reuse of retired product. Marketing literature must be co-produced with regulatory strategy and recycling technologies. It’s connected more than ever.
But the bad news is the good news. Yes, things are more interwoven and the spider web is more tangled. But the upside – companies that can manage the complexity will have a significant advantage. Those that can navigate within connectedness will win.
The first step is to admit there’s a problem, and before connectedness can be managed, it must be recognized. And before it can become competitive advantage, it must be embraced.
Acceleration Is King
Everything is about speed – speed through process reengineering, waste elimination, standardization, modularity, design reuse. All valid, but not all that powerful. Real speed comes from avoiding rapid progress in the wrong direction, from avoiding a blistering pace on the wrong stuff. Real speed comes from saying no to the work that creates drag in order to say yes to work that accelerates.
It’s healthy to have time limits and due dates, finite resources, and budgets. These constraints are helpful because they force a cutoff decision: what work will get done and what won’t. And thankfully, all businesses have them – take them away and eliminate all hope of profitability and sustainability. But from a speed perspective, sometime we look at them in a backward way.
Yes, that work would change the game, but we don’t have time. That argument is a little misleading. Truth is, there’s the same amount of time as last year – a week is still a week, and there are still 52 of them in a year. It’s not about time; it’s about the work done during that time. With a backwards view, the constraint calls attention to work won’t get done, but the constraint is really about work that will get done. If the work that doesn’t make the cut is less magical than the work that does, the constraint creates a speed problem – too slow on the game-changing work. The speed problem is realized when the new kid on the block makes magic and you don’t. If the constraint helps say yes to magic and no to lesser work, there’s no speed problem.
Yes, we could reinvent the industry, but we don’t have resources. No, we have resources. But the constraint isn’t really about resources, it’s about the work. And not any old work, the constraint is about the work that will get done. (Not the work that won’t.) If the constraint causes us to stuff our fingers in the holes in the dyke at the expense of eliminating it altogether, the constraint caused a speed problem. It’s a problem because while we’re plugging holes, an eager competitor will dismantle the need for the dyke. Speed problem.
Sure, we’d leapfrog the competition, but we don’t have the budget. No, we have a budget. But, like the other constraints, the budgetary one is also about the work that will get done. If the constraint prioritizes same-as-last-time over crazy, it creates a speed problem. New competitors who don’t have to protect the old guard products will work on crazy and bring it to market. And that’s a problem because you’ll have more of what you’ve always had and they’ll have crazy.
Yes, in all cases, choose the bigger bet. Choose crazy over sane, magical over mundane, and irregular over regular. And choose that way because it’s faster. And here’s why faster is king: The number of countries with a well educated work force is growing; there’s an ever increasing number of micro companies who can afford to bet on disruptive technologies; and the internet has shown the world how their lives could be and created several billion people who will use their parental fortitude to do whatever it takes to make life better for their kids. (And there’s no stronger force on earth.) And it all sums to an incredible amount of emotional energy relentlessly pushing the pace.
The world isn’t just getting faster, it’s accelerating – yes, next month will be faster than this month, but that’s not the real trick with acceleration. With acceleration the faster things get, the faster they get faster. Is there really any question how to use your constraints?
Product Thinking
Product costs, without product thinking, drop 2% per year. With product thinking, product costs fall by 50%, and while your competitors’ profit margins drift downward, yours are too high to track by conventional methods. And your company is known for unending increases in stock price and long term investment in all the things that secure the future.
The supply chain, without product thinking, improves 3% per year. With product thinking, longest lead processes are eliminated, poorest yield processes are a thing of the past, problem suppliers are gone, and your distributers associate your brand with uninterrupted supply and on time delivery.
Product robustness, without product thinking, is the same year-on-year. Re-injecting long forgotten product thinking to simplify the product, product robustness jumps to unattainable levels and warranty costs plummet. And your brand is known for products that simply don’t break.
Rolled throughput yield is stalled at 90%. With product thinking, the product is simplified, opportunities for defects are reduced, and throughput skyrockets due to improved RTY. And your brand is known as a good value – providing good, repeatable functionality at a good price.
Lean, without product thinking has delivered wonderful results, but the low hanging fruit is gone and lean is moving into the back office. With product thinking, the design is changed and value-added work is eliminated along with its associated non-value added work (which is about 8 times bigger); manufacturing monuments with their long changeover times are ripped out and sold to your competitors; work from two factories is consolidated into one; new work is taken on to fill the emptied factories; and profit per square foot triples. And your brand is known for best-in-class quality, unbeatable on time delivery, world class performance, and pioneering the next generation of lean.
The sales argument is low price and good payment terms. With product thinking, the argument starts with product performance and ends with product reliability. The sales team is energized, and your brand is linked with solid products that just plain work.
The marketing approach is stickers and new packaging. With product thinking, it’s based on competitive advantage explained in terms of head-to-head performance data and a richer feature set. And your brand stands for winning technology and killer products.
Product thinking isn’t for everyone. But for those that try – your brand will thank you.
The Flux Lines of Innovation
There are countless books, tools, processes, methodologies and frameworks for innovation.
And cutting across all theory and practice, the biggest fundamental of innovation is fear.
We define fear as bad because it limits new thinking and new actions, but there’s another way to look at it. We should look at fear as a leading indicator of innovation potential.
When inputs, outputs, or contexts are different than expectations, our bodies create physical symptoms we recognize as fear. It’s this chemical change in the body, manifested as cold sweats, tingling hands, difficulty in breathing, or knotted stomachs, that’s the tell-tale sign innovation is in the house.
If things are predictable, knowable, understandable, there is no fear. And if things are predictable, knowable, understandable there is no innovation. By the associative theorem: no fear, no innovation.
We should learn to use our bodies as innovation barometers. When pressure builds, especially when we don’t know why, we should recognize our fear, not as a blocker of innovation, but as a leading indicator of it.
Innovation, especially the type that reinvents, is not an in-the-head thing, it’s an in-the-chest thing. It’s indescribable, un-scriptable, and almost spiritual. Just as migratory birds sense weak magnetic fields to guide themselves home, we can use our bodies to sense fear and guide ourselves along the flux lines of innovation.
Fear is scary and can be uncomfortable. But for innovation, it’s scarier if there’s no fear.
Wrestle Your Success To The Ground
Innovation, as a word, has become too big for its own good, and, as a word, is almost useless. Sure, it can be used to enable magical reinvention of business models and revolutionary products and technologies, but it can also be used to rationalize the rehash work we were going to do anyway. The words that send angry chills down the back of the would-be-innovative company – “We’re already doing it.”
When company leaders talk about doing more innovation, there’s a lot of pressure in the organization to point to innovative things already being done. The organization misinterprets the desire for more innovation as a negative commentary on their work. The mental dialog goes like this – We’re good at our work, we’re working as hard as we can, and we’re doing all we can to meet objectives – hey, look at this innovative stuff we’re doing. Clearly this isn’t what company leaders are looking for, but the word does have that influence.
What can feel better is to describe what is meant by innovation. Wherever we are, whatever successes we’ve had, we want to change our behaviors to create new, more profitable business models; create new products and technologies that obsolete our best, most profitable ones; and change our behaviors to create new, more profitable markets. The key is to acknowledge that our existing behaviors are the very thing that has created our success (and thank them for it), and to acknowledge the desire to build on our success by obsoleting it. When we ask for more innovation, we’re asking for new behaviors to dismantle our current day success behind us to create the next level of success.
There’s a tight link to innovation and failure – risk, learning, experimentation – but there’s a missing link with success. Acknowledgement of success helps the organization retain its self worth and helps them feel good about trying new stuff. However, even still, success is huge deterrent to innovation. Company success will retain the behaviors that created it, and more strongly, as new behaviors are injected, the antibodies of success will reject them. Our strength becomes our weakness.
Strong technologies become anchors to themselves; successful, stable, long-running markets hold tightly to resources that created them; and time-tested business models are above the law. New behaviors almost don’t stand a chance.
Fear of losing what we have is the number one innovation blocker. Where failure blocks innovation narrowly in the blast zone, success smears a thick layer of inaction across the organization. What’s most insidious, since we celebrate success, since we laud customer focus, since we track and reward efficiently doing what we’ve done, we systematically thicken and stiffen the layer that gums up innovation.
Instead of starting with a call-to-arms for innovation, it’s best to define company values, mission, and strategic objectives. Then, and only then, define innovation as the way to get there. First company objectives, then innovation as the path.
Innovation, as a word, isn’t important. What’s important are the new behaviors that will wrestle success to the ground, and pin it.
What They Didn’t Teach Me in Engineering School
The technical stuff is the easy part. Technical systems respond predictably, but people don’t.
There’s nothing worse than solving the wrong problem, so before you start solving you’ve better done a whole lot of defining.
There is no exact answer; engineering is all about judgment.
Organizational structure is important. Whatever the structure, see its strengths and make them work for you. If you try to fight it, it will eat you.
Innovation isn’t about ideas, innovation is about commercializing ideas.
Engineering analysis can win minds, but not hearts. And hearts govern minds.
The engineer’s role is not to minimize risk; it’s to understand the commercial reward and take risk accordingly.
What people believe is far more powerful than what they think.
New technology threatens status quoers, and, in turn, they block it.
There is no problem unless someone important thinks there’s one.
All technical systems are really human systems masquerading as technical systems.
If you let it, fear dominates. Be afraid and do it anyway. But along the way, keep in mind that others are too afraid to try.
Engineering is not sane and rational; engineering is about people.
Starvation, Pressure, and Perspective Shift
I like Dave Snowden’s thinking on innovation – starvation, pressure, and perspective shift. Here’s what it means to me:
Starvation – Left to our own, we’ll do as we did before. Starvation of resources pushes thinking away from stale, worn paths. Almost in reverse, define what you don’t want, then construct intelligent constraints (the most difficult part of the whole deal) so it’s out of the design space. Constrain the team so they can’t use the most expensive material; constrain the team so they can’t use the same old technology; constrain them so they can’t use the tried and true business model. It’s reverse thinking, but constraints – telling them what they can’t do – frees up design space. Constraints say “Do anything you want, except this.” which constrains far less than specifications. Constrain them to free them.
Pressure – Left to our own, we’ll reuse old thinking. Time pressure drags thinking out of the ruts of our success. Define creative constraints then, to create pressure, give the team insufficient time to think it through. Force them to swim differently with the problem. The best way I know is to explain the constraints then give the team fifteen minutes to build a prototype. (Yes, fifteen.) The prototype is non-functional, and can be made from whatever is on hand – cardboard, clay, duct tape, or packing peanuts. The short time frame creates pressure, and the pressure extrudes different thinking. Building a prototype shifts from learning-in-the-brain to learning-with-the-hands. And since hands learn differently than brains, new thinking is cast.
Perspective Shift – Left to our own, we’ll do a remake. Perspective shift moves us to a different place to create a healthy disrespect for today’s thinking. Seen in the right new light, our successes should look problematic. (From the front a skunk isn’t so bad, but from behind things aren’t so good.) Building a bridge to a new perspective can shift things a little, but for a tectonic shift, formalize the consequences of inaction. Think – “If we don’t do this, a very bad thing will happen.” Perspective shift is all about creating action in a new direction.
You won’t get it right the first time, but, no matter. The real enemy is inaction.
Own The Behavior
The system is big and complex and its output is outside your control. Trying to control these outputs is a depressing proposition, yet we’re routinely judged (and judge ourselves) on outputs. I think it’s better to focus on system inputs, specifically your inputs to the system.
When the system responds with outputs different than desired, don’t get upset. It’s nothing personal. The system is just doing its job. It digests a smorgasbord of inputs from many agents just like you and does what it does. Certainly it’s alive, but it doesn’t know you. And certainly it doesn’t respond differently because you’re the one providing input. The system doesn’t take its output personally, and neither should you.
When the system’s output is not helpful, instead of feeling badly about yourself, shift your focus from system output to the input you provide it. (Remember, that’s all you have control over.) Did you do what you said you’d do? Were you generous? We’re you thoughtful? We’re you insightful? Did you give it your all or did you hold back? If you’re happy with the answers you should feel happy with yourself. Your input, your behavior, was just as it was supposed to be. Now is a good time to fall back on the insightful grade school mantra, “You get what you get, and you don’t get upset.”
If your input was not what you wanted, then it’s time to look inside and ask yourself why. At times like these it’s easy to blame others and outside factors for our behavior. But at times like these we must own the input, we must own the behavior. Now, owning the behavior doesn’t mean we’ll behave the same way going forward, it just means we own it. In order to improve our future inputs we’ve got to understand why we behaved as we did, and the first step to better future inputs is owning our past behavior.
Now, replace “system” with “person”, and the argument is the same. You are responsible for your input to the person, and they are responsible for their output (their response). When someone’s output is nonlinear and offensive, you’re not responsible for it, they are. Were you kind? Thoughtful? Insightful? If yes, you get what you get, and you don’t get upset. But what if you weren’t? Shouldn’t you feel responsible for their response? In a word, no. You should feel badly about your input – your behavior – and you should apologize. But their output is about them. They, like the system, responded the way they chose. If you want to be critical, be critical of your behavior. Look deeply at why you behaved as you did, and decide how you want to change it. Taking responsibility for their response gets in the way of taking responsibility for your behavior.
With complex systems, by definition it’s impossible to predict their output. (That’s why they’re called complex.) And the only way to understand them is to perturb them with your input and look for patterns in their responses. What that means is your inputs are well intended and ill informed. This is an especially challenging situation for those of us that have been conditioned (or born with the condition) to mis-take responsibility for system outputs. Taking responsibility for unpredictable system outputs is guaranteed frustration and loss of self-esteem. And it’s guaranteed to reduce the quality of your input over time.
When working with new systems in new ways, it’s especially important to take responsibility for your inputs at the expense of taking responsibility for unknowable system outputs. With innovation, we must spend a little and learn a lot. We must figure out how to perturb the system with our inputs and intelligently sift its outputs for patterns of understanding. The only way to do it is to fearlessly take responsibility for our inputs and fearless let the system take responsibility for its output.
We must courageously engineer and own our behavioral plan of attack, and modify it as we learn. And we must learn to let the system be responsible for its own behavior.