Shipulski On Design

Posts Tagged ‘Engineering Mindset’

If you want to make a difference, you’ve got to add energy.  And the more you can add the bigger difference you can make.

Doing new is difficult and demands (and deserves) all the energy you can muster.  Often it feels you’re the only one pushing in the right direction while everyone else is vehemently pushing the other way.  But stay true and stand tall.  This is not an indication things are going badly, this is a sign you’re doing meaningful work.  It’s supposed to feel that way.  If you’re exhausted, frustrated and sometimes a bit angry, you’re doing it right.  If you have a healthy disrespect for the status quo, it’s supposed to feel that way.

Meaningful work has a long time constant and you’ve got to run these meaningful projects like marathons, uphill marathons.  Every day you put in your 26 miles at a sustainable pace  – no slower, but no faster.  This is long, difficult work that doesn’t run by itself, you’ve got to push it like a sled.  Every day you’ve got to push.  To push every day like this takes a lot of physical strength, but it takes even more mental strength.  You’ve got to stay focused on the critical path and push that sled every day.  And you need to preserve enough mental energy to effectively ignore the non-critical path sleds.  You’ve got to be able to decide which tasks you must get your whole body behind and which tasks you must discount.  And you’ve got to preserve enough energy to believe in yourself.

Meaningful work cannot be accomplished by sprinting full speed five days a week.  It’s a marathon, and you’ve got to work that way and train that way.  Get your rest, get your exercise, eat right, spend time with friends and family, and put your soul into your work.

Choose work that is meaningful and add energy.  Add it every day.  Add it openly.  Add it purposefully. Add it genuinely.   Add energy like you’re an aircraft carrier and others will get pulled along by your wake.  Add energy like you’re bulldozer and others will get out of your way.  Add energy like you’re contagious and others will be infected.

Image credit – anton borzov

Innovation creates things that are novel, useful and successful.  Something that’s novel is something that’s different, and something that’s different creates uncertainty.  And, as we know, uncertainty is the enemy of all things sacred.

Lean and Six Sigma have been so successful that the manufacturing analogy has created a generation that expects all things to be predictable, controllable and repeatable.  Above all else, this generation values certainty.  Make the numbers; reduce variability; reduce waste; do it on time  – all mantras of the manufacturing analogy, all advocates of predictability and all enemies of uncertainty.

With the manufacturing analogy, a culture of accountability is the natural end game (especially when it comes to outcomes), but what most don’t understand is a culture that values accountability of outcomes is a culture that cannot tolerate uncertainty.  And what fewer understand is a culture intolerant of uncertainty is a culture intolerant of innovation.

By definition, innovation and uncertainty are a matched pair – you can’t have one without the other.  You can have both or neither – that’s the rule.  And though we usually use the word “risk” rather than “uncertainty”, risk is a result of uncertainty and uncertainty is the fundamental.

When a product is launched and it’s poorly received, it’s likely due to an untested value proposition. And the reason the value proposition went untested is uncertainty, uncertainty around the negative consequences of challenging authority.  Someone on high decreed the value proposition was real and the organization, based on how leadership responded in the past, did not challenge the decree because the last person who challenged authority was fired, demoted or ostracized.

When the new product is 3% better than the last one, again, the enemy is uncertainty.  This time it’s either uncertainty around what the customer will value or uncertainty around the ability to execute on technology work.  The organization cannot tolerate the risk (uncertainty), so it does what it did last time.

When the new product has more new features and functions than it has a right to, intolerance to uncertainty is the root cause.  This time it’s uncertainty around the negative consequences of prioritizing one feature over another.  Said another way, it’s about uncertainty (and the resulting fear) around using judgement.

These three scenarios are reward looking, as the uncertainty has already negatively impacted the innovation work.  To mitigate the negative impacts on innovation, uncertainty must be part of the equation from the outset.

