Product innovation in established orgs: new products, expansion and spin-offs

Established companies often reach a point where innovation becomes a must. Here’s how different business contexts can push you toward product innovation:

• Horizontal expansion: spotting a new use case that fits well with your existing product? Time to expand horizontally.
• Vertical expansion: launching a new product or edition aimed at a different segment, like moving from SMB-focused to enterprise solutions.
• Platform evolution: if your product is thriving, turning it into a platform can unlock even more potential.
• Tech adaptation: disruptive technologies, like Gen AI, can completely change your product’s experience.
• Diversification: when growth slows down, diversifying into new product areas can be a game-changer.
• Sequencing: sometimes, strategically building new capabilities is key – like how HubSpot developed their CRM to strengthen their core offerings.
• Internal pilots: a successful internal project or enterprise client solution can often evolve into a full-fledged product.

Here’s something I’ve learned over the years: launching new products in an established org isn’t like running a startup, nor is it just “business as usual.” It demands a different strategy, mindset, product focus and management style. And let’s be real – the odds are against you: 90% of these efforts fail on the first go. The challenge is turning that grim statistic in your favor.

The real blockers aren’t technical – they’re human. We all have biases and habits, and shifting from the familiar to the new is hard. From my own experience (and plenty of lessons learned), I decided to share what I’ve learned about navigating product innovation in established orgs. There are three key areas I’ll cover:

• Assessing your strategy and idea: how you, your stakeholders and your org should align before moving forward;
• Setting up the system for innovation: what it takes to create an environment where innovation can thrive (from mindset shifts to structuring your product team and resources);
• Your process and cadence: how to prioritize, iterate, measure, and communicate effectively as you bring your new product to life.

 Let’s get into it.

2. Assess Your Strategy and Idea (You, Stakeholders, Your Organization, Customers)

Innovation often kicks off with a strong belief in an idea, but rushing into product development can lead to skipping the fundamentals. It’s crucial to pause and challenge the core hypothesis: are your assumptions really worth testing? Success hinges on aligning your strategy, validating bold bets, and setting realistic expectations—starting with clear assumptions, commitment levels, and success metrics.

2.1 You & SHs: Core Underlying Hypothesis or Beliefs

Even seasoned teams can get caught up jumping straight into product hypotheses, MVPs, and product-market fit. The goal of innovation often feels obvious, so everyone rushes to figure out how to build and test it. But there’s a crucial step that’s easy to miss: questioning the higher-level hypothesis. Why does it even make sense for us to chase this new product or use case? There are usually three drivers behind this:

1. Feasibility (tech or process strength): confident your existing tech can be applied to a new use case?
2. Desirability (customer Insight): a hunch your customers have an unmet need closely tied to what you already offer?
3. Viability (business model): strong belief that proven growth tactics or channels could be extended?

Your job is to zero in on which of these drives your push and then find the fastest, cheapest way to test it. That might mean no product building at all. The right discovery – interviews, prototypes, simulations – could change your mind or even shift your whole strategy.

2.2. You & SHs: Level of Belief and Boldness of the Bet

In the beginning, everyone’s pumped – everything’s pink and rosy. But reality hits when expectations start drifting apart. To avoid this, you (as a product leader) need to align with stakeholders and decision-makers, all the way up to the CEO. That alignment defines your runway, resources, and how many tries you’ll get before people lose interest.

There are usually three attitudes:

• One of many hypotheses: your new product idea is just another experiment in the mix. Low commitment – if it fails, you move on.
• Opportunity exploration: you’re testing a potential growth area. There’s some excitement but also acceptance that it’s just an experiment – no hard feelings if it doesn’t work out.
• Strategy bet (“all in”): this is the big one. The company’s betting on it, and you’ve got the mandate to iterate and pivot until it works. The pressure’s real, but so are the resources.

2.3 You & SHs: Definition of Success

With various product innovation projects, I realized that the usual “one big goal” (one success metric) approach just doesn’t cut it for new product ventures. Instead, it’s better to think in terms of two levels: minimum and maximum success.

1. Max success: this is your "shoot-for-Mars" goal – the big and bold one. In business terms, it often boils down to top-line growth (more customers, more revenue) or bottom-line impact (better efficiency). But let’s be real – people tend to overestimate what they can achieve in the short to medium term. So, you also need a min success criteria.
2. Min success: the “land-on-the-Moon” scenario – less flashy, but still valuable. This could be both early customer adoption and signs of traction, as well as even less tangible things like learning that validates the direction, brand benefits (like increased loyalty or recognition). 

