Needs Capture

Updated 14 May 2026

Definition

Needs Capture is the capability to receive, register, and coarsely classify portfolio-level needs raised by sponsors with organizational mandate — the intake function of the portfolio. The capability is neutral on relevance and value: it does not filter, evaluate, or decide what proceeds; that work belongs downstream at Triage.

Purpose in the system

The portfolio’s strategic and economic decisions are only as good as the option space they consider. When candidates are filtered informally — at the moment of submission, by whoever happens to receive them — that filtering happens without strategic context, without comparative view, and without explicit accountability. Options the portfolio never knew it had are lost before anyone authorized to weigh them has seen them.

Needs Capture is the system intervention that keeps the option space visible and complete. The capability accepts submissions from sponsors with sufficient organizational mandate to fund portfolio-level investments — intake is not an open suggestion box. Each submission that meets the substance threshold is registered as a candidate and held until an explicit decision is made. Filtering on relevance and value still happens — but at Triage, by the portfolio leadership group, with strategic intent and capacity context in view. The discipline is holding without deciding.

The capability operates upstream of all other portfolio decision-making. Its outputs feed Strategic Relevance Assessment at Triage and Gate 1, where the first filtering decision is made. From there, registered candidates that pass Gate 1 enter the discovery domain, where they are sequenced by Initiative Prioritization and matured by Discovery and Business Casing toward Gate 2. Without intake discipline upstream, every downstream capability inherits the blind spots of whoever gates submission.

In a portfolio with the capability well developed, capture and assessment remain distinct activities. Capture is open to sponsoring submitters with substantive needs to raise. Assessment is deliberate: the people accountable for investment decisions apply the strategic and capacity context that distinguishes signal from noise. Conflating the two collapses both — submissions are quietly turned away before anyone authorized to decide has seen them, and the portfolio’s view of incoming demand narrows without anyone noticing.

What the capability consists of

The capability has three parts: the information it requires, the judgments it makes, and the outputs it produces.

Information required

Needs originate from several distinct domains across the organization. No single domain captures the full demand picture, which is why the capability ensures sponsoring submitters exist for each domain — so that nothing of strategic substance is structurally muted at the source.

The mix of origin domains is itself a portfolio diagnostic. A portfolio whose intake is dominated by one domain — typically internal stakeholders — has a structural blind spot. Customer-originating needs and externally-scanned signals are commonly under-represented even when they carry high strategic weight.

A need’s origin and its submitter are distinct. Origin is where the need comes from in the world — a customer pain, a compliance requirement, a delivery-system constraint, an environmental signal. Submission requires a sponsor with sufficient organizational mandate to fund a portfolio-level investment. The capability’s discipline is to ensure that each origin domain has sponsoring submitters who can carry needs into intake — so that no domain is structurally muted.

For a need to be registerable, it must carry enough articulation to be assessed at portfolio level: a problem or opportunity statement, an identifiable source, a coarse classification. The structured information that registered candidates carry — and how it grows as the candidate matures through the flow — is the substance of the Initiative artifact.

Judgments made

Intake makes a small set of deliberately limited judgments. The thresholds for who may submit and what is required are flow policies defined in Portfolio Kanban Flow; intake applies them. Strategic, economic, and feasibility judgments belong downstream — at Strategic Relevance Assessment and beyond.

Sponsorship. Does the submitter have sufficient organizational mandate to sponsor a portfolio-level investment? Initiatives represent significant investment commitments and require a responsible sponsor; intake is not an open suggestion box. A submission without a sponsor is referred back to find one, not registered.

Articulation. Is the submission articulated enough to be a coherent candidate? A submission described only as “improve the platform” is not yet a need; it is a starting point that requires further articulation before it can be registered. The threshold is low — just enough structure for downstream assessment to be possible — but it is real.

Coarse classification. Each candidate receives an initial classification — typically among business need, enabler, compliance, and strategic. The classification is a routing aid, not an evaluation. A compliance candidate may follow a slightly different early path than a discretionary business need; the classification ensures candidates reach the right downstream context. It does not rank or prioritize.

Duplication and hygiene. Is this candidate already in the system? Has registration accumulated stale items that no longer warrant attention? These are housekeeping judgments — recurring rather than one-time — and they keep the intake legible as a signal rather than a noisy archive.

The capability does not judge strategic relevance, expected value, feasibility, or priority. Conflating any of these with capture is the failure mode that produces informal filtering at the wrong place in the system.

Outputs

The capability produces three things:

• Registered initiative candidates — submissions that have passed sponsorship and articulation thresholds, carrying their coarse classification and source context, visible to the portfolio leadership group and ready for Triage.
• Acknowledgment to submitters — confirmation that the submission has entered the system. This is not a commitment to act on it; it is confirmation that an explicit decision will be made.
• A maintained intake list — the live, current view of registered candidates that have not yet received a Gate 1 decision.

The intake list is not a backlog. A backlog implies priority order and near-term intent to act; the intake list implies neither. The distinction matters operationally — an organization that treats intake as a backlog feels pressure to keep it short, and shortens it by discarding informally. An organization that understands intake as a holding area for unvalidated possibilities can capture liberally because filtering happens later, deliberately, and with accountability.

How the capability expresses itself

A delivery system with this capability well developed has several observable characteristics.

