Innovate by decision: method, not gift

Learning Objectives

Upon completing this book, you will be able to:

• Explain why innovation is an executable method and not a gift, and why what seems like inspiration is often invisible method.
• Distinguish between block/being stuck due to representation, the type of problem that this course unlocks, and three other types that are resolved in a different way.
• Describe the two images that underlie the course: the problem as a multifaceted object, and the innovator as the operator who makes decisions.
• Mentally execute the loop of work, diagnosing, choosing, executing, evaluating, and re-diagnosing, which will be repeated throughout the course.
• Classify your own problems as candidates or non-candidates for these techniques.
• Calibrate how much to trust each technique based on its level of evidence, and recognize what things this course decided not to teach.

The Bug That Was Solved by Walking

A programmer spends six hours fighting with a bug. The code should work and it doesn't. He reviews it line by line, changes one thing, changes it back, and tries again. Nothing. Frustrated, he closes his laptop and goes for a walk without a destination. After ten minutes, without having looked for it, the answer appears complete in his head: the problem wasn't where he was looking. He returns, writes three lines, and it works.

We all know some version of this story, in the shower, driving, about to fall asleep, and almost all of us draw the wrong conclusion from it.

The trap question is this: what solved the problem, the walk... or the six previous hours?

If it were the walk, anyone could solve that bug by going for a walk. But you can't solve that programmer's bug even if you walk all day, because you didn't load the problem. The walk didn't create the solution; it only allowed something to emerge that the six hours of work had prepared. The visible part, the walk, the "magical" moment, takes all the credit. The invisible part, the previous loading, did the work.

This is the first myth that the course debunks, and it debunks it with that single question. Inspiration didn't come out of nowhere. It came to the only person who had done the work to receive it.

“What seems like inspiration is, almost always, invisible method.”, Thesis of the course

The two myths that this course dismantles

Most people believe two things about innovation, and both are false, or at least, useless as a strategy. Before learning to innovate by decision, you have to dismantle them.

Myth 1: “Good ideas come when they want to”. It is the belief that inspiration is an uncontrollable event: it either happens to you or it doesn't, like rain. Whoever thinks this way treats innovation like an artist waiting for the muse. They sit, wait, and if the idea doesn't come, they conclude that “today was not the day”.

The problem is not that ideas never come this way, sometimes they do. The problem is that waiting is not a strategy. You cannot schedule an epiphany. But, as we will see, you can execute the method that increases its probability: loading the problem, choosing a way to turn it, and capturing what appears. Insight is never guaranteed; the method that triggers it can be repeated.

“A writer stuck with the second act of their novel can wait weeks for “the idea” to come. Or they can load the problem thoroughly, what the character needs, what prevents them from achieving it, what endings they have already discarded and why, and go for a walk. The walk without the load produces nothing. The load without the walk sometimes suffices. What never works is waiting seated.”

Myth 2: “Innovating is inventing from scratch”. The second myth is that innovating means creating something that did not exist, pulling an idea out of thin air. This belief paralyzes, because almost no one can invent from scratch, and whoever believes it feels incapable by definition.

The truth is more liberating: innovating is almost never inventing; it is reinterpreting and recombining. The automobile was an existing engine on an existing carriage. Gutenberg's press combined a wine press with movable type: two existing things put together for the first time. Neither piece was new; the configuration was. We will see this in detail in Module III, but the idea starts here: you don't have to invent the material, just see it in a different way.

Both myths, together, produce the classic paralysis of those who want to innovate: they believe they must wait for something they do not control (Myth 1) to create something impossible (Myth 2). The course replaces both with a single operational idea, which is the following section.

What is really being stuck

If innovating is not waiting or inventing out of thin air, what is it? To answer, we must first understand what being stuck is.

When you've spent hours stuck on a difficult problem, your difficulty is almost never a lack of data or a lack of intelligence. It's that your mind has become attached to a way of seeing the problem, a representation, and that way has become rigid. You keep pushing from the same angle, and from that angle, there is no way out. The science of insight confirms this: the solution to a difficult problem rarely comes from processing more information, but from reinterpreting the information you already have, by changing your representation of the problem (Kounios and Beeman).

This is why the moment of insight feels so sudden, like a "click". It's not that you've accumulated data until you've filled a glass; it's that suddenly you see the same information arranged in a different way, and the solution that was previously invisible becomes obvious.

Image 1: the problem is an object with many faces. Keep this image in mind, because it will come up again in each book. Imagine that your problem is a solid object with many faces, like a die, but with more sides. You're stuck because you've spent hours looking at the same face. All the information you need may be on another face, one you're not looking at.

Each technique in this course is a different way to turn the object to see a new face. Analogy turns it towards other domains; inversion turns it 180°; constraints turn it by taking away resources; first principles disassemble it down to the core. Six techniques that seem to have nothing to do with each other are, in reality, six ways to do the same thing: turn the object. This image is what unifies them.

The Innovator as Operator

