Stop Using Methods. Start Building Molecules.

You ran a Design Sprint on Friday, everyone felt great. By Wednesday, the insights were gathering dust in a Miro board no one opens.

You built a Lean Canvas. It only took an hour, it clarified some things. Then it sat in a Google Doc while the team went back to building whatever they were already building.

Sound familiar? You're not bad at innovation - you're just not optimising your outputs.

The single-method trap

Most teams reach for innovation methods the way you reach for a painkiller. Something hurts, you grab the nearest tool, you hope it fixes things. Customer churn? Run some user interviews. No product direction? Do a Business Model Canvas. Team stuck? Brainstorm.

The method works. Sort of. It produces an output but the output doesn't connect to anything. There's no before, no after, no chain reaction. You end up with a pile of artefacts and no momentum.

This is the single-method trap, and nearly every team falls into it. Not because the methods are bad, but because a method on its own is like a chemical element sitting in a jar. Interesting to look at but inert until you combine it with something else.

Think like a chemist, not a pharmacist

Here's a better mental model.

In chemistry, elements are the building blocks. Hydrogen, oxygen, carbon. Each has specific properties. But elements don't do much by themselves. The interesting stuff happens when they bond together into molecules. Hydrogen and oxygen are just gases. Combine them the right way and you get water. Combine them a different way and you get hydrogen peroxide. Same ingredients, different structure, very different results.

Innovation methods work the same way. A Problem Interview is an element. So is a Lean Canvas, a Design Sprint, a set of Pirate Metrics. Each one has properties, strengths, and limitations. But the real power shows up when you string them together into sequences, where the output of one becomes the input of the next.

We call these sequences "molecules." And building them deliberately, rather than grabbing methods at random, is the difference between teams that ship things that matter and teams that run workshops.

What a molecule looks like

Take startup validation. A common molecule looks like this:

Challenge Brief → Problem Interview → Solution Interview → Lean Canvas

Each element does a specific job. The Challenge Brief forces you to articulate what you're actually trying to solve. The Problem Interview tests whether real people have that problem. The Solution Interview checks whether your proposed fix resonates. The Lean Canvas captures the whole thing as a testable business hypothesis.

Notice the bonding logic... Each method's output feeds directly into the next method's input. The Challenge Brief gives your interviews focus. Interview insights feed the Lean Canvas. Without that chain, each method floats on its own. With it, you get something that has emergent properties: a validated direction that no single method could have produced.

Or take a team that's already past product-market fit and trying to scale:

Product/Market Fit → Pilot Canvas → Scaling Operations → Scaling Playbook

This molecule takes you from "we know this works" to "we can operate this at scale." Try jumping straight from product-market fit to a scaling playbook and you'll miss the hard operational questions that the middle steps force you to answer. Remember: preamture optimisation is the root of all evil.

Why order matters

Chemistry is not just about which elements you combine but rather about how. H₂O is water. H₂O₂ is hydrogen peroxide. Same atoms, different bonds, very different outcomes.

The same is true for methods.

"Problem Interview → Lean Canvas → Build-Measure-Learn" is a stable, well-tested molecule. It moves you from understanding to hypothesis to experiment. Flip it around to "Build-Measure-Learn → Problem Interview → Lean Canvas" and you've got a mess. You're building before you've talked to anyone, then interviewing after you've already committed, then writing a canvas that rationalises what you've already done. Same elements, wrong bonds, bad chemistry.

Getting the sequence right matters because each method has what you might think of as valence: open connection points that need specific inputs and produce specific outputs. A Problem Interview needs a clear problem statement as input (that's what the Challenge Brief provides) and produces customer insights as output (which feed a Lean Canvas or Solution Interview). Ignore the valence and you get weak bonds. Respect it and the molecule holds together.

Playlists: molecules you can actually use

This is why we built Playlists into MethodPunks.

A Playlist is a pre-assembled molecule. It's an ordered sequence of methods designed for a specific situation, with the bonding logic already worked out. Instead of staring at a dozen methods wondering which to pick, you start from your situation ("I need to validate a new market" or "my team is stuck in ideation") and get a sequence that's been tested and refined.

We didn't build Playlists because we think teams can't figure this out on their own. We built them because assembling good molecules requires experience that most teams haven't had time to build. You need to know that a Facts, Assumptions, and Doubts session is a better starting point than a Brainstorm when your team is stuck. You need to know that a DFV Matrix should follow ideation, not precede it. You need to know that research-led product design has a specific arc: insight gathering, then design principles, then storyboarding, then prototyping. Not the reverse.

Playlists encode that sequencing knowledge. They're the recipes, and the Periodic Table is the ingredient list.

Start building

If you take one thing from this: stop thinking about which method to use and start thinking about which sequence to build. Ask yourself three questions:

Where am I starting from? What do I already know, what have I already done? This determines your first element.

Where do I need to get to? A validated hypothesis? A shipped MVP? A growth engine? This determines your last element.

What's the shortest stable path between them? This is your molecule. Each step should produce something the next step needs.

If that sounds like work, it is. But it's dramatically less work than running disconnected workshops and wondering why nothing changes.

The Periodic Table gives you the elements. Playlists give you proven molecules. Your job is to understand the chemistry well enough to know which molecule fits your situation, or to build your own when the situation demands it.

That's what we'll cover in the rest of this series. Next up: a guided tour of the Periodic Table of Innovation and how its structure helps you pick the right elements. After that: why some method combinations blow up in your face, and how to spot unstable molecules before you waste a sprint on them.

---

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.