Submission is accessible to sponsors. The portfolio’s sponsoring submitters — those with organizational mandate to fund a portfolio-level investment — know where and how to register, and the channel is consistently used. The path from each origin domain to a sponsoring submitter is itself part of how the capability is operated; an origin domain whose sponsors face friction in submitting is structurally muted regardless of how visible its needs are at the source.

Capture and assessment are separated. The Portfolio Office administers registration. The Portfolio Leadership Group makes the relevance and investment decisions. Submissions are not informally turned away as “not relevant” at the moment of receipt. Filtering, when it happens, is explicit and comes from the people with the strategic context and authority to filter responsibly.

Acknowledgment is reliable but uncommitted. Submitters know their submission has entered the system. They do not receive promises that work will follow — only confirmation that an explicit decision will be made. This combination — visible receipt without false commitment — keeps the channel trusted and used over time.

The intake list is hygienically maintained. Items either progress to a Gate 1 decision, receive an explicit deferral, or are discarded with a stated reason. Items do not accumulate silently. The list’s value as a signal degrades when it fills with unresolved candidates, and the Portfolio Office’s recurring hygiene review prevents that decay.

Source mix is monitored. The portfolio sees which origin domains are producing candidates and which are not. A dominant domain is treated as a finding worth surfacing, not a fact to live with. The diagnostic question — what are we not hearing? — is part of how the capability is operated.

Initial classification serves routing, not ranking. Candidates carry a coarse classification because some downstream paths differ slightly. The classification does not rank candidates against each other; that is downstream work, performed with downstream information.

Relationship to other capabilities

Needs Capture sits at the upstream-internal edge of the portfolio. Its inputs come from across the organization and from one upstream portfolio capability; its primary output feeds the immediate downstream consumer at Triage.

Needs Capture at the upstream-internal edge of the portfolio. Three origin domains are external to portfolio capabilities; Environmental Scanning is the one upstream portfolio capability that feeds it. The immediate downstream consumer is Strategic Relevance Assessment at Triage.

Upstream — origin domains.

Three domains — customers and users, internal stakeholders, value streams — originate in the organization at large. Sponsoring submitters with mandate carry needs from these domains into intake. The capability sits at the edge between the organization’s broader sense-making and the portfolio’s structured decision flow.

Environmental Scanning is the one upstream portfolio capability that feeds intake. It produces externally-originated candidates — needs identified through structured monitoring of market, competitive, technology, regulatory, and organizational signals — that enter intake the same way as internally-generated needs. The two paths converge at the registered candidate; once registered, origin is information, not a privilege.

Downstream — capabilities that consume registered candidates.

Strategic Relevance Assessment is the immediate consumer. At Triage, it evaluates registered candidates against current strategic direction and produces the first investment decision — Gate 1 — which determines whether a candidate enters the discovery flow or is deferred or discarded. Capture and assessment are operationally adjacent: capture registers, assessment decides.

Initiative Prioritization operates further downstream, in the discovery domain, sequencing candidates that have crossed Gate 1 against analytical capacity. Intake quality affects prioritization indirectly — the discovery-domain list is only as informed as the candidates it draws from, which is only as informed as intake captures.

Discovery and Business Casing takes the highest-priority candidates from the discovery domain and matures them toward Gate 2. It is where registered candidates become initiative candidates with Lean Business Cases attached.

The flow context. Portfolio Kanban Flow is the flow mechanic within which intake operates as the first stage of Continuous Sensing. The flow document defines the intake flow policies (Who may submit, What is required) and the stage progression; this capability document describes what intake itself does within those policies.

The capability and its container. Needs Capture is one of the capabilities that together constitute Agile Portfolio Management — the broader capability of governing portfolio investments strategically.

Supporting documents

• Practice — forthcoming. A practice document covering submission channel design, problem statement guidance, source-mix diagnostics, and intake hygiene operations.
• Roles — Portfolio Roles. The Portfolio Office administers registration and intake hygiene; the Portfolio Leadership Group makes Gate 1 decisions. Specific responsibilities are documented there.
• Artifact — Initiative. The information carrier that registered candidates become — describes the field set required at intake and how it matures through the flow.
• Flow — Portfolio Kanban Flow. Intake is the first stage of Continuous Sensing; the flow document describes the stages, gates, flow policies, and progression.
• Metric — gap. Source-mix balance, time-to-Gate-1, and intake-list age are candidate diagnostics; specific metric definitions are not yet documented. Known gap.

Sources

• Donald Reinertsen — Principles of Product Development Flow (2009). Queue theory and the economic case for managing intake discipline at portfolio level. The cost-of-queues argument that motivates explicit intake separation.
• David J. Anderson — Kanban: Successful Evolutionary Change for Your Technology Business (2010). Pull systems, flow policies, and the discipline of explicit intake — including the principle that intake is administered, not gated by the act of capture.
• Patrick Steyaert — Essential Upstream Kanban (2015). The separation of upstream (option discovery) from downstream (delivery) as distinct systems with different purposes — the basis for treating intake as a system stage in its own right rather than as a queue feeding delivery.
• Marty Cagan — Inspired (2017). The importance of capturing customer- and market-originating signals as a primary source of portfolio-level investment candidates.
• Jeff Gothelf and Josh Seiden — Lean UX (2013). Hypothesis-driven framing of needs before commitment to analysis or delivery — supports the holding without deciding discipline.