Shipulski On Design

Archive for the ‘Innovation’ Category

Innovation starts with recognition of a big, meaningful problem. It can come from the strategic planning process; from an ongoing technology project that isn’t going well; an ongoing product development project that’s stuck in the trenches; or a competitor’s unforeseen action. But where it comes from isn’t the point. What matters is it’s recognized by someone important enough to allocate resources to make the problem go away. (If it’s recognized by someone who can’t muster the resources, it creates frustration, not progress.)

Once recognized, the importance of the problem is communicated to the organization. Usually, a problem is important because it blocks growth, e.g., a missing element of the new business model, technology that falls short of the distinctive value proposition (DVP), or products that can’t deliver on your promises. But whether something’s in the way or missing, the problem’s importance is best linked to a growth objective.

Company leaders then communicate to the organization, using one page. Here’s an example:

WHY – we have a problem. The company’s stock price cannot grow without meeting the growth goals, and currently we cannot meet them. Here’s what’s needed.
WHAT – grow sales by 30%.
WHERE – in emerging markets.
WHEN – in two years.
HOW – develop a new line of products for the developing world.

Along with recognition of importance, there must be recognition that old ways won’t cut it and new thinking is required. That way the company knows it’s okay to try new things.

Company leaders pull together a small group and charters them to spend a bit of time to develop concepts for the new product line and come back and report their go-forward reccommendations. But before any of the work is done, resources are set aside to work on the best ones, otherwise no one will work on them and everyone will know the company is not serious about innovation.

To create new concepts, the small group plans an Innovation Burst Event (IBE). On one page they define the DVP for the new product line, which describes how the new customers will use the new products in new ways. They use the one page DVP to select the right team for the IBE and to define fertile design space to investigate. To force new thinking, the planning group creates creative constraints and design challenges to guide divergence toward new design space.

The off-site location is selected; the good food is ordered; the IBE is scheduled; and the team is invited. The company leader who recognized the problem kicks off the IBE with a short description of the problem and its importance, and tells the team she can’t wait to hear their recoomendations at the report-out at the end of the day.

With too little time, the IBE team steps through the design challenges, creates new concepts, and builds thinking prototypes. The prototypes are the center of attention at the report-out.

At the report-out, company leaders allocate IP resources to file patents on the best concepts and commission a team of marketers, technologists, and IP staff to learn if viable technologies are possible, if they’re patentable, and if the DVP is viable.(Will it work, can we patent it, and will they buy it.)

The marketer-technologist-IP team builds prototypes and tests them in the market. The prototypes are barely functional, if at all, and their job is to learn if the DVP resonates. (Think minimum viable prototype.) It’s all about build-test-learn, and the learning loops are fast and furious at the expese of statistical significance. (Judgement carries the day in this phase.)

With viable technology, patentable ideas, and DVP in hand, the tri-lobed team reports out to company leaders who sanctioned their work. And, like with the IBE, the leaders allocate more IP resources to file more patents and commission the commercialization team.

The commercialization team is the tried-and-true group that launches products. Design engineering makes it reliable; manufacturing makes it repeatable; marketing makes it irresistible; sales makes it successful. At the design reviews more patents are filed and at manufacturing readiness reviews it’s all about process capability and throughput.

Because the work is driven by problems that limit growth, the result of the innovation work is exactly what’s needed to fuel growth – in this case a successful product line for the developing world. Start with the right problem and end up with the right solution. (Always a good idea.)

With innovation programs, all the talk is about tools and methods, but the two things that really make the difference are lightning fast learning loops and resources to do the innovation work. And there’s an important philosophical chasm to cross – because patents are usually left out of the innovation equation – like an afterthought chasing a quota – innovation should become the umbrella over patents and technology. But because IP reports into finance and technology into engineering, it will be a tough chasm to bridge.

It’s clear fast learning loops are important for fast learning, but they’re also important for building culture. At the end of a cycle, the teams report back to leadership, and each report-out is an opportunity to shape the innovation culture. Praise the good stuff and ignore the rest, and the innovation culture moves toward the praise.

