Shipulski On Design

Archive for the ‘New Thinking’ Category

Doing new things doesn’t take a long time. What takes a long time is seeing things as they are. Getting ready takes time, not doing new. Awareness of assumptions, your assumptions, others’ assumptions, the company’s – that’s critical path.

An existing design, product, service, or process looks as it does because of assumptions made during long ago for reasons no longer relevant (if they ever were). Design elements blindly carried forward, design approaches deemed gospel, scripted service policies that no longer make sense, awkward process steps proceduralized and rev controlled – all artifacts of old, unchallenged assumptions. And as they grow roots, assumptions blossom into constraints. Fertile design space blocked, new technologies squelched, new approaches laughed out of town – all in the name of constraints founded on wilted assumptions. And the most successful assumptions have the deepest roots and create the deepest grooves of behavior.

Cows do the same thing every day. They wake up at the same time (regardless of daylight savings), get milked at the same time, and walk the same path.  They walk in such a repeatable way, they make cowpaths – neat grooves walked into the landscape – curiously curved paths with pre-made decisions. No cow worth her salt walks outside the  cowpath. No need. Cows like to save their energy for making milk at the expense of making decisions. If it was the right path yesterday, it’s right today.

But how to tell when old assumptions limit more than they guide? How to tell when it’s time to step out of the groove? How to tell a perfectly good cowpath from one that leads to a dry watering hole? When is it time to step back and create new history? Long ago the first cow had to make a choice, and she did. She could have gone any which way, and she did. She made the path we follow today.

With blind acceptance of assumptions, we wither into bankruptcy, and with constant second-guessing we stall progress. We must strike a balance. We must hold healthy respect for what has worked and healthy disrespect for the status-quo. We must use forked-tongue thinking to pull from both ends. In a yin-yang way, we must acknowledge how we got here, and push for new thinking to create the future.

Our organizations are set up in silos, and we’re measured that way. (And we wonder why we get local optimization.) At the top of engineering is the VP of the Red Team, who is judged on what it does – product.  At the top of manufacturing is the VP of the Blue Team, who is judged on how to make it – process. Red is optimized within Red and same for Blue, sometimes with competing metrics.  What we need is Purple behavior.

Here’s a link to a short video (1:14): Organizationally Challenged

And embedded below:

Let me know what you think.

Creating new products that provide a useful function is hard, and insuring they function day-in and day-out is harder.  Plain and simple, engineering is hard.

Planes must fly, cars must steer, and Velcro must stick. But, at every turn, there are risks, reasons why a new design won’t work, and it’s the engineer’s job to make the design insensitive to these risks. (Called reducing signal to noise ratio in some circles.) At a fundamental level engineering is about safety, and at a higher level it’s about sales – no function, no sales.

That’s why at every opportunity engineers reduce risk . (And thank goodness we do.) It makes sense that we’re the ones that think things through to the smallest detail, that can’t move on until we have the answer, that ask odd questions that seem irrelevant. It all makes sense since we’re the ones responsible if the risks become reality. We’re the ones that bear ultimate responsibility for product function and safety, and, thankfully, it shapes us.

But there’s a dark side to this risk reduction mindset – where we block our thinking, where we don’t try something new because  of problems we think we may have, problems we don’t have yet. The cause of this innovation-limiting behavior: problem broadening, where we apply a thick layer of problem over the entirety of a new concept, and declare it unworkable. Truth is, we don’t understand things well enough to make that declaration, but, in a knee-jerk way, we misapply our natural risk reduction mindset. Clearly, problems exist when doing new, but real problems are not broad, real problems are not like peanut butter and jelly spread evenly across the whole sandwich. Real problems are narrow; real problems are localized, like getting a drip of jelly on your new shirt.

How to get the best of both worlds? How to embrace the risk reduction mindset so products are safe and help engineering folks to try something radically new? To innovate?

We’ve got the risk reduction world covered, so it’s all about enhancing the try-something-new side. To do this we need to combat problem broadening; we need a process for problem narrowing. With problem narrowing, engineers drill down until the problem is defined as the interaction of two elements (the jelly and your shirt), defined in space (the front of your shirt) and time (when the knife drops a dollop on your shirt). Where problem broadening tells us to avoid making peanut butter and jelly sandwiches altogether (those sandwiches will always dirty our shirts), problem narrowing tells use to put something between the knife and the front of your shirt, or to put on your new shirt after you make your sandwich, or to do something creative to keep the jelly away from our shirt.

Problems narrow as knowledge deepens. Work through your fears, try something new, and advance your knowledge. Then define your problems narrowly, and solve them.

Innovate.