When it’s time for you to call for more innovation, it’s also the time to acknowledge you want more uncertainty.  And it’s not enough to say you’ll tolerate more uncertainty because that takes you off the hook and puts it all on the innovators.  You must tell the company you expect more uncertainty.  This is important because the innovators won’t limit their work by an unnaturally low uncertainty threshold, rather they’ll do the work demanded by the hyper-aggressive growth goals.

And when you ask for more uncertainty, it’s time to explicitly tell people you expect them to use their judgment more freely and more frequently.  With uncertainty there is no best practice, but there is best judgment.  And when your best people use their best judgement, uncertainty is navigated in the most effective way.

But, really, if you ask for more uncertainty you won’t get it. The level of uncertainty in the trenches is set by your risk disposition.  People in your company know, based on leadership’s actions – what’s rewarded and what’s punished – the company’s risk disposition and it governs their actions. If you take the pulse of your portfolio of technology projects you will see your risk disposition.  The thing to remember is your risk disposition is the boss and the level of innovation is subservient.

When the CEO demands you change the innovation work for the better, politely suggest a plan to change the company’s risk disposition.  And when the CEO asks how to do that, politely suggest a visit to Jim McCormick’s website.

Image credit – Suzanne Gerber

When it’s time for a tough decision, it’s time to use data.  The idea is the data removes biases and opinions so the decision is grounded in the fundamentals.  But using the right data the right way takes a lot of disciple and care.

The most straightforward decision is a decision between two things – an either or – and here’s how it goes.

The first step is to agree on the test protocols and measure systems used to create the data.  To eliminate biases, this is done before any testing.  The test protocols are the actual procedural steps to run the tests and are revision controlled documents.  The measurement systems are also fully defined.  This includes the make and model of the machine/hardware, full definition of the fixtures and supporting equipment, and a measurement protocol (the steps to do the measurements).

The next step is to create the charts and graphs used to present the data. (Again, this is done before any testing.) The simplest and best is the bar chart – with one bar for A and one bar for B.  But for all formats, the axes are labeled (including units), the test protocol is referenced (with its document number and revision letter), and the title is created.  The title defines the type of test, important shared elements of the tested configurations and important input conditions.   The title helps make sure the tested configurations are the same in the ways they should be.  And to be doubly sure they’re the same, once the graph is populated with the actual test data, a small image of the tested configurations can be added next to each bar.

The configurations under test change over time, and it’s important to maintain linkage between the test data and the tested configuration.  This can be accomplished with descriptive titles and formal revision numbers of the test configurations.  When you choose design concept A over concept B but unknowingly use data from the wrong revisions it’s still a data-driven decision, it’s just wrong one.

But the most important problem to guard against is a mismatch between the tested configuration and the configuration used to create the cost estimate.  To increase profit, test results want to increase and costs wants to decrease, and this natural pressure can create divergence between the tested and costed configurations. Test results predict how the configuration under test will perform in the field.  The cost estimate predicts how much the costed configuration will cost.  Though there’s strong desire to have the performance of one configuration and the cost of another, things don’t work that way.  When you launch you’ll get the performance of AND cost of the configuration you launched.  You might as well choose the configuration to launch using performance data and cost as a matched pair.

All this detail may feel like overkill, but it’s not because the consequences of getting it wrong can decimate profitability. Here’s why:

Profit = (price – cost) x volume.

Test results predict goodness, and goodness defines what the customer will pay (price) and how many they’ll buy (volume).  And cost is cost.  And when it comes to profit, if you make the right decision with the wrong data, the wheels fall off.

Image credit – alabaster crow photographic

Innovation is about new; innovation is about different; innovation is about “never been done before”; and innovation is about preparation.

Though preparation seems to contradict the free-thinking nature of innovation, it doesn’t.  In fact, where brainstorming diverts attention, the right innovation preparation focuses it; where brainstorming seeks more ideas, preparation seeks fewer and more creative ones; where brainstorming does not constrain, effective innovation preparation does exactly that.

