Two-Sided Technology Roadmap Flywheel
Coordinate infrastructure and products so each side accelerates the other
- Difficulty
- Advanced
- Time to result
- ~ongoing to results
- Steps
- 5
- Confidence
- 90%
The Two-Sided Technology Roadmap Flywheel coordinates development across an enabling infrastructure layer and the products customers use. Participation in infrastructure provides early knowledge of upcoming standards, constraints, and capabilities. Product teams translate that knowledge into devices or applications ready to exploit the infrastructure as it arrives. Usage from those products then reveals which infrastructure improvements matter most, informing the next development cycle. Huawei applied this mechanism by making carrier networking equipment while also building handsets, allowing its consumer products to adopt 3G, 4G, Android, and later technologies early. The advantage is not integration for its own sake; it is faster information flow and synchronized execution across dependent layers. The model requires strong roadmapping because the layers may have different customers, sales cycles, regulations, and economic incentives.
Origin
Huawei expanded from carrier networking equipment into handsets and used knowledge from both sides of telecommunications to coordinate infrastructure and consumer-device innovation.
Core principles
- 01Treat adjacent layers of the technology stack as one innovation system
- 02Use infrastructure knowledge to anticipate product capabilities
- 03Use product adoption to increase the value of infrastructure investment
- 04Coordinate roadmaps without ignoring the needs of external customers
How to run it
- 1
Map the dependency chain
Document how infrastructure, standards, components, products, and customer behavior depend on one another. Identify where coordination delays prevent value from reaching users.
Pro tip Focus on dependencies that repeatedly create chicken-and-egg adoption problems.
Watch out Do not integrate adjacent businesses merely because they are technically related.
- 2
Choose the strategic second side
Select the adjacent layer that provides the most valuable early information or control over adoption. Decide whether to build, acquire, or form a deep partnership.
Pro tip Prioritize information advantages and roadmap influence over superficial revenue synergies.
Watch out Owning too many layers can dilute focus and alienate customers who compete in one of them.
- 3
Create a shared roadmap
Coordinate milestones across both layers so products are ready when new enabling capabilities become available. Give teams visibility into standards, constraints, and launch timing.
Pro tip Maintain explicit dependency milestones rather than separate roadmaps linked only by meetings.
Watch out A delay on one side can strand investment on the other.
- 4
Translate capability into products early
Design products that make practical use of emerging infrastructure before competitors can respond. Communicate the customer benefit rather than merely advertising technical novelty.
Pro tip Prototype against pre-release infrastructure whenever standards and regulations permit.
Watch out Being early has little value if coverage, reliability, or customer demand is insufficient.
- 5
Feed usage back across the stack
Use product adoption and behavior to determine which infrastructure capabilities deserve further investment. Continue cycling information between both sides.
Pro tip Create shared metrics that connect infrastructure performance to end-user outcomes.
Watch out Internal products should not become the only source of feedback if the infrastructure serves a broader ecosystem.
In the wild
Huawei developed telecommunications infrastructure while expanding into consumer handsets. Its knowledge of carrier standards and upcoming network capabilities helped it introduce products early for 3G, 4G, Android, and later generations, while handset experience informed how network capabilities would be used.
→ Huawei became both the largest telecom-equipment manufacturer and the second-largest handset manufacturer by global shipments.
A grid-management company builds a connected home battery alongside its utility software. Knowledge of upcoming demand-response programs shapes the battery roadmap, while household usage data shows utilities when and how distributed storage can stabilize the grid.
→ Both products improve faster because infrastructure planning and user behavior inform one another.
Common mistakes
Integrating without an information edge
Owning two layers adds complexity unless knowledge or control from one side materially improves decisions on the other.
Ignoring channel conflict
Infrastructure customers may distrust a supplier that also competes with them or their partners in an adjacent layer.
Shipping before the ecosystem is ready
An advanced product can disappoint customers when infrastructure coverage, standards, or complementary services remain immature.
Is it for you?
Best for
It is best for companies operating where infrastructure and end-user products evolve together through shared standards.
Not ideal for
It is not ideal when adjacent-layer integration adds major complexity without producing proprietary insight or customer value.
From the transcript
“Huawei, I think saw the opportunity in having both sides of this business that because they were driving a lot of the innovation on standards…”
“their business strategy is really brilliant by participating heavily in both sides here, as we were saying, you know, they're able to drive a lot…”
“nobody has really been able to take the roadmap of what was going to be coming on the infrastructure side and translate that into compelling…”
From the episode
Huawei