Shipulski On Design

Archive for the ‘How To’ Category

I like Dave Snowden’s thinking on innovation – starvation, pressure, and perspective shift. Here’s what it means to me:

Starvation – Left to our own, we’ll do as we did before. Starvation of resources pushes thinking away from stale, worn paths. Almost in reverse, define what you don’t want, then construct intelligent constraints (the most difficult part of the whole deal) so it’s out of the design space. Constrain the team so they can’t use the most expensive material; constrain the team so they can’t use the same old technology; constrain them so they can’t use the tried and true business model. It’s reverse thinking, but constraints – telling them what they can’t do – frees up design space. Constraints say “Do anything you want, except this.” which constrains far less than specifications. Constrain them to free them.

Pressure – Left to our own, we’ll reuse old thinking. Time pressure drags thinking out of the ruts of our success. Define creative constraints then, to create pressure, give the team insufficient time to think it through. Force them to swim differently with the problem.  The best way I know is to explain the constraints then give the team fifteen minutes to build a prototype. (Yes, fifteen.) The prototype is non-functional, and can be made from whatever is on hand – cardboard, clay, duct tape, or packing peanuts. The short time frame creates pressure, and the pressure extrudes different thinking.  Building a prototype shifts from learning-in-the-brain to learning-with-the-hands. And since hands learn differently than brains, new thinking is cast.

Perspective Shift – Left to our own, we’ll do a remake. Perspective shift moves us to a different place to create a healthy disrespect for today’s thinking. Seen in the right new light, our successes should look problematic. (From the front a skunk isn’t so bad, but from behind things aren’t so good.) Building a bridge to a new perspective can shift things a little, but for a tectonic shift, formalize the consequences of inaction. Think – “If we don’t do this, a very bad thing will happen.” Perspective shift is all about creating action in a new direction.

You won’t get it right the first time, but, no matter.  The real enemy is inaction.

We often forget, but regardless of industry, technology, product, or service, it’s a battle for hearts and minds.

The building blocks of business are processes, machines, software, and computers, but people are the underpinning.  The building blocks respond in a repeatable way – same input, same output – and without judgment.  People, however, not so much.

People respond differently depending on delivery – even small nuances can alter the response, and when hot buttons are pushed responses can be highly nonlinear. One day to the next, people’s responses to similar input can be markedly different.  Yet we forget people are not like software or machines, and we go about our work with expectations people will respond with highly rational, highly linear,  A-then-B logic.  But in a battle between rational and emotional, it’s emotional by a landslide.

Thankfully, we’re not just cogs in the machine.  But for the machine to run, it’s imperative to win the hearts and minds. (I feel a little silly writing this because it’s so fundamental, but it needs to be written.)  And it’s hearts then minds.  The heart is won by emotion, and once the emotional connection is made, the heart tells the mind to look at the situation and construct logic to fit.  The heart clears the path so the mind can in good conscience come along for the ride.

Hearts are best won face-to-face, but, unfortunately today’s default mode is PowerPoint-to-face.  We don’t have to like it, but it’s here to stay.  And so, we must learn to win hearts, to make an emotional connection, to tell stories with PowerPoint.

To tell a story with PowerPoint, we must bring ourselves to the forefront and send PowerPoint to the back.  To prevent ourselves from hiding behind our slides, take the words off and replace them with a single, large image – instead of a complex word-stuffed jumble, think framed artwork.  While their faces look at the picture, tell their hearts a story.  Eliminate words from the slides and the story emerges.

[There’s still a place for words, but limit yourself to three words per slide, and make them big – 60 point font. And keep it under ten slides.   More than that and you haven’t distilled the story in your head.]

Whatever business you’re in, you’re in the people business.  Win hearts and minds follow.  And so do profits.

That’s a best practice. Look, there’s another one. We need a best practice. What’s the best practice?  Let’s standardize on the best practice.  Arrrgh.  Enough, already, with best practices.

There are no best practices, only actions that have worked for others in other situations.  Yet we feverishly seek them out, apply them out of context, and expect they’ll solve a problem unrelated to their heritage.

To me, the right practices are today’s practices.  They’re the base camp from which to start a journey toward new ones.  To create the next evolution of today’s practices, for new practices to emerge, a destination must be defined. This destination is dictated by problems with what we do today.  Ultimately, at the highest level, problems with our practices are spawned by gaps, shortfalls, or problems in meeting company objectives.  Define the shortfall – 15% increase in profits – and emergent practices naturally diffuse to the surface.