Ideas are the sexy part of innovation; commercialization is the profitable part; and preparation is the most important part.  Before developing creative, novel ideas, there must be a customer of those ideas, someone that, once created, will run with them.  The tell-tale sign of the true customer is they have a problem if the innovation (commercialization) doesn’t happen. Usually, their problem is they won’t make their growth goals or won’t get their bonus without the innovation work.  From a preparation standpoint, the first step is to define the customer of the yet-to-be created disruptive concepts.

The most effective way I know to create novel concepts is the IBE (Innovation Burst Event), where a small team gets together for a day to solve some focused design challenges and create novel design concepts.  But before that can happen, the innovation preparation work must happen.  This work is done in the Focus phase. The questions and discussion below defines the preparation work for a successful IBE.

1. Why is it so important to do this innovation work?

What defines the need for the innovation work?  The answer tells the IBE team why they’re in the room and why their work is important. Usually, the “why” is a growth goal at the business unit level or projects in the strategic plan that are missing the necessary sizzle. If you can’t come up with a slide or two with growth goals or new projects, the need for innovation is only emotional.  If you have the slides, these will be used to kick off the IBE.

2. Who is the customer of the novel concepts?

Who will choose which concepts will be converted into working prototypes? Who will convert the prototypes into new products? Who will launch the new products? Who has the authority to allocate the necessary resources? These questions define the customers of the new concepts.  Once defined, the customers become part of the IBE team.  The customers kick off the IBE and explain why the innovation work is important and what they’ll do with the concepts once created.  The customers must attend the IBE report-out and decide which concepts they’ll convert to working prototypes and patents.

Now, so the IBE will generate the right concepts, the more detailed preparation work can begin.  This work is led by marketing.  Here are the questions to scope and guide the IBE.

3. How will the innovative new product be used?

How will the innovative product be used in new way? This question is best answered with a hand sketch of the customer using the new product in a new way, but a short written description (30 words, or so) will do in a pinch. The answer gives the IBE team a good understanding, from a customer perspective, what new things the product must do.

What are the new elements of the design that enable the new functionality or performance? The answer focuses the IBE on the new design elements needed to make real the new product function in the new way.

What are the valuable customer outcomes (VCOs) enabled by the innovative new product? The answer grounds the IBE team in the fundamental reason why the customer will buy the new product.  Again, this is answered from the customer perspective.

4. How will the new innovative new product be marketed and sold?

What is the tag line for the new product? The answer defines, at the highest level, what the new product is all about. This shapes the mindset of the IBE team and points them in the right direction.

What is the major benefit of the new product? The answer to this question defines what your marketing says in their marketing/sales literature.  When the IBE team knows this, you can be sure the new concepts support the marketing language.

5. By whom will the innovative new product be used?

In which geography does the end user live? There’s a big difference between developed markets and developing markets.  The answer to the question sets the context for the new concepts, specifically around infrastructure constraints.

What is their ability to pay? Pocketbooks are different across the globe, and the customer’s ability to pay guides the IBE team toward concepts that fit the right pocket book.

What is the literacy level of the end customer?  If the customer can read, the IBE team creates concepts that take advantage of that ability.  If the customer cannot read, the IBE team creates concepts that are far different.

6. How will the innovative new product change the competitive landscape?

Who will be angry when the new product hits the market? The answer defines the competition.  It gives broad context for the IBE team and builds emotional energy around displacing adversaries.

Why will they be angry? With the answer to this one, the IBE team has good perspective on the flavor of pain and displeasure created by the concepts.  Again, it shapes the perspective of the IBE team.  And, it educates the marketing/sales work needed to address competitors’ countermeasures.

Who will benefit when the new product hits the market? This defines new partners and supporters that can be part of the new solutions or participants in a new business model or sales process.

