K
KnowMBAAdvisory
StrategyAdvanced8 min read

Value Network Analysis

Value Network Analysis (VNA), formalized by Verna Allee in 'The Future of Knowledge' (2003) and 'Value Networks and the True Nature of Collaboration' (2008), maps how value flows between roles in a business ecosystem โ€” including BOTH tangible exchanges (money, products, contracts) AND intangible exchanges (knowledge, reputation, advocacy, trust). Unlike a traditional supply chain, a value network shows that an enterprise creates value through a web of mutual exchanges with customers, partners, regulators, communities, and suppliers โ€” and that ignoring intangible flows (e.g., 'developer goodwill', 'brand equity', 'data exhaust') leads to strategic blindness.

Also known asVNAVerna Allee Value NetworkTangible/Intangible Value MappingValue Web Analysis

The Trap

Mapping only the tangible flows (cash, contracts, products) and missing the intangible flows that actually drive long-term value. Example: a company optimizes its 'paying customer' relationship and ignores 'unpaid developer community' โ€” then a competitor builds an open-source alternative on the back of that ignored community and disrupts the business. The intangibles ARE the moat. Companies like Stripe, GitHub, and Notion grew because they engineered intangible flows (developer trust, ease of integration, status) that competitors couldn't replicate by adding features.

What to Do

Run a VNA workshop in 4 steps: (1) List all roles in your ecosystem (not just customers โ€” include partners, communities, regulators, employees-as-advocates, alumni). (2) For each role-to-role relationship, map TANGIBLE exchanges (money, products, contracts, data). (3) For each relationship, map INTANGIBLE exchanges (knowledge, reputation, advocacy, trust, status). (4) Identify the top 3 intangibles you depend on but don't actively manage โ€” these are your hidden risks AND your hidden leverage points.

In Practice

Verna Allee developed Value Network Analysis at Allee Associates (1990s-2000s) and applied it inside Boeing, Cisco, the World Bank, and the U.S. Department of Defense. Her 2003 paper 'Value Networks and the True Nature of Collaboration' (published with the Holistic Management Institute) is foundational. The methodology was used by Cisco to map its partner ecosystem when transitioning from box-selling to services โ€” identifying that 'partner certification advocacy' was a critical intangible flow that the company hadn't been actively managing, leading to a redesign of the partner program that grew indirect revenue from $5B to $12B over 4 years.

Pro Tips

  • 01

    Always identify 'value sinks' โ€” roles that consume value without generating return flows. Common sinks: regulatory compliance teams (cost without revenue contribution), unprofitable customer segments (consume support without margin), legacy partners (consume engineering attention without driving growth). Sinks aren't always bad (compliance is necessary), but you should know they exist.

  • 02

    Intangible flows compound. A 'developer trust' intangible from year 1 becomes 'preferred platform' status in year 3 and 'industry standard' in year 5. The intangibles are often worth 5-10x the tangible balance sheet.

  • 03

    Use VNA before any major partnership decision. If a partnership produces tangible inflow (money) but intangible outflow (you train them, they leave), it's a bad partnership disguised as a revenue line.

Myth vs Reality

Myth

โ€œValue flows only in money and productsโ€

Reality

Verna Allee's research showed that in knowledge-economy enterprises, intangibles (knowledge, reputation, advocacy) account for 60-80% of total value created. Companies that measure only tangibles (revenue, units shipped) miss most of what makes them valuable. This is why software companies trade at 10-20x revenue while industrial companies trade at 1-2x โ€” the multiple is the market's estimate of intangibles.

Myth

โ€œValue Network = Supply Chainโ€

Reality

Supply chains are LINEAR (raw material โ†’ factory โ†’ distributor โ†’ customer) and TANGIBLE. Value Networks are WEBS with bidirectional flows that include intangibles. A supply chain views the customer as the END of the line; a value network views the customer as a NODE with their own outflows (data, advocacy, requirements) that feed back into the system.

Try it

Run the numbers.