It’s high tide for innovation – innovate, innovate, innovate. Do it now; bring together the experts; hold an off-site brainstorm session; generate 10⁶ ideas. Fast and easy; anyone can do that. Now the hard part: choose the projects to work on. Say no to most and yes to a few. Choose and execute.

To choose we use processes to rank and prioritize; we assign scores 1-5 on multiple dimensions and multiply. Highest is best, pull the trigger, and go. Right? (Only if it was that easy.) Not how it goes.

After the first round of scoring we hold a never-ending series of debates over the rankings; we replace 5s with 3s and re-run the numbers; we replace 1s with 5s and re-re-run. We crank on Excel like the numbers are real, like 5 is really 5. Face it – the scores are arbitrary, dimensionless numbers, quasi-variables data based on judgment. Face it – we manipulate the numbers until the prioritization fits our judgment.

Clearly this is a game of judgment. There’s no data for new products, new technologies, and new markets (because they don’t exist), and the data you have doesn’t fit. (That’s why they call it new.) No market – the objective is to create it; no technology – same objective, yet we cloak our judgment in self-invented, quasi-variables data, and the masquerade doesn’t feel good. It would be a whole lot better if we openly acknowledged it’s judgment-based – smoother, faster, and more fun.

Instead of the 1-3-5 shuffle, try a story-based approach. Place the idea in the context of past, present, and future; tell a tale of evolution: the market used to be like this with a fundamental of that; it moved this way because of the other, I think. By natural extension (or better yet, unnatural), my judgment is the new market could be like this… (If you say will, that’s closeted 1-3-5 behavior.) While it’s the most probable market in my judgment, there is range of possible markets…

Tell a story through analogy: a similar technology started this way, which was based on a fundamental of that, and evolved to something like the other. By natural evolution (use TRIZ) my technical judgment is the technology could follow a similar line of evolution like this…. However, there are a range of possible evolutionary directions that it could follow, kind of like this or that.

And what’s the market size? As you know, we don’t sell any now. (No kidding we don’t sell any, we haven’t created the technology and the market does not exist. That’s what the project is about.) Some better questions: what could the market be? Judgment required. What could the technology be? Judgment. If the technology works, is the market sitting there under the dirt just waiting to be discovered? Judgment.

Like the archeologist, we must translate the hieroglyphs, analyze the old maps, and interpret the dead scrolls. We must use our instinct, experience, and judgment to choose where to dig.

Like it or not, it’s a judgment game, so make your best judgment, and dig like hell.

We are responsible for our actions, for what we do, for our work, and others are responsible for their response to it. (That’s why they call it responsibility.) Though we know we can’t control others, we still snare ourselves in worry trap: What will they think? Will they like it? What will they say?

Worse than the worry trap, however, is when we actually change our work based on what others will think. A big no-no. We’re asked to do the work because we’re talented, we’re uniquely qualified, we’re the experts. Why do we let opinions of others wield so much power? Who cares what they say. We will let our work speak for itself.

There’s not much in life we have control over, but work is one of them. We control most everything about it: the what and how, the caliber, the tenor. We choose to do marginal work, average work, great work, or magical work.  It’s our choice.  We choose. When we chose to do magical work, its voice powerful enough to drown out the less capable, the politically motivated, and the CEO.

So go do magical work. Do work so good you don’t remember how you did it, so good you don’t think you could do it again, so good it scares you. But be ready – magical work, by definition, is misunderstood.

What will they say about your magic?  It doesn’t matter, magic’s voice will drown them out.

Doing new is hard and starting new is particularly hard. Once fear is overcome and new is started, doing new becomes a battle with discouragement. Not managed, discouragement can stop new.

Slumped shoulders and a head hung low are the signs and a mismatch with expectations is the source. Expectations are defined in the form of a project plan, but, since the work is new, expectations are not grounded, not calibrated. How long will it take to do something we’ve never dreamed of doing? Yet when disguised as a project plan, uncalibrated expectations become a hard deadline.

When you want to do new, you give the project to your best. When they use the right tools, the latest data, and the best processes, yet new does not come per the plan, your best can become discouraged. But this discouragement is misplaced. Sure, the outcome is different from the plan, but reality isn’t the problem, it’s the plan, the expectations. They did everything right, so tell them. Tell them the expectations are out of line. Tell them you think their doing a good job. Tell them if it was easy, you’d have given the project to someone else. Tell them they can feel discouraged for five more minutes, but then they’ve got to go back, look new in the eye, and kick its ass.

