Collecting Portfolio Data

Strategic intent: Ground the Portfolio Map in how the organization actually operates — not in how leadership thinks it operates. The whole pipeline is downstream of this technique.

#Overview

The Portfolio Map is a 5-layer view of the organization spanning Customer Ecosystem → Customer Needs → GTM Strategies → Market-Facing Value Propositions → Organizational Elements. The quality of the map depends entirely on the quality of the data feeding it. Guessing produces fiction.

This technique walks through the disciplined data-collection process: stakeholder identification across functions and seniority levels, interview design, dependency mapping, draft creation, and iterative validation.

The ultimate aim is a map that captures the horizontal-vertical taxonomy of the organization (from Horizontals, Verticals, and the ILC Model): which offerings are platform-style horizontals, which are vertical solutions targeting specific segments, which are bundles formed by integration across verticals.

#When to use it

• At the start of any Portfolio Mapping engagement (always before Market-Facing or Organizational analysis)
• When leadership claims to "know the portfolio" but Product Owners and Sales have different views
• After acquisitions, when the portfolio has grown organically
• Before any restructuring decision, to ensure decisions are grounded
• When applying the Playing to Win framework — Where to Play and How to Win both depend on understanding what the portfolio actually delivers today

#Composition

This technique is centered on the Portfolio Map Canvas and is iterative.

1. #1. Identify stakeholders to interview

   Aim for diverse perspectives across roles, not just leadership:

   • Product Owners — know their products deeply, the maturity, the roadmap
   • Domain Leads — know organizational boundaries, dependencies, internal politics
   • Industry Platform leaders (where 3EO is in place) — know strategic domain investments
   • Shared Service Managers — know cross-cutting services and where the friction lives
   • Sales / Business Development — know customer needs, GTM motions, deal patterns
   • Operations leaders — know real cost structure and process bottlenecks
   • Customer Success / Account Management — know what customers actually use vs what's sold

   Aim for 6–12 interviews covering all roles. Skipping a role is a known blind spot.

2. #2. Design the interview protocol

   A 45–60 min interview should cover:

   • Customer view — who do you serve? Which segments? What are their needs (operate vs innovate vs integrate vs optimize use cases)?
   • Product view — what offerings do you own / contribute to? Which are horizontal platforms, which are verticals, which are bundles?
   • Maturity view — actual maturity (one-off / bespoke / productized / API), not aspirational
   • GTM view — how are these offerings sold? Self-service, solution selling, enterprise system integration?
   • Org view — who do you depend on (SSPs, other MEs, external)? Who depends on you? Which agreements (formal or informal)?
   • Pain points — where do things break? Where are overlaps with other units?
   • Hypotheses — what would you change if you could?

   Keep the protocol consistent so synthesis is comparable across interviews.

3. #3. Conduct interviews and capture verbatim

   Capture key quotes, not just summaries. Verbatim reveals where stakeholders disagree — those discrepancies are signals worth investigating.

   Tag each quote with: speaker role, layer of the map (customer / needs / GTM / offering / org), and stance (current / aspirational / pain).

4. #4. Draft the preliminary map top-down

   Work in this exact order:

   1. Customer Ecosystem — diagram of customers and how they relate. In B2B this often means core enterprise customers (60–80% of revenue, 2–3 industries) plus emerging segments (united by needs rather than industry) plus mediators/integrators
   2. Customer Needs — position in the 2×2 (specific/standardized × strategic/operational); also tag along the Operate / Innovate / Integrate / Optimize dimensions
   3. GTM Strategies — the 4-stage spectrum (consulting → solution → product → self-service)
   4. Market-Facing Value Propositions — offerings positioned on the maturity spectrum, distinguishing horizontals from verticals from bundles
   5. Organizational Elements — teams, units, infrastructure with explicit boundaries

   Tag pain points and discrepancies with visual markers.

5. #5. Validate iteratively

   Bring the preliminary map back to stakeholders in collaborative review sessions (group of 3–5 stakeholders, 90 min).

   Challenge assumptions: "Is this how it really works, or how we wish it worked?"

   Expect the first draft to be 60% right at best. The validation cycle is where the map becomes real.

#Inputs

• Required: access to stakeholders across roles
• Required: time and political backing to do the interviews properly
• Recommended: prior outputs from Understanding Ecosystems — the customer ecosystem layer can reuse them

#Outputs

• Stakeholder interview transcripts — tagged and structured
• Discrepancy register — where stakeholders disagree (gold for restructuring)
• Preliminary Portfolio Map — populated, ready for analysis
• Pain point catalogue — explicit list of frictions
• Horizontal-vertical taxonomy hypothesis — early classification of offerings

#Process heuristics

• Interview from multiple levels — execs see strategy, ICs see reality. Both are needed
• Cross-functional interviews are most revealing — Product + Sales + Ops in the same room reveals more than three separate ones
• Verbatim quotes beat summaries — they preserve the disagreements that matter
• Visual markers for pain points — red dots, yellow warnings — make the map feel the problems
• The first draft will be wrong — plan for at least 2 validation rounds
• Start tagging horizontal vs vertical early — even a hypothesis taxonomy guides the interview probes

#Validation criteria

• At least 6 stakeholder interviews completed
• All key roles represented (Product, Sales, Ops, Customer-facing)
• Verbatim quotes tagged by speaker role and map layer
• Preliminary map populated for all 5 layers
• Discrepancies between stakeholders explicitly captured
• At least one validation round with stakeholders completed

#Common mistakes

• Skipping interviews to save time — produces a fiction map
• Only interviewing leadership — misses how the organization actually operates
• Hiding discrepancies — they're signals, not noise; surface them
• Not validating — first drafts are usually 30–50% wrong; without validation those errors compound
• Treating "horizontal" and "vertical" as just labels — the distinction has real implications for investment cycles and organizational topology

#Used in pipelines

• Portfolio Mapping — as Phase 1

#Connections

• Feeds: Market-Facing Analysis and Organizational Elements Analysis
• Connects to: Scanning & Mapping the Ecosystem — if it has been run, the customer ecosystem layer is partly populated already

#Related reading

• The Portfolio Map Canvas Application Guide v0.1 — full long-form narrative in Legacy Portfolio Map
• Horizontals, Verticals, and the ILC Model — the taxonomy framework
• Playing to Win in Platform Organizations — strategic choice chartering for portfolios