Developing New Products and Services: From Idea to Commercial Launch

We're doing a deep dive today into something pretty fundamental. The systematic approach companies take to develop new market offerings, you know, the products and services that really fuel growth and give them an edge. Right, it's a critical process. And the insights we're exploring here come from strategic marketing management by Alexander Ternev, who's a professor of marketing at Northwestern University. A great foundation for this discussion. So our mission really is to get under the hood. Understand how businesses can actually minimize those inherent risks that come with innovation, how they optimize resources, which is always a challenge, and navigate that whole journey often pretty complarious from just an idea to real market success. It's more than just a single launch, isn't it? It's about building a capability. Exactly. It's about crafting a sustainable engine for growth, not just hoping for a one-hit wonder. Okay, let's unpack this a bit. In the business world, we hear constantly about innovation. It's everywhere. But why are new market offerings specifically? So fundamentally critical. Why is it more than just, you know, a nice to have? Well, it's absolutely foundational. You could say new offerings are the lifeblood, really the engine for business growth. The engine, yeah. Because they let companies meet evolving customer needs. And customer needs, as we know, are never static. They shift technology pushes things forward. Constantly changing. Right. And if you're not keeping up, you're effectively falling behind. But it's not just reactive. It's more than just keeping pace with existing needs. Okay. New offerings can actually open doors to completely new markets for a company. Yeah. Markets they weren't even playing in before. And maybe most powerfully, they can sometimes generate entirely new demand, create a need where maybe people didn't even realize they had one. So it's not just filling an existing gap, but potentially creating a whole new space. Redefining the playing field. Precisely. They don't just fill a gap. They can fundamentally redefine what's possible for consumers. And by extension, what's possible for your own business model? That really shifts the perspective, doesn't it? From innovation being defensive, just keeping current customers happy to being really offensive, actively shaping the market. How do companies balance that? You know, the resources needed for tweaking existing stuff versus chasing these high risk, maybe high reward, new market creations. That's a core strategic tension, absolutely. And it points to the multiple benefits. It's not just about the revenue from that one new shiny product. Right. It's also about strengthening customer loyalty. Because when you consistently innovate, you're showing customers you understand them. You're relevant, maybe even anticipating needs they haven't articulated yet. Building that trust, that connection. Exactly. And crucially, new offerings provide avenues for diversification. That's so important for long-term strategic resilience. Spreading the risk. If you're two dependent and one product, one market segment, you're incredibly vulnerable, shift in tech, a new competitor, an economic downturn. It could be devastating. Diversification through new offerings creates resilience and new revenue streams. So the bigger picture, it's less about a single product launch. Yes, it's more about building a continuous capability, almost like a muscle for value creation within the organization. Successful companies don't just think about the next product. They cultivate a culture where innovation is expected. Where spotting unmet needs is everyone's job. Maybe where calculated failure is seen as learning. Designing the organization for it. Designing it for perpetual curiosity and adaptability. Not just isolated projects. Okay, but that brings us to a pretty stark reality. One that often gets maybe downplayed. The high failure rate. The fact is most new offerings don't make it in the market. That's subring. It is. A very sobering statistic. What does that failure rate tell us about the fundamental nature of bringing something new out there? And how does smart companies really prepare for that? Not just acknowledge it, but actively plan for it. Well, that high failure rate tells us fundamentally that innovation is messy. It's inherently complex. It's riddled with uncertainty. Not a straight line. Definitely not. The path from idea to success is rarely straightforward. The core challenge is dealing with that significant uncertainty because more uncertainty directly translates to a higher risk of failure. Makes sense. So for the smart companies, recognizing and actively managing these risks isn't an afterthought. Something you bolt on at the end. It's a vital, deeply integrated part of the entire development process right from day one. Baked in from the start. Exactly. It's about systematically guiding resources towards the ideas with a better shot at success. And just as importantly, being disciplined enough to weed out the ones that look less promising or maybe are even fundamentally flawed before you sink too much time, money, and effort into them. So being brutally honest at each step. Rubbly honest, yes, it requires that discipline. So it's definitely more than just gut feel when launching something new. It's a structured effort to minimize that uncertainty. And I guess that uncertainty looks different depending on what you're launching. It's not a one-size-fits-all risk profile, is it? You're absolutely right. The level of novelty involved makes a huge difference to the risk. We can generally think about new offerings falling into two broad categories. Revolutionary and evolutionary. OK, let's start with revolutionary. That sounds dramatic. What sets them apart? How do they change the game? Revolutionary offerings are the ones delivering truly new to the world benefits. They're not just incremental improvements. They often create entirely new market categories or fundamentally redefine existing ones. Game changers. Total game changers. Think about their power to disrupt entire industries, reshape how consumers behave. Netflix is a classic example. They didn't just offer another way to rent movies. Right, they completely changed entertainment consumption. Exactly. From physical DVDs by mail to streaming on demand and eventually creating their own content, that was revolutionary. Or Uber, not just another taxi service, right? No, it changed personal transport. Using an app, the transparency. It revolutionized it. Challenge regulations, everything. An Airbnb. Transformed hospitality. Offered personalized, often cheaper lodging. Directly competing with hotels by using existing spaces differently. Democritizing travel in a way. In a way, yes. These offerings provided benefits competitors just couldn't easily match at the time. They fundamentally altered consumer habits, market structures, even some social norms. They saw problems people maybe didn't even know they had or solved existing problems in a radically better way. Okay, so that's the revolutionary side. What about the other end evolutionary offerings? What do those look like? Evolutionary offerings. Well, they involve relatively minor tweaks, modifications, enhancements to products or services that already exist. A more familiar territory. Much more familiar. Things like different colors, maybe new flavors, different sizes, slightly updated designs, new packaging. They tend to offer higher performance on attributes people already understand, but without dramatically changing the competitive landscape or fundamentally altering how people use them. So like the next generation of a smartphone. Exactly. Successive generations of mobile phones, computers, even things like razors. Each new model might have a slightly faster chip, a better camera, maybe a closer shave, but it's still fundamentally a phone, a computer, a razor. Operating in an established market. Right. Within an established market with known competitors, they improve, they optimize, they keep the product line fresh and competitive, extend its life cycle. But they don't disrupt in that same fundamental way. Their value is in those incremental gains that keep customers satisfied. Okay, so we have these two types. Does the way you manage them differ significantly, especially around risk? Well, the core principles will talk about apply to both, definitely. But the management of uncertainty and risk, that's particularly acute, much more intense for those new to the world revolutionary offering. Why is that? Just because it's unknown territory. Precisely. You're stepping into genuinely uncharted waters. There's no established playbook, no reliable historical market data to lean on, like you might have for an evolutionary tweak. Forecasting demand, predicting how competitors will react, understanding potential regulatory hurdles, it all becomes exponentially harder. Protests work involved. More informed guesswork, hopefully, but yes, more uncertainty. Which makes a systematic approach to managing that risk even more critical. You're navigating with far more unknowns. Okay, so given that higher risk, especially for the revolutionary stuff, let's break down the specific types of risks companies face. You mentioned market risk and technological risk earlier. Can we dig into those? What are the big blind spots leaders might have? Right, the challenge of uncertainty is really the crux of it. More uncertainty equals higher risk of failure. So systematic risk management is non-negotiable. Now, when we talk about market risk, we're talking about the uncertainty tied to the five key factors defining any market. Often called the five Cs. With five Cs, okay, what are those? They are customers, the company itself, its collaborators, its competitors, and the broader context or environment. Uncertainty around any of these create market risk. Can you give us some concrete examples for each sue? Where do companies typically stumble with these market risks? Sure, let's start with customers. A big risk here is developing something brilliant, or so you think, but the customer needed addresses turns out to be short lived. Maybe it's a fad. Like a slash in the pan? Exactly. Or maybe the need is real, but it's confined to a market segment that's just too small to justify the investment in development, marketing, distribution. You build it, but not as people actually buy it to make it worthwhile. Investing heavily for a niche that just can't sustain the business, that sounds painful. It happens. Then there's company risk. This is internal. Does your organization actually have the necessary resources, maybe a specific expertise like knowing how to work with a new material, maybe just sheer capital to scale up production, or even the manufacturing capacity itself. So you have the idea maybe even the market, but lack the internal muscle to execute. Right. You might lack the capability or the institutional knowledge to plug it off effectively or efficiently. Think of a small software startup, suddenly trying to build complex hardware without any manufacturing experience. Big internal risk there. Okay. What about collaborators? Partners seem essential, but they can also be a weak link, right? Absolutely vital and often an underestimated risk. Your success can hinge on your partners. If key suppliers can't meet quality standards, or maybe they can't deliver on time. Your whole launch could be jeopardized. Completely derailed. Or what if a crucial distributor doesn't push your product effectively, or even drops it? Your market access disappears. Your success depends on their reliability, their commitment, their strategic priorities, aligning with yours. It's a network and any weak link. Breaks the chain, makes sense, and competitors that seems pretty obvious they react. Obvious, but still dangerous. The risk is clear. Rivals might quickly copy your technology, maybe with a cheaper version, effectively turning your innovation into a commodity almost overnight. Undercutting you. Or even worse, maybe they enhance your idea, leapfrogging you with a superior product before you've even established a foothold. We see that constantly in tech, right? Rapid iteration and improvement by competitors. Yeah, the smartphone market is a classic example, and the last C context. That sounds really broad, almost unpredictable. It is broad and often the hardest to actively control. Context risk comes from unforeseen shifts in the wider environment. Think rapid technological advances that suddenly make your brilliant new offering obsolete. Like betting on the wrong tech standard. Exactly. Or major economic shifts, like a certain recession that decimates consumer spending power. Or unexpected regulatory changes new rules, new standards that create hurdles or even ban aspects of your product. Or even new tariffs or taxes that just blow up your cost structure. Things entirely outside your control. Or really outside your direct control. Yes. Think about how fast things like AI regulations or shifts in environmental policy could change the game in certain industries. Any big contextual shift can undermine a previously solid market position. Wow. That's a lot to juggle. O stumpomers, company, collaborators, competitors, context. It sounds like a business leader needs almost a 360 degree view to spot all these potential pitfalls. Where do they most often miss step? Is it underestimating competitors or maybe misjudging their own internal capabilities? How do these risks interact? You've hit a key point. Their interconnectedness. Often the biggest blind spot isn't just one C in isolation. It's the cascade effect when they interact. Ah, the ripple effect. Precisely. A common pattern is maybe underestimating company risk thinking you have the internal chops when you don't. This leads to delays or cost overruns which introduces technological risk. Okay. So one problem creates another. Right. And those delays then give competitors time to catch up or react. Or maybe customer needs shift while you're delayed making your product less desirable by the time it finally launches. See how they link. It's a chain reaction. And this interconnectedness also applies strongly to technological risk itself. This is the uncertainty around feasibility. Can we actually build this thing reliably at scale? That can't be done. Question. Exactly. Concrete examples. Maybe desired features turn out to be technically impossible with current tech. Or the product design looks great but is functionally flawed or unreliable. Using new, unproven technologies is inherently risky. It might compromise reliability leading to failures. So a great idea. Clear market need. But the tech just isn't ready or stable. It happens. And this is where a seemingly technical problem rapidly becomes a market problem. If tech issues push your launchback by months or even a year. The market moves on. Market moves on. Competitors might emerge customer preferences evolve. That initial window of opportunity might shrink or close entirely before you even get there. So managing these isn't just about ticking boxes for each risk type. It's understanding their potential interplay across the entire venture. Okay. Given all that complexity, all those interconnected risks, it's obvious that just, you know, winging it the throw spaghetti at the wall approach to innovation is not going to work. Definitely not sustainable, which brings us to a really crucial framework, the stage gate approach. You described it as a disciplined roadmap. How exactly does it provide that systematic path, steering clear of just ad hoc decisions? It really functions as that roadmap. And it's a very popular one specifically designed to manage risk throughout new offering development. The core idea is quite elegant. It breaks the whole process down into distinct stages like idea generation, concept development, etc. Okay. And between each stage, there's a gate, a rigorous checkpoint. An idea or a concept or a product has to meet specific criteria at that gate to be allowed to receive to the next stage. So formal decision point, formal decision points. Exactly. This structure forces a systematic way of designing and validating the business model step by step. The key benefits, it minimizes risk by catching flaws early. It helps optimize how you allocate scarce resources, time, money people. And it ensures the whole process is geared towards creating something that actually delivers clear market value, not just building something cool because you can. Right. It builds in that validation at every step, preventing you from pouring good money after bad if something's fundamentally not working. That's the essence of it. Fail early, fail cheaply if you're going to fail. Okay. Let's walk through these stages then. Stage one. Idea generation and validation. The very beginning, the seed of innovation. Where does this process kick off? What are companies looking for? Fundamentally, it starts with discovering an unmet market need. A problem people have, a desire not being fulfilled, and then generating a novel idea to address that need. And novel doesn't just mean new tech. Not at all. Novelty can come in many forms. Sure, it could be a groundbreaking new technology, but it could also be an original branding approach that makes you stand out. Or an innovative pricing model that unlocks a new segment, maybe unique incentives for customers or partners, or even entirely new ways to communicate or distribute the offering. The idea is that initial spark, that hypothesis about how value can be created differently. And where did these sparks usually come from? Is it always the lone genius in a lab having a eureka moment? Rarely. Ideas have incredibly diverse origins and smart companies cast a really wide net. They can certainly come from internal sources. Maybe deep analysis of market research data reveals a hidden need. Or frontline employees have suggestions based on customer interactions. Listening to the people closest to the customer. Exactly. But external sources are just as vital. Direct customer feedback from surveys, focus groups, maybe even online communities or crowd sourcing platforms. And don't forget, collaborators, suppliers, distributors, co-developers, often have unique insights into market gaps or potential solutions. So building a pipeline of potential ideas from multiple sources. A robust pipeline, yes. And once you have an idea, you don't just run with it immediately, right? There's this crucial step, idea validation. This sounds like the first filter. It is absolutely critical first case. Idea validation is about assessing the fundamental soundness of the idea and the accuracy of the assumptions behind it. It boils down to two main things at this early stage. Preliminary desirability. Does this idea actually address an unmet need that a meaningful group of customers genuinely cares about? Is the problem real and important to them? And the second preliminary viability. Looking ahead, could an offering based on this idea realistically create sustainable value, meaning profit for the company you're asking, is this solving a real important problem? And can we potentially build a business around solving it? If the answers aren't reasonably positive, the idea needs work. Or maybe it's just not the right fit. That sounds like a tough filter. I imagine companies can make costly mistakes here, either killing a good idea too soon, or letting a bad one proceed. How do you strike that balance? They absolutely can make mistakes, and there are really two types of errors to worry about. The first is failing to reject a poor idea. You let something through that's unlikely to succeed, and you end up wasting valuable time, money, talent, pursuing a dead end. That's the obvious painful one. Sunk costs later on. Exactly. But the second error, often less visible, but potentially just as damaging, is rejecting a good idea. Killing something with real potential, simply because it didn't fit neatly into existing boxes or initial assessments, seemed lukewarm. Missing a big opportunity. Missing a huge opportunity that maybe a competitor then picks up. Took me. While the high failure rate of new products might make you think the first error pursuing bad ideas is more common, it's not always the case. Failure also comes from missed opportunities, or from those inherent market and tech risks we talked about hitting you later, even with a good initial idea. It requires a delicate balance. Critical evaluation, yes, but also open-mindedness to possibilities. Do diligence mix with a bit of daring? Okay. Now, when generating these ideas, you mentioned different approaches. Let's look at top-down idea generation. That sounds very market focused. It is. Top-down is explicitly market-driven. It often represents a more, let's say, strategic and less serendipitous path to innovation. It starts by identifying a significant market opportunity first, essentially finding a widespread problem that's looking for an invention, a solution. Then you work on creating that solution. The focus is on uncovering an important customer problem that your company might be uniquely positioned to solve better than anyone else. Or, Maybe a problem no one is addressing adequately. - So market analysis, customer empathy, understanding the pain points first. - Exactly, it's problem solver first and venture second. You're looking for unmet needs where you can offer a superior solution. - Can you give us some classic examples of companies that really nailed this problem first approach? - Oh, absolutely, think about Apple's iPod. Portable music players existed, but they were often clunky, limited storage, terrible interfaces. Apple saw a clear unmet need for something user-friendly that could hold your whole library. - Right, a thousand songs in your pocket. - That was the solution to a clear problem. The iPhone did something similar. Integrated a phone, PDA, music player, camera, into one seamless device, solved the fragmentation problem. The iPad filled a gap between phone and laptop. - Okay, beyond Apple. - Procter and gamble swiffer. Address the hassle and inefficiency of traditional mobs. Huge unmet need for easier floor cleaning. Herman Miller's Aaron Chair designs specifically to solve ergonomic problems for office workers. Not just look good. Tesla's Model S tackled the perception that electric cars had to be slow, small, or compromised, aiming for a premium, high-performance EV. Dyson's vacuum cleaner directly addressed the universal frustration of vacuums losing suction. - A very tangible pain point. - Very tangible. Uber solved the problem of unreliable, inconvenient taxi services using tech. Airbnb tackled the need for affordable, unique lodging options. All started with a clearly defined market problem. - So finding that friction, that gap, and building a much better mouse trap. Strength seems obvious. You're likely solving a real need. What's the potential downside though? - Well, the strength is that you're inherently more likely to create something with market value because you started with the need. But it doesn't guarantee you can actually create a viable solution. You might identify a massive problem, but find it's technically impossible to solve with current technology. Or the cost of the solution might be so high that it's just not economically feasible. So identifying the problem is only half the battle. Finding a workable, profitable solution is the other half. - Right, now what about the flip side? Bottom-up idea generation. This sounds more like invention-driven, maybe accidental. - It's off in the reverse, yes. More characterized by discovery, sometimes serendipity. Bottom-up starts with an invention often, quite literally, an invention searching for a problem it can solve. - An invention looking for a job. - Pretty much. Then the task becomes identifying a market need that this new invention, this new technology can actually address effectively. It's not driven by market research identifying a need. First, it's driven by the breakthrough itself, often coming out of R&D labs, led by scientists or engineers. The question becomes, okay, we've discovered this cool thing. What can it do for people? Are there famous examples of this, maybe accidental discoveries that became huge? - Loads of them. Penicillin is a classic. Alexander Fleming wasn't looking for an antibiotic. He noticed mold accidentally killing bacteria on a petri dish. - A lucky accident. - A world-changing, lucky accident. Post-it notes are another famous one. A 3M scientist trying to make a super strong glue accidentally made a weak reusable one. It was a solution without a problem until a colleague found a use for it as a bookmark. - Wow. - The microwave oven came from an engineer noticing a chocolate bar melting near radar equipment. Velcro was inspired by birds sticking to a dog's fur after a hike. - Nature providing the idea. - Exactly. Even big pharma has examples. Regain for hair loss started as a high blood pressure drug. Hair growth was a side effect. Viagra was originally studied for angina. It's effects on erectile dysfunction were unintended, but obviously led to a massive new application. Teflon, the non-stick coating was discovered during research into refrigerants. - Incredible stories. It shows innovation can really spark from anywhere. So the key lesson here, even with a brilliant bottom-up invention. - Is that it still needs to solve a real unmet market need to succeed commercially. Novel technology alone isn't enough. - Needs a purpose. - It needs a purpose, people value. Market value is the ultimate arbiter, regardless of origin. An invention without a market problem is just a curiosity. It might be scientifically fascinating, but it's not a business until it connects with the compelling need or desire. - Makes perfect sense. And building on that idea of need, you also categorize offerings based on whether they are problem solving or experience enhancing. What's the difference there and why does that distinction matter so much for strategy? - Well, fundamentally to great value, an offering has to improve a customer's well-being by addressing some unmet need. Problem solving offerings tackle critical, often urgent needs. They alleviate a tangible pain point. - Fixing something broken or frustrating. - Exactly. Because customers see these as essential fixing something annoying or preventing something bad. The value proposition is usually pretty clear, easy to communicate. Think about the Dyson vacuum example again, solving suction loss. Or maybe a new cybersecurity tool that stops ransomware attacks. People perceive these as must-haves. - So faster adoption likely. - Often, yes. Because the need is urgent or deeply felt. - And experience enhancing offerings. What's their role? - These are different. They improve upon existing solutions. They provide a gain rather than alleviating a pain. It makes something that already works reasonably well, even better, more satisfying, more convenient, higher performing. - Like upgrading from good to great. - Precisely. Adoption for these tends to be slower. It usually requires more investment in educating customers, convincing them why they need this enhancement when their current solution might feel good enough. Think about software upgrades a new version of Microsoft Office, or Adobe Creative Suite, or the yearly updates to smartphones from Apple or Samsung. Your current phone works fine. The software does its job. The new version is often perceived as nice to have. Not an urgent must-have. - Okay, so why is this distinction paying versus game must-have versus nice-to-have? So significant for business leaders. - It impacts almost everything strategically. Marketing budget, expected adoption speed, pricing power, everything. This raises an important question for leaders. Is it more strategic for us to solve a deep problem or to enhance an existing experience? Which path to take? - Both are valid paths to innovation, of course. But a common failure point is companies overestimating their ability to educate customers about the benefits of an experience enhancing offering, especially if it doesn't solve a pressing problem. - They think the game is bigger than the customer perceives it. Or they underestimate the inertia, the switching costs. The effort required to get someone to change behavior for a non-urgent benefit. If you're solving a clear problem, the value is often self-evident. Customers might even seek you out. If you're just enhancing an experience, you usually have to work much harder, spend more on marketing to convince people they need that upgrade. It often means higher customer acquisition costs at a longer payback period. Being honest about which category your offering fits into is critical for realistic planning. - That's a really practical distinction. Okay, that wraps up stage one idea generation and initial validation. Now we move into stage two, concept development and validation. Refining the vision, what's the main goal here? How do we give that initial idea a more concrete form? - The primary purpose of concept development is really risk reduction. It's about significantly reducing the risks inherent in full product development before you commit major capital. By creating a detailed but still simplified version of the offering, a tangible representation, a concept that you can use to evaluate its desirability and feasibility more deeply before you invest heavily in building the final thing. Bringing something new to market takes serious time, money, effort. So validating a concept first one that captures the core features is just crucial for efficiency. - You wanna find the flaws now, not after building the factory. - Exactly, fail fast, fail cheap. If the core concept isn't resonating or isn't buildable. - And a huge part of this is prototyping, right? You mentioned the Greek root, prototype on primitive form. This is where ideas start to feel real. - Prototyping is absolutely central here. It's about creating those scaled down tangible versions. The goal is rapid refinement, get feedback on the core benefits, gauge customer reactions, test feasibility assumptions, and ultimately maximize market potential, all with minimal initial investment. - You mentioned the MIT Media Lab pre-do, demo or die. - Yes, a powerful reminder. Ideas only gain real value, real traction when they become tangible, when people can interact with them, react to them. And prototypes don't have to be super sophisticated initially. They can be rough models, simple mockups, even storyboards, just to test a user flow or a core value proposition. - And these prototypes evolve, right? From simple sketches maybe to something much more interactive later on, how do you decide the right level of detail? - Yes, the complexity varies hugely depending on what you need to learn. Early on, it might just be a diagram showing how features connect, or a basic physical model showing form factor, or a low fidelity wireframe for digital product. Later, especially as you move towards offering development, prototypes become much more advanced, with the detailed design, maybe functional elements, looking much closer to the final product. - So it's iterative. - Highly iterative. Prototyping isn't a one-off step. It's a cycle of building, testing assumptions, learning, and refining the concept continually. The fidelity you choose depends entirely on the specific assumption you need to validate at that moment. Core desirability might only need a sketch. Usability testing needs something more interactive. - And this whole iterative loop, build, test, learn, refine, that's what we call validated learning, it sounds different from just doing market research up front. - It is quite different. Validated learning is that continuous cycle. Observe the market, form a hypothesis, your idea. Build a prototype to test it. Get it in front of real users, measure the outcome, what worked what didn't learn from that data, and then refine your idea or prototype based on those learnings. It's fundamentally data driven using empirical tests in a real or simulated environment to optimize the concept. How does it differ from traditional market research then? Traditional market research is often done heavily upfront before much is built, and can rely a lot on asking people hypothetical questions. Would you buy this? Validated learning is about building something, even simple, putting it out there, and seeing what people actually do with it, then iterating. It's a much more dynamic, action-oriented loop integrated throughout the development process, minimizing the risk of building something based on faulty upfront assumptions. Okay, and this iterative refinement eventually leads into alpha and beta testing. What's the difference and how much testing is enough? Right, alpha testing is typically internal, done within the company, maybe by employees, QA teams, small control group. The goal is finding major bugs, usability issues, breaking points before it goes external. Kicking the tires internally? Exactly. Beta testing is when you go external. You put the prototype or early version out to a larger group of actual end users, in their own real world environments. This is where you get feedback on usability in diverse situations, performance across different setups, overall satisfaction, and uncover issues you've never find in the lab. And how much is needed? The more novel and complex the offering, the more extensive both alpha and beta testing usually need to be. If it's a radically new piece of software, for example, that needs to work on different operating systems, with different hardware, for users with varying technical skills, you need broad beta testing to catch all the potential compatibility issues in edge cases. You want to surface as many problems as possible before a wide commercial launch. Okay, let's unpack this. The story of Sir James Dyson's supersonic hairdryer really brings this intense validation to life, doesn't it? That sounds like an almost obsessive level of testing. It's an absolutely prime example of validated learning and rigorous concept validation taken to an extreme. Dyson, already known for vacuum and fan innovations, spent over four years developing that supersonic hairdryer. Four years for a hairdryer. It wasn't a quick project. The validation effort was incredibly intensive. They created get this more than 600 prototypes before settling on the final design. 600. That's staggering. It is. Over 100 engineers worked on it. Defiled more than 250 patents during development, protecting every little innovation. Wow. For companies that maybe don't have Dyson's resources or that singular focus, what's a more realistic goal for iteration? How do you avoid endless tinkering but still do enough? When is good enough, actually good enough, especially with market pressures? That's the constant strategic tension, isn't it? Dyson's level of investment was extraordinary, maybe unique. But the core lesson isn't the number 600. It's the commitment to iterative refinement before launch. For other companies, it's about ruthlessly prioritizing the most critical assumptions, the biggest risks, and finding the leanest fastest ways to test those. Minimum viable testing, almost. In a sense, good enough is reached when you've confidently validated the core desirability, feasibility, and viability for your initial target market. And the data suggests diminishing returns from further tweaking. You don't need 600 prototypes for everything, but you need enough evidence to de-risk the launch significantly. What's fascinating with Dyson, though, is the detail. They tested on over 1,000 miles of real human hair in labs and user tests to understand diverse hair types. 1,000 miles of hair. And they performed over 7,000 acoustic tests just to get the sound profile right to make it quieter, the result. A product that was genuinely faster, quieter, lighter, better designed. It justified its premium price and dominated the market. That obsessive validation was key to its success. Okay, so after all that relentless testing and refining, we arrive at concept validation. This is the critical gate, the decision point after stage 2. What exactly is being validated here and what happens if the concept just doesn't pass this gate? Yes, concept validation is that crucial gate. It's the checkpoint ensuring the core concept is solid enough to justify serious investment in development and launch. It focuses intently on two things, now with much more evidence than in the initial idea stage. Feasibility. Is it technologically possible to actually build a fully functional reliable version of this concept at scale within reasonable cost? And desirability. Does this concept, as refined through prototyping and testing, strongly appeal to target customers? Does it effectively address their need better than the alternatives? So can we build it and do they really want it? That's the essence. If the concept fails validation at this gate, maybe it turns out to be technically much harder or more expensive than anticipated. Or maybe user testing revealed customers just weren't that excited about the core benefit after all. Then what? Pull the plug. The company faces a critical decision. They either have to pivot, make a significant change, redefine the concept based on what they learned. Or if multiple attempts at refinements still don't lead to a validated concept, they might have to reevaluate the original idea entirely, potentially shelving the project. He is. You don't proceed to stage three and start spending big development money until this concept validation gate is passed. Makes sense. So assuming the concept is validated, we move to stage three, business model design and validation. Now we're ensuring viability. How does the focus shift here? It's less about the product itself and more about the whole commercial structure, right? This is where the rubber really meets the road financially. Exactly. You've nailed the shift. Stage two, concept development was heavily focused on desirability. Do they want it? And feasibility can we build it? Stage three, business model design uniquely adds that crucial third leg viability. Viability can make money. Can it generate sustainable value, typically profits for the company? It's about figuring out how the offering will actually create and capture market value. Not just for customers, but also for collaborators and critically for the company itself. This stage moves beyond just having a cool validated concept to mapping out the entire strategic and financial blueprint for how this offering will succeed as a business. So what are the key pieces you need to define when designing this business model? It sounds like laying the foundation for the entire venture. It is laying that foundation. There are three core interconnected components you need to design and validate. First, the target market. Really defining who you're creating value for. This means digging deep into those five seas again, understanding the specific customers, the competitive landscape, potential collaborators, your own company's strengths and weaknesses relative to this market and the broader context. Getting crystal clear on the playing field. Second is the value proposition. What specific value are you creating? You need to articulate the benefits for target customers versus their costs, money, time, effort. But also what's the value for your collaborators? Why should they partner with you? And crucially, what value does the company aim to capture revenue, market share, strategic positioning? Defining the win, win, win. Yes. And the third component is the market offering itself. This is the how. How will you actually create, communicate, and deliver that value? This covers the specifics. The product features, the service elements, the brand identity, the pricing strategy, any incentives, the communication channels you'll use, the distribution methods. It's the operational plan for bringing the value proposition to the target market. Okay, so it connects the concept to the commercial reality. What are the guiding questions here? How do you ensure you're actually creating market value, not just a cool product? And how does this tie directly to the financial side? Because like you said, a great product with no viable business model is just an expensive hobby. The overarching goal is creating and capturing market value, so the guiding questions are intensely focused on that. How does our offering create superior value for target customers compared to their alternatives? They need a compelling reason to care to you. How does it create value for our collaborators, ensuring their motivated partners? And how does it create superior value, specifically profit and sustainable advantage for our company, answering these forces a holistic view? And the financial validation. This is absolutely where the rubber meets the road financially. You have to rigorously validate the entire business model, which means bringing those three core principles, desirability, feasibility, and viability together with hard numbers and realistic projections. They form an interconnected trio, a failure in one inevitably undermines the others. Let's break down that trio again in the context of the business model, desirability first. Desirability here is about whether target customers find the overall offering appealing, considering everything, the product, the price, the ease of access, the brand perception. It's the balance of perceived benefits versus perceived costs, money, time, effort, psychological costs. If the benefits aren't compelling enough, or the costs seem too high, desirability drops. Can you give us examples where things failed primarily on desirability at the business model stage? Maybe the concept was okay, but the overall package wasn't right? Sure. Crystal Pepsi is a good example again. Feasible to make, PNG had the resources, but the overall proposition clear cola just wasn't desirable to enough consumers. Apples leased a computer too. Technologically feasible, revolutionary even, but the $10,000 price tag in the early 80s made the overall offering undesirable for almost everyone. The value proposition didn't match the cost. Okay. Then feasibility in the business model context. Is it just technical feasibility again? Yeah. It includes technical feasibility, but it's broader here. It's about whether the company possesses or can realistically acquire all the resources and capabilities needed to execute the entire business model as designed. Can you manufacture at the required scale and cost? Do you have the market? experience, can you build a distribution network, can you secure the necessary partnerships? It's about the operational feasibility of the whole system. For instance, long range EVs weren't truly feasible as a mass market business model until battery tech costs came down and charging infrastructure started to be billed out. The whole ecosystem needed to be feasible. Got it. And finally, viability, the bottom line. Viability is purely about the offering's ability to create value for the company, which for most means generating profits. It comes down to the fundamental economics. Do the projected revenue streams exceed the total cost structure, development, production, marketing, distribution, overhead? Can you make money doing this? Pets.com is the classic cautionary tale here. Highly desirable brand during the.com bubble seemed feasible with online ordering. Yeah. Completely unviable. They lost money on almost every sale because shipping heavy bags of pet food was prohibitively expensive. Weak financial fundamentals, unsustainable cost structure. Boom. Material, desirability, feasibility, viability, they're like a three-legged stool for the business model. Exactly. A very robust sanity check. Neglecting any one leg means the whole thing collapses. An undesirable offering won't generate revenue, making it unviable. An unfeasible model can't deliver the promised value, making it undesirable. They're completely intertwined. You have to rearsely validate all three components of the business model. Product market assumptions, value proposition strength, and market offering execution against all three criteria before you commit to full development. Many ventures fail because they only get one or two right. That's a really clear framework. Okay. Assuming the business model passes validation, it's desirable, feasible, and viable we finally get to stage four. Offering development. Bringing the vision fully to life. What's the first major step here? Building the actual thing. Well, almost. The very first step is actually developing or securing all the core resources needed to implement that validated business model. You've designed the blueprint, now you need the materials and tools. Ah, getting the infrastructure ready. Exactly. To succeed, the company needs everything in place. Intellectual property, physical assets, human capital, partnerships, often companies don't have all this internally. So after validating the business model, the next logical move is securing those missing pieces. How do they do that? Several ways. You can build resources internally, develop them from scratch. You can outsource certain functions or activities. You can acquire resources from third parties, maybe a licensed technology by a supplier. Or you can engage in strategic collaborations or partnerships. What kinds of resources are we talking about? Sounds like more than just factories and machines. Oh, it's much broader. Yes, it includes establishing the necessary business infrastructure, maybe new manufacturing facilities, customer service centers, IT systems. It also means developing reliable supply chains, recruiting and training employees with the right skills, gathering crucial knowledge or intellectual property, maybe even developing supporting products or services that form an ecosystem around the main offering. Like apps for a hardware device. Exactly. And critically, establishing the communication and distribution channels to reach the market and securing the ongoing capital needed to fund it all. It's comprehensive. Now, that decision about acquiring resources build internally versus partner externally, what seems like a huge strategic fork in the road, especially for something new? What are the pros and cons of collaboration here? I can't just be about speed, can it? You're right. It's a deeply strategic choice with major long-term consequences. Collaboration offers real benefits no doubt. It lets companies leverage external expertise they might lack internally. Tap into specialized knowledge. Right. It can increase cost efficiency through shared scale or infrastructure. It often requires a smaller up-front resource commitment than building everything yourself, which gives you more flexibility. And yes, it can definitely speed things up, getting access to capabilities faster than developing them internally, which is crucial in fast markets. Sounds good. What are the downsides? The risks. The drawbacks can be significant. You inevitably lose some degree of control over the process, maybe even the strategic direction. Relying too heavily on partners for core functions might weaken your own company's internal competencies over time, making you less innovative independently down the road. You're coming too dependent. Exactly. And a big one. Your partner, by working closely with you, might develop their own strategic capabilities, learn your secrets, and potentially emerge as a future competitor, especially if you're sharing sensitive IP or market knowledge. Ouch. The partner becomes the rival. It happens. So the strategic implications of build versus partner are immense. It affects your long-term competitive advantage, your IP security, your future agility. For a collaboration to make sense, the benefits really have to clearly outweigh these risks, and there needs to be clear reciprocal value for both parties. It's a calculated risk, not a simple outsourcing decision. Okay. So once the resources are secured, then comes the part where you actually develop the market offering itself, transforming that validated concept into the final product or service ready for launch. Yes, now you're building the thing. This is where you translate the refined concept, the advanced prototypes, into the actual market ready offering. This stage often involves even more advanced prototyping and final market testing beyond what happened in stage two. More testing. Why? The extent depends on novelty, complexity, and crucially how costly it would be to make changes after launch. Truly new to the world products usually need extensive real world testing, because the unknowns are still high, highly complex products, or things that require massive investment to change post launch, like retooling a car factory, demand incredibly rigorous final testing to catch any remaining flaws before you commit fully. You want maximum confidence at this point. What's fascinating here is the idea of the minimum viable offering or MVO. It sounds like a really agile way to get to market without betting the farm on the full bells and whistles version up front, but it feels counterintuitive, doesn't it? Making something minimum, what's the biggest hurdle for companies adopting that mindset? It is a key strategic choice at this stage, and you've hit the core tension. A company could aim to launch the ultimate fully featured version right out of the gate, packed with everything they envision, the perfect product, the perfect product, or they can start with a much simpler version, one that includes only the core functionality needed to deliver the primary customer benefits, solve the main problem, that's the MVO. The simplest version capable of delivering that core value. So what's the hurdle? Why not always launch the MVO? The biggest psychological barrier is Austin Turnell. It's the desire for perfection, the fear of launching something that feels incomplete. The worry that customers won't be impressed, or that competitors will point out missing features. Managers often push to add just one more feature, a bit more polished. Feature creep driven by fear. Often, yes, fear perceived imperfection. But the alternative building that full scale ultimate version immediately requires massive investment at a time when, frankly, market and technological uncertainties while reduced are still significant. You might still be wrong about some assumptions. Exactly. If your assumptions about certain features, or even the core viability, turn out to be incorrect after launch, you potentially wasted huge resources on things nobody valued, or built a complex product that needs major, costly rework. Learning with an MVO dramatically reduces that initial investment and risk, learn faster with less at stake, precisely. Get something into the hands of real customers, validate your core assumptions with real market data, learn quickly, and minimize potential losses if you've got something wrong. It's not about being cheap or lazy, it's about being strategically lean, agile, and data driven in the face of uncertainty. Okay, it makes sense. And that leads us finally to stage five, commercial deployment, launching and scaling, the culmination of all this work. It's the smart way to actually get the offering out into the market, just flip the switch everywhere. Rarely is a simultaneous global launch, the best approach, especially for something truly new. Commercial deployment has two main steps, informing target customers effectively and making the offering available. Because large scale rollouts are expensive and still carry risk, companies often start with selective market entry. So not everywhere at once. No, they test the waters, launch it a few carefully chosen markets, or target specific customer segments first, before going broad. Why do that? It lets you test the entire offering and business model in a real world natural environment. You can observe genuine customer responses, see how competitors really react, check if your collaborator, distributors, et cetera, are performing as expected. It keeps you agile, allows for final tweaks and adjustments based on real results before you commit to the much higher costs and complexities of a full rollout. Think of it as a final large scale validation phase with real money on the line. And how do you pick those initial markets or segments you mentioned low-hanging fruit? Who are they? Exactly. That initial group is often called the primary target. They are typically the low-hanging fruit, chosen carefully to achieve several goals. Prove the business model's viability in a real market, gather crucial feedback for final refinements, and generate that important initial revenue and buzz. The selection is usually guided by three key factors, first target attractiveness. How likely are customers in this segment or market to adopt the offering quickly and enthusiastically? You look for the path of least resistance. Who needs it most? Who gets it fastest? Right. Customers who clearly have the need, recognize it as a problem, and are maybe actively seeking a solution already. These are your ideal early adopters, often more open to new things, less risk-averse. Makes sense. Second factor. Efficiency. How easily and cost-effectively can your company actually reach and serve these customers? This is the path of least resources. Can we affordably market? to them, delivered to them. Exactly. Maybe target customers already familiar with your brand, or those reachable through existing sales channels, or geographically concentrated groups where marketing and logistics are simpler. Maximize impact with minimum waste. And the third factor. Scale sufficiency. Is this initial target market large enough to be meaningful from the company's perspective? This is the minimum viable target. Big enough to matter. Big enough to generate sufficient initial revenue to help offset costs. And, crucially, provide enough data and learning to validate your business model assumptions. It needs to be substantial enough to prove the concept works commercially. The sweet spot. The optimal primary target lies at the intersection of these three. Attractive, high need likely adopters efficient, easy to reach and serve, and sufficient, large enough to be meaningful. That initial launch isn't just about giving sales. It's a vital strategic learning phase that informs everything that comes next. And once that selective entry proves successful, then comes market expansion going broader. This sounds like it brings a whole new set of challenges. It absolutely does. It's the logical next step. But it's far from just turning up the volume. Market expansion means extending beyond that primary target to reach all the customers the offering was designed for. Scaling up everything. Everything. Scaling up production, launching broader marketing campaigns, building out comprehensive distribution to ensure wide availability. But the challenge is you're often moving into tougher territory now. How so? You might be targeting customers who are less aware of the need, harder to convince, more price sensitive, or maybe have different cultural preferences or usage habits than your early adopters. Reaching and converting these segments typically requires more time, more effort, and significantly more resources than the initial launch. So the strategy might need to change? Often. Yes. A crucial aspect is that broader markets usually mean more diverse customer needs. What worked for your initial niche might not work for everyone. This often necessitates a strategic shift from offering just a single product to developing a product line with variations tailored to different segments. Different versions for different folks. Exactly. Your initial MVO might have appealed to tech enthusiasts willing to pay a premium. Now you need to reach the mass market. That might mean a leaked version may be a lower price model with fewer features, or a pro version for power users, or maybe versions adapted for specific regions with different languages or regulatory requirements. That sounds complex to manage. It is. This strategic shift isn't trivial. It impacts R&D marketing messages, pricing, supply chain. Managing that increase complexity without deluding the brand or breaking the bank is a major challenge of the expansion phase. It tests the organization's ability to scale smartly. Right. Now a really important point through all these stages from the first idea to full market expansion is that this isn't usually a smooth straight line. Is it? Innovation rarely follows the plan perfectly. So that stage gate framework, it's not totally rigid. You have to be ready to adjust maybe even you turn. You've hit on a critical reality. While stage gate provides a valuable systematic structure, the actual process on the ground is rarely linear or seamless. It's fundamentally an iterative process. It involves discovery, learning, constant refinement. And that often means making course corrections along the way, what we call realignments and pivots, to keep steering towards a desirable, feasible, and viable offering based on the feedback and data you're gathering. So the neat stages are a map, but the journey might involve detours. Excellent analogy. The map is useful, essential even, but you need to be prepared to navigate unexpected terrain. The idea of just marching cleanly from stage one to stage five without setbacks or changes, that's mostly a myth and real innovation. You're constantly getting new information that challenges your initial plan. Okay, let's clarify those terms then. Realignments versus pivots, what's the difference between a small tweak and a major change of direction? Good distinction to make. Realignments are relatively minor, more tactical adjustments. You're modifying specific aspects of the offering of the plan, but the core value proposition, the fundamental direction remains intact. Like fine tuning. Exactly. Think about slightly changing the packaging design based on feedback, adjusting a price point up or down a bit, or maybe refining your targeting within the same broad market segment. Small course correction. Pivots are much bigger. They are major strategic changes that fundamentally revisit the project's foundation. You're significantly reshaping some or maybe even all the key elements. The original core idea, the target market, the value proposition, the technology approach, the business model itself. These are true strategic inflection points where you decide the original path isn't working and make a substantial shift in direction. A fundamental rethink. A fundamental rethink, yes. And given the high uncertainty in new offerings, both realignments and pivots are actually very common, more common than not probably. So hitting a roadblock isn't necessarily failure, it's an opportunity to adjust. That's the adaptive mindset. It's normal for a project to pass idea validation, but then struggling concept development. Maybe the prototype just doesn't resonate with users, or you might get further along, validate the concept and business model, but then hit a wall on stage four, perhaps you can't secure critical funding, or a key technology partner falls through. When these challenges hit, you must revisit earlier stages, reassess the validity of your assumptions based on the new reality, and potentially restart parts of the process, or make that realignment or pivot. It's this iterative looping back, this willingness to adapt, that actually increases the odds of success, even if the final success looks different from the initial vision. So being willing to pivot isn't weakness, it's resilience. It's a hallmark of resilient, adaptable innovation. It's smart management, recognizing reality, and adjusting course. And there's a really famous example of a strategic pivot that perfectly illustrates this. The story of Groupon, it really shows how crucial that adaptability can be. Oh, it's a fantastic case study. A true masterclass in pivoting. The company we now know as Groupon started life is something completely different. A platform called the point. The point. What was its point? Its point was fundraising. It was designed as a social media platform to help people organize collective action, specifically fundraising campaigns. It addressed a real problem. Donor hesitation. People are sometimes reluctant to donate if they think their small contribution won't make a difference, or if the campaign might fail. Right, the fear of wasting your donations. Exactly. So the point had a clever mechanism. It set a tipping point for each campaign. Donations would only be collected if the fundraising goal was actually met. This gave Donor's confidence that their money would only go towards a viable supported cause. That actually sounds like a pretty solid idea, addressing a real psychological barrier for Donors. So why didn't it work? What went wrong? Well, despite tackling what seemed like a valid customer problem with an innovative solution, the point just didn't gain significant traction as a fundraising platform. It struggled to get enough users, enough campaigns, enough momentum to reach those tipping points consistently. The core fundraising behavior wasn't scaling up as they'd hoped. So the original concept wasn't resonating enough in the market. But then, something unexpected started happening on the platform, an emergent use case. Precisely. This is where observation and adaptability became key. While the fundraising side was languishing, the team noticed a really interesting trend. A growing number of users were using the platform's tipping point feature for something totally different, something unintended. What were they doing? They were using it to organize group discounts. People were banding together saying, hey, if none of us commit to buying this pizza, this spa treatment, this product, can we get a discount? They were using the collective action mechanism, not for altruism, but for collective bargaining power to get deals. The most successful campaigns weren't fundraisers. They were group purchase efforts. Wow, so the users basically hacked the platform for a different purpose. Recognizing that, that takes real insight. And then acting on it, that takes courage to abandon your original vision. It meant courage and foresight. This is the pivot in action. The team saw this emergent behavior, realized where the actual energy and traction was on their platform and made a dramatic decision. They didn't just add a deals feature to the fundraising site. They fundamentally redefined their entire business model. How did they redefine it? They shifted their focus completely. Away from individual fundraisers and nonprofits, towards local business owners, restaurants, spas, retailers, they created a new value proposition, allowing these vendors to offer a steep discount, but only if a minimum number of people, the tipping point, signed up to buy it within a specific time frame. So the risk shifted. Exactly. For the vendor, it was brilliant. They got a guaranteed influx of new customers at the deal tipped, generating business. But if not enough people signed up, the deal didn't happen. No one was charged and the vendor owed nothing. It eliminated the risk of offering deep discount that nobody took advantage of. It was market validation, driving a completely new business model. And the rest is history. From the point, struggling fundraising platform to group on, the massive deal of the day company, it's an incredible story of adaptation. It really is. That strategic pivot transformed the company into group on, which became a multi billion dollar global phenomenon. It's such a powerful illustration that the true market value of your innovation might not lie in your initial grand plan, but an emergent use case, an unexpected customer behavior that you have to be agile and observant enough to recognize and seize. It underscores the power of that validated learning loop. Pay attention to what users actually do. Absolutely. Well, that brings us towards the end of this deep dive into developing new market offerings. We've really covered the whole journey, haven't we? From that initial idea spark, through all the stages of rigorous validation, designing the business model, sorting out resources, and finally, the strategic deployment into the market. We have. And I think the central thing that emerged is that success here isn't really about having a perfect linear plan, you just execute flawlessly. It's much more about embracing a systematic discipline, but also fundamentally iterative process. It's about constantly adapting to market feedback, proactively managing those inherent risks, and crucially, having the willingness to realign or even make those big pivots when the evidence tells you to. It's about building in those checks, those gates, and being ready to learn and change direction, seeing that not as failure, but as intelligent adaptation. Precisely. So what does all this mean for you listening in, as you think about the next potential big idea for your business, or maybe the next strategic initiative in your role? How can you apply these frameworks? And perhaps this raises a final important question to Ponder. How might truly embracing the iterative nature of innovation, that willingness to test assumptions relentlessly, to learn from failures, to realign tactics, or even to make a bold pivot based on market realities? How might that unlock unforeseen opportunities and perhaps completely redefine what success looks like for your next venture?