Environmental stability, aka, Green, is just starting. Most are still in reluctant compliance mode, hoping beyond hope that this newest of corporate initiatives dies on the vine, that it’s just another corporate initiative. Wrong. Very wrong. It’s the way we’re going to grow our business; it’s the way we’re going to make money. It’s time to open our minds, grab Green by the throat, and shake it. Green is here to stay, and Green will demand we change our thinking, will make us see our problems differently, will require we dismantle our intellectual inertia, will require innovation.

Pretend you’re a manufacturer of jeans, the blue ones, the ones that feel so good when you put them on, the ones you’d like to wear to work if you could. (Maybe that’s just me.) Year-on-year your innovation efforts focus on adding pockets then removing them, adding holes then removing them, zippers here then there, dark wash then light, baggy then tight, and yellow stitching than red. What else can a jean innovator do?

Corporate sends the memo: “We’re going Green.” Green jeans. They hire the best sustainability consultants and you, the jean innovator, sit through the sustainability audit results. Their recommendation – reduce carbon footprint: use materials that consume less energy, reduce electricity in your factories, minimize distribution’s fuel costs, and reduce travel miles of your sales folks. Brilliant. Whatever we paid these guys, it was too much. But then they twist your brain. The carbon footprint from the use of your product dwarfs everything else. Your customers generate a massive carbon footprint when they wash and dry your jeans, and you have no control over it. Your jeans are made once and washed and dried countless times. Whoa. Your eyes roll back in your head. What’s a jean innovator to do? First thing – forget about the stupid pockets. Next, figure out how to reduce the carbon footprint generated by your customers. Define the problem and innovate. But what’s the problem?

Why do folks wash their jeans? The obvious answer – they’re dirty. Let’s figure a way to prevent jeans from getting dirty, right? No. The real answer – they stretch, they get baggy and don’t fit right; so we wash them to tighten things up. We wash CLEAN jeans because they get baggy, not because they’re dirty. Let’s fix that.

Believe it or not, there are many likely innovative solutions to make jeans de-baggy themselves, but that’s not the point. The point is we must innovate on jeans that reconfigure, and must not innovate on keeping jeans clean (though we may innovate on that down the road) and must not innovate on pockets, zippers, and stitching.

Green shaped our innovation work. We now have Green jeans that feel good and spring back after wearing and fit great on day two – no washing required. We now have Green jeans that save customers time and money while flattering their backside. But here’s the point – we would have never invented de-baggying jeans without opening our minds to Green as a way to grow our business, to Green as a way to make money. Reluctant compliance won’t get us there. Grab Green by the throat and shake it…before your competitors do.

“Constraint” is most often an excuse rather than a constraint. In fact, there are very few true constraints, with most of them living in the domain of physics.

A constraint is when something cannot be done. It’s not when something is difficult, complex, or unknown. And, it’s not when the options are costly, big, or ugly. There are no options with a true constraint. Nothing you can do.

The Physical Constraint
If your new product requires one of its moving parts to go faster than the speed of light, that’s a physical constraint (and not a good idea). If your new technology requires a material that’s stronger than the strongest on record, that’s a constraint (and, also, not a good idea). If your new manufacturing process consumes more water than your continent can spare, that’s a constraint. (This may not be a true constraint in the physics sense, but it’s damn close.) Don’t try to overpower the physical constraint – you can’t beat Mother Nature. The best you can do is wrestle her to a tie, then, when you tire, she pins you.

The Legal Constraint
If your approach violates a law, that’s a legal constraint. Not a true constraint in a physical sense, as there are options. You can change your approach so the law is not violated (maybe to a more costly approach), you can lobby for a law change (may take a while, but it’s an option), or you can break the law and roll the dice. To be clear, I don’t recommend this, just wanted to point out that there are options. Options exist when something is not a constraint, though the consequences can be most undesirable, severe, and may not fit with who we are.

The Emotional Constraint
If a person in power self-declares something as a constraint, decides there are no options, that’s an emotional constraint. Not a true constraint in a physical sense, but the most dangerous of the triad. When there is no balance in the balance of power, or the consequences of pushing are severe, the self-declared emotional constraint stands – there are no options. Like with the speed of light, where adding energy cannot overcome the speed constraint, adding reasoning energy cannot overcome the emotional constraint. I argue that most constraints are emotional.

Physical and legal constraints are relatively easy to see and navigate, but the emotional constraint is something different altogether. Difficult to see, difficult to predict, and difficult to overcome. Person-based rather than physics or law-based.

Strategies to overcome emotional constraints must be based on the particulars of the person declaring the constraint. However, there is one truism to all successful strategies: Just as the person in power is the only one who can convince himself something is a constraint, he is also the only one who can convince himself otherwise.