Pressure-test the concept against your own knowledge โ€” answer the challenge or try the live scenario.

๐Ÿงช

Knowledge Check

A SaaS company runs a free tier that costs them $2M/year in infrastructure with $0 direct revenue from those users. They're considering killing the free tier. What does Value Network Analysis suggest looking at first?

Real-world cases

Companies that lived this.

Verified narratives with the numbers that prove (or break) the concept.

๐Ÿ”—

Cisco Systems

2002-2008 partner ecosystem redesign

success

Cisco hired Verna Allee to apply Value Network Analysis to its channel partner program when transitioning from hardware-only to services. The VNA revealed that 'partner certification advocacy' (intangible) drove far more revenue than the partner co-marketing dollars Cisco had been measuring (tangible). Cisco redesigned the partner program around intangible flow optimization โ€” investing in partner certifications, partner-to-partner knowledge networks, and partner advisory boards. Indirect revenue grew from $5B to $12B over 4 years.

Channel Revenue Growth

$5B โ†’ $12B (4 years)

Partners Certified

60K+

Intangibles Identified

23 distinct flows

Strategy Shift

Co-marketing โ†’ Co-capability

What you measure is what you manage. Cisco only measured tangible partner flows until VNA forced them to map intangibles. Once mapped, the intangibles became the strategic priority โ€” and the tangible revenue followed.

Source โ†—

Decision scenario

The Free Tier Kill Decision

You're the CFO of a B2B SaaS company. The free tier costs $3M/year in infrastructure and serves 200K free users with $0 direct revenue. The CEO wants to kill it to improve margins. You're asked to do the value analysis.

Free Tier Cost

$3M/year

Free Tier Direct Revenue

$0

Paid Conversion from Free

2.4% over 18 months

Free Users

200K

Paid Users

12K @ $200/mo avg

01

Decision 1

Initial analysis: 200K free users ร— 2.4% conversion ร— 18 months = 4,800 future paid users at $200/mo = $11.5M/year future revenue. Already, killing the free tier costs ~$8.5M net. But you do a full VNA and find: free users generate 35% of inbound leads via word-of-mouth, contribute 2,100 community Q&A answers/month (saving $400K in support), and are the talent pipeline for 18% of new engineering hires.

Kill the free tier โ€” $3M cost saving is concrete; intangibles are speculativeReveal
Within 6 months: paid signups drop 30% (loss of free-to-paid funnel), inbound leads drop 35% ($4M increased CAC), community Q&A volume drops to near-zero (support costs +$400K), and engineering recruiting becomes harder ($50K+ per hire premium). Total annual damage: ~$15M against $3M saved. Worse, the brand suffers โ€” competitors capitalize on 'we're free, they're not'. The CEO blames you.
Free Tier Cost: $3M โ†’ $0 (saved)Total Damage: +$15M annuallyBrand Position: Premium-only (lost mindshare)
Keep the free tier but add usage limits to cap infrastructure cost at $1.5M, and instrument the intangible flows (NPS of free users, community contribution rate, free-to-paid conversion) so you can manage them like real metricsReveal
You preserve all intangible flows while halving the cost. By instrumenting intangibles, you discover that free users with >10 community contributions convert at 8% (vs 2.4% baseline), so you create a 'community champion' tier with elevated free limits. Within 12 months: cost drops to $1.5M, paid conversion rises to 3.1%, community contributions grow 40%. Net annual value created: ~$8M.
Free Tier Cost: $3M โ†’ $1.5MPaid Conversion: 2.4% โ†’ 3.1%Net Value Created: +$8M annually

Related concepts

Keep connecting.

The concepts that orbit this one โ€” each one sharpens the others.

Beyond the concept

Turn Value Network Analysis into a live operating decision.

Use this concept as the framing layer, then move into a diagnostic if it maps directly to a current bottleneck.

Typical response time: 24h ยท No retainer required

Turn Value Network Analysis into a live operating decision.

Use Value Network Analysis as the framing layer, then move into diagnostics or advisory if this maps directly to a current business bottleneck.