2.4. You & SHs: Time Horizon and Iterations

Another key alignment point – and one often dictated by everything I’ve already covered – is your time horizon and iteration cadence. You and your organization might have short-term (6 months or less), mid-term (1 year), or long-term (2 years and more) expectations horizon, and knowing that sets the pace for everything else:

1. Iteration limits: the timeline dictates how many tries you get to refine your value proposition;
2. Definition of done: short timelines may require lowering the bar for what counts as “done” in each iteration (especially compared to what you do in your core product org);
3. Hiring strategy: tight schedules demand people who deliver from day one. Longer timelines allow some room for growth and learning on the job (especially valid for hard skills).

2.5. Customers: How much you know them

One of the biggest traps in established product teams is the belief that you already know your customers well enough to make confident decisions for a new product. It’s an easy mistake to make – and a costly one.

If you’re targeting a completely new customer segment, it’s obvious that you need to do the homework. But when it’s a new use case for the same customers or a similar persona, the temptation is to rely on what you already “know.” That’s where the real danger lies. Those assumptions can lead you to skip discovery, thinking you’ve got it covered. In fact, you don’t, so don’t fall into that trap. 

2.6. Your Org: Superpowers

When launching a new product within an established organization, leveraging your existing superpowers is not just a good idea – it's a necessity. Unlike a startup that begins with nothing but a unique market insight or founder-market fit, your starting point in a larger organization must be your existing competitive advantages. These superpowers can make or break your success.

The reality is that large organizations come with inherent processes, constraints, and (sometimes) more relaxed environments (compared to startups) that can slow things down. So, if the new product isn’t anchored in a real superpower, these might outweigh any benefits. Consider these key types of superpowers:

1. Product & tech superpowers: existing product feature, platform, or technology that you can extend or repurpose;
2. GTM superpowers: proven marketing or sales channel that gives you an edge in reaching the market;
3. Talent & knowledge superpowers: your team’s deep expertise or specialized skills that would be hard to replicate.

The critical question is how decisive these superpowers are for your new product’s success. Sometimes, what seems like a strong asset might only be a bonus, not the core of your new idea. Your job is to make sure you’re betting on a superpower that truly matters for this new venture.

2.7 Your Org: Limitations – A Reality Check

Before diving into a new product within your established org, be real about the constraints you’ll face. These limitations will either guide your strategy or trip you up if ignored.

1. GTM: Channels and Customer Base: your existing channels and customer base might seem like the easy option, but don’t assume they’re the best fit;
2. Product & tech: if they are not your clear superpower, they could be holding you back with additional integration requirements and DoDs that don’t bring competitive power and don’t help building a moat around your new value prop;
3. Culture: how does your org handle risk? Keep in mind that innovation doesn’t thrive in zero-fault tolerance environments. Does your company lean toward deliberate planning, or is there room for a “let’s go try” approach? The cultural stance on innovation, along with what drives the company (revenue, user success), will dictate how much space your new product has to grow.

3. Setting up the the system for innovation

Creating an environment where innovation thrives in established organizations requires balancing entrepreneurial freedom with corporate strengths. The real challenge is ensuring new ideas aren’t stifled by traditional processes. It’s about finding the right structure, team, and resources while fostering a culture where risk-taking is encouraged and new projects become a strategic priority.

3.1. System: Defining the Right Model for Your Innovation Project

Selecting the right structure for a product innovation project in an established organization is crucial, as different models serve different purposes. Here is a quick overview alongside my notes on when each one is most applicable:

Org model

How It works

Best For

Not Good For

Innovation Team (Spin-Off)

A dedicated, cross-functional team operates mostly independently from the broader organization. They move fast, follow their own processes, and focus entirely on specific tasks. The trade-off is limited access to company-wide resources.

Products deeply aligned with the company’s strategy where a strategic, all-in bet is being placed.

Products that need significant organizational resources and extensive long-term support from entire org and can't be handled by a small cross-functional team

Distributed Innovation

Multiple departments across the company (product, engineering, go-to-market, operations) collaborate on a new product. After the initial launch, it transitions into “business as usual.” Suitable for projects that scale quickly and integrate smoothly.

Company-wide initiatives with a clear path to scale and integrate within existing processes after the MVP stage.

High-risk projects needing numerous iterations. Existing teams focused on mature products often struggle to manage new, fast-paced projects with different priorities.

Venture Studio

A corporate venture studio is like an internal incubator. It focuses on building and testing multiple new business ideas rapidly, using a repeatable process. It’s a structured approach to ideating, validating, and scaling concepts, often leveraging underutilized assets.