There’s a natural progression of the work. Start – do one project; spread – use the learning to do the next ones; systematize – embed the new behaviors into existing business processes; sustain – praise the best performers and promote them.

When innovation starts with business objectives, the objectives are met; when innovation starts with company leadership, resources are allocated and the work gets done; and when the work shapes the culture, the work accelerates. Anything less isn’t innovation.

Image credit – Jaybird

The most difficult part of innovation is starting, and the best way to start is the Innovation Burst Event, or IBE. The IBE is a short, focused event with three objectives: to learn innovation methods, to provide hands-on experience, and to generate actual results. In short, the IBE is a great way to get started.

There are a couple flavors of IBEs, but the most common is a single day even where a small, diverse group gets together to investigate some bounded design space and to create novel concepts. At the start, a respected company leader explains to the working group the importance of the day’s work, how it fits with company objectives, and sets expectations there will be a report out at the end of the day to review the results. During the event, the working group is given several design challenges, and using innovation tools/methods, creates new concepts and builds “thinking prototypes.” The IBE ends with a report out to company leaders, where the working group identifies patentable concepts and concepts worthy of follow-on work. Company leaders listen to the group’s recommendations and shape the go-forward actions.

The key to success is preparation. To prepare, interesting design space is identified using multiple inputs: company growth objectives, new market development, the state of the technology, competitive landscape and important projects that could benefit from new technology. And once the design space is identified, the right working group is selected. It’s best to keep the group small yet diverse, with several important business functions represented. In order to change the thinking, the IBE is held at location different than where the day-to-day work is done – at an off-site location. And good food is provided to help the working group feel the IBE is a bit special.

The most difficult and most important part of preparation is choosing the right design space. Since the selection process starts with your business objectives, the design space will be in line with company priorities, but it requires dialing in. The first step is to define the operational mechanism for the growth objective. Do you want a new product or process? A new market or business model? The next step is to choose if you want to radically improve what you have (discontinuous improvement) or obsolete your best work (disruption). Next, the current state is defined (knowing the starting point is more important than the destination) – Is the technology mature? What is the completion up to? What is the economy like in the region of interest? Then, with all that information, several important lines of evolution are chosen. From there, design challenges are created to exercise the design space. Now it’s time for the IBE.

The foundation of the IBE is the build-to-think approach and its building blocks are the design challenges. The working group is given a short presentation on an innovation tool, and then they immediately use the tool on a design challenge. The group is given a short description of the design challenge (which is specifically constructed to force the group from familiar thinking), and the group is given an unreasonably short time, maybe 15-20 minutes, to create solutions and build thinking prototypes. (The severe time limit is one of the methods to generate bursts of creativity.) The thinking prototype can be a story board, or a crude representation constructed with materials on hand – e.g., masking tape, paper, cardboard. The group then describes the idea behind the prototype and the problem it solves. A mobile phone is used to capture the thinking and the video is used at the report out session. The process is repeated one or two times, based on time constraints and nature of the design challenges.

About an hour before the report out, the working group organizes and rationalizes the new concepts and ranks them against impact and effort. They then recommend one or two concepts worthy of follow on work and pull together high level thoughts on next steps. And, they choose one or two concept that may be patentable. The selected concepts, the group’s recommendations, and their high level plans are presented at the report out.

At the report out, company leaders listen to the working group’s thoughts and give feedback. Their response to the group’s work is crucial. With right speech, the report out is an effective mechanism for leaders to create a healthy innovation culture. When new behaviors and new thinking are praised, the culture of innovation moves toward the praise. In that way, the desired culture can be built IBE by IBE and new behaviors become everyday behaviors.

Innovation is a lot more than Innovation Burst Events, but they’re certainly a central element. After the report out, the IBE’s output (novel concepts) must be funneled into follow on projects which must be planned, staffed, and executed. And then, as the new concepts converge on commercialization, and the intellectual comes on line, the focus of the work migrates to the factory and the sales force.