There are two choices: choose someone else’s best practices and twist, prune, and bend them to fit, or define the incremental functionality you’d like to create and lay out the activities (practices) to make it happen. Either way, the key is starting with the problem.

The important part – the right practices, the new activities, the novel work, whatever you call it, emerges from the need.

It’s a problem hierarchy, a problem flow-down.  The company starts by declaring a problem – profits must increase by 15% – and the drill-down occurs until a set of new action (new behaviors, new processes, new activities) is defined that solves the low level problems. And when the low level problems are solved, the benefits avalanche to satisfy the declared problem – profits increased by 15%.

It’s all about clarity — clearly define the starting point, clearly define the destination, and express the gaps in a single page, picture-based problem statements.  With this type of problem definition, you can put your hand over your mouth, with the other hand point to the picture, and everyone understands it the same way. No words, just understanding.

And once everyone understands things clearly, the right next steps (new practices) emerge.

If you want to learn, to really learn, experiment.

But I’m not talking about elaborate experiments; I’m talking about crude ones. Not simple ones, crude ones.

We were taught the best experiments maximize learning, but that’s dead wrong. The best experiments are fast, and the best way to be fast is to minimize the investment.

In the name of speed, don’t maximize learning, minimize the investment.

Let’s get right to it. One of the best tricks to minimize investment is to minimize learning – learning per experiment, that is. Define learning narrowly, design the minimum experiment, and run the trial. Learning per trial is low, but learning per month skyrockets because the number of trials per month skyrockets. But it gets better. There’s an interesting learning exponential at work. The first trial informs the second which shapes the third. But instead of three units of learning, it’s cubic. And minimizing learning doesn’t just half the time to run a trial, it reduces it by 100 or more. It’s earning to the hundredth power.

Another way to minimize investment is to minimize resolution. Don’t think nanometers, think thumbs up, thumbs down. Design the trial so the coarsest measuring stick gives an immediate and unambiguous response. There’s no investment in expensive measurement gear and no time invested in interpretation of results. Think sledgehammer to the forehead.

A third way to minimize investment is to evaluate relative differences. The best example is the simple, yet powerful, A-B test . Run two configurations, decide which is better, and run quickly in the direction of goodness.  No need to fret about how much better, just sprint toward it.  The same goes for trial 1 versus trial 2 comparisons. Here’s the tricky algorithm: If trial 2 is better, do more of that.  And the good news applies here too –  the learning exponential is still in play. Better to the hundredth power, in record time.

I don’t care what norms you have to bend or what rules you have to break. If you do one thing, run more trials.

But don’t take my word for it. Dr. Seuss had it right:

And I would run them in a boat!
And I would run them with a goat…
And I will run them in the rain.
And in the dark. And on a train.
And in a car. And in a tree.
They are so good so good you see!

When engineers see a big opportunity, we want desperately to move the company in the direction of our thinking, but find it difficult to change the behavior of others. Our method of choice is usually a full frontal assault, explaining to anyone that will listen the opportunity as we understand it. Our approach is straightforward and ineffective. Our descriptions are long, convoluted, complicated, we use confusing technical language all our own, and omit much needed context that we expect others should know. The result – no one understands what we’re talking about and we don’t get the behavior we’re looking for (immediate company realignment with what we know to be true).  Then, we get frustrated and shut down – opportunity lost.

To change the behavior of others, we must first change our own. As engineers we see problems which, when solved, result in opportunity. And if we’re to be successful, we must go back to the problem domain and set things straight. Here’s a sequence of new behaviors we as engineers can take to improve our chances of changing the behavior of others:

Step 1. Create a block diagram of the physical system using simple nouns (blocks) and verbs (arrows). Blue arrows are good (useful actions) and red arrows are bad (harmful actions). Here’s a link to a PowerPoint file with a live template to create your own.

Step 2. Reduce the system block diagram down to its essence to create a distilled block diagram of the problem, showing only the system elements (blocks) with the problem (red arrow).For a live template, see the second page of the linked file. [Note – if there are two red arrows in the system block diagram, there are two problems which must be solved separately. Break them into two and solve the first one first. For an example, see page three of the linked file.]

Step 3. Create a hand sketch, or cartoon, showing the two system elements (blocks) of the distilled block diagram from step 2. Zoom in so only the two elements are visible, and denote where they touch (where the problem is), in red. For an example, see page four of the linked file.

Step 4. Now that you understand the real problem, use Google to learn how others have solved it.

Step 5. Choose one of Google’s most promising solutions and prototype it. (Don’t ask anyone, just build it.)