If being stuck is an object that needs to be turned, who turns it, and how? This is where the second image of the course comes in, the one that defines the correct attitude.

Image 2: Operator, not Artist in Waiting. When faced with being stuck, the artist in waiting prays for inspiration: they sit and wait for the muse. The operator, on the other hand, does what a technician would do with a stopped machine: diagnoses the type of failure and chooses the right tool. They don't wait; they act methodically. This is the attitude that gives the course its name. You can't control whether insight arrives, that's never guaranteed, but you can control the method that increases its probability: when you load the problem, what technique you choose based on the type of block, and how you capture what appears. That's why it's called Controlled.

"The artist waits for the muse; the operator diagnoses and chooses the tool.", The Two Images of the Course

The Loop: the Heart of the Method. The operator's attitude is embodied in a repeatable work loop. It's the skeleton of the entire course, and you'll execute it many times:

Diagnose the block → Choose the technique → Execute it → Evaluate what it produces → and if nothing appears: re-diagnose and choose another side of the problem.

Read it slowly, because each step matters. Diagnosing the block prevents applying the method to the wrong problem (Module I). Choosing the technique based on what you feel prevents using a hammer where a screwdriver is needed (Module IV). Executing it and evaluating what it produces closes the cycle without killing half-formed ideas (Modules II and III). And the final rule, if nothing comes out, don't insist with the same technique; go back to the diagnosis, that's what separates the operator from someone who hits the machine harder hoping it will start.

What problems does this course respond to

Here comes one of the most important lessons, and the easiest to forget in the enthusiasm: not every difficulty is a representation block. These techniques unlock a specific type of problem. Applying them to the wrong problem not only doesn't help: it wastes time and discredits the method.

A problem is a candidate for this course when you know enough, the approach is solid, and yet you're still stuck going around in circles. It's not a candidate when the difficulty comes from elsewhere.

They do respond (candidates):

• Divergent problems: they admit many solutions and none obvious.
• Formulation problems: the challenge is to pose the question well.
• Strategic decisions stuck: you're going around in circles without seeing the levers.
• Creative blockages: the draft, design, or product isn't moving forward.

They don't respond (something else):

• Mechanical execution: you know what to do, you just need to do it.
• Direct calculation: there's a known procedure that gives the answer.
• Pure lack of information: you're missing a piece of data; the solution is to investigate, not to go around in circles.
• Poorly formulated problem: it's not stuck: it's poorly formulated; it needs to be rephrased.

Topic 2 of this module will give you a tool, the diagnostic semaphore, to distinguish between them with precision. For now, it's enough that you grasp the principle: diagnose before unlocking. Incubating a problem that was actually due to a lack of data doesn't lead anywhere.

The Case That Will Accompany Us

The entire course will revolve, literally, around a single problem. You will load it, incubate it, and solve it in your own way by passing it through six different techniques. It's not your problem: it's a real case, already solved by history, chosen because it's the perfect example of representation blockage. And for now, you won't know how it was solved. That's the rule of the course: the historical solution remains hidden until the end. Your job is to get to your own solution first.

Thread Case, Pan-Atlantic. The problem of loading a ship

United States, 1955. Malcom McLean runs a large road transport company, Pan-Atlantic. His business moves goods between factories, warehouses, and ports. But when a load has to continue by ship, the bottleneck appears: the products arrive at the port inside a truck and cannot continue inside it. They have to be unloaded piece by piece, boxes, barrels, sacks, machinery, from the truck to the warehouse, and from the warehouse to the ship. At the destination, everything is reversed. The ship crosses the ocean quickly, but it spends too much time stopped at the dock while it is loaded and unloaded by hand.

The problem, in one sentence:

How can Pan-Atlantic transfer large quantities of goods between trucks and ships without unloading, classifying, and reloading each product individually?

You are the innovation team hired in 1955. You don't know the solution that the company will implement later. You have to design it.

Why this case and not one of your own? For three reasons. First, because it's a perfect candidate: in 1955, no one lacked information or intelligence, and yet the shipping industry had been stuck on the same side of the problem for decades, "how can we load faster?", without seeing that there were other sides. It's collective fixation, pure and verifiable. Second, because anyone can understand it: boxes, trucks, ships, and cranes don't require technical vocabulary. And third, because keeping the same problem in your head throughout the course allows you to feel how each technique reveals a side that the previous one didn't show. That's the central learning, and it can't be had by jumping from one problem to another.

A note of honesty: what this course does not teach

Before proceeding, a statement of honesty that this course makes only once, early on, because it marks a difference with almost everything taught about creativity.

We do not teach group brainstorming as a central technique. It is the most famous technique in the world and is in all creativity courses. But the evidence is uncomfortable: group brainstorming often produces fewer and worse ideas than the same people working separately and combining them later. The reasons have names: block/being stuck (while one person speaks, the others wait and forget), evaluation anxiety (no one proposes something unusual for fear of judgment), and herd thinking (the group converges early on the first decent idea). We say it openly because here we do not repeat what everyone says: we teach what works for a person who is truly stuck.