The IBE is designed to break through the three most common innovation blockers – no time to do innovation; lack of knowledge of how do innovation (though that one’s often unsaid); and pie-in-the-sky, brainstorming innovation is a waste of time. To address the time issue, the IBE is short – just one day. To address the knowledge gap, the training is part of the event. And to address the pie-in-the-sky – at the end of the day there is tangible output, and that output is directly in line with the company’s growth objectives.

It’s emotionally challenging to do work that destroys your business model and obsoletes your best products, but that’s how it is with innovation. But for motivation, think about this – if your business model is going away, it’s best if you make it go away, rather than your competition.  But your competition does end up changing the game and taking your business, I know how they’ll do it – with Innovation Burst Events.

Image credit – Pascal Bovet

If you want to run a brainstorming session to generate a long list of ideas, I’m out. Brainstorming takes the edge off, rounds off the interesting corners and rubs off any texture. If you want me to go away for a while and come back with an idea that can dismantle our business model, I’m in.

If you can use words to explain it, don’t bother – anything worth its salt can’t be explained with PowerPoint. If you need to make a prototype so others can understand, you’ve got my attention.

If you have to ask my permission before you test out an idea that could really make a difference, I don’t want you on my team. If you show me a pile of rubble that was your experiment and explain how, if it actually worked, it could change the game, I’ll run air cover, break the rules, and jump in front of the bullets so you can run your next experiments, whatever they are.

If you load me up to with so many projects I can’t do several I want, you’ll get fewer of yours. If you give me some discretion and a little slack to use it, you’ll get magic.

If, before the first iteration is even drawn up, you ask me how much it will cost, I will tell you what you want to hear. If, after it’s running in the lab and we agree you’ll launch it if I build it, I won’t stop working until it meets your cost target.

If there’s total agreement it’s a great idea, it’s not a great idea, and I’m out. If the idea is squashed because it threatens our largest, most profitable business, I’m in going to make it happen before our competitors do.

If twice you tell me no, yet don’t give me a good reason, I’ll try twice as hard to make a functional prototype and show your boss.

To do innovation, real no-kidding innovation, requires a different mindset both to do the in-the-trenches work and to lead it. Innovation isn’t about following the process and fitting in, it’s about following your instincts and letting it hang out. It’s about connecting the un-connectable using the most divergent thinking.  And contrary to belief, it’s not in-the-head work, it’s a full body adventure.

Innovation isn’t about the mainstream, it’s about the fringes. And it’s the same for the people that do the work.  But to be clear, it’s not what it may look like at the surface. It’s not divergence for divergence’s sake and it’s not wasting time by investigating the unjustified and the unreasonable. It’s about unique people generating value in unique ways. And at the core it’s all guided by their deep intention to build a resilient, lasting business.

image credit: Chris Martin.

If you haven’t done it before and you want to start, you have only one option – to start.

Much as there’s a huge difference between lightning and lightning bug, there’s a world of difference between starting and talking about starting. Where talking about starting flutters aimlessly flower to flower, starting jolts trees from the ground; fries all the appliances in your house; and leaves a smoldering crater in its wake. And where it’s easy to pick a lightning bug out of the grass and hold it in your hand, it’s far more difficult to grab lightning and wrestle it into submission.

Words to live by: When in mid conversation you realize you’re talking about starting – Stop talking and start starting. Some examples:

Instead of talking about starting a community of peers, send a meeting request to people you respect. Keep the group small for now, but set the agenda, hold the meeting, and set up the next one. You’re off and running. You started.

Replace your talk of growing a culture of trust with actions to demonstrate trust. Take active responsibility for the group’s new work that did not go as planned (aka – failure) so they feel safe to do more new work. Words don’t grow trust, only actions do.