What will customer throw away, reuse, or recycle? This question defines the level of disruption.  If the new products cause your existing customers to throw away the products of your existing customers, it’s a pure market share play.  The level of disruption is low and the level of disruption of the concepts should also be low.  On the other end of the spectrum, if the new products are  sold to new customers who won’t throw anything away, you creating a whole new market, which is the ultimate disruption, and the concepts must be highly disruptive.  Either way, the IBE team’s perspective is aligned with the level appropriate level of disruption, and so are the new concepts.

Answering all these questions before the creative works seems like a lot of front-loaded preparation work, and it is. But, it’s also the most important thing you can do to make sure the concept work, technology work, patent work, and commercialization work gives your customers what they need and delivers on your company’s growth objectives.

Image credit — ccdoh1.

Creative products are novel and useful; Innovative products are novel, useful, and successful. Beforehand, it’s impossible to know if something will be successful, but if it’s useful there’s a chance it could be; beforehand, it’s subjective whether something will be useful, but if it’s novel there’s a chance; but no one is sure what novel means, so replace it with “different” and you’re onto something. It’s clear if something is different, and if it’s different, there’s a chance it could be creative and innovative. Said another way,

if something isn’t different it cannot be creative, nor can it be innovative.

If you can generate more things that are different, you’ve increased your chances of creativity and innovation. And if you generate more ideas that are different, you’ll create more things that are different. Go on a quest to create more ideas that are different and you’ll have more creativity and innovation.

Ideas that are different come from the firing of different neural pathways. And to get different pathways to fire, you’ve got to first recognize when the old ones are firing. To do this, you’ve got to be aware of your worn pathways and be aware you’re reusing the overused. A different environment is needed – an environment that governs speed. If you have a culture of speed and productivity, this will be different.  It doesn’t matter what the different environment is, it matters what it isn’t.

Different ideas result from the collision of old ideas seen from a new perspective. Put different people together who have different old ideas and different perspectives and different ideas will grow from the collisions. There’s no recipe for the exact distribution of people, but if you don’t put them together now, then those are them.

And to break new neural pathways, the environment in which ideas should be different. Again, there’s no prescription for the type of space or the furniture, just that it’s different. If the engine that creates the old ideas lives in an ordered space, make the different one disordered; if there’s carpet all around, lay down some linoleum; if there’s no art on the corporate walls, hang some; if the furniture matches across the teams, make it a clustered-jumble of mismatched pieces. The general approach: whatever it looks like and feels like where the same ideas are regurgitated day-in-day-out, do the opposite.

And to attract different colliders and their ideas, provide something different in the different space. If your regular coffee is terrible, the different coffee should be amazing; where people queue up to use the same tired tools, provide too many seats of the newest and best; where low fat, low calorie, responsible food is doled out in reasonable portions, provide free (and unlimited) access to irresponsible junk food.

Creativity and innovation start with different.

Image credit: quinet.

If you’re serious about innovation, you must learn, as second nature, to convert your ideas into prototypes.

Funny thing about ideas is they’re never fully formed – they morph and twist as you talk about them, and as long as you keep talking they keep changing. Evolution of your ideas is good, but in the conversation domain they never get defined well enough (down to the nuts-and-bolts level) for others (and you) to know what you’re really talking about. Converting your ideas into prototypes puts an end to all the nonsense.

Job 1 of the prototype is to help you flesh out your idea – to help you understand what it’s all about. Using whatever you have on hand, create a physical embodiment of your idea. The idea is to build until you can’t, to build until you identify a question you can’t answer. Then, with learning objective in hand, go figure out what you need to know, and then resume building. If you get to a place where your prototype fully captures the essence of your idea, it’s time to move to Job 2. To be clear, the prototype’s job is to communicate the idea – it’s symbolic of your idea – and it’s definitely not a fully functional prototype.

