Shipulski On Design

Archive for the ‘Top Line Growth’ Category

Engineers fear social media, but shouldn’t. Our fear comes from lack of knowledge around information flow. Because we don’t understand how information flow works, we stay away. But our fear is misplaced – with social media information flow is controllable.

For engineers, one-way communication is the best way to start. Engineers should turn on the information tap and let information flow to them. Let the learning begin.

At first, stay away from FaceBook – it’s the most social (non-work feel), least structured, and most difficult to understand – at least to me.

To start, I suggest LinkedIn – it’s the least social (most work-like) and highly controllable. It’s simple to start – create an account, populate your “resume stuff” (as little as you like) and add some connections (people you know and trust). You now have a professional network who can see your resume stuff and they can see yours. But no one else can, unless you let them. Now the fun part – find and join a working group in your interest area. A working group is group of like-minded people who create work-related discussions on a specific topic. Mine is called Systematic DFMA Deployment. You can search for a group, join (some require permission from the organizer), and start reading the discussions. The focused nature of the groups is comforting and you can read discussions without sharing any personal information. To start two-way communication, you can comment on a discussion.

After LinkedIn, engineers should try Twitter. Tweets (sounds funny, doesn’t it?) are sentences (text only) that are limited to 140 characters. With Twitter, one-way communication is the way to start – no need to share information. Just create an account and you’re ready to learn. With LinkedIn it’s about working groups, and with Twitter it’s about hashtags (#). Hashtags create focus with Twitter and make it searchable. For example, if the tweet creator uses  #DFMA in the sentences, you can find it.  Search for #DFMA and you’ll find tweets (sub-140 character sentences) related to design for manufacturing and assembly. When you find a hashtag of interest, monitor those tweets. (You can automate hashtag searches – HootSuite – but that’s for later). And when you find someone who consistently creates great content, you can follow them. Once followed, all their tweets are sent to your Twitter account (Twitter feed). To start two-way communication you can retweet (resend a tweet you like), send a direct message to someone (like a short email), or create your own tweet.

Twitter’s format comforts me – short, dense bursts of sentences and no more. Long tweets are not possible. But a tweet can contain a link to a website which points to a specific page on the web. To me it’s a great combination – short sentences that precisely point to the web.

With engineers and social media, the goal is to converge on collaboration. Ultimately, engineers move from one-way communication to two-way communication, and then to collaboration. Collaboration on LinkedIn and Twitter allows engineers to learn from (and interact with) the world’s best subject matter experts. Let me say that again – with LinkedIn and Twitter, engineers get the latest technical data, analyses, and tools from the best people in the world. And it’s all for free.

For engineers, social and media are the wrong words. For engineers, the right words are – controlled, focused, work-related information flow. And when engineers get comfortable with information flow, they’ll converge on collaboration. And with collaboration, engineers will learn from each other, help each other, innovate and, even, create personal relationships with each other.

Companies still look at social media as a waste of work time, and that’s especially true when it comes to their engineers. But that’s old thinking.  More bluntly, that’s dangerous thinking. When their engineers use social media, companies will develop better products and technologies and commercialize them faster.

Plain and simple, companies that accelerate their engineers into social media will win.

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.

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.

We all want to increase profits, but sometimes we get caught in the details and miss the big picture:

Profit = (Price – Cost) x Volume.

It’s a simple formula, but it provides a framework to focus on fundamentals. While all parts of the organization contribute to profit in their own way, engineering’s work has a surprisingly broad impact on the equation.

The market sets price, but engineering creates function, and improved function increases the price the market will pay. Design the product to do more, and do it better, and customers will pay more. What’s missing for engineering is an objective measure of what is good to the customer.

To read the complete article, click this link.

We’ve all done Voice of the Customer (VOC) work, where we jump on a plane, visit our largest customers, and ask leading questions. Under the guise of learning it’s mostly a mechanism to justify what we already want to do, to justify the products we know want to launch. (VOC should stand for Validate Our Choices.)

It’s a waste of time to ask customers for the next big thing or get their thoughts on a radical technology. First off, it’s not their job to know the next big thing, it’s ours. The next big thing is bigger than their imagination, never mind what they do today. (That’s why it’s called the next big thing.) And if we wait for customers tell us the next big thing, we’re hosed. (Their time horizon is too short and ours is shorter.) In this case it’s best to declare failure; our competitors figured it out a long time ago (they didn’t wait for the customer) and are weeks from commercialization. We should get busy on the next, next big thing because we’ve already missed this next generation. Next time we’ll silence the voice of the customer (VOC) and listen to the voice of the technology (VOT).

As far as radical technology, if we wait for customers to understand the technology, it’s not radical. Radical means radical, it means game-changing, a change so radical it obsoletes business models and creates unrecognizable, ultra-profitable, new ones. That’s radical. If we don’t start technical work until our customers understand the new technology, it’s no longer radical, and our competitors have already cornered the market. Again, we’ve missed an entire generation. Next time we’ll silence the voice of the customer (VOC) and listen to the voice of the technology (VOT).

Technology has a life force; it has a direction; it knows what it wants to be when it grows up. It has a voice. Independent of customer, it knows where it wants to go and how it will get there. At the highest level it has character traits and preferred paths, a kind of evolutionary inevitability; this is the voice of technology (VOT).

Technology will evolve to complete itself; it will move toward natural periodicity among its elements; it will harmonize itself; it will become more controllable; it will shorten its neural flow paths;  it will do yoga to improve its flexibility; its feet will grow too fast and create adolescent imbalance; it will replicate into multiples selves; it will shrink itself;  it will improve its own DNA. This is VOT.

Technology cannot tell us its lower-level embodiments (we control that), but it does sing hymns of its high-level wants and desires, and we must listen. No need to wait for VOC, it’s time to listen to VOT.

Like a dog whistle, technologists can hear VOT while others cannot. We understand the genetics of technology and we understand its desires (because we understand its physics.) We can look back to its ancestors, see its trajectory of natural evolution, and predict attributes of its offspring. Before everyone else, we see what will be.

Next time, instead of VOC, ask your technologists what the voice of technology is saying, and listen.

Sometimes we engineers know the answer before the question, sometimes we know the question’s wrong before it’s asked, and sometimes we’re just plain pig-headed. And if we band together, there’s no hope of changing how things are done. None. So, how to bring new thinking to the engineering community? In three words: WHAT, WHY, HOW.

WHY – Don’t start with WHAT. If you do, we’ll shut down. You don’t know the answer, we do. And you should let us tell you. Start with WHY. Give us the context, give us the problem, give us the business fundamentals, give us the WHY. Let us ask questions. Let us probe. Let us understand it from all our angles. Don’t bother moving on. You can’t. We need to kick the tires to make sure we understand WHY. (It does not matter if you understand WHY. We need understand it for ourselves, in our framework, so we can come up with a solution.)

WHAT – For God’s sake don’t ask HOW – it’s too soon. If you do, we’ll shut down. You don’t know the answer, we do. And, if you know what’s good for you, you should let us tell you. It’s WHAT time. Share your WHAT, give us your rationale, explain how your WHAT follows logically from your WHY, then let us ask questions. We’ll probe like hell and deconstruct your WHY-WHAT mapping and come up with our own, one that makes sense to us, one that fits our framework. (Don’t worry, off-line we’ll test the validity of our framework, though we won’t tell you we’re doing it.) We’ll tell you when our WHY-WHAT map holds water.

HOW – Don’t ask us WHEN! Why are you in such a hurry to do it wrong?! And for sanity’s sake, don’t share your HOW. You’re out of your element. You’ve got no right. Your HOW is not welcome here. HOW is our domain – exclusively. ASK US HOW. Listen. Ask us to explain our WHAT-HOW mapping. Let us come up with nothing (that’s best). Let us struggle. Probe on our map, push on it, come up with your own, one that fits your framework. Then, and only then, share how your HOW fits (or doesn’t) with ours. Let us compare our mapping with yours. Let us probe, let us question, let us contrast. (You’ve already succeeded because we no longer see ours versus yours, we simply see multiple HOWs for consideration.) We’ll come up with new HOWs, hybrid HOWs, all sorts of HOWs and give you the strengths and weaknesses of each. And if your HOW is best we’ll recommend it, though we won’t see it as yours because, thankfully, it has become ours. And we’ll move heaven and earth to make it happen. Engineering has new thinking.

Whether it’s my favorite new thinking (product simplification) or any other, the WHY, WHAT, HOW process works. It works because it’s respectful of our logic, of our nature. It fits us.

Though not as powerful a real Vulcan mind meld, WHY, WHAT, HOW is strong enough to carry the day.

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.

Five percent here, three percent there. I’m tired as hell of continuous improvement. Sure there’s a place for it, but it shouldn’t be the only type of work we do. But, unfortunately, that’s just what’s happened in manufacturing. To secure the balance sheet, the pendulum swung too far toward continuous improvement. Just look at what we’re writing about – the next low cost country, shorter lead times, how to be profitable where there’s no profit to be had. Those topics scream continuous improvement – take nickels and dimes out of processes to increase profits. But there’s a dark side to all this focus on continuous improvement.  It has created a big problem: it has come at the expense of discontinuous improvement.

Continuous improvement is a philosophy of minimization with a focus on cost and waste reduction, while discontinuous improvement is a philosophy of maximization with a focus on creation of new markets through product innovation. As of late, we’ve minimized waste at the expense of invention and innovation. I propose we flip this on its head and maximize through discontinuous improvement at the expense of continuous improvement. That’s right; I said do less lean and Six Sigma.

But we must ask ourselves if we’re capable of doing discontinuous improvement. Remember, we ignored or dismantled our innovation engines over the last years. And what about our big thinkers, our creative thinkers, our innovators? Do they still work for us, or have they just stopped talking about big ideas? I urge you to answer that question because your next actions depend on it.

If your innovative thinkers are gone, go out and hire the best you can find ASAP. If you were fortunate enough to retain your big thinkers, congratulations. Now it’s time to get the band back together, but first you’ve got to do some reconnaissance to ferret them out of their hiding places. Once you find them, invite them to a nice lunch – the nicer the better. Don’t push too hard at lunch, just start to  get reacquainted. In time you’ll get to talk about their ideas on new technologies and how to create new markets.

It will be difficult to get your company swing the pendulum away from continuous improvement, but you must try. Without discontinuous improvement your company will be destined to wrestle for nickels using lean and Six Sigma.

Congratulations. You’ve managed to keep your product development engine running. Good work.  But now the hard part. Marketing and sales know new products are a key to profitability, and so does the CEO. So they’ve all asked for more new products, and now you have more active product development projects in the pipeline. The product development folks will do whatever they can to crank out the products. But can they get it done?

When does the product pipeline become too much for your product development engine to handle? We all know you can’t keep adding more new product development projects without adding capacity or improving productivity. Sure you can ask your product development engine to do more (and more), and it will try; but at some point it will run out of gas. So, ask yourself: Has your product development engine run out of gas? How can you tell? If it hasn’t, do you know how many miles are left in the tank?

If you don’t measure it you can’t improve it, that’s what the black belts say. But what to measure? What are the right metrics to tell you if your product development engine is out of gas? One of the best books on the subject is Managing the Design Factory, by Don Reinertsen. The rest of the post is strongly shaped by Don’s book, if not taken directly from it. Remember, genius steals.

The best metrics are simple, relevant to the objective, and are leading indicators. Simple so they’re easy to interpret; relevant so they move you toward the objective, in this case launching more new products; and are leading indicators, in that they are predictors of outcomes, so you can take action before catastrophic outcomes occur.  Here are three good ones. Read the rest of this entry »

2009 is a tough year, especially for CEOs.

CEOs have a strong desire to do what it takes to deliver shareholder value, but that’s coupled with a deep concern that tough decisions may dismantle the company in the process.

Here is the state-of-affairs:

Sales are down and money is tight.  There is severe pressure to cut costs including those that are linked to sales – marketing budgets, sales budgets, travel – and things that directly impact customers – technical service, product manuals, translations, and warranty.

Pricing pressure is staggering.  Customers are exerting their buying power – since so few are buying they want to name their price (and can).  Suppliers, especially the big ones, are using their muscle to raise prices.

Capacity utilization is ultra-low, so the bounce-back of new equipment sales is a long way off.

Everyone wants to expand into new markets to increase sales, but this is a particularly daunting task with competitors hunkering down to retain market share, cuts in sales and marketing budgets, and hobbled product development engines.

There is a desire to improve factory efficiency to cut costs (rather than to increase throughput like in 2008), but no one wants to spend money to make money – payback must be measured in milliseconds.

So what’s a CEO to do?  Read the rest of this entry »

Like you, I have been thinking a lot about the recession.  We all want to know how to move ourselves to the other side, where things are somewhat normal (the old normal, not the new one).  Like usual, my mind immediately goes to products.  To me, having the right products is vital to pulling ourselves out of this thing.  There is nothing novel in this thinking;  I think we all agree that products are important.  But, there are two follow-on questions that are important.  First, what makes products “right” to move you quickly to the other side?  Second, do you have the capability to engineer the “right” products?

The first question – what makes products “right” for these times?  Capacity is important to understanding what makes products right.  Capacity utilization is at record lows with most industries suffering from a significant capacity glut.  With decreased sales and idle machines, customers are no longer interested in products that improve productivity of their existing product lines because they can simply run their idle machines more.  And, they are not interested in buying more capacity (your products) at a reduced price.  They will simply run their idle machines more.  You can’t offer an improvement of your same old product that enables customers to make their same old products a bit faster and you can’t offer them your same old products at a lower price.  However, you can sell them products that enable them to capture business they currently do not have.  For example, enable them to manufacture products that their idle machines CANNOT make at all.  To do that means your new products must do something radically different than before; they must have radically improved functionality or radically new features.  This is what makes products right for these times.

On to the second question – do you have the capability to engineer the right products?  Read the rest of this entry »