Displace your words of building a culture of innovation with deeds that demonstrate caring. When someone does a nice job or goes out of their way to help, send words of praise in an email their boss – and copy them, of course. Down the road, when you want help with innovation you’ll get it because you cared enough to recognize good work. Ten emails equal twenty benefactors for your future innovation effort. Swap your talk of creating alignment with a meeting to thank the group for their special effort. But keep the meeting to two agenda items – 1. Thank you. 2. Pizza.

When it comes to starting, start small. When you can’t start because you don’t have permission, reduce size/scope until you do, and start. When you’re afraid to start, create a safe-to-fail experiment, and start. When no one asks you to start, that’s the most important time – build the minimum viable prototype you always wanted to build. Don’t ask – build. And if you’re afraid to start even the smallest thing because you think you may get fired – start anyway. Any company that fires you for taking initiative will be out of business soon enough. You might as well start.

Talk is cheap and actions are priceless. And if you never start a two year project you’re always two years away. Start starting.

Image credit – Vail Marston

If you’re not thinking differently, you’re thinking the same. And if you’re thinking the same, you’re going to get the same. Same may feel safe, and at some level it is. But when sameness festers into staleness, too much of a good thing isn’t wonderful.

In our fast moving Bizzaro World, safe is dangerous; repeatable is out and remarkable is in; improving what is is displaced by creating what isn’t; more capacity is outlawed and new capability is the only way; growing existing markets is wasteful because it gets in the way of creating new ones.

Ask your company leaders if they’re doing innovation, and the answer is yes. It’s a loaded question, and nothing good can come of it. “No, we don’t do innovation.” is a career-limiting response. Here are two better questions: What are you doing that’s different? What are you doing differently? These questions are effective because they require answers that are relative – relative to what you used to do. And because innovation starts with different, these questions are a good start.

Our assembly process is different and we increased productivity 0.3%; our product design is different and we made it stronger by 2.1%; our customer service tools are different and we decrease waiting time by 1.7%; our plastics are different and we reduced product cost by 0.6%. The difference is clear, but it didn’t really make a difference. Innovation starts with different, but all different isn’t created equal. Instead of shades of gray, think binary, think black to white, think no to yes.

Here are some better questions:

• Have we stopped distracting ourselves by focusing on growth of our biggest markets?
• Did we change the value proposition with our new product?
• Have we increased sales people in the undeveloped markets at the expense of sales people in our biggest markets?
• Do our new technologies change the argument?
• Are we working on the new products that will obsolete our most profitable product?
• Does the new product do less of anything so it can do more of something else?
• Are we working on the technologies so we can sell into Africa?
• Are we hiring experts in mobile technology?
• How about experts in data science?

There’s no hard and fast definition of what makes for the right no-to-yes thinking but their telltale sign is their wake of oblique problems. If your organization doesn’t know how to do something, then it could be an indication of powerful no-to-yes behavior. For example, if your translations group doesn’t know how to translate into a new language requested by sales, it could be because a new region of the world is now important. If your sales managers want to use a new search firm because your longstanding one can’t find the right new candidates, it may be because your new product demands a new flavor of sales people. If your compensation structure doesn’t let you make an acceptable offer to an engineer you really need, it could be because you need to hire for new specialties from different industries with radically different compensation norms.

“Are you doing innovation?”, as a question, is not skillful.  Instead, do the work so you must sell where you haven’t sold; use materials you’ve never used; use technologies you’ve never heard of; hire people you never had to hire; and create problems related to new geographies and new languages.  And when someone asks “Are you doing innovation?”, tell them you used to, but you’ve found something better.

Image credit – JD HANCOCK PHOTOS

Innovation is like growing orchids – both require a complex balance of environmental factors, both take seasoned green thumbs to sprout anything worth talking about, what worked last time has no bearing on this time, and they demand caring and love.

A beautiful orchid is a result of something, and so is innovation. It all starts with the right seeds, but which variety? Which color? With orchids, there are 21,950 – 26,049 species found in 880 genera and with innovation there are far more options. So which one and why? Well, it depends.

