Shipulski On Design

Archive for the ‘Seeing Things As They Are’ Category

Not Invented Here (NIH) is ever-present and misunderstood.

An operational definition of NIH: Group 1 creates new thinking that falls within the official domain of Group 2. When presented with the new thinking, Group 2 rejects it.

It is said Group 2 rejects new thinking because they’re threatened.   But that’s too high level to be helpful.  To get at the root of it, we need to dig.

First, some NIH:

• Your new thinking is out of alignment with my priorities. Even if I spend a lot of time to understand it, I’m afraid I’ll fail. I reject your new thinking.
• Your new thinking is out of alignment with responsibility.  (That thinking should come from me.) If I adopt your new thinking, I’ll look stupid, and I’m afraid I’ll fail. I reject your new thinking.
• Your new thinking is out of alignment with my knowledge. I’m afraid I’ll fail. I reject your new thinking.
• Your new thinking is out of alignment with how I do things. I’m afraid I’ll fail.  I reject your new thinking.

Now, some non-NIH :

• My priorities are out of alignment with your new thinking. Though I already have several good ideas that I don’t have time for, can you give me more details so together we can combine the best elements?
• My responsibility is out of alignment with your new thinking, but your new thinking is good. Can you give me more details so together we can investigate possibilities?
• My knowledge is out of alignment with your new thinking. Can you give me more details so we can learn together?
• My way of doing things is out of alignment with your new thinking. Can you give me more details so together we can rethink things?

The key to NIH reduction is to create alignment. With your new thinking not yet fully formed, ask Group 2 for their input. Better yet, ask for their help. Tell them what you don’t know, tell them what you have wrong, tell them how they have a better perspective because it’s their domain, and ask them to help improve it.  (All this is best done informally and off-line, at least to start.)

One little-known fact about NIH – it’s pronoun sensitive. Take care to replace I, you, and yours with we.

Some thoughts on vacation:

Take fewer longer vacations at the expense of shorter ones.

Work hard, but on something else.

On route to your destination, throw your cell phone from a moving vehicle.

Forget about your work so you can do it better when you return.

Don’t check in at work – that undoes all the relaxation.

Vacation with kids, and take your cues from them.

Engineers hate uncertainty. (More precisely, it scares us to death.) And our role in the company is to snuff it out at every turn, or so we think.

To shield ourselves from uncertainty, we take refuge in our analyses. We create intricate computer wizardry to calm our soles. We tell ourselves our analytic powers can stand toe-to-toe with uncertainty. Though too afraid to admit, at the deepest level we know the magic of our analytics can’t dispatch uncertainty. Like He-Who-Should-Not-Should-Be-Named, uncertainty is ever-present and all-powerful. And he last thing we want is to call it by name.

Our best feint is to kill uncertainty before it festers. As soon as uncertainty is birthed, we try slay it with our guttural chant “It won’t work, it won’t work, it won’t work”. Like Dementors, we drain peace, hope, and happiness out of the air around a new idea. We suck out every good feeling and reduce it to something like itself, but soulless. We feed on it until we’re left with nothing but the worst of the idea.¹

Insidiously, we conjure premonitions of mythical problems and predict off-axis maladies. And then we cast hexes on innovators when they don’t have answers to our irrelevant quandaries.

But our unnatural bias against uncertainty is misplaced. Without uncertainty there is no learning. Luckily, there are contrivances to battle the dark art of uncertainty.

When the engineering warlocks start their magic, ask them to be specific about their premonitions. Demand they define the problem narrowly – between two elements of the best embodiment; demand they describe the physical mechanisms behind the problem (warlocks are no match for physics); demand they define the problem narrowly in time – when the system spools up, when it slows down, just before it gets hot, right after it cools down. What the warlocks quickly learn is the problem is not the uncertainty around the new idea; the problem is the uncertainty of their knowledge. After several clashes with the talisman of physics, they take off their funny pointy hats, put away their wands, and start contributing in a constructive way. They’re now in the right frame of mind to obsolete their best work

