Needs-driven product planning beats market analysis at finding gaps
Product planning can broadly be organized into two approaches: “market-analysis-driven” and “needs-driven.”
Market-Analysis-Driven
This method observes market trends and breaks things down into how many people want what kind of thing, how much business opportunity exists given that supply-demand balance, and so on. I think this is widely understood as a very common approach. With this method, pricing and the target market become very clear, and strategy is easy to build, so I suspect most companies adopt it. A major advantage is that it’s highly reproducible and can easily be extended or applied elsewhere, but it has the drawback that more or less anyone who does it arrives at roughly the same result. (In other words, competitors reach the same conclusion too.)
Needs-Driven
This approach amounts to “just make the thing you want!” It looks reckless at first glance, but it actually contains a lot of suggestive insight.
“Does a solitary eccentric, untouched by anyone else, even exist?”
Everyone is influenced by the market. Information now floods both the streets and the internet, and there’s no way to avoid being exposed to it. Even someone who thinks “I’m a solitary eccentric” is, to some degree, subject to an information bias from popular trends, reputations, friends’ opinions, advertising, and the like. So the argument can actually run the other way: someone who thinks of themselves as “a bit of an eccentric” is precisely positioned to propose something “slightly off from the norm,” which raises the chance of getting ahead of rivals and building something that matches market needs.
Someone once made this observation about online posts and abusive comments:
“It’s ultimately a skewed way of thinking held by just 1 in 10,000 people. But Japan alone has 100 million people, so it’s possible for 10,000 of that 1-in-10,000 group to gather. Once 10,000 of them gather, you really can’t ignore it anymore.”
This was a comment about what’s known as “2channel.”
Interpreted positively for product planning, it means that even a plan nobody inside the company (say, out of 10,000 people) agrees with might still have 10,000 supporters out in the world (100 million people in Japan alone). If there really are 10,000 users out there, whether it becomes a business is just a matter of execution. And taking a global approach might draw in even more people.
Today there’s a very effective way to test such a “needs hypothesis”: crowdfunding. You desperately want something yourself, but you’re unsure whether there’s truly demand for it in the market, and if there is, how many people would back it — so why not try crowdfunding first? Using crowdfunding this way has become far more common in recent years.
This is just my personal view, but I think plans built through the needs-driven approach tend to have a characteristic that market-analysis-driven plans lack: the central figure, the proposer, rarely has their resolve broken. Market-analysis simulations often produce different results just by tweaking the initial conditions slightly. But a personal feeling of “this is what I want!” rarely changes. When you show a plan to various people, they often find fault with the analysis method or approach, and you might find yourself thinking, “Ah, maybe they’re right.” But if you stay true to your own conviction, it doesn’t matter what others say. I think the needs-driven approach is the one that more often lets someone carry an initial concept through to the end, consistently.
It’s difficult to argue which is better or worse, but if there’s one thing I can say, it’s this: strongly thinking “I want this!” or “I want to make this!” doesn’t actually happen all that often, so that feeling should be treasured.
The content of this post is an excerpt (original text) from the following book. If you’re interested, please get a copy.
The Shape of a Happy IoT Startup
The Shape of a Happy IoT Startup
Originally published in Japanese at https://clazytech.com/2022/09/1218/. Translated with LLM assistance and reviewed before publication.