It’s no small feat to grow orchids or innovate:

To propagate orchids from seed, you must work in sterile conditions. The seeds must be grown in a gelatinous substance that contains nutrients and growth hormones. You must also be very patient. It takes months for the first leaves to develop, and, even then, they will only be visible with a magnifying glass. Roots appear even later. It will be at least three, and possibly as many as eight years before you see a bloom. — http://www.gardeners.com/how-to/growing-orchids/5072.html

[This is one of the best operational definitions of innovation I’ve ever seen.]

But there’s another way:

It is far easier to propagate orchids by division. But remember that dividing a plant means forsaking blooms for at least a year. Also, the larger the orchid plant, the more flowers it will produce. Small divisions take many years to mature. — http://www.gardeners.com/how-to/growing-orchids/5072.html

So do you grow from seed or propagate by division? It depends. There are strengths and weaknesses of both methods, so which best practice is best? Neither – with orchids and innovation no practices are best, even the ones described in the best books.

If you’ve been successful growing other flowers, you’re success is in the way and must be unlearned. Orchids aren’t flowers, they’re orchids. And if you’ve been successful with lean and Six Sigma, you’ve got a culture that will not let innovation take seed. Your mindset is wrong and you’ve got to actively dismantle the hothouse you’ve built – there’s no other way. Orchids and innovation require the right growing climate – the right soil, the right temperature, the right humidity, the right amount of light, and caring. Almost the right trowel, almost the right pot, and almost the right mindset and orchids and innovation refuse to flower.

And at the start the right recipe is unknown, yet the plants and the projects are highly sensitive to imperfect conditions. The approach is straightforward – start a lot of seeds, start a lot of propagation experiments, and start a lot of projects. But in all cases, make them small. (Orchids do better in small pots.)

Good instincts are needed for the best orchids to come to be, and these instincts can be developed only one way –  by growing orchids. Some people’s instincts are to sing to their orchids and some play them classical music, and they’re happy to do it. They’re convinced it makes for better and fuller blooms and who’s to say if it matters? With orchids, if you think it matters, the orchids think it matters, so it matters. And let’s not kid ourselves – innovation is no different.

With orchids and innovation, mindset, instincts, and love matter, maybe more than anything else. And for that, there are no best practices.

Image credit — lecercle.

Innovation is about selling different products and services to different customers. Different means growth because you’re not yet selling the different products and you’re not yet selling to the different customers.

If you can learn to see your customers differently, you’ll create new products that are different; and if you can learn to see your products and services differently, you’ll create new customers that are different.

Innovation is all about connecting the unconnected, and that’s what’s behind the push for diversity within innovation teams. A diverse group brings more things to connect and more perspectives to see connections.

And it’s best to innovate where there’s little to no competition. If you’re the only one developing new products for those new customers or your the only one creating a whole new community of customers, you’ll be more successful – your products have only to compete with products that don’t exist.

In almost every industry and market there’s a huge community of new customers just waiting for products and services that fit them – women. Women have ever more say over family finances, ever more buying power and, thankfully, ever more influence over our society. If you want to sell new and different products, you should learn how to innovate for women.

