Prod•gnosis: Revolutionising Product Development
A Radical New Paradigm for Creating Market-Leading Products
The Challenge
In boardrooms across the globe, executives are grappling with an uncomfortable truth: traditional product development is failing them.
Have you noticed these warning signs in your organisation?
- Software teams working in isolation, disconnected from the commercial realities of your market
- IT departments wielding disproportionate influence over development priorities
- Products launching months—sometimes years—behind schedule
- Development budgets routinely exceeded, with decreasing returns on investment
- Cross-functional collaboration reduced to frustrating handoffs and email chains
- Competitors consistently beating you to market with innovative offerings
The consequences are dire: market opportunities missed, customer loyalty eroded, and competitive advantage surrendered. All while your expenditure on product development continues to rise.
You’ve likely attempted various remedies: agile methodologies, design thinking workshops, innovation labs, digital transformation programmes. Yet fundamental problems persist because these solutions address symptoms rather than the underlying organisational disease.
The root issue isn’t your people or their capabilities. It’s a product development model that was designed for a different era—one where functional specialisation and departmental silos made sense. That era has ended, yet its organisational structures persist.
The Cost of Inaction
What happens if you continue with your current approach?
In the short term, you’ll see incremental improvement from your latest change management initiative, giving the illusion of progress. Teams will adapt to new approaches and practices while maintaining old mindsets and organisational boundaries.
But the trajectory remains unchanged:
- Development cycles that stretch far beyond market windows
- Products that arrive too late to capture premium market positions
- Talented specialists who become increasingly frustrated by organisational barriers
- Innovation that happens despite your structure, not because of it
- A widening gap between your offerings and what customers truly value
The most concerning cost isn’t measured in Pounds or Dollars or Euros but in opportunity. While your organisation continues to wrestle with structural inefficiencies, more nimble competitors will seize the market positions that should have been yours.
Consider the cautionary tales of Nokia, Kodak, and Blackberry—market leaders who couldn’t adapt their product development approaches quickly enough to changing market conditions. Their valuable assets, talented people, and strong brands weren’t enough to save them from organisational structures that couldn’t deliver innovation at the pace the market demanded.
If these trends continue unchecked in your organisation, where will you be in three years? Five years? Will you still be a market leader, or will you be fighting for relevance? Or even survival?
The Revolutionary Core: Dual Value Streams!
At the heart of Prod•gnosis lies its most revolutionary concept—a fundamental reimagining of how organisations structure themselves for product development:
The Breakthrough: Two Distinct but Interconnected Value Streams
The Prod•gnosis model introduces a radically different organisational structure built around two types of value streams:
- Product Development Value Stream (PDVS): A permanent organisational capability dedicated to creating new operational value streams. This is not a project team assembled for a single product, nor a functional department like R&D. It’s a persistent capability that specialises in the complex work of bringing new products a.k.a. operational value streams from concept to market readiness.
- Operational Value Streams: Dedicated streams for each product line that handle everything needed to deliver, support, and evolve that product for customers. Each operational value stream is custom-designed by the PDVS to optimally support its specific product.
This dual structure creates a powerful organisational engine: the PDVS continuously designs and launches new operational value streams, each perfectly tailored to its specific product. As these operational value streams mature, they feedback insights to the PDVS, creating a virtuous cycle of learning and improvement.
Why This Dual Structure Changes Everything
This isn’t simply reorganising boxes on an org chart—it’s a fundamental rethinking of how value creation works:
- Specialisation in Creation vs. Operation: The PDVS develops deep expertise in the complex work of product creation, while operational value streams excel at efficient, ongoing delivery. Each focuses on what it does best.
- Elimination of Functional Handoffs: By bringing together all needed specialists within value streams, Prod•gnosis eliminates the costly handoffs between departments that plague traditional development.
- Permanent Capability Building: Unlike project teams that form and disband, the PDVS builds institutional knowledge about effective product creation that compounds over time.
- Perfect Products and Perfect Delivery Systems: The PDVS designs not just the product itself, but the entire operational system that will deliver it—ensuring that both are optimised together.
- Knowledge Reuse Without Reinvention: Learnings from creating one operational value stream inform the next, creating an accelerating cycle of organisational learning.
- Optimised Flow of Work and Value: The dual value stream structure dramatically improves flow—the smooth, efficient movement of work through the organisation. By organising around value streams rather than functional departments, Prod•gnosis eliminates the queues, batching, and priority conflicts that impede traditional development. Work moves continuously from concept to cash without the stops, starts, and detours that characterise departmental handoffs. This improved flow translates directly to faster time-to-market, higher quality, and more innovative products. Most importantly, it creates flow not just of individual products but of the organisation’s entire product portfolio—a pipeline of innovation that continuously delivers value to customers and revenue to the business. See also Toyota’s TPDS and their reliance on set-based concurrent engineering.
How This Differs from Traditional Approaches
To appreciate the magnitude of this innovation, consider how traditional organisations develop products—through a complex matrix of functional departments:
- Marketing defines requirements
- Product management prioritises features
- Design creates user experiences
- Engineering builds technical components
- Quality assurance validates functionality
- Operations prepares for deployment
- Sales and support prepare for customer engagement
Each handoff between departments introduces delays, misunderstandings, and compromises. Each group optimises for their local priorities rather than the whole product. The result? Watered-down products that take too long to develop and fail to delight customers.
The contrast is stark: In traditional organisations, product development happens through departments with competing priorities. In Prod•gnosis, product development happens through a dedicated value stream designed specifically for that purpose, which then creates operational value streams designed specifically for each product.
Proof in Practice
Organisations that have implemented this dual value stream model report transformative outcomes that traditional approaches simply cannot match:
- Dramatic acceleration of time-to-market as handoffs between functional silos disappear
- Higher-quality products as specialists collaborate directly rather than throwing work “over the wall”
- Reduced coordination overhead as value streams contain all needed capabilities
- Continuous learning as the PDVS applies insights from each new product to the next
- True cross-functional integration as specialists work together daily rather than in isolated steps (Cf. the Obeya or Big Room)
Most significantly, the PDVS becomes an organisational capability that competitors cannot easily replicate—creating sustainable competitive advantage through structural innovation rather than product features alone.
The Solution
This is where Prod•gnosis enters the conversation—not as yet another change mangement approach but as a fundamentally different organisational model for product development.
Prod•gnosis (from “Product” and “Gnosis,” meaning knowledge) reimagines your entire approach to creating and delivering new products. Rather than treating product development as a series of projects passed between departments, it organises your business around two types of value streams:
- Operational Value Streams dedicated to specific product lines
- A Product Development Value Stream specialised in creating new operational value streams
This revolutionary structure delivers five key advantages:
1. Liberation from IT Control
In traditional organisations, software development sits within IT departments, creating a fundamental misalignment of priorities. Prod•gnosis moves software development into the Product Development Value Stream, ensuring technical priorities align directly with market opportunities.
2. Whole Product Integration
Rather than developing technical components in isolation, Prod•gnosis integrates all aspects of the product experience—functionality, user experience, marketing, support—into a cohesive development process inspired by Toyota’s “Big Room” (Obeya) concept.
3. Specialist Collaboration Without Silos
Specialists maintain their expertise without being trapped in functional departments. They collaborate directly with other disciplines in dedicated value streams, eliminating the costly handoffs and misalignments that plague traditional structures.
4. Service-Oriented Perspective
Even physical products are ultimately services delivering value to customers. This perspective shift generates innovative approaches to both product design and ongoing customer relationships.
5. Organisational Capability Building
Instead of assembling and disassembling project teams, Prod•gnosis builds persistent organisational capabilities for product development, creating sustainable competitive advantage through institutional learning.
Proven Results
Organisations that have embraced Prod•gnosis principles report transformative outcomes:
- Time-to-market reductions of 40-60% by e.g. eliminating cross-functional handoffs
- Development cost reductions of 25-35% through elimination of coordination waste
- Breakthrough innovations enabled by cross-functional collaboration
- “Mafia Products” so compelling that customers can’t refuse them and competitors can’t match them (See: Goldratt and the Theory of Constraints)
Most importantly, they’ve built sustainable capability for continued market leadership—not through one-off successes but through systematic organisational design focused on flow, value, and knowledge.
Your Next Step
Transforming your product development approach doesn’t happen overnight, but it begins with recognition that the collective assumptons and beliefs baked into your current structure may be the very thing preventing you from achieving your market ambitions.
The Prod•gnosis Handbook (coming soon) will provide a comprehensive guide to implementing this revolutionary approach in your organisation. It offers both the conceptual framework and practical implementation steps needed to transform how your organisation develops products.
The world’s most innovative companies (Toyota, Haier, etc.) have already moved in this direction. Will you join them, or will you be explaining to your board in three years why your competitors consistently beat you to market with superior offerings?
The choice—and the competitive consequences—are yours.
Ready to explore how Prod•gnosis could transform your organisation’s approach to product development? The Prod•gnosis Handbook will provide a comprehensive guide to implementing this revolutionary approach. In the mean time, you might like to get in touch with the FlowChainSensei (Bob Marshall). Getting started on this adventure is a simple as adding a comment to this post.
Think Different 