Uncertainty is not bad. Denying it exists is bad, and pretending we can eliminate it is bad. It’s time to demonstrate Potter-like behavior and name what others dare not name.

Uncertainty, Uncertainty, Uncertainty.

 ¹ Remus Lupin

As a subject matter expert (SME), you have more power than you think, and certainly more than you demonstrate.

As an SME, you have special knowledge. Looking back, you know what worked, what didn’t, and why; looking forward, you know what should work, what shouldn’t, and why.  There’s power in your special knowledge, but you underestimate it and don’t use it to move the needle.

As an SME, without your special knowledge there are no new products, no new technologies, and no new markets. Without it, it’s same-old, same-old until the competition outguns you. It’s time you realize your importance and behave that way.

As an SME, when you and your SME friends gang together, your company must listen. Your gang knows it all. From the system-level stuff to the most detailed detail, you know it. Remember, you invented the technology that powers your products. It’s time you behave that way.

As an SME, with your power comes responsibility – you have an obligation to use your power for good. Figure out what the technology wants, and do that; do the sustainable thing; do the thing that creates jobs; do what’s good for the economy; sit yourself in the future, look back, and do what you think is right.

As an SME, I’m calling you out. I trust you, now it’s time to trust yourself. And it’s time for you to behave that way.

Some ideas are so powerful they change you. More precisely, some ideas are so powerful you change your beliefs to fit them.

These powerful ideas come in two strains: those that already align with your beliefs and those that contradict.

The first strain works subtly. While you think on the idea, your beliefs test it for safety. (They work in the background without your knowledge.) And if the idea passes the sniff test, and your beliefs feel safe, they let the subconscious sniffing morph into conscious realization – the idea fits your beliefs. The result: You now better understand your beliefs and you blossom, grow, and amplify yourself.

The second strain is subtle as a train wreck – a full frontal assault on your beliefs. This strain contradicts our beliefs and creates an emotional response – fear, anger, stress. And because these ideas threaten our beliefs, our beliefs reject them for safety’s sake. It’s like an autoimmune system for ideas.

But this autoimmune system has a back door. While it rejects most of the idea, for unknown reasons it passes a wisp to our belief system for sniffing. Like a vaccine, it wants to strengthen our beliefs against the strain. And in most cases, it works. But in rare cases, through deep introspection, our beliefs self-mutate and align with the previously contradicting idea. The result: You change yourself fundamentally.

Truth is, ideas are not about ideas; ideas are about beliefs. Our beliefs give life to ideas, or kill them. But we give ideas too much responsibility, and take too little. Truth is, we can change what we think and feel about ideas.

More powerfully, we can change what we think and feel about our beliefs, but only if we believe we can.

Lean has rolled through our factories and generated profits at every turn.  Now it’s time to get serious about savings and realize the next level of savings. Companies are pushing lean into the back office, but that won’t get it done.  The savings will be good, but not great.  After picking low-hanging factory fruit, there’s uncertainty around what’s next for lean. 

Make it where you sell it, that’s next for lean.  Like a central theorem, this simple phrase will become lean’s mantra, and it will change everything, including our organizations themselves. The big multi-national companies have already started their journey, and we can take our cues from them.

The major automakers have assembly plants on all continents – objective evidence of make it where you sell it.  There are many benefits to make it where you sell it, but the top three are: speed, speed, speed.  The automotive value stream without make it where you sell it: make a car, put it on a boat, deliver it to a dealer, and sell it.  Make it where you sell it eliminates the boat: make it, deliver it, and sell it.  Inventory is proportional to cycle time and eliminating the long boat ride shortens the value stream, improves response time and reduces inventory. 

Make it where you sell it starts closest to the customer, and final assembly is the first to be established in-market. Engines and transmissions still ride the boat, but not for long.  After final assembly, make it where you sell it targets big, heavy, expensive subassemblies, so expect in-market engine and transmission plants.  (However, big ones like these may stay put for while due to technological, political, or cultural reasons.)

