Over the past few months, we’ve been exploring how fragmented systems and disconnected workflows slow product development and introduce unnecessary risk. More recently, we looked at where that friction actually lives. Not in the stage-gate process itself, but in the systems that support it.
That raises a more practical question: If system interfaces are the source of friction, what is sustaining that fragmentation?
In many organizations, the answer is surprisingly consistent. Spreadsheets.
Why Spreadsheet-driven Product Development Persists
Spreadsheets are not inherently the problem. They are flexible, familiar and fast. Teams rely on them to bridge gaps between systems, track decisions and maintain control when other tools fall short.
In the absence of fully connected workflows, spreadsheets become the default layer for:
- Aggregating formulation and specification data
- Tracking changes across versions
- Coordinating inputs from suppliers and internal teams
- Supporting regulatory and labeling checks
In short, spreadsheets become the operational glue that holds the process together. The same flexibility that makes spreadsheets valuable also makes them difficult to control at scale.
Where Control Breaks Down
Spreadsheets create the appearance of control. Most teams never chose spreadsheets, they inherited spreadsheet-based workflows built over time.
In practice, spreadsheets often degrade control:
- Multiple versions exist without clear ownership
- Data is copied, modified and re-entered across files
- Approval decisions are tracked informally or not at all
- Critical assumptions are not visible outside the immediate team
At each stage of development, teams rely on these files to make decisions. But as products move forward, the underlying data becomes harder to trace and validate. What begins as a simple workaround becomes a structural dependency.
See how leading teams replace spreadsheet-driven product development with integrated workflows
Version Control Is Not Governance
Version control is often treated as a substitute for governance. If the latest file is labeled correctly, the assumption is that the information is current and aligned. But version control does not answer critical questions:
- Is this the validated formulation?
- Does this specification reflect the latest regulatory inputs?
- Have all changes been reviewed and approved across functions?
- Can this decision be defended if challenged?
Without clear answers, teams are forced back into manual validation. Files are reviewed again. Data is rechecked. Assumptions are confirmed. And the cycle repeats.
The Hidden Cost of the Spreadsheet Layer
This reliance creates a familiar pattern:
- Decisions are delayed while teams reconcile versions
- Rework increases as inconsistencies surface
- Approvals slow due to lack of traceability
- Confidence declines across R&D, QA and Regulatory
These are not isolated issues. These are symptoms of a system that relies on manual coordination to function. In an environment where regulatory scrutiny is increasing and product requirements are more complex, that dependency becomes harder to sustain. As a result, teams are forced into repeated validation cycles that delay execution and increase the likelihood of late-stage rework.
What Leading Teams Are Changing
Leading organizations are not eliminating spreadsheets entirely.
They are deliberately removing spreadsheets from critical workflows and shifting toward:
- Centralized data environments where formulation, specification and compliance information align
- Structured workflows that capture decisions and approvals in context
- Real-time visibility across functions, reducing the need for manual reconciliation
The objective is not to remove flexibility. It is to ensure that flexibility does not come at the expense of control.
What Comes Next
If spreadsheets are sustaining fragmentation, the next challenge becomes clear: How do teams move from manually coordinated workflows to connected systems that support faster, more confident execution?
In our next discussion, we’ll explore how organizations are making that shift and what it takes to move from isolated tools to integrated product development workflows.
See how leading teams are moving away from spreadsheet-driven product development.
Read our eBook, The Product Development Leader’s Guide to Digital Integration, to see how to reduce late-stage surprises and move faster with confidence.