We do not teach problem definition techniques. The five whys, mind maps, 5W/H, what, who, when, where, why, how, are useful, but they do not unblock: they organize. They belong to the diagnostic phase or a problem formulation course, not an innovation workshop. In this course, they live within the traffic light of Topic 2, not as techniques to turn the object around. Confusing "defining better" with "unblocking" is one of the reasons why people apply the wrong tool and conclude that "it did not work".

The Honesty Rule: Levels of Evidence

This course does not treat all its techniques as equally proven, and it says so. It is not about doing science, but about not lying to someone who can no longer find a way out. Saying what is proven and what is not is part of the help. Each technique, when its book arrives, will declare its level of evidence. Here is the complete map in advance:

• Incubation: strong (controlled studies). Base: meta-analysis of 117 studies (Sio and Ormerod).
• Analogy / Biomimicry: strong (controlled studies). Base: analogical transfer (Gick and Holyoak).
• Inversion: solid logic heuristic. Base: decision tradition (Jacobi, Munger).
• Constraints: heuristic with some evidence. Base: research on constraints and creativity.
• First principles: reasoning framework. Base: Aristotelian tradition; technological application.
• Recombination (SCAMPER): heuristic with a good track record. Base: Osborn / Eberle.

Notice something counterintuitive: saying "this is just a heuristic, it's not proven in a lab" does not weaken the tool in your eyes. It strengthens it. You trust more, not less, when someone tells you what is rock and what is scaffolding. The scaffolding holds just the same; it's just convenient to know what you're standing on.

Guided Practice

Innovation is not learned by reading, but by executing. This section has two parts: first, we classify the course case together, and then you classify three of your own problems.

Let's classify Pan-Atlantic (together). Let's pass the case through the question from section 5. Does Pan-Atlantic lack information? No: in 1955, the costs, times, and operation were perfectly well-known. Is it poorly posed? No: the question, transferring load without handling it piece by piece, is solid and clear. Do we know enough, is the approach solid, and yet the industry has been stuck for decades? Yes. Green light: it's a representation block. Pan-Atlantic is a perfect candidate. That's why it's our case.

Now you: three problems of your own. Think of three real problems you have right now, from work, a project, or your life. For each one, decide if it's a candidate, not a candidate, or you're not sure. Keep this sheet: one of these problems will come back at the end of the course, when you learn to apply the method to your own work.

Glossary of Key Terms

• Representation Block: State of being stuck on a difficult problem caused not by a lack of data, but by a rigid way of viewing the problem. It is the type of difficulty that this course unlocks.
• Insight: Sudden reinterpretation of a problem: the moment when the same information is rearranged in a different way and the solution becomes obvious (Kounios and Beeman).
• Controlled Innovation: Approach that does not guarantee insight, but controls the method that increases its probability: loading, choosing the technique, and capturing.
• The Operator: Attitude towards being stuck: diagnosing and choosing the tool, rather than waiting for inspiration like an artist in waiting.
• The Loop: Repeatable work cycle of the course: diagnose → choose → execute → evaluate → rediagnose.
• The Two Images: The problem as a multi-faceted object (mechanism) and the innovator as the operator who decides (attitude).
• Candidate: Problem that responds to this course: divergent, formulation, strategic or creative, and genuinely stuck.

Final Reflection and Self-Assessment

Before moving on to Topic 2 (Diagnosing the block), take a moment to check your understanding. It's not about memorizing, but about making sure you can apply the ideas.

Bibliography and Recommended Readings

• Kounios, J. and Beeman, M. (2009). The Aha! Moment: The Cognitive Neuroscience of Insight. Current Directions in Psychological Science, 18(4). [Central thesis of the course: insight is representation change.]
• Wallas, G. (1926). The Art of Thought. [The classic four-phase model, preparation, incubation, illumination, verification, of which this course is the operational version.]

• Levinson, M. (2006). The Box: How the Shipping Container Made the World Smaller and the World Economy Bigger. Princeton University Press. [The verified history of the Pan-Atlantic case.]
• Sio, U. N. and Ormerod, T. C. (2009). Does Incubation Enhance Problem Solving? A Meta-Analytic Review. Psychological Bulletin, 135(1).
• Kahneman, D. (2011). Thinking, Fast and Slow. Farrar, Straus and Giroux. [Thinking fast, thinking slow, Editorial Debate.]

Next Topic

You already know that innovation is a method, not a gift; that your problem is a multi-faceted object; and that you are the operator who turns it. You also know how to distinguish, in broad strokes, a real block/being stuck from a difficulty of another kind.

The following book, Topic 2: Diagnosing the Block, refines that distinction until it becomes a tool. You will learn to recognize cognitive fixation in yourself with measurable signals, and to use the diagnostic traffic light: three questions that prevent you from applying the method to the wrong problem. With that, you will complete Module I, the operator and the diagnosis, and you will be ready to load the engine: the incubation.

What seems like inspiration is, almost always, invisible method.