Situations with numerous ideas around a specific asset that need systematic exploration.

Generating product ideas from scratch without clear direction. The venture studio is primarily about validating numerous ideas or bets, not the ideation process itself.

Venture Fund

Instead of internal development, the company invests in external teams that build solutions aligned with its core offering. This allows external innovation without overwhelming internal resources.

Cases where internal expertise or bandwidth is lacking, and external innovation is needed to complement the product or ecosystem.

Internal projects that could be better handled with in-house resources or where close integration with internal teams is crucial from the start.

3.2. People: The Team You Need

When launching a new product in an established organization, you’ll almost certainly need talent that isn’t currently available in your org – or at least people you’re hesitant to pull from business-critical roles. And let’s face it - it must be tough (otherwise, you’re not hiring the right people). Here are the 2 angles I take to define the requirements for the product innovation team.

1. A-Players: These are people with obviously strong core skills (whether in product, engineering, or GTM), but most importantly they are quick learners, resilient, and flexible. They thrive in uncertain, high-stakes environments, where “doing it all” is the daily grind. In a healthy enterprise org you’d have a ratio of A players 1:4. In your initial product innovation team it should be at least reversed to 4:1. That’s tough, but any tradeoffs made at this stage diminish your success chances dramatically. 
2. Mixed generalist background:
3. Product: Ideally, they’re at the intersection of tech, human behavior, and business. You want at least two of these in their DNA.
4. Engineering: Senior generalists first with architect-like thinking. You might need niche experts, but only if that’s truly core to your tech.
5. GTM: Product-savvy and with experience outside the usual corporate comfort zone – they’ll need to operate without the usual safety nets.

3.3. People: hiring process

Given the importance of adaptability and learning in new products and product innovation, focus your recruitment process on evaluating how candidates respond to feedback and adapt their thinking when presented with new insights. One of the most effective methods I’ve used is an iterative case discussion tied to real or analogous scenarios from your product domain.

1. Iterative case studies: engage candidates in multiple rounds of case development, offering feedback in a coaching style and introducing new information or arguments along the way. The goal is to assess how they transform their perspectives based on new inputs and insights.
2. Creative solutions and right questions: whether it’s for product, design, engineering, or GTM roles, prioritize candidates who can generate creative solutions in a new environment. The case should revolve around domain analysis, identifying key inputs, and generating relevant solutions.
3. Current cases, not past experiences: ensure the scenarios are aligned with your current challenges rather than relying solely on the candidate’s distant past experiences, which may have occurred in very different circumstances. Gauge how they perform outside their experience zone. However, stay aware of your own biases about what you consider the “right answers” –  focus on their thought process and adaptability rather than looking for a specific perspective.

3.4. Culture: Mindset Shift

Launching a new product in an established company requires a serious mindset shift, especially in how you approach risk. Big orgs have ingrained ways of thinking that work for scaling existing products but can backfire in new ventures. Here are the typical cultural biases:

1. ‘Minimize risk’ mentality: Large companies are built to analyze every detail and avoid all kinds of risks – reputational, product issues, you name it. But when launching something new, this approach needs to be toned down. Excessive caution kills the agility you need at this stage.
2. ‘Reduce waste’ mentality: Efficiency and cutting waste are great once you’re scaling. But early on, optimizing processes isn’t the priority. The focus should be finding product-market fit, talking to customers, and running as many tests as possible – fast.
3. Reliance on existing resources: Established orgs are used to leaning on their built-in capabilities – finance, marketing, engineering. But for a new product, this can be a trap. Often, the skills you need aren’t fully there, and relying on in-house resources can drag you down. Sometimes, bringing in external help – consultants, part-timers – is the smarter move.
4. "Can do it" mentality: there’s a strong belief in large orgs that with the right tactics, success is inevitable. But in a venture setting, you need to be more tolerant of failure and ready to pivot. The goal is to learn fast and adapt, not stubbornly stick to a plan when uncertainty is sky-high.

3.5. Culture: Increased Tension

Creating a high level of tension is crucial when driving product innovation in an established organization. Without startup-like pressure, the project’s survival chances drop sharply. Key elements of the :

1. high-bar expectations: overall expectations should be set high, and a product leader should especially be the bar raiser for the team;
2. external deadlines: fixed, externally imposed deadlines (like events or any sort of public commitments) push for execution speed;
3. limited financial runway: pre-set budget constraints and clear milestone-linked funding decisions enforce focus;
4. team disbandment: the understanding that the project is time-limited and that the team could be dissolved if key milestones aren’t met keeps everyone on their toes;
5. compensation structure: align incentives with product success. Consider performance-based bonuses or equity tied directly to this product – especially if the broader org doesn’t follow such practices.