Job 2 of the prototype is to help others understand your idea. There’s a simple constraint in this phase – you cannot use words – you cannot speak – to describe your prototype. It must speak for itself. You can respond to questions, but that’s it. So with your rough and tumble prototype in hand, set up a meeting and simply plop the prototype in front of your critics (coworkers) and watch and listen. With your hand over your mouth, watch for how they interact with the prototype and listen to their questions. They won’t interact with it the way you expect, so learn from that. And, write down their questions and answer them if you can. Their questions help you see your idea from different perspectives, to see it more completely. And for the questions you cannot answer, they the next set of learning objectives. Go away, learn and modify your prototype accordingly (or build a different one altogether). Repeat the learning loop until the group has a common understanding of the idea and a list of questions that only a customer can answer.

Job 3 is to help customers understand your idea. At this stage it’s best if the prototype is at least partially functional, but it’s okay if it “represents” the idea in clear way. The requirement is prototype is complete enough for the customer can form an opinion. Job 3 is a lot like Job 2, except replace coworker with customer. Same constraint – no verbal explanation of the prototype, but you can certainly answer their direction questions (usually best answered with a clarifying question of your own such as “Why do you ask?”) Capture how they interact with the prototype and their questions (video is the best here). Take the data back to headquarters, and decide if you want to build 100 more prototypes to get a broader set of opinions; build 1000 more and do a small regional launch; or scrap it.

Building a prototype is the fastest, most effective way to communicate an idea. And it’s the best way to learn. The act of building forces you to make dozens of small decisions to questions you didn’t know you had to answer and the physical nature the prototype gives a three dimensional expression of the idea. There may be disagreement on the value of the idea the prototype stands for, but there will be no ambiguity about the idea.

If you’re not building prototypes early and often, you’re not doing innovation. It’s that simple.