Step 6. Show the results to your engineering friends. If the problem is solved, it’s now clear how the opportunity can be realized. (There’s a big difference between a crazy engineer with a radically new market opportunity and a crazy engineer with test results demonstrating a new technology that will create a whole new market.)

Step 7. If the problem is not solved, or you solved the wrong problem, go back to step 1 and refine the problem

With step 1 you’ll find you really don’t understand the physical system, you don’t know which elements of the system have the problem, and you can’t figure out what the problem is. (I’ve created complicated system block diagrams only to realize there was no problem.)

With step 2, you’ll continue to struggle to zoom in on the problem. And, likely, as you try to define the problem, you’ll go back to step 1 and refine the system block diagram. Then, you’ll struggle to distill the problem down to two blocks (system elements). You’ll want to retain the complexity (many blocks) because you still don’t understand the real problem.

If you’ve done step 2 correctly, step 3 is easy, though you’ll still want to complicate the cartoon (too many system elements) and you won’t zoom in close enough.

Step 4 is powerful. Google can quickly and inexpensively help you see how the world has already solved your problem.

Step 5 is more powerful still.

Step 6 shows Marketing what the future product will do so they can figure out how to create the new market.

Step 7 is how problems are really solved and opportunities actually realized.

When you solve the real problem, you create real opportunities.

There are a lot of complex self-help programs out there to help us reach our potential. These programs are designed to take us to the next level by building on what we have. And they do help. But implicitly the programs assume we’ve got a foundation in place and it’s solid enough to stand on. But I think our foundation is rickety.

To be what we must be is our responsibility, and if we’re going to get any value from our self-help programs it’s our responsibility to establish the conditions for growth.

Here are three forgotten pillars that must be in place if we’re to grow:

Good sleep habits – most of us our sleep deprived, yet the data is clear that a rested brain thinks better. If we’re to grow, we’ve got to think better, and to think better we need more rest.

Good eating habits – most of us eat poorly. We eat too much which hurts our bodies and we eat too infrequently which hurts our brains. We all know our muscles need calories or they don’t work well, but what we forget is our brain also needs calories. (It’s 2% of our weight but consumes about 20% of our total calories.) And when we eat infrequently our blood sugar drops and so does our brains’ ability to think. If we’re to grow, we need to eat better.

Good fitness habits – most of us don’t exercise daily. Our brain is connected to our body, and they interact. When the muscles are exercised they cause the brain to make chemicals that sooth and calm. When we exercise we have a better attitude, have more stamina, and think better. If we’re to grow, we need more exercise.

The big three are far more powerful than the best self-help scheme, but they’re also far scarier. They’re so scary because they’re easy to measure and completely within our control.

After a one month trial you’ll know if you’ve slept more, worked out more, and ate better. And if you haven’t, you’ll also know who is responsible.

Whether it’s innovation, creativity, continuous improvement, or discontinuous improvement, it’s all about cultural change, and cultural change is about change in behavior.

With the police state approach, detailed processes are created and enforced; rules are created and monitored; and training is dealt out and attendance taken. Yes, behavior is changed, but it’s fleeting. Take your eye off the process, old behavior slips through the fence; look the other way from the rules, old behavior clips the barbed wire and climbs over the wall. To squelch old behavior with the police state approach, gulag energy must be consistently applied.

To squelch is one thing, but to create lasting behavior change is another altogether. But as different as they are, there’s a blurry line of justice that flips innocent to guilty. And to walk the line you’ve got to know where it is:

• Apply force, yes, but only enough to prevent backsliding – like a human ratchet. Push much harder and heels dig in.
• The only thing slower than going slow is going too fast. (Remember, you’re asking people to change the why of their behavior.) Go slow to go fast.
• Set direction and stay the course, unless there’s good reason to change. And when the team comes to you with a reason, deem it a good one, and the cornerstone of trust is laid. (This is a game of trust, not control.)

But there are some mantras to maximize:

• Over emphasize the positive and overlook the negative.
• Praise in public.
• Don’t talk, do.

The first two stand on their own, but the third deserves reinforcement.

This isn’t about your words, it’s about your behavior. And that’s good because you have full authority over your behavior. Demonstrate the new behavior so everyone knows what it looks like. Lead the way with your actions. Show them how it’s done. For lasting change, change your behavior.

Even if changing your behavior influences only one person, you’re on your way. The best prison riots start with a single punch.

Today’s answer to everything is process and tools. Define the desired outcome; create the process; create the tools.  Problem solved.

But if the desired outcome is lasting change, deterministic processes and static tools won’t get us there.  Lasting change comes from people and their behavior.

