Sep 29, 2026 · All Things Product with Teresa and Petra · 5 min read

Redefining Innovation: Customer Value Over Novelty

This executive brief challenges the corporate obsession with novelty, arguing that true innovation is defined by solving customer problems effectively rather than introducing complex new features. It highlights the cognitive costs of forced novelty and the strategic value of cross-functional collaboration in identifying viable solutions.

Product Management Business Strategy Innovation

The takeaways

Prioritize Problem Solving Over Novelty. Shift organizational goals from achieving novelty to solving customer problems effectively. Novel solutions are only valuable if they serve the user better than existing patterns.
Account for User Cognitive Costs. Evaluate the mental burden of new features on users. Complex innovations often introduce friction that outweighs long-term benefits, especially for non-technical audiences.
Leverage Cross-Functional Collaboration. Foster deep collaboration between product, engineering, and design teams. The most viable innovations often emerge from technical feasibility discussions rather than top-down mandates.
Accept Pedestrian Solutions When Effective. Do not force innovation on established user patterns if they already solve the problem well. Simplicity and familiarity are often more valuable than disruptive change.
Distinguish Internal vs External Value. Recognize that technical innovations may benefit internal operations without impacting the user experience. Ensure that external-facing changes directly address user needs.
Use Novelty for Strategic Differentiation. Deploy novel features strategically to differentiate from competitors when they genuinely improve the customer experience. Novelty should be a tool for value, not the goal itself.

The Misalignment of Innovation Goals

Corporate culture often conflates innovation with novelty, creating a strategic misalignment that prioritizes complex, new features over effective problem-solving. This episode argues that the primary objective of product development should be serving the customer, not achieving a novel status. When organizations fixate on novelty, they risk introducing unnecessary complexity that increases user friction and cognitive load, ultimately degrading the customer experience.

The Cost of Forced Novelty

A key insight is that novelty carries a hidden cost: the mental burden on users to learn new flows. For example, while magic links were initially an innovative improvement over traditional logins, they introduced friction for users relying on password managers. This illustrates that an innovative solution can become obsolete or detrimental as user behaviors and tools evolve. The goal is not to reinvent the wheel, but to remove friction. If a standard pattern works, it should be retained. Innovation is only valuable when it solves a specific customer problem more effectively than existing alternatives.

Strategic Implications for Product Teams

Product leaders must distinguish between internal technical innovations and external user-facing changes. Technical upgrades may improve code maintainability or performance without altering the user interface, which is a valid form of innovation but does not require user education. Conversely, user-facing changes must be justified by clear value propositions. Cross-functional collaboration is critical here; engineers often identify "just now possible" solutions that are technically feasible and user-friendly, whereas isolated product teams may propose novel ideas that are impractical or overly complex.

Conclusion

To drive sustainable growth, companies should redefine innovation as the effective resolution of customer problems. This approach encourages teams to challenge assumptions and explore boundaries without being trapped by the need for novelty. By focusing on simplicity, reducing cognitive load, and leveraging cross-functional insights, organizations can deliver products that are both innovative and genuinely useful, ensuring that differentiation is driven by value rather than complexity.

Key insights

Innovation is often misdefined as novelty, leading to complex solutions that do not necessarily serve the customer better. The true goal is solving customer problems, with novelty being a potential means rather than the end.

Strategy →

Impact: Aligns product development with customer value, reducing wasted resources on features that do not improve user experience.
Novel solutions impose cognitive costs on users, requiring them to learn new flows. This friction can outweigh the benefits of innovation, especially for mainstream users.

User Experience →

Impact: Encourages a more empathetic approach to product design, prioritizing ease of use over technological novelty.
Cross-functional teams are more likely to produce viable innovations because they combine user insights with technical feasibility. Engineers often identify solutions that are both novel and practical.

Team Dynamics →

Impact: Improves the quality of product decisions by integrating diverse perspectives and reducing the risk of impractical features.
Standard patterns should be retained if they effectively solve the user's problem. Forcing innovation on established workflows can degrade the user experience without adding value.

Product Design →

Impact: Reduces unnecessary changes and maintains user trust by respecting established mental models and habits.
Technical innovations that do not impact the user interface are still valuable for internal efficiency but should not be marketed as user-facing innovations. Distinguishing between internal and external value is crucial for clear communication.

Communication →

Impact: Prevents misleading marketing claims and ensures that stakeholders understand the true scope and impact of product changes.

Action items

Reframe innovation goals in product roadmaps to focus on solving specific customer problems rather than achieving novelty. Define success metrics based on user outcomes, not feature uniqueness.

Impact: Shifts team focus toward value delivery, reducing the risk of developing features that do not resonate with users.
Conduct cognitive load assessments for new features to evaluate the mental burden on users. If a new flow requires significant learning, ensure it provides substantial value to justify the cost.

Impact: Improves user adoption rates by minimizing friction and ensuring that innovations are worth the effort required to use them.
Implement regular cross-functional workshops where product, engineering, and design teams collaborate on problem-solving. Encourage engineers to propose solutions based on technical feasibility and user needs.

Impact: Enhances the quality of product ideas by leveraging diverse expertise and ensuring that innovations are both practical and user-centric.
Audit existing product features to identify areas where standard patterns are being unnecessarily replaced by novel solutions. Revert to simpler, proven patterns if they meet user needs effectively.

Impact: Reduces complexity and improves user satisfaction by removing unnecessary changes that do not add value.
Develop clear communication guidelines for internal and external innovations. Ensure that marketing and sales teams accurately represent the scope and impact of product changes to stakeholders and customers.

Impact: Builds trust with customers and stakeholders by providing transparent and accurate information about product capabilities and improvements.

Quotes

“Our job is to make the login process as easy as possible for our customers.”

“Innovation is only valuable if it solves the customer problem.”

“I'd rather we help companies be better at solving customer problems.”