Here’s how innovation goes:
(Words uttered. // Internal thoughts.)

That won’t work. Yes, this is a novel idea, but it won’t work. You’re a heretic. Don’t bring that up again. // Wow, that scares me, and I can’t go there.

Yes, the first experiment seemed to work, but the test protocol was wrong, and the results don’t mean much. And, by the way, you’re nuts. // Wow. I didn’t believe that thing would ever get off the ground.

Yes, you modified the test protocol as I suggested, but that was only one test and there are lots of far more stressful protocols that surely cannot be overcome. // Wow. They listened to me and changed the protocol as I suggested, and it actually worked!

Yes, the prototype seemed to do okay on the new battery of tests, but there’s no market for that thing. // I thought they were kidding when they said they’d run all the tests I suggested, but they really took my input seriously. And, I can’t believe it, but it worked. This thing may have legs.

Yes, the end users liked the prototypes, but the sample size was small and some of them don’t buy any of our exiting products. I think we should make these two changes and take it to more end users. // This could be exciting, and I want to be part of this.

Yes, they liked the prototypes better once my changes were incorporated, but the cost is too high. // Sweet! They liked my design! I hope we can reduce the cost.

I made some design changes that reduce the cost and my design is viable from a cost standpoint, but manufacturing has other priorities and can’t work on it. // I’m glad I was able to reduce the cost, and I sure hope we can free up manufacting resources to launch my product.

Wow, it was difficult to get manufacturing to knuckle down, but I did it, and my product will make a big difference for the company. // Thanks for securing resources for me, and I’m glad you did the early concept work when I was too afraid.

Yes, my product has been a huge commercial success, and it all strarted with this crazy idea I had. You remember, right? // Thank you for not giving up on me. I know it was your idea. I know I was a stick-in-the-mud. I was scared. And thanks for kindly and effectively teaching me how to change my thinking. Maybe we can do it again sometime.
________________

There’s nothing wrong with this process; in fact, everything is right about it because that’s what people do. We’ve taught them to avoid risk at all costs, and even still, they manage to walk gingerly toward new thinking.

I think it’s important to learn to see the small shifts in attitude as progress, to see the downgrade from an impossible problem to a really big problem as progress.

Instead of grabbing the throat of radical innovation and disrupting yourself, I suggest a waterfall approach of a stepwise ratchet toward problems of a lesser degree. This way you can claim small victories right from the start, and help make it safe to try new things. And from there, you can stack them one on top of another to build your great pyramid of disruption.

And don’t forget to praise the sorceres and heretics who bravely advance their business model-busting ideas without the safety net of approval.

We spend too much time on the mundane. Every day people come to work, turn on their PCs, and the mundane magically happens on its own accord. Email gets sent, phones get answered, mail gets delivered, and processes get followed. And after lunch, the hamster wheel spins back up and the mundane consumes the rest of our day. Yet there’s no need because that stuff runs on its own. It’s time to leave it alone and manage the mundane by exception. If there’s a hiccup, give it a drink of water, and otherwise leave it alone. It’s time to recognize the massive opportunity cost of the mundane – mundane comes at the expense of meaningful.

But when the mundane withers and there’s finally time for meaningful, there’s another chasm to cross – no one asks for meaningful work. Because meaningful work makes a difference and making a difference threatens the legacy of success, no one asks you for it. Because it’s considered impossible, there’s no request to do it. And because it’s considered a strength of your business, no one suggests you dismantle it. Crazy, but it’s time to stop the mundane so you can start doing work no one is asking you to do.

But it’s not any old work no one is asking for, it’s a special flavor, a flavor that meets a tight set of criteria.

Don’t do it unless it will make a difference. But not any old difference, a difference of epic proportions. If you explain the concept to the customer and they want to buy ten, you’re on the right track. If after you show the prototype the customer won’t give it back to you with a wrestling match, that’s the right work. If you present the concept to the core business unit and they immediately try to scuttle it, you’re on to something.

Don’t do it unless it resonates with you, personally. As subject matter expert, it must make your hair stand on end. As the inventor who must swim against the tide of “you can’t do that”, it must fill your deep need to help others. As the pariah who threatens the success of the company, it must be more than an idea – it must be part of you.

Leaders – it’s time to ask your people to work on things that are meaningful to them. Give them four hours a week and ask for an informal fifteen minute presentation every other week. They’ll make extreme progress and amaze you. Magically, because they’ll be so charged up, there will be time for all the work. Morale will skyrocket, the best folks will ask to work on your team, and you’ll have working prototypes for all the things you should have asked for.

There’s a natural hierarchy to work.  Your job, if you choose to accept it is to climb the ladder of hierarchy rung-by-rung. Here’s how to go about it:

Level 1. Work you can say no to – Say no to it. Say no effectively as you can, but say it. Saying no to level 1 work frees you up for the higher levels.

Level 2. Work you can get someone else to do – Get someone else to do it. Give the work to someone who considers the work a good reach, or a growth opportunity. This isn’t about shirking responsibility, it’s about growing young talent. Maybe you can spend a little time mentoring and the freed up time doing higher level work. Make sure you give away the credit so next time others will ask you for the opportunity to do this type of work for you.

Level 3. Work you’ve done before, but can’t wiggle out of – Do it with flair, style, and efficiency; do it differently than last time, then run away before someone asks you to do it again. Or, do it badly so next time they ask someone else to do it. Depending on the circumstance, either way can work.

Level 4. Work you haven’t done before, but can’t wiggle out of – Come up with a new recipe for this type of work, and do it so well it’s unassailable. This time your contribution is the recipe; next time your contribution is to teach it to someone else. (See level 2.)

Level 5. Work that scares others – Figure out why it scares them; break it into small bites; and take the smallest first bite (so others can’t see the failure).  If it works, take a bigger bite; if it doesn’t, take a different smallest bite.  Repeat, as needed. Next time, since you’ve done it before, treat it like level 3 work. Better still, treat it like level 2.

Level 6. Work that scares you – Figure out why it scares you, then follow the steps for level 5.

Level 7. Work no one knows to ask you to do – You know your subject matter better than anyone, so figure out the right work and give it a try.  This flavor is difficult because it comes at the expense of work you’re already signed up to do and no one is asking you to do it. But you should have the time because you followed the guidance in the previous levels.

Level 8. Work that obsoletes the very thing that made your company successful – This is rarified air – no place for the novice. Ultimately, someone will do this work, and it might as well be you.  At least you’ll be able to manage the disruption on your own terms.

In the end, your task, if you choose to accept it, is to migrate toward the work that obsoletes yourself. For only then can you start back at level 1 on the ladder of your own making.

Our threshold for uncertainty is too low.

Early in projects, even before the first prototype is up and running, you know what the product must do, what it will cost, and, most problematic, when you’ll be done. Independent of work content, level of newness, and workloads, there’s no uncertainty in your launch date. It’s etched in stone and the consequences are devastating.

A zero tolerance policy on uncertainty forces irrational behavior. As soon as possible, engineering gets something running in the lab, and then doesn’t want to change it because there’s no time. The prototype is almost impossible to build and is hypersensitive to normal process variation, but these issues are not addressed because there’s no time.  Everyone agrees it’s important to fix it, and agrees to fix it after launch, but that never happens because the next project is already late before it starts. And the death cycle repeats project after project.

The root cause of this mess is the mistaken porting of manufacturing’s zero uncertainly mindset into design. The thinking goes like this – lean and Six Sigma have achieved magical success in manufacturing by eliminating uncertainty, so let’s do it in product design and achieve similar results. This is a fundamental mistake as the domains are fundamentally different.

In manufacturing the same product is made day-in and day-out – no uncertainty; in product design no two product development efforts are the same and there’s lots of stuff that’s done for the first time – uncertainty by definition. In manufacturing there’s a revision controlled engineering drawing that defines the right answer (the geometry and the material) – make it like the picture and it’s all good; in product design the material is chosen from many candidates and the geometry is created from scratch – the picture is created from nothing. By definition there’s more inherent uncertainty in product design, and to tighten the screws and fix the launch date at the start is inappropriate.

Design engineers must feel like there’s enough time to try new things because new products that provide new functionality require new technologies, new materials, and new geometries. With new comes inherent uncertainty, but there are ways to manage it.

To hold the timeline, give on the specification and cost. Design as fast as you can until you run out of time then launch. The product won’t work as well as you’d like and it will cost more than you’d like, but you’ll hit the schedule. A good way to do this is to de-feature a subassembly to reduce design time, and possibly reduce cost. Or, reuse a proven subassembly to reduce design time – take a hit in cost, but hit the timeline. The general idea – hold schedule but flex on performance and cost.

It feels like sacrilege to admit that something’s got to give, but it’s the truth. You’ve seen how it goes when you edict (in no uncertain terms) that the timeline will be met and there’ll be no give on performance and cost. It hasn’t worked, and it won’t – the inherent uncertainty of product design won’t let it.

Accept the uncertainty; be one with it; and manage it. It’s the only way.

Accomplishments in 2013

• Fourth year of weekly blog posts without missing a beat or repeating a post. (251 posts in total.)
• Third year of daily tweets – 2,170 in all. (@mikeshipulski)
• Second year as Top 40 Innovation Bloggers (#12) – Innovation Excellence, the web’s top innovation site.
• Seventh consecutive year as Keynote Speaker at International Forum on DFMA.
• Fourth year of LinkedIn working group – Systematic DFMA Deployment.
• Third year writing a column for Assembly Magazine (6 more columns this year).
• Wrote a book — PRODUCT PROCESS PEOPLE – Designing for Change (Which my subscribers can download for free.)

Top 5 Posts

1. What They Didn’t Teach Me In Engineering School — a reflection on my learning after my learning.
2. Guided Divergence — balancing act of letting go and shaping the future.
3. Innovation in 26 words — literally.
4. Lasting Behavioral Change — easy to say, tough to do.
5. Prototype The Unfamiliar — test early and often.

I look forward to a great year 5.