Going forward, instead of creating process, create an environment of trust so people will investigate the unfamiliar; and instead of creating tools, create time – time for people to prototype the unfamiliar.

I’ve been thinking about how to use video to train engineers.  The trouble with video is it takes time and money to create.  But what if you could create lessons using existing video?  That’s what the new TED-Ed platform can do.  With TED-Ed, any YouTube video can be “flipped” into a customized lesson.

Instead of trying to describe it, I used the new platform to create a video lesson.  Click the link below and give it a try. (The platform is still in beta version, so I’m not sure how will go. But that’s how it is with experiments.)

Video lesson: Innovation, Caveman-Style

When answering the questions, it may ask you to sign up for an account.  Click the X in the upper right of the message to make it go away, and keep going.  If the video does not work at all, poke around the TED-Ed website.

Either way, so we can accelerate our learning and get out in front, please post a comment or two.

The stalled world economy will make growth difficult, and companies are digging in for the long haul, getting ready to do more of what they do best – add more function and features, sell more into existing markets, and sell more to existing customers. More of the same, but better. But growth will not come easy with more-on-more thinking. It will be more-on-more trench warfare – ugly hand-to-hand combat with little ground gained. It’s time for another way. It’s time for less. It’s time to create new markets with less-with-far-less thinking.

Real growth will come from markets and consumers that don’t exist. Real (and big) growth will come from the developing world. They’re not buying now, but they will. They will when product are developed that fit them. But here’s the kicker – products for the developed world cannot be twisted and tweaked to fit. Your products must be re-imagined.

The fundamentals are different in the developing world. Three important ones are – ability to pay, population density, and literacy/skill.

The most important fundamental is the developing world’s ability to pay. They will buy, but to buy products must cost 10 to 100 times less. (No typo here – 10 to 100 times less.) Traditional cost reduction approaches such as Design for Manufacturing and Assembly (DFMA) won’t cut it – their 50% cost reductions are not even close. Reinvention is needed; radical innovation is needed; fundamental innovation is needed. Less-with-far-less thinking is needed.

To achieve 10-100X cost reductions, the product must do less and do it far more efficiency (with far less). Product functionality must be decimated – ripped off the bone until only bone remains. The product must do only one thing. Not two – one. The product must be stripped to its essence, and new technology must be developed to radically improve efficiency of delivering its essence. Products for the developing world will require higher levels of technology than products for the developed world.

Radical narrowing of functionality will make viable the smaller, immature, more efficient technologies. Infant technologies usually have lower output and less breadth, but that’s just what’s needed – narrow, deep, and less. Less-with-far-less.

In the developing world, population density is low. People are spread out, and rural is the norm. And it’s not developed world rural, it’s three-day-hike rural. In the developing world, people don’t go to products; products go to people. If it’s not portable, it won’t sell. And developing world portable does not mean wheels – it means backpack. Your products must fit in a backpack and must be light enough to carry in one.

Big, stationary, expensive equipment is not exempt. It also must fit in a backpack. And this cannot be achieved with twist-and-bend engineering. To fit in a backpack, the product must be stripped naked and new technology must be developed to radically improve efficiency. This requires radical narrowing, radical reimagining, and radical innovation. It requires less-with-far-less thinking. (And if it doesn’t run on batteries, it should at least have battery backup to deal with rolling blackouts.)

People in the developing world are intelligent, but most cannot read well and have little experience with developed world products. Where the developed world’s solution is picture-based installation instructions, less-with-far-less products for the developing world demand no instructions. For the developing world, the instruction manual is the on button. And this requires serious technology – software algorithms fed by low cost sensors. And the only way it’s possible is by distilling the product to its essence. Algorithms, yes, but algorithms to do only one thing very well. Less-with-far-less.

The developed world makes products with output that requires judgment – multi-colored graphical output that lets the user decide if things went well. Products for the developing world must have binary output – red/green, beep/no-beep. Less-with-far-less. But again, this seemingly lower-level functionality (a green light versus a digital display) actually requires more technology. The product must interpret results and decide if it’s good – much harder than a sexy graphical output that requires interpretation and judgement.

Creating products for the developing world requires different thinking. Instead of adding more functions and features, it’s about creating new technologies that do one thing very well (and nothing more) and do it with super efficiency. Products for the developing world require higher technologies than those for the developed world. And done well, the developed world will buy them. But the crazy thing is, the less-with-far-less products that will be a hit in the developing world will boomerang back and be an even bigger hit in the developed world.

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.