Innovation is all about learning. And if the objective of innovation is learning, why not start with learning objectives?

Here’s a recipe for learning: define what you want to learn, figure how you want to learn, define what you’ll measure, work the learning plan, define what you learned and repeat.

With innovation, the learning is usually around what customers/users want, what new things (or processes) must be created to satisfy their needs and how to deliver the useful novelty to them. Seems pretty straightforward, until you realize the three elements interact vigorously. Customers’ wants change after you show them the new things you created. The constraints around how you can deliver the useful novelty (new product or service) limit the novelty you can create. And if the customers don’t like the novelty you can create, well, don’t bother delivering it because they won’t buy it.

And that’s why it’s almost impossible to develop a formal innovation process with a firm sequence of operations. Turns out, in reality the actual process looks more like a fur ball than a flow chart. With incomplete knowledge of the customer, you’ve got to define the target customer, knowing full-well you don’t have it right. And at the same time, and, again, with incomplete knowledge, you’ve got to assume you understand their problems and figure out how to solve them. And at the same time, you’ve got to understand the limitations of the commercialization engine and decide which parts can be reused and which parts must be blown up and replaced with something new. All three explore their domains like the proverbial drunken sailor, bumping into lampposts, tripping over curbs and stumbling over each other. And with each iteration, they become less drunk.

If you create an innovation process that defines all the if-then statements, it’s too complicated to be useful. And, because the if-thens are rearward-looking, they don’t apply the current project because every innovation project is different. (If it’s the same as last time, it’s not innovation.) And if you step up the ladder of abstraction and write the process at a high level, the process steps are vague, poorly-defined and less than useful. What’s a drunken sailor to do?

Define the learning objectives, define the learning plan, define what you’ll measure, execute the learning plan, define what you learned and repeat.