With one piece flow, right-sized machines, and short product runs, lean has taught us the most economic scale is far smaller than we’d imagined.  We’ve learned for our factories smaller is better, and make it where you sell it extrapolates smaller-is-better to the organization itself.  Here again, the big guys lead the way.  Multinationals are breaking themselves into smaller units, right-sizing into smaller regional companies – still big, but smaller.  Their in-country manufacturing creates nice tight feedback loops between customer and factory.  And there’s an important benefit to the brand – it becomes a local brand.  Not only can the brand better serve regional tastes, it provides goodwill in the form of jobs.

[Disclaimer: I don’t advocate outsourcing.  I’m simply explaining the forces at work and their consequences.]

Lean cares about speed, not countries, and make it where you sell it causes jobs flow across company boarders.  This is especiallylevant as countries compete for manufacturing jobs like their survival depended on them.  For those countries that understand manufacturing jobs are the bedrock of a sustainable economy, make it where you sell it can be threatening.  If you’re a country that doesn’t buy a lot of manufactured goods, you and your economy trouble – jobs will flow to where products are sold.

Make it where you sell it won’t stop at making, and will extend up stream.  The next logical extension is design it where you sell it, R&D it where you sell it, and innovate it where you sell it. (The biggest companies are already doing this with regional R&D centers.) More jobs will flow across borders, but this time they’ll be the coveted thinking jobs.

Make it where you sell it is the guiding principle companies are using to become more responsive, more productive, and local.  It has already broken the biggest companies into smaller ones. They’ve realized that the most economic scale is small, and they’re getting there using make it where you sell it.

Make it where you sell it will change all companies, even small ones.  And the mantra for small companies: think narrow and deep.

I will hold a half-day Workshop on Systematic DFMA Deployment on June 13 in RI.  (See bottom of linked page.) I look forward to meeting you in person.

Whether it’s a top-down initiative or a bottom-up revolution, your choice will make or break it.

When you have the inspiration for a bottom-up revolution, you must be brave enough to engage your curiosity without self-dismissing. You’ll feel the automatic urge to self-reject – that will never work, too crazy, too silly, too loony – but you must resist. (Automatic self-rejection is the embodiment of your fear of failure.) At all costs you must preserve the possibility you’ll try the loony idea; you must preserve the opportunity to learn from failure; you must suspend judgment.

Now it’s time to tell someone your new thinking. Summon the next level of courage, and choose wisely. Choose someone knowledgeable and who will be comfortable when you slather them with the ambiguity. (No ambiguity, no new thinking.) But most importantly, choose someone who will suspend judgment.

You now have critical mass – you, your partner in crime, and your bias for action. Together you must prevent the new thinking from dying on the vine. Tell no one else, and try it. Try it at a small scale, try it in your garage. Fail-learn-fail until you have something with legs. Don’t ask. Suspend judgment, and do.

And what of top down initiatives? They start with bottom-up new thinking, so the message is the same: suspend judgment, engage your bias for action, and try it. This is the precursor to the thousand independent choices that self-coordinate into a top-down initiative.

New thinking is a choice, and turning it into action is another. But this is your mission, if you choose to accept it.

I will be holding a half-day Workshop on Systematic DFMA Deployment on June 13 in RI. (See bottom of linked page.)  I look forward to meeting you in person.

As professionals we get paid to think. But unlike professional athletes, we’ve forgotten the importance of mind and body.

Clearly, mind is connected to body. (I’m not talking about a metaphysical connection, I’m talking about a physical physical connection.) There are electromechanical connections (nerves) that pass information between the two and hydromechanical connections (blood vessels) that pass chemistry (oxygen and glucose, among others). The coupling is clear – what happens in one influences the other, then the other retorts. This back-and-forth ringing is complex and real. From the outside, our system architecture is highly coupled, yet from the inside we forget.

