The Periodic Table of Innovation: A User's Guide

The real periodic table is one of the greatest organising ideas in science. Mendeleev didn't just list elements - he arranged them so that their position on the table tells you something about their behaviour. If you know where an element sits, you already know a lot about what it does and how it reacts with other elements.

We built the Periodic Table of Innovation with the same intent. It's not a catalogue, it's a map. And like any good map, it's more useful once you know how to read it.

The structure: families and periods

The real periodic table groups elements into families (columns) based on shared chemical properties. Alkali metals behave like other alkali metals. Noble gases behave like other noble gases. You don't need to memorise every element's properties because the family tells you most of what you need to know.

Our table works the same way. The methods in the MethodPunks collection are organised into methodology families: Design Thinking, Lean Startup, Agile, Growth Hacking, Stage Gate, Open Innovation, Product Development, and Lean Enterprise.

Methods in the same family share a worldview.

Design Thinking methods tend to start from empathy and work toward prototypes. Lean Startup methods tend to start from hypotheses and work toward validated learning. Agile methods tend to start from backlogs and work toward shipped increments. Growth Hacking methods tend to start from metrics and work toward experiments.

This matters because when you're building a 'molecule', a sequence of methods for a specific job, you often start within a family and then cross into another. Knowing which family a method belongs to tells you what kind of thinking it requires and what kind of output it produces. That's your first clue about whether two methods will bond well.

Difficulty as atomic weight

Each method in our table has a difficulty rating: Beginner, Intermediate, or Advanced. Think of this like atomic weight. Heavier elements are harder to work with and less stable in inexperienced hands.

Beginner methods like Brainstorming, How Might We, Kanban Boards, and Mind Mapping are lightweight. They're easy to facilitate, require minimal setup, and produce quick results. They're the hydrogen and carbon of innovation: fundamental, versatile, present in almost every molecule.

Intermediate methods like Design Sprint, Business Model Canvas, Customer Journey Map, and A/B Testing require more skill to run well. They have more moving parts, need better facilitation, and their outputs are more nuanced. Most of the table sits at this level.

Advanced methods like Product/Market Fit, Building Your Flywheel, Scaling Playbook, and Four Steps to the Epiphany are the heavy elements. They're powerful but harder to handle. They require significant context, experience, and often multiple rounds to get right. You wouldn't start a brand-new team on Scaling Operations any more than you'd hand a chemistry student a lump of plutonium.

A well-designed molecule usually starts lighter and gets heavier. You warm up with a Challenge Brief (Beginner), move through Problem Interviews and Lean Canvas work (Intermediate), and arrive at Product/Market Fit (Advanced) only after you've earned it through prior steps. Jumping straight to the heavy stuff without foundation is one of the most common mistakes teams make.

Reactivity: which methods combine well

In chemistry, some elements are highly reactive. Drop sodium in water and you get a violent reaction. Noble gases, on the other hand, barely react with anything. They're stable on their own.

Methods have reactivity too. Some are designed to feed into other methods. A Challenge Brief is highly reactive. Its output (a well-framed problem statement) bonds naturally with Problem Interview, How Might We, Problem Reframing, and half a dozen other methods. It almost never appears alone.

Other methods are more self-contained. A Design Sprint is closer to a noble gas. It's a five-day process with its own internal structure: Lightning Demo, Rapid Ideation, Rapid Prototyping, and Usability Testing are all built in. You can use it as a standalone method and get a complete result. It still bonds with other methods (Design Sprint → MVP Specification → Development Sprints is a strong molecule), but it doesn't need them the way a Challenge Brief does.

Understanding reactivity helps you avoid two common mistakes.

First, using a highly reactive method in isolation. Running a Problem Interview without a Challenge Brief to focus it, or generating How Might We questions without prior research, produces vague results because the method is missing the input it was designed to bond with. Second, trying to force a bond between two low-reactivity methods that don't need each other. Bolting a Design Sprint onto a Scaling Playbook doesn't produce useful chemistry. They belong in different molecules.

Element families: a quick tour

Design Thinking methods (User Personas, Customer Journey Map, Design Principles, Prototyping, Usability Testing, and others) focus on understanding human experience and building for it. They're empathy-first and prototype-heavy. They bond well with each other and frequently cross-react with Lean Startup methods.

Lean Startup methods (Lean Canvas, Build-Measure-Learn, Pivot or Persevere, Problem Interview, Solution Interview, MVP Specification) focus on hypothesis testing and validated learning. They're assumption-first and experiment-heavy. They're some of the most reactive methods in the table because their outputs (validated/invalidated hypotheses) feed so naturally into decision-making.

Agile methods (Development Sprints, Kanban Boards, Product Owner, Acceptance Criteria, MoSCoW Prioritisation) focus on delivery. They're execution-first and cadence-heavy. They typically appear later in molecules, after direction has been set by Discovery or Strategy methods.

Growth Hacking methods (Pirate Metrics, A/B Testing, North Star Metric, One Metric That Matters, 1000 True Fans) focus on measurable growth. They're data-first and experiment-heavy. They bond well with Lean Startup methods and tend to form molecules that sit in the post-launch phase.

Stage Gate methods (Challenge Brief, DFV Matrix, Research Plan, Technology Readiness Levels, and others) provide structure and governance. They're the connective tissue that helps large organisations manage innovation without killing it. They bond with almost everything because they're process methods, not content methods.

Open Innovation methods (Crowdsourcing, Hackathons, Accelerator Program, Innovation Mapping, Public and Social Innovation Labs) bring external input into the process. They're boundary-crossing methods that often form their own distinct molecules for organisations working beyond their own walls.

Product Development methods (Product Requirements Document, Product Roadmap, Test Plan, Site Maps) focus on turning validated ideas into shippable products. They bond tightly with Agile methods and often form the back half of longer molecules that started in Discovery or Design Thinking.

Reading the map

Here's the practical version of all this. When you're facing a challenge and trying to pick methods:

Start with your situation, not the table. Are you trying to understand a problem? Validate a solution? Ship a product? Scale a business? Your situation tells you which region of the table to look in.

Pick from the right family first. If you're in discovery mode, start with Design Thinking or Lean Startup methods. If you're in delivery mode, start with Agile or Product Development methods. If you're in growth mode, start with Growth Hacking methods.

Respect the difficulty gradient. Start with Beginner or Intermediate methods. Work toward Advanced methods only after you've built the foundation they require.

Check the bonds. Before you add a method to your sequence, ask: does the previous method produce something this method needs as input? If you can't answer that clearly, the bond is weak and the molecule won't hold.

The Periodic Table of Innovation isn't a menu where you pick your favourite dish. It's a system where position, family, and relationships between elements all carry information. Learn to read it and you'll stop wondering which method to use. You'll start seeing which combinations to build.

Next in this series: why some method combinations produce breakthroughs and others produce confusion, and how to tell the difference before you commit resources to finding out.

---

Ready to explore the elements? Browse the Periodic Table of Innovation to see all 70+ methods, filter by methodology family, and start building your own molecules.