Data Strategy, Value and the Data Portfolio · Lesson 2

Evaluate a portfolio of data domains and products

10 min read

Lesson objectives

  • Prioritize data investments after eligibility gates, weight sensitivity and dependency analysis.

A portfolio turns competing data requests into capacity and investment decisions. Separate eligibility from priority before ranking: a product without a committed consumer, use right or source contract does not compete regardless of attractive value. Compare eligible items through one decision unit covering outcome, total cost, dependency, risk and reversibility. Mandatory constraints stay outside a weighted average, and a score is never a permanent promise; ranking changes when evidence changes.

A portfolio selects interdependent investments under constraint; it is not a cosmetic ranking of domains. It begins with non-tradeable eligibility, then compares value, risk reduction, readiness and cost among eligible choices. Dependencies prevent funding a product that requires a missing capability. Governance approves weights and constraints; management gathers evidence, runs trials and updates the record.

Use a portfolio register with four distinct judgments. Eligibility rejects items missing a consumer, right or source. Value testing links each item to a decision change. Dependency analysis identifies what must precede construction. Capacity allocation then funds eligible items with an explicit reserve. Preserve the rejection reason and fact that restores an item, because an unconditional backlog becomes a hidden commitment.

Supplier is ineligible because the right to create a derived product is undocumented. Customer offers higher benefit but waits for an identity service; product offers faster learning with ready data. A third option funds source repair only. The staged decision funds product for eight weeks, preserves customer for review after the identity decision and does not turn deferral into permanent rejection.

If customer scores 8 for value, 7 for risk reduction and 6 for readiness, its result at 50%, 30% and 20% is 7.3. Product scores 7, 5 and 8, producing 6.6. Raising readiness to 40% while lowering value to 30% narrows the gap. Record scale direction and unrounded inputs; a sensitivity-dependent ranking is not a permanent fact.

Do not monitor a portfolio through delivery alone. Compare realized benefit with actual capacity, the share of items losing eligibility, investment concentration in one domain and time dependencies remain open. An on-time unused product creates no value; a shared repair consuming current capacity but unlocking three items may beat a quick standalone report. Indicators expose that trade-off rather than compressing it.

After the quarter, the portfolio lead compares realized benefit with actual capacity. A product consuming 35% of capacity while changing one decision is not protected by its old score. Alternatives are re-estimated with new information, and the record distinguishes dependency delay, weak adoption and optimistic estimation.

The portfolio decision is which domain receives trial funding next quarter, not which domain is universally most important. Customer data supports churn reduction, product data supports lower stockouts and supplier data supports continuity. Apply eligibility gates before weighting. Supplier depends on third-party data whose contract permits operations but not a derived analytical product, so it is temporarily excluded; a weight cannot purchase a missing right. Customer and product remain. Customer estimates 180,000 fictional units of benefit but needs six months for an identity service. Product can test 110,000 of benefit in eight weeks with lower continuing cost. Define decision value, risk reduction and readiness on scales that point in one direction, retaining raw values before normalization. At 50% value, 30% risk and 20% readiness, customer leads narrowly; raising readiness to 35% puts product first. A ranking reversed by a small weight change is fragile. The unavailable identity dependency supports funding product now, with a customer review after the identity decision. Eight weeks later, measure whether replenishment choices changed and stockouts fell without inflating obsolete stock. If source quality prevents the test, product returns to the readiness gate. The decision record contains gates, raw scores, transformation, weights, sensitivity, dependencies, cost and the fact that would return each option to competition. This prevents the strongest presentation from winning and keeps mandatory constraints outside tradeable scores.

At quarter close, reconstruct the decision from the old record before viewing outcomes: did the evidence available then justify the choice? Update estimates with new learning without judging a sound earlier decision through hindsight. Also record the alternative opportunity displaced by capacity so council sees the cost of continuing, not only the cost of stopping. Portfolio stress test: reduce forecast benefit 30%, increase transition cost 20% and delay a major dependency one month. Identify items whose position changes and require more evidence before commitment. An item remaining eligible and preferred across scenarios is more robust than one leading through a single fragile score. The decision also exposes its concentration cap.

FieldDecision or evidence
TitlePortfolio record
Decisionfund one trial this quarter within 120,000 units.
Eligibilityapproved purpose, usage right, consumer and decision, measurable baseline and accountable owner.
Customer180,000 benefit, readiness 6/10, 70,000 operating cost and dependency on an unapproved identity service.
Product110,000 benefit, readiness 8/10, 35,000 operating cost and an available source.
Supplierpossible 150,000 benefit but ineligible because third-party rights are absent.
Base weightsvalue 50%, risk reduction 30%, readiness 20%.
Sensitivityrecalculate at 35% readiness and with cost 20% higher.
Decisiontrial product now, review customer after identity approval and exclude supplier until authority is documented.
Trial measurelower stockouts without obsolete inventory exceeding 4%.
Stop conditionsource coverage below 90% or expected operating cost above 50,000.
Dependencyproduct definition and key precede measurement.
Reviewend of week eight using replenishment decisions, not screen count.
FieldDecision or evidence
TitlePortfolio decision lab
Situationtwelve data products request priority in the same quarter, while engineering capacity supports four.
Decision unitscredit risk product, customer register, demand forecast, workforce reports and seven local products; do not confuse a broad domain with a fundable product.
Eligibilitynamed owner, committed consumer, lawful use, known source and support route. Two products fail use rights and three lack a committed consumer.
Valuemeasure changed decisions, not visits. Risk prevents incorrect approval, demand reduces stockouts and the workforce report merely replaces manual extraction.
Costbuild, operation, documentation, support and consumer migration; a shared platform does not make each product free.
Riskcustomer register has high potential but unresolved identity conflict, so it remains ineligible pending a merge test.
Dependenciesdemand forecast depends on product and inventory definitions; its interface should not be funded before those contracts are repaired.
Alternativesweighted ranking of everything, mandatory work first or eligible baskets with a concentration cap. A weighted average can hide a legal constraint.
Decisionfund risk, demand forecast, customer identity repair and shared contract capability; do not fund workforce reporting despite easy delivery.
Evidenceevery choice has a benefit hypothesis, guardrail and review date; every rejection names the fact that could restore it.
Concentration capno domain takes over half the capacity despite high scores unless a documented risk decision allows it.
Stress casebudget falls 25%; mandatory work remains, while the demand interface waits but inventory-contract repair continues.
Stop rulepause a product after two missed consumer sessions or a failed rights condition and reassign capacity to the highest eligible item.
Judgmentthe portfolio is a changing decision record, not a static ranking or a promise that every request enters construction.
FieldDecision or evidence
TitlePortfolio review
1Stress ranking by reducing forecast benefit 30% and raising transition cost 20%. A stable choice is more robust; a reversed one needs evidence before commitment. Prevent the ineligible queue becoming a permanent graveyard by assigning owner, enabling fact and date. After the quarter compare realized benefit with consumed capacity and move funding when consumer or dependency disappears, not when sponsor volume rises.
2The portfolio record retains its prior version and reason for reallocations, explaining why a less attractive item can precede one with higher forecast benefit.
3Each item regains eligibility when a consumer appears or rights constraint clears.
FieldDecision or evidence
TitlePortfolio verification
1Rerank after removing the highest benefit estimate and delaying a dependency one month. Record which items move and why. Confirm mandatory work was not scored against optional work on the same scale, and every deferred product has a review date rather than an open promise.
Final boundarymandatory constraints remain outside trade-offs regardless of forecast benefit.

Lesson summary

Prioritize data investments after eligibility gates, weight sensitivity and dependency analysis.