Together, these strategies help cultivate a distinct subculture – one of intrapreneurship – that may stand apart from the more relaxed (in a good way) or stable environment of the broader organization.

3.6. Resources: Examine Your Shared Resources

When building something new within an established org, it’s obviously the right thing to lean on existing resources. But here’s the catch: those resources might not be built to handle your unique challenges. A few points to keep in mind:

1. Goal alignment is key: don’t assume shared resources will automatically fit your needs. You need to align your objectives with those of the teams you’ll be working with. If their OKRs don’t reflect your product’s success, you’re setting yourself up for friction.
2. When shared resources work: if your org has centralized teams (e.g., user research, design, DevOps) that operate in a service model, supporting various products, leverage that. They’re used to juggling diverse challenges and can adapt to the specific needs of your project.
3. When they don’t: If these teams are mostly tied up with maintaining the core product, they’re less likely to give your innovation the focus it needs. When they’re focused on established processes, supporting something experimental can be a stretch.

3.7. Resources: Examine Your Shared Resources

When working on product innovation, especially within established organizations, leveraging external expertise is crucial. It’s not always feasible or timely to bring in all the necessary skills in-house full-time. While your core product team(s) may lack experience with the unique challenges of a new product or domain. That's where external resources come into play –  either consultants, partners, contractors or just peers that can advise. Here’s my advice to get it right:

1. Be deliberate in your search: finding the right external partner takes time and focus. You need capacity for this – treat it as a core task, not an afterthought.
2. Know what you need before you ask: don’t engage external help until you’ve gotten your hands dirty and run into specific challenges. When you approach experts with well-defined problems, you get much more value out of their input.
3. Relevance is everything: look for people who’ve solved exactly what you’re dealing with in a similar environment. This isn’t about general expertise; it’s about context-specific knowledge that’s directly applicable to your situation.

4. Your product processes

Execution is where many innovation efforts falter. Established products have clear processes and metrics, but new ventures demand different priorities and faster iterations. The challenge lies in balancing lean testing with strategic alignment and measurable impact. Prioritizing problems, leveraging customer insights, iterating effectively, and tailoring your metrics are key to staying on track while navigating uncertainty.

4.1. Prioritization: Right Customer Problems to Focus

Prioritizing which customer problems to tackle in a new product isn’t business as usual. When running an established product, you're typically focused on improving specific metrics or hitting strategic targets. But in a new venture, those playbooks don’t quite fit – your goals are more independent, and reliable metrics can be elusive, volatile and hardly measurable. Here’s the way I approach it, through three prioritization lenses:

1. Proof: First, filter everything through the “proof” lens. What’s going to confirm or disprove your core product-market fit hypothesis? Prioritize the use cases that make or break your product’s feasibility, desirability and viability.

2. Sufficient Value: Next up is the “sufficient value” lens.

1. If you’re building a standalone product, the focus is simple: what will convince early adopters to pay (“minimum sellable product”)? 
2. For embedded products (features), it’s about users building habits – daily, weekly, at least monthly. Anything that doesn’t help hit this habit threshold is a distraction you rather skip for now.

3. Utilize Your Superpowers: Finally, put on the “superpower” lens. In an “intrapreneurship” environment, if you’re not leveraging what your company does exceptionally well, why are you even trying this internally? Prioritize use cases that tap into those unique strengths – this is what justifies doing the innovation in-house.

4.2. Customer Voice: Access to Customers As a Superpower

In launching a new product, your established customer base is your biggest asset; actually, it could be your real superpower in the terms we discussed above. Unlike a startup starting from scratch, you have a direct line to customers who are already engaged with your brand. Here’s my advice here:

1. Leverage these existing relationships to get the feedback you need faster and more accurately. 
2. Don’t bypass product discovery just because you think you know your customers well enough. Instead, use this opportunity to deepen your understanding and turn it into a shortcut available only to you.

4.3. Iteration: Lean and Precise Execution

When driving innovation, especially within an established org, jumping straight into building a product (MVP, MVP 2.0, etc.) is a costly mistake. Your main focus should be testing and validating hypotheses around product-market fit. And you can achieve this without heavy commitments.