I’m not talking about the 1950’s-like worldview where men innovate and sell new dish detergent and vacuum cleaners to women. I’m talking about all products and all markets. What does a cordless drill look like when it’s designed for women? I don’t know because I’m a man. (The only thing I do know is it’s not the same old drill wrapped in pink. That’s just patronizing.

Plain and simple, women know best how to innovate for women.

The most important way to increase the diversity of your innovation teams is to add more women. Women can see unmet needs to which I, as a man, am blind. Women can connect things that I cannot. Women have an unique worldview that, as a man, I cannot fully appreciate.

If you really want a competitive advantage, replace some of your innovation leaders with women. And if you want to accelerate the transformation, your Chief Innovation Officer should be a woman.

There’s been a strong effort to teach STEAM/STEM to our girls and young women, and that’s good. But it’s time to create the climate where our girls and young women see themselves as the innovators of our future.

Image credit – Judepics.

Today is a celebration.

I have written a blog post every Wednesday evening for the last five years. No guest blogs, no ghost writer, no repeat blogs, and no editor. Just me.

The main theme last year was around doing new. Though I used the word innovation too many times, I provided real examples and grounded observations on what to do and why. There are many tools, processes, and philosophies around innovation – too many to cover fully even over a year or two of blogs – but there are two things that apply to all of us.

Innovation is context specific. Whatever you do going forward is strongly shaped by what you did to make the present what it is. And because every company’s history is different, every company’s go-forward activities will be different. Yes, become knowledgeable about best practices, but use only the ones that fit and don’t use them as-is – twist them to match the curves of your company. Yes, understand what other companies have done, but don’t copy them.

Innovation is all about people. If you can get people to try new things, you’re well on your way. And to get them to try new things, figure out why they’re afraid and do the small things, the everyday things, that make is safe to try.

My goal for year six – another year of meaningful writing.

Thanks for reading.

Mike

Image credit – woodleywonderworks.

Innovation results in things that are novel, useful, and successful. These things can be products, services, data, information, or business models, but regardless of the flavor, they’re all different from what’s been done before.

And when things are different, they’re new; and that means we don’t know how to do them. We don’t know how to start; don’t know how to measure; don’t know how they’ll be received; don’t know if they’ll be successful.

In the commercial domain, successful means customers buy your products and pay for your services. When customers value your new stuff more than they value their money, they pay; and when they pay it’s success. But first things first – before there can be success, before there can be innovation, there must be customer value. With innovation, customer value is front and center.

How do you come up with ideas that may have customer value? There’s a goldmine of ideas out there, with some veins better than others, and any dowsing you can use to pan the high grade ore is time well spent. There are two tools of choice: one that channels the voice of the customer and a second that channels the voice of the technology.

Your technology has evolved over time and has developed a trajectory which you can track. (Innovation On Demand, Fey and Riven.) But at the highest level, as a stand-in for technology, it’s best to track the trajectory of your products – how they’ve improved over time. You can evaluate how your products improved over multiple lines of evolution, and each line will help you to channel the future from a different perspective.

The voice of your customers is the second divining rod of choice. What they say about you, your company, and your products can help you glean what could be. But this isn’t the same as VOC. This is direct, unfiltered, continuous real time capture of self-signified micro stories. This is VOC without the soothsaying, this is direct connection with the customer. (Sensemaker.)

There are two nuggets to pan for: limiting cant’s and purposeful misuse. You seek out groups of customer stories where customers complain about things your product cannot do and how those cant’s limit them. These limiting cant’s are ripe for innovation since your customers already want them. Purposeful misuse is when the radical fringe of your customer base purposely uses your product in a way that’s different than you hoped. These customers have already looked into the future for you.

Do these ideas have customer value? The next step is to evaluate the value of your diamonds in the rough. The main point here is only customers can tell you if you’ve hit the mother lode. But, since your ideas are different than anything they’ve experienced, in order assay the ideas you’ve got to show them. You’ve got to make minimum viable prototypes and let them use their loop to judge the potential cut, color, clarity, and carat. As a prospector, it’s best to evaluate multiple raw gemstones in parallel, and whatever customers say, even if you disagree, the learning is better than gold.

How can we deliver on the customer value? With your innovations in the rough – ideas you know have customer value – it’s time to figure out what it will take to convert your pyrite prototypes into 24 carat products. There are missing elements to be identified and fundamental constraints to be overcome and backplane of the transmutation is problem definition. Done right, the technology development work is a series of well-defined problems with clear definitions of success. From the cleaving, blocking and cutting of technology development the work moves to the polishing of product development and commercialization.

Innovation can’t be fully defined with a three question framework. But, as long as customer value is the crowned jewel of your innovation work, most everything else will fall into place.

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.