5 Questions: Ellen DiResta on Why Best Practices Fail
For decades, we’ve faithfully followed innovation’s best practices. The brainstorming workshops, the customer interviews, and the validated frameworks that make innovation feel systematic and professional. Design thinking sessions, check. Lean startup methodology, check. It’s deeply satisfying, like solving a puzzle where all the pieces fit perfectly.
Problem is, we’re solving the wrong puzzle.
As Ellen Di Resta points out in this conversation, all the frameworks we worship, from brainstorming through business model mapping, are business-building tools, not idea creation tools.
Read on to learn why our failure to act on the fundamental distinction between value creation and value capture causes too many disciplined, process-following teams to create beautiful prototypes for products nobody wants.
Robyn: What’s the one piece of conventional wisdom about innovation that organizations need to unlearn?
Ellen: That the innovation best practices everyone’s obsessed with work for the early stages of innovation.
The early part of the innovation process is all about creating value for the customer. What are their needs? Why are their Jobs to be Done unsatisfied? But very quickly we shift to coming up with an idea, prototyping it, and creating a business plan. We shift to creating value for the business, before we assess whether or not we’ve successfully created value for the customer.
Think about all those innovation best practices. We’ve got business model canvas. That’s about how you create value for the business. Right? We’ve got the incubators, accelerators, lean, lean startup. It’s about creating the startup, which is a business, right? These tools are about creating value for the business, not the customer.
R: You know that Jobs to be Done is a hill I will die on, so I am firmly in the camp that if it doesn’t create value for the customer, it can’t create value for the business. So why do people rush through the process of creating ideas that create customer value?
E: We don’t really teach people how to develop ideas because our culture only values what’s tangible. But an idea is not a tangible thing so it’s hard for people to get their minds around it. What does it mean to work on it? What does it mean to develop it? We need to learn what motivates people’s decision-making.
Prototypes and solutions are much easier to sell to people because you have something tangible that you can show to them, explain, and answer questions about. Then they either say yes or no, and you immediately know if you succeeded or failed.
R: Sounds like it all comes down to how quickly and accurately can I measure outcomes?
E: Exactly. But here’s the rub, they don’t even know they’re rushing because traditional innovation tools give them a sense of progress, even if the progress is wrong.
We’ve all been to a brainstorm session, right? Somebody calls the brainstorm session. Everybody goes. They say any idea is good. Nothing is bad. Come up with wild, crazy ideas. They plaster the walls with 300 ideas, and then everybody leaves, and they feel good and happy and creative, and the poor person who called the brainstorm is stuck.
Now what do they do? They look at these 300 ideas, and they sort them based on things they can measure like how long it’ll take to do or how much money it’ll cost to do it. What happens? They end up choosing the things that we already know how to do! So why have the brainstorm?”
R: This creates a real tension: leadership wants progress they can track, but the early work is inherently unmeasurable. How do you navigate that organizational reality?
E: Those tangible metrics are all about reliability. They make sure you’re doing things right. That you’re doing it the same way every time? And that’s appropriate when you know what you’re doing, know you’re creating value for the customer, and now you’re working to create value for the business. Usually at scale
But the other side of it? That’s where you’re creating new value and you are trying to figure things out. You need validity metrics. Are we doing the right things? How will we know that we’re doing the right things.
R: What’s the most important insight leaders need to understand about early-stage innovation?
E: The one thing that the leader must do is run cover. Their job is to protect the team who’s doing the actual idea development work because that work is fuzzy and doesn’t look like it’s getting anywhere until Ta-Da, it’s done!
They need to strategically communicate and make sure that the leadership hears what they need to hear, so that they know everything is in control, right? And so they’re running cover is the best way to describe it. And if you don’t have that person, it’s really hard to do the idea development work.”
But to do all of that, the leader also must really care about that problem and about understanding the customer.
We must create value for the customer before we can create value for the business. Ellen’s insight that most innovation best practices focus on the latter is devastating. It’s also essential for all the leaders and teams who need results from their innovation investments.
Before your next innovation project touches a single framework, ask yourself Ellen’s fundamental question: “Are we at a stage where we’re creating value for the customer, or the business?” If you can’t answer that clearly, put down the canvas and start having deeper conversations with the people whose problems you think you’re solving.
To learn more about Ellen’s work, check out Pearl Partners.
To dive deeper into Ellen’s though leadership, visit her Substack – Idea Builders Guild.
To break the cycle of using the wrong idea tools, sign-up for her free one-hour workshop.