1. Prototype instead of MVP: Prototypes should be your go-to over full MVPs. Whether it’s a lightweight model using a no-code tool, an Excel simulation, a visual mockup, or even leveraging a competitor’s product, the goal is quick validation with minimal effort and cost. Prioritize options that give you quick learnings without unnecessary development.
2. Adapt your Definition of Done (DoD): Your DoD for new products often could be stripped down compared to what’s used for the core products. Mature products focus on robustness, scalability, and efficiency. In contrast, your focus now is validating core assumptions. Many typical DoD criteria would just slow you down and add needless complexity. Only include what’s directly tied to learning and iterating rapidly.

4.4. Measurement: Tailoring Metrics for Innovation

Measuring new product success within an established organization requires a shift. The usual metrics and OKRs won’t fully capture your progress here. Focus on three key categories:

1. Traction MetricsDon’t rely on absolute numbers, which are often lagging indicators. Instead, use metrics that show relative growth and penetration, such as:
2. Customer-base penetration: How many customers have adopted the product?
3. Channel penetration: How many sales execs or partners have the product in their pipeline or have closed deals with it?

These metrics are critical because new products often rely on existing channels and customers, which can both be an advantage and a constraint. Tracking penetration helps you see how well the product is being adopted within your defined segments.

1. Learning Metrics. Early-stage success isn’t just about revenue – it’s also about insights. Measure your success by proving hypothesis on product feasibility, desirability and viability. These learnings are vital because they inform your path toward product-market fit.
2. End Business Outcomes. Ultimately, you’ll need to measure business impact:
3. Top-line revenue growth: Is the product contributing to overall revenue?
4. Bottom-line impact: Are there measurable improvements in profitability?
5. Portfolio share: How much of the company’s revenue is driven by this new product?

While these metrics are important, remember they’re usually lagging indicators.

4.5. Communication: Overcommunicate for Success

Clear communication is crucial for any product leader, but for those driving innovation, it becomes critically essential: overcommunicate. Communicate often, then communicate more.

Your messaging should cover vision, strategy, plans, and goals for different audiences:

1. Customers: Engage current and potential customers early. If your existing users overlap with the target audience for your new product, get them on board as early adopters willing to volunteer feedback.
2. C-level: secure ongoing buy-in from leadership while staying aligned with their strategic goals. Your project must remain connected to the broader organization to avoid drifting out of focus.
3. Teams: cross-functional teams need to be fully aligned with your objectives. Unlike established products, support functions might not automatically back your new project, making it your responsibility to keep everyone informed and inspired.

Isolation is your enemy – overcommunicating ensures your project remains integrated and relevant. Everyone involved should be informed and excited; this is critical to your success.

Conclusion & Further Reading

Navigating product innovation within an established organization comes with its own unique challenges, but a few key principles can help set you up for success:

1. Start with a solid strategic hypothesis: before jumping into product development, take a step back and validate the core assumptions driving your new product idea. Often, you can gain crucial insights without even building a thing, allowing you to pivot or refine your approach early on.
2. Lean into your org’s superpowers, but stay realistic: your organization’s strengths – whether it’s tech, market reach, or talent – can be a significant advantage. But don’t assume existing resources will automatically align with your innovation goals. Be clear about where your company’s strengths will truly help and where they might hold you back.
3. Tailor your process and metrics for innovation: standard processes and metrics won’t cut it. Focus on lean, rapid iterations and prototypes, and measure success differently – prioritize early traction, valuable learnings, and long-term business impact. And remember, consistent and clear communication across all levels is critical to keeping your project moving forward.

If you’re looking to explore these ideas further, here are a few books I’ve found super relevant for product leaders tackling innovation in established companies:

1. Profit from the Core (by Chris Zook): a sharp look at how sticking to your core strengths is key when expanding or innovating – just like leveraging those organizational superpowers we talked about.
2. Unstoppable (by Chris Zook and James Allen): a great read on pushing through barriers and aligning growth strategies with innovation – right in line with the mindset shifts we discussed.
3. Dual Transformation: How to Reposition Today’s Business While Creating the Future (by Scott D. Anthony and others) guides established products and companies on balancing the present while creating future opportunities, echoing the dual focus on existing strengths and new bets.
4. Empowered: Ordinary People, Extraordinary Products (by Marty Cagan and Chris Jones): an inspiring take on empowering product teams to own innovation and make things happen – exactly the kind of culture shift that’s essential for intrapreneurship.
5. Corporate Explorer (by Andrew Binns and others): this one’s all about building new ventures from within and fostering that entrepreneurial spirit inside larger organizations – something crucial if you’re setting up a spin-off or internal innovation project.