The Partnership Portfolio That Revealed Nothing
A mid-size technology company recently completed a strategic review of its business development portfolio. Over three years, the organization had signed:
- Partnerships with enterprise system integrators requiring deep customization
- SMB resellers demanding self-service products
- White-label deals that stripped away the company’s brand
- Co-development agreements positioning the firm as a premium innovator
When asked what business the company was in, the CEO answered without hesitation.
When shown the partnership portfolio, he went quiet.
The deals—each rational on its own—pointed in four contradictory directions. The Business Development team had been busy, disciplined, and successful by their own metrics. But collectively, they had committed the company to four different business models at once.
This is the business development problem no one talks about: Business Development without doctrine doesn’t just fail to create value—it actively creates strategic incoherence.
What “Doctrine” Actually Means
Clarity is needed about what doctrine means in a business context. This is not a vision statement, nor a set of corporate values.
Business doctrine is a belief system that defines how and why a company competes, grows, and operates—beyond individual strategies or tactics.
It helps to distinguish doctrine from the other pillars of leadership:
- Strategy is the map for the current terrain
“We will enter the German market this year.” - Doctrine is the compass, it tells you which direction is North regardless of where you are standing
“We only enter markets where we can own the primary data relationship.” - Culture governs behavior
“How we treat each other.”
Doctrine governs operational logic—how we believe value is created and how we win.
A robust business doctrine codifies:
- Core beliefs about value creation – where advantage truly comes from
- Strategic orientation – market-led or product-led, first-mover or fast follower
- Operating principles – how decisions are made and resources allocated
- Value priorities – What trade-offs will the organization make? speed vs. accuracy, scale vs. control, growth vs. profitability
- Approach to risk – how uncertainty, failure, and opportunity are treated
- Theory of value – the mental model linking actions to durable advantage
Doctrine vs. Mission: The Operational Divide
Doctrine is often confused with mission—but the two serve fundamentally different purposes. But while Mission is aspirational and external-facing, Doctrine is operational and internal-facing.
Mission answers “Why do we exist?” Doctrine answers “How do we believe the world works, and how will we operate within it?”
| Feature | Mission | Doctrine |
|---|---|---|
| Focus | Inspiration & alignment | Differentiation & trade-offs |
| Nature | Aspirational | Operational |
| Audience | External & internal | Primarily internal |
| Example | “Democratize access to finance” | “Inclusion requires platform scale and algorithmic decision-making” |
Two companies can share a mission yet operate under incompatible doctrines.
Netflix and HBO both aim to deliver world-class entertainment. But Netflix’s doctrine prioritizes data-driven personalization at scale (algorithms over curation), while HBO’s doctrine emphasizes editorial judgment and curated quality over quantity.
Same mission. Radically different doctrines.
What Business Development-Specific Doctrine Looks Like
If doctrine matters for organizations in general, it is essential for business development. A Business Development-specific doctrine must address five pillars.
1. Identity Doctrine: What Business Are We In?
If the doctrine says platform, Business Development focuses on ecosystem orchestration.
If it says service provider, Business Development pursues deep, embedded client relationships.
You cannot be a platform on Mondays and a service firm on Thursdays.
2. Value Creation Doctrine: Where Does Advantage Come From?
Your theory of value determines partnership coherence—network effects, operational excellence, customer intimacy, or something else entirely.
3. Capability Boundary Doctrine: Build vs. Buy vs. Partner
Which capabilities are so central to advantage that they must be built internally?
Without clarity, Business Development quietly partners away differentiation.
4. Growth Doctrine: Depth vs. Breadth
Does value come from a few deep, strategic alliances—or many tactical channel relationships?
Trying to do both simultaneously usually means doing neither well.
5. Control vs. Scale Trade-off Doctrine
Every Business Development decision lives on a spectrum:
Direct Sales (high control) → Channel Partners → Platform Ecosystems (maximum scale)
Doctrine determines where you are willing—and unwilling—to play.
The “Any Revenue Is Good Revenue” Fallacy
Without doctrine, Business Development defaults to strategy through accumulation. The result is strategic schizophrenia: trying to be two incompatible businesses at once.
| Requirement | Enterprise Doctrine | SMB / Volume Doctrine |
|---|---|---|
| Product | Bespoke, deeply customized | Standardized, self-service |
| Support | High-touch services | Automated, low-friction |
| Sales Cycle | 12–18 months | 12–18 minutes |
| BD Focus | Deep system integrators | Massive affiliate networks |
When Business Development signs both, it isn’t diversification—it’s organizational self-harm. Engineering and support get pulled apart at the seams.
What Happens Without Doctrine: Predictable Pathologies
When Business Development operates in a doctrinal vacuum, the failure modes are remarkably consistent:
- Strategic drift – Each deal looks fine alone; together they commit the firm to an unintended business model
- Capability fragmentation – You cannot excel simultaneously at premium customization and mass self-service
- Channel conflict – Direct sales undercut resellers; partners compete with the company
- Resource incoherence – Product and engineering inherit promises they never agreed to make
- Identity crisis – The company eventually forgets what it is trying to be
Doctrine in Action: The Authenticity Test
Real doctrine reveals itself in moments of hard trade-offs.
- Amazon’s doctrine of customer obsession and long-term thinking shapes every strategic decision
- Tesla’s doctrine of vertical integration explains why it builds its own infrastructure
- IKEA’s doctrine of democratic design determines which suppliers it co-develops with
Microsoft’s Doctrine Shift
Doctrine is not static. Microsoft operated for decades under a “Windows everywhere” doctrine. When Satya Nadella shifted the company to “cloud-first, mobile-first,” Business Development had to unwind exclusive agreements and put Office on iOS and Android.
The new strategy was impossible without a new doctrine.
The Business Development portfolio is the ultimate authenticity test. If leadership claims “premium positioning” while Business Development pursues volume discount resellers, the doctrine is theater.
Building Your Doctrine: Where to Start
- Audit the portfolio – Map existing deals against the five pillars and surface contradictions
- Surface implicit beliefs – What do Business Development decisions actually reveal about how the organization thinks the world works?
- Create decision principles – Translate doctrine into filters (e.g., “We partner for reach, but build for differentiation”)
- Embed in governance – Ensure deal reviews surface doctrinal conflict, not just revenue upside
The Bottom Line
Back to the quiet CEO. He realized his BD team had succeeded in a vacuum. By failing to provide doctrine, he had left them navigating by the stars of opportunity rather than the compass of identity.
Partnerships always follow doctrine.
If you don’t define yours, your partnership portfolio will define it for you—and you may not like the result.