Professional athletes want high performance, and they get it through hard work, good food, regimented eating schedules, and rest. From the outside it seems they’re all about body, but on the inside they’re all whole system optimization – mind and body. (Yogi Berra – baseball is 90% mental and the other half physical.) They know food and rest influence the body, but they also know it influences the mind. They remember, we forget.

As a professional thinker, I urge you to do all you can to think well. Eat well, eat regularly, and get rest. The cost of a bad decision is high, and they’re more likely when blood sugar is low and you’re tired. If you don’t do it for your career, do it for your company – remember, they’re paying you to think.

(Image credit: iStockphoto)

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.

The No. 1 reason initiatives are successful is support from top management. Whether it’s lean, Six Sigma, Design for Six Sigma or any program, top management support is vital. No argument. It’s easy with full support, but there’s never enough to go around.

But that’s the way it should be. Top management has a lot going on, much of it we don’t see: legal matters, business relationships, press conferences, the company’s future. If all programs had top management support, they would fail due to resource cannibalization. And we’d have real fodder for our favorite complaint—too many managers.

When there’s insufficient top management support, we have a choice. We can look outside and play the blame game. “This company doesn’t do anything right.” Or we can look inside and choose how we’ll do our work. It’s easy to look outside, then fabricate excuses to do nothing. It’s difficult to look inside, then create the future, especially when we’re drowning in the now. Layer on a new initiative, and frustration is natural. But it’s a choice.

We will always have more work than time….

Link to complete article

The new product development process creates more value than any other process. And because of this it’s a logical target for improvement.  But it’s also the most complicated business process.  No other process cuts across an organization like new product development. Improvement is difficult.

The CEO throws out the challenge – “Fix new product development.” Great idea, but not actionable. Can’t put a plan together.  Don’t know the problem.  Stepping back, who will lead the charge? Whose problem is it?

The goal of all projects is to solve problems.  And it’s no different when fixing product development – work is informed by problems. No problem, no fix. Sure you can put together one hell of a big improvement project, but there’s no value without the right problem. There’s nothing worse than spending lots of time on the wrong problem.  And it’s doubly bad with product development because while fixing the wrong problem engineers are not working on the new products.  Yikes.

Problems are informed by outcomes.  Make a short list of desired outcomes and show the CEO.  Your list won’t be right, but it will facilitate a meaningful discussion.  Listen to the input, go back and refine the list, and meet again with the CEO.  There will be immense pressure to start the improvement work, but resist.  Any improvement work done now will be wrong and will create momentum in the wrong direction.  Don’t move until outcomes are defined.

With outcomes in hand, get the band back together. You know who they are.  You’ve worked with them over the years. They’re influential and seasoned.  You trust them and so does the organization.  In an off-site location show them the outcomes and ask them for the problems. (To get their best thinking spend money on great food and a relaxing environment.)  If they’re the right folks, they’ll say they don’t know.  Then, they’ll craft the work to figure it out – to collect and analyze the data.  (The first part of problem definition is problem definition.) There will be immense pressure to start the improvement work, but resist.  Any work done now will be wrong.  Don’t move until problems are defined.

With outcomes and problems in hand, meet with the CEO.  Listen.  If outcomes change, get the band back together and repeat the previous paragraph. Then set up another meeting with the CEO.  Review outcomes and problems.  Listen.  If there’s agreement, it’s time to put a plan together.  If there’s disagreement, stop.  Don’t move until there’s agreement.  This is where it gets sticky.  It’s a battle to balance everyone’s thoughts and feelings, but that’s your challenge.  No words of wisdom on than – don’t move until outcomes and problems are defined.

There’s a lot of emotion around the product development process.  We argue about the right way to fix it – the right tools, training, and philosophies. But there’s no place for argument.  Analyze your process and define outcomes and problems.  The result will be a well informed improvement plan and alignment across the company.