Horizontal-Vertical Alignment Test
Choose platform ownership without undermining cross-platform scale
- Difficulty
- Advanced
- Time to result
- ~months to results
- Steps
- 6
- Confidence
- 94%
The test begins by classifying the economic engine of a company. A horizontal business wins through broad distribution across many platforms, while a vertical business wins through control of an integrated experience. Owning both can create incentives to reserve features, delay rival-platform releases, or optimize the horizontal product for proprietary hardware. The company must therefore choose which model has priority and assign the other asset a supporting role. It then establishes cross-platform parity rules, separate incentives where needed, and metrics tied to the chosen objective. Android illustrates a support model in which an operating system protects distribution for Google services without needing to become the primary profit engine. The framework does not prohibit integration; it requires every integration decision to strengthen rather than contradict the company's declared strategic center.
Origin
Extracted from The Shawn Ryan Show
Core principles
- 01Horizontal businesses maximize reach across competing platforms.
- 02Vertical businesses optimize an integrated proprietary experience.
- 03Operating both models creates conflicting incentives.
- 04A vertical asset should have a clearly defined role in supporting the horizontal core.
- 05Governance and metrics must prevent ecosystem favoritism.
- 06Integration is valuable only when it strengthens the chosen strategic model.
How to run it
- 1
Classify the economic engine
Determine whether the core business creates value through maximum cross-platform reach or through a controlled end-to-end experience. Use revenue sources and customer behavior rather than branding language.
Pro tip Ask whether the business benefits more from ubiquity or exclusivity.
Watch out Calling the company hybrid does not resolve the underlying incentive conflict.
- 2
Locate the channel conflict
List decisions where the proprietary platform could receive earlier releases, exclusive features, better performance, or preferential distribution. Estimate what each choice would cost the horizontal core.
Pro tip Review product roadmaps and launch sequencing for practical evidence of favoritism.
Watch out Small platform preferences can accumulate into a substantial reach disadvantage.
- 3
Declare strategic priority
Choose which business model wins when objectives conflict. Communicate whether the vertical asset is the core, a profit center, or an insurance mechanism.
Pro tip Tie the declaration to explicit executive and board-level metrics.
Watch out Employees will optimize for local goals if leadership leaves the hierarchy ambiguous.
- 4
Design supporting boundaries
Create rules governing exclusivity, feature parity, data sharing, branding, and team integration. Preserve autonomy where shared management would create incompatible incentives.
Pro tip Use documented exceptions with expiration dates instead of informal promises.
Watch out Total separation can also prevent useful technical collaboration.
- 5
Align incentives and talent
Reward the vertical team for supporting the declared corporate objective while still producing a competitive platform. Ensure the mission remains attractive to strong employees.
Pro tip Give the platform team meaningful product goals that do not require harming rival-platform support.
Watch out A team described only as an insurance policy may struggle to recruit and retain exceptional people.
- 6
Audit real decisions
Regularly examine launches, staffing, partnerships, and resource allocation for divergence from the chosen model. Correct structural incentives rather than treating each conflict as an isolated exception.
Pro tip Compare the user experience and release cadence across every major platform.
Watch out Stated cross-platform neutrality is meaningless without operational evidence.
In the wild
Facebook's core social service depended on reaching users across every major device, while Oculus represented a proprietary hardware platform. Deeper integration risked encouraging Facebook-only Oculus features or weaker support for competing VR systems. The alignment test would classify Facebook as the horizontal priority, define Oculus as strategic insurance, and require first-class Facebook experiences on every important VR platform.
→ The company could preserve broad social-network scale while retaining a credible proprietary access point.
Google distributed search, Gmail, and Maps across platforms while supporting Android as an open operating-system layer for many hardware partners. Android reduced Google's dependence on another mobile platform owner and helped preserve distribution for its services. The operating system supported the horizontal advertising and services engine rather than replacing it as the main revenue source.
→ Google secured mobile distribution while continuing to offer important services on competing devices.
Common mistakes
Leaving strategic priority implicit
Teams interpret ambiguity in ways that favor their own products and metrics. Leadership must specify which objective prevails when platform ownership conflicts with cross-platform reach.
Forcing integration for its own sake
Combining teams, roadmaps, or features can create channel conflict without producing customer value. Integrate only where the benefit exceeds the loss of neutrality.
Starving the supporting platform
A platform cannot provide leverage or insurance if it is uncompetitive. Give it sufficient talent and resources while constraining harmful exclusivity.
Is it for you?
Best for
It is best for software and internet companies considering hardware, operating-system, marketplace, or infrastructure ownership.
Not ideal for
It is not ideal for businesses already committed to a fully integrated model with no need for broad third-party distribution.
From the transcript
“Facebook is a horizontal company. Facebook needs to make sure that they are on every single platform in the same way so that the most…”
“it's when you then cross over into trying to be both vertical and horizontal that you get the Office for iPad situation.”
“They just have to figure out a way, and Google took years to do this to be clear that Android exists to power the search…”
From the episode
Oculus