A Solution Looking for a Problem

In 1968, Spencer Silver invented a glue that didn’t work.

3M had tasked him with creating a super-strong adhesive. Instead, he created a weak one — a goo that stuck to surfaces but peeled off without leaving residue. It held, but barely. It was perfect for nothing. 3M filed the patent and moved on.

The adhesive sat on a shelf for six years.

The Assumption That Almost Buried It

The assumption at 3M — like the assumption at almost every engineering organization — was that stronger is better. A glue that barely holds is a failure. A glue that leaves no residue is a defect. The entire culture of adhesive research was oriented toward a single axis: how strong can we make it?

Silver’s invention scored low on that axis. By every metric that mattered to the department, it was a miss. He believed it was interesting — he could feel there was something there — but he couldn’t articulate what problem it solved. He spent years presenting it internally. Nobody wanted it. Because nobody had a question for which this was the answer.

This is the most common failure mode in engineering: a brilliant solution to a question nobody is asking.

With this new humility, if you could separate the problem from the solution — and ask what question this technology is really answering — you would discover that the most valuable inventions are often answers to questions nobody has asked yet.

The Question That Found the Answer

Arthur Fry sang in his church choir. His problem was mundane but universal: the paper bookmarks in his hymnal kept falling out. He needed something that would stick to the page, hold through a service, but remove cleanly without damaging the book. He needed an adhesive that was strong enough to hold, but weak enough to let go.

Fry knew about Silver’s “failed” adhesive. He had heard the presentation. And in that moment in the church pew, he connected two things that had never been connected before: a problem he had, and a solution someone else had discarded.

The adhesive wasn’t a failure. It was a solution looking for the right problem. Silver’s job was to invent the glue. Fry’s job was to find the question the glue was trying to answer.

From the lab to the pew

Why This Matters for Engineers

The Post-it Note story is usually told as a tale of perseverance or serendipity. But it’s really a story about framing. Silver was working inside the frame of “make the strongest adhesive possible.” Within that frame, his invention was worthless. Fry stepped outside that frame and asked a different question: “What problem needs an adhesive that is purposely weak?”

That shift in framing turned a failed experiment into one of the most successful office products in history. 3M launched Post-it Notes in 1980 (originally called “Press ‘n Peel”). Today, the category generates over a billion dollars in annual revenue.

The frame shift is the hard part. Engineers are trained to solve problems, not to question whether the problem is framed correctly. We receive a requirement and we optimize against it. We build what was asked for, beautifully and efficiently and exactly to spec. But the spec itself is a frame. And if the frame is wrong, the best solution to the wrong problem is still wrong.

The teams that avoid this trap build a habit of asking one question before they start solving: What is the real problem here, and how do we know this is the right way to frame it?

With this new discipline of framing, if you could spend the first 20% of any project questioning the problem before solving it, you wouldn’t just find the right answer faster — you’d find answers that no one else could see.

The Right Question Is the Real Invention

Spencer Silver spent years trying to sell a solution without a problem. He couldn’t, because nobody was buying what he was selling. The solution was invisible until the right question appeared.

There is a lesson here for every engineer, every product team, every founder: the hardest part of building is not finding the right answer. It is finding the right question. A brilliant solution to an unasked question is invisible. A simple solution to a real problem — that is a revolution.

Before you start CAD, before you write a line of code, before you spin a board: ask the question. Ask it again. Ask it differently. Make sure it is the right question, because the right question will make the solution obvious.

And sometimes, the right question comes from a choir loft.

Framing a difficult engineering problem?

RaviK Consulting helps teams step back, reframe the question, and find solutions that others miss.

Start a Conversation