There is a groundswell of interest in innovation across the planet. As historians know, the interest in innovation is cyclic, and this year it’s surely in vogue. Everyone wants more of it, even if we don’t know what it is – we want it. And we want it because we want it; it’s an emotional want. Never mind that we don’t know how to do it, damn it, we’re going to do more innovation come hell or high water. Not knowing how to do innovation is an obstacle, but it can be overcome with the right tools, processes and a good training plan. Our people are capable and willing, so there’s no problem there. But there is a show-stopper out there: the innovation edict is incremental work – it’s another thick layer of work slopped onto our already full plates. Even before the innovation edict, we’re doing two or three jobs, we’ve extended the do-more-with-less mantra beyond the ridiculous, and we’re stretched to the breaking point with workloads that defy all tests of reason. How can we be expected to do more?

The truth of the matter is we cannot do more; we’re already diluted beyond all effectiveness. Any more dilution would be like watering down water with more water. It has no meaning. And what makes the innovation edict especially ludicrous is that innovation requires a lot of thinking time, quality thinking time, uninterrupted thinking time. It’s a thinking person’s sport. And not just mortal thinking, it requires novel thinking, thinking we’ve never done before. Do you have time to think with your current workload? I don’t think so.

Thinking? You’re crazy. We don’t have time to think, we need to do innovation!

As we know, managers have extreme difficulty discerning activity from progress, and not many think that thinking is progress. It sure doesn’t look like activity. If you want to aggravate a manager, sit at your desk and think. When they ask you what you’re doing, tell them you’re thinking. Then watch their face turn colors like a New England foliage.

What do we do about it? The answer comes from Jim Collins – create a stop doing list. We must create innovation bandwidth by stopping work on lower priority activities. Stop. Stop. Stop. And don’t just talk about stopping, actually stop doing things. It’s the only way. Of course this is difficult because it requires prioritization. It requires judgment and guts. And feelings will get hurt because some projects will stop. So be it. Actually, I think major disagreement, anger, and long, difficult meetings are objective evidence that activities are actually stopping. No anger, no difficult meetings, no freed up innovation bandwidth. Do you want to do innovation or just talk about doing innovation?

There’s no free lunch with innovation. Innovation requires our most precious resource – our time.

In a previous post I defined the term brand-damaging threshold and said I’d talk about how to improve product robustness. So, here goes.

Every company is at a different stage in their formalized product robustness efforts, so it’s challenging to talk meaningfully to everyone. But there are two especially meaningful principles that have served me well through the years.

I had the privilege of working with Don Clausing - Total Quality Design, The House of Quality, Enhanced QFD, and Robust Quality. I vividly remember the conversation where Don shared one of his secrets. As we watched a robustness test run, Don, in his terse way, barked out a guiding principle of improving product robustness. He said:

“Improve robustness at the expense of predicting it.”

I asked Don what the hell he meant (he liked to make his students work for it), and after some prodding, he went on to explain why it’s so important. He said people spend far too much time running tests to predict robustness and then spend even more time calculating mean time between failures (MTBF). If that’s not enough, then they spend time arguing about MTBFs and the confidence intervals. He said companies should dedicate all their time and energy improving robustness. “That’s what matters to the customer,” he said. And then he continued with something like: “Predicting robustness is worse than a simple waste of time.” (He wasn’t that polite.) But I still didn’t get it. What’s the big deal about predicting robustness? Read the rest of this entry »

It’s time to write, but, again, no topic.  This writing-once-a-week thing is tough.  I drop my son off at the hockey rink and walk back to the parking lot to write in my car (I’m telling you, this is a good place to write). Before I get to my car, my cell phone rings. It’s a teacher friend of mine. He’s the guy at the high school who helps kids work out issues with substance use/abuse and related topics. He’s a real pro – every high school should have a person of his caliber. Without introducing himself, he says, “You want to go for a hike tomorrow?” “I have to work,” I say. “It’s Veteran’s Day,” he says. “Yeah, I know, and I have to work,” I reply. “Oh ya, I forgot about that,” he says with a chuckle.

My mind clicks and I remember a discussion we had the previous week while on a walk.  I ask, “Do you remember talking about that trick to break intellectual inertia?” “Ya, we talked about how I used it to help a kid work himself out of some destructive behavior. Make it worse and do the opposite,” he says. “I love it; it works great,” he says. I now have my topic. We talk for a while and he helps my thinking converge. This one is a joint effort.

Here’s the problem: problems are stressful. We have a physiological reaction to problems; adrenaline rushes through our veins; our blood pressure increases; our heart rate increases; we get flushed. This is real. It’s run or attack, flight or fight. Our mental processing is all about survival. And there is real reason for concern; there are real consequences to not solving a problem – your reputation, your authority, your job. Read the rest of this entry »