The decision tree and the reveal

Learning Objectives

Upon completing this book, you will be able to:

• Choose the appropriate technique for each block/being stuck using the decision tree, diagnosing what you feel, not the name of the technique.
• Apply the tree in four distinct domains: strategy, writing, programming, and product design.
• Consolidate your portfolio into a complete proposal before comparing it with reality.
• Compare your proposal with the historical solution by function, not by appearance.
• Classify your differences as favorable, neutral, unfavorable, or not verified.

Six Tools, a New Problem

You already have six techniques in your belt: incubation, analogy, inversion, constraints, first principles, and recombination. But imagine that tomorrow you get stuck with a new problem. When faced with block/being stuck, which of the six do you choose? If you choose wrong, you waste time, incubating a problem that is actually one of configuration, or inverting one that only needed a constraint.

The temptation is to choose based on the name of the technique or which one you liked the most. This is a mistake. The correct way to choose does not look at the technique: it looks at what you feel when you are stuck. Each type of block/being stuck has a characteristic feeling, and each feeling points to a technique. Learning to read that feeling is the operational climax of the course, what turns six loose tools into a method.

Remember Image 2: the operator does not pray for inspiration, diagnoses and chooses the tool. The decision tree is, at last, the operator's tool of choice.

The Decision Tree

Here is the heart of "by decision, not by inspiration". The tree is organized by what the person feels, not by the name of the technique. Locate your feeling in the left column and you have your technique:

• "I've already said everything I know and I'm going in circles" (and I have time): Incubation (Topics 3-4).
• "My field no longer gives me new ideas": Analogy / Biomimicry (Topic 5).
• "I don't see where to enter or what the levers are": Inversion (Topic 6).
• "I have too much freedom, everything feels the same": Constraints (Topic 7).
• "I suspect that an inherited assumption is limiting me": First principles (Topic 8).
• "I have the pieces but not the configuration": Recombination (SCAMPER) (Topic 9).

The Tree in Four Domains

The tree works in any field. Four mini-cases, one per domain, show the same logic of choice in very different contexts.

Strategy: the stuck decision. A team has been going around in circles with a decision for weeks and can't see the important variables. Feeling: "I don't see where to start or what the levers are". The tree points to inversion: "how would we guarantee that this decision turns out poorly?" reveals the risks that optimistic deliberation was hiding. If they also suspect that an industry assumption is limiting them, they chain first principles.

Writing: incubate structure, not words. A writer stuck on a chapter re-reads without making progress. Feeling: "I've said everything I know and I'm still going in circles", and they have time. The tree points to incubation, but with a nuance: incubate the structure (what the scene needs, what's missing), not the exact words. Load the structural problem, go for a walk, and let the return bring order, not prose.

Programming: the classic fixation. It's the case of Topic 1: six hours fighting with a bug, the same three hypotheses in rotation. Pure feeling of fixation with time available. The tree points to incubation, the bug of the walk, . And if upon returning they're still stuck because "it's always been done this way" in the inherited code, first principles: what truly obliges that architecture?

Product Design: when to stop iterating head-on. A team iterates over and over on the same screen and all versions feel equally valid. Feeling: "I have too much freedom, everything feels the same". The tree points to constraints: "redesign it with half the elements", "on a single screen". And if the design field has been exhausted, analogy: how does another industry solve this?

The moment of truth: present your dossier

Before raising the curtain, consolidate. During five books you turned Pan-Atlantic on five sides and were adding pieces. Now gather them into a single coherent proposal. Do not continue reading until you have answered, even if only in draft, these six questions, which are the ones a real innovation team would have to answer:

• The unit of cargo. How is the merchandise grouped? Form, size, material, opening system, protection.
• The transfer. How does the unit move from the warehouse to the truck, to the port, to the ship, and back?
• Compatibility. What needs to be modified in trucks, ships, ports, cranes?
• Safety. How do you avoid openings, displacements, falls, damage, loss of stability?
• The economic model. What investment, what savings, how many operations to recover the cost?
• The pilot test. How would you test the Newark-Houston route without transforming the entire fleet at once?

Write your answers before turning the page. Seriously: the value of the revelation depends on you arriving at it with your proposal already formed. Comparing yourself to history only teaches if you have something to compare.

The Revelation

Let's lift the curtain. This is what actually happened.

🎬 The Revelation, Port Newark, April 26, 1956.

On that day, a modified oil tanker, the Ideal-X, set sail from Port Newark bound for Houston, carrying 58 metal cargo units on its deck.

Malcom McLean's solution consisted of separating the box containing the merchandise from the truck chassis and wheels. That box could be filled at the customer's facilities, travel on a chassis on land, detach from the vehicle, be lifted with a crane, be placed on the ship, cross the sea without being opened, be unloaded at the destination, be placed on another chassis, and continue by road. Zero manipulation of the merchandise between origin and destination.

But the innovation was not just the box. Pan-Atlantic had to develop or coordinate an entire system: resistant containers, systems for lifting them, structural connection points, holding mechanisms, modified ships, port cranes, compatible chassis, loading and weight distribution procedures, and coordinated land and sea operations. Years later, international normalization established dimensions, fastenings, and stacking forms so that any company could use a compatible system.

There it is. And now compare it with what you derived. If your dossier ended up as a sealed unit, separated from the wheels, standardized, moved with cranes on modified ships, and filled at the origin, you arrived there alone, with method, at containerization. Not because you are a genius, but because the five techniques led you there, face to face. That is innovating by decision, not by inspiration.

Functional Comparison

We don't evaluate you for having drawn an exact container. We evaluate you for functions fulfilled. Your proposal can differ greatly from the historical one and still be excellent, or resemble it and hide a flaw. The comparison is made function by function:

The functions that Pan-Atlantic (the historical solution) fulfills, and against which you will compare your proposal, are:

• Avoids unloading products individually.
• Separates the load from the wheels and chassis.
• Allows for land and sea transportation.
• Protects the merchandise.
• Can be lifted mechanically.
• Can be secured during the trip.
• Takes advantage of the ship's space.
• Requires modifying infrastructure.
• Can be used on different routes.
• Can become a standard.
• Can be implemented with a pilot test.

Where your proposal differs from the historical one, classify the difference into one of four categories. This classification, not the resemblance, is what measures the quality of your solution:

• Favorable: your proposal fulfills the same function with less cost, risk, infrastructure, or complexity. You improved upon history.
• Neutral: you use a different mechanism, but the result is comparable. Different path, same destination.
• Unfavorable: your proposal eliminates an important advantage or introduces a difficult-to-implement dependency.
• Unverified: it seems possible, but you don't have enough evidence that it would work. Lacking proof.

Guided Practice

Take your consolidated dossier (section 4) and the revelation (section 5), and make the complete comparison. The deliverable is your filled functional table, with each difference classified and the key question answered.

Glossary of Key Terms

• Decision Tree: A tool that chooses the technique based on what you feel when you're stuck, not based on the name of the technique. The operational climax of the course.
• Sensation-Based Diagnosis: Identifying the type of block by the characteristic sensation it produces, to choose the suitable technique.
• Functional Comparison: Evaluating a solution by the functions it fulfills, not by its similarity to another. Instrument of evaluation of the course.
• Categories of Difference: Favorable, neutral, unfavorable, or not verified: the classification of how your solution differs from the historical one.
• Innovation as a System: The principle that an important innovation rarely is a standalone object, but rather a coordinated system of parts.

Final Reflection and Self-Assessment

Bibliography and Recommended Readings

• 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 containerization and the Ideal-X.]

• Kounios, J. and Beeman, M. (2009). The Aha! Moment. [The change of representation, revisited with the solution in view.]
• Arthur, W. B. (2009). The Nature of Technology. [Innovation as a system of components, not as an isolated object.]

Next Topic

You already know how to choose a technique, and you already know how the story ends. You turned Pan-Atlantic on its six sides, presented your dossier, and compared it with the Ideal-X. The case fulfilled its mission: it taught you the entire method using a single problem, solved in your own way.

The last book, Topic 11: Sustained Rhythm and Transfer, concludes the course by taking you back to your world. So far, you have practiced using someone else's case; now you will take one of your real problems, the one you classified in Topic 1, and run it through the tree, executing a technique on it. Additionally, you will set up your weekly rhythm plan so that controlled innovation becomes a habit and not an event. The case trained you; the next book sets you free to fly solo.

A great innovation is rarely an object. It is almost always a system.