Strategic Relevance Assessment

Updated 10 May 2026

Definition

Strategic Relevance Assessment is the capability to evaluate whether an initiative — candidate or active — is aligned with where the portfolio is going. The assessment activates first at Triage as a filter on what enters the discovery domain, and is then applied continuously to candidates and active initiatives as direction evolves and circumstances change. Both modes apply the same underlying judgment.

Purpose in the system

A portfolio that lets every plausible idea consume analytical capacity collapses under its own intake. Discovery is expensive — it commits scarce skill and time to investigating one option at the expense of others. A portfolio without an early relevance filter accumulates work whose strategic foundation no one has examined, and the analytical function spends itself reading material that is not yet worth reading.

Strategic Relevance Assessment is the system’s deliberate filter. It refuses to absorb work whose connection to current direction is not visible, and it does so explicitly — at Triage, by people with the strategic context and authority to filter responsibly. This is the inverse of the failure mode Needs Capture is designed to prevent: informal filtering at the moment of submission, performed without strategic context, by whoever happens to receive the submission. Capture and assessment are operationally adjacent — capture registers, assessment decides — and the discipline of separating them is what protects both.

The capability does not stop after Gate 1. Strategic relevance is a property of an initiative’s relationship to a moving target — the portfolio’s direction, the environment, the competitive picture, the regulatory frame. An initiative judged highly relevant when approved may be less so six months later as themes shift, evidence accumulates, or the environment moves. A candidate ranked correctly for delivery at one point may sit below new entrants at the next. The capability is the input that keeps the rest of the portfolio’s decision-making current. Without continuous reassessment, prioritization runs on stale data and the Delivery Queue accumulates initiatives that no longer earn their place.

The capability operationalizes Principle 01 — Value and Outcomes Focus at portfolio level. Strategic Goal Management operationalizes the same principle at the level of setting and maintaining direction; this capability operationalizes it at the level of applying direction to filter investment. The two are paired. Direction without filtering produces drift; filtering without direction produces opinion.

What the capability consists of

The capability has three parts: the information it requires, the judgments it makes, and the outputs it produces. Both operating modes — initial filter at Triage, and continuous reassessment thereafter — draw on the same components.

Information required

Strategic relevance is a relational judgment. The capability requires inputs that describe what the portfolio is steering toward and inputs that describe each initiative being assessed.

The first two inputs — themes and environmental interpretations — are produced by capabilities that operate as feeders to assessment. Without them, relevance judgment has nothing to anchor on. A portfolio whose themes are stale or whose environmental scanning is silent will quietly drift into informal relevance judgment, which is the failure mode this capability exists to prevent.

Judgments made

The capability applies four judgments. At Triage they are applied to incoming candidates; in continuous reassessment they are applied to candidates already in the discovery domain and to active initiatives in delivery. The judgments themselves are the same.

Direction fit. Does the initiative connect to at least one active strategic theme or outcome goal, and does that connection still hold? At Triage, plausible connection is sufficient — proof of value comes later. In continuous reassessment the question becomes sharper: has the theme moved, has the outcome goal been recalibrated, has the connection that justified approval weakened?

Level appropriateness. Is this a portfolio-level matter at all? An item that turns out to be a feature for a single value stream, or an operational decision better made at DVS or team level, is not a portfolio investment regardless of its relevance to a theme. Misclassification at Triage produces noise in the discovery domain; the same judgment applies if a candidate’s nature becomes clearer during Investigate.

Articulation sufficiency. Is the problem or opportunity statement specific enough to assess? An item described only as “improve the platform” is not yet an item the capability can rule on — it is a starting point that requires articulation before relevance can be judged. The threshold is low at Triage but real, and the same judgment may surface later if Investigate reveals the original framing was hollow.

Classification reasonableness. Does the candidate’s initial classification — Strategic Initiative or Initiative; business need, enabler, compliance, or strategic — appear consistent with the substance? This is a routing judgment, not a ranking judgment. The classification may be revised in later stages as understanding develops.

In the continuous mode, two further triggers warrant reassessment without changing the underlying judgments: material change in the environment that affects an active initiative’s basis, and outcome evidence that contradicts the LBC hypothesis. Both feed back into the direction-fit judgment — does this initiative still earn the position it holds?

The Triage Group, when convened, applies the judgments and prepares a recommendation. The Triage Group’s composition and operation are documented in Portfolio Kanban Flow and Portfolio Roles. Decision authority rests with the Portfolio Leadership Group, in both operating modes.

Outputs

The capability produces three outputs at three different points in the flow.

Strategic Relevance Assessment produces a Triage recommendation, the relevance input to the Gate 1 decision, and a continuous relevance signal that feeds prioritization and pivot/persevere/stop decisions throughout the flow.

• Triage recommendation — the Triage Group’s output for each registered candidate: proceed to Gate 1, park for later reconsideration, or stop. This is a recommendation, not a decision.
• Gate 1 decision input — the substance the Portfolio Leadership Group acts on at Gate 1. Gate 1 is a relevance filter, not a quality gate; the assessment is the basis for the Group’s go/no-go on entry to the Discovery Queue.
• Continuous relevance signal — the input Initiative Prioritization consumes when re-sequencing the discovery and delivery queues, and the input that informs pivot, persevere, or stop decisions on active initiatives during Investigate, Investment Framing, and Implementing. The signal moves with the assessment, not on a fixed cadence.

What the capability does not produce is an estimate of value, a sizing, or a feasibility judgment. Those belong to Discovery and Business Casing and to Initiative Prioritization. Conflating relevance with value or feasibility collapses the discipline of having a separate filter early in the flow.

How the capability expresses itself

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

Triage is rapid and rule-bound. Candidates are assessed against the same set of judgments each time. A candidate that meets the bar moves; one that does not is parked or stopped. The Triage cycle does not stretch into analysis — analysis is what Gate 1 protects.

Relevance is judged against documented direction, not against inclination. Strategic themes and outcome goals are findable, current, and used. A relevance assessment that cannot point to a theme it engages is not yet a relevance assessment.

Park and stop are real outcomes. A meaningful proportion of candidates do not pass Gate 1. A portfolio whose Triage outcomes are dominated by proceed is signaling either that intake has narrowed too much upstream or that Triage is performing acknowledgment rather than filtering.

Continuous reassessment is part of governance, not an exception. At every Portfolio Kanban Review the question does this initiative still earn its place? is on the table for active items where conditions warrant. At every Portfolio Sync the LBC health check carries the same question. At the Strategic Portfolio Review theme-level shifts surface and propagate to active initiatives whose relevance now reads differently.

Stops are explicit and infrequent enough to be credible. An initiative that no longer fits direction faces an explicit decision. Stops are not the dominant mode — most initiatives proceed to completion — but they are real and visible enough that no initiative continues by default.

Authority and recommendation are visibly separated. The Triage Group’s recommendation and the Portfolio Leadership Group’s decision are recorded as distinct events. A capability that consistently shows recommendation and decision diverging is one where one of the two needs examination.

The capability runs even when direction is uncertain. Periods of strategic ambiguity are not periods when relevance assessment pauses — they are periods when it becomes more cautious, raises more parking decisions, and surfaces strategic-direction questions back to Strategic Goal Management more frequently.

Relationship to other capabilities

Strategic Relevance Assessment sits between intake and the discovery flow, and operates continuously across the rest of the portfolio. Its inputs come from upstream capabilities; its outputs feed the prioritization and discovery work that follows.

Strategic Relevance Assessment consumes direction from Strategic Goal Management, environmental interpretations from Environmental Scanning, and registered candidates from Needs Capture. Its outputs feed Initiative Prioritization and the Discovery work that follows Gate 1.

Upstream — capabilities that feed assessment.

Strategic Goal Management produces the strategic themes and outcome goals that relevance is judged against. The capability does not invent direction; it applies the direction this upstream capability maintains. When themes shift or outcome goals are recalibrated, the next round of relevance assessment carries the new direction forward.

Environmental Scanning provides targeted interpretations on demand: whether a trend is real and sustained, whether a technology is maturing, whether a regulatory development is firm. These interpretations matter most for candidates whose relevance hinges on an external assumption — a market window opening, a competitor’s move, a compliance deadline. Without the scanning input, the assessment has to assume the environmental basis rather than verify it.

Needs Capture registers the candidates that arrive at Triage and supplies their problem statement, source, and initial classification. Capture and assessment are operationally adjacent — capture registers without filtering, assessment filters with strategic context. The discipline of separating them keeps both functions sound.

Downstream — capabilities that consume assessment output.

Initiative Prioritization takes the relevance signal as one of its primary inputs. Prioritization sequences initiatives by economic logic — value, time-criticality, capacity — but a low-relevance initiative does not earn position regardless of its economic profile. Relevance is the upstream check; prioritization is the downstream sequencing.

Discovery and Business Casing takes candidates that have passed Gate 1 and matures them toward Gate 2. Discovery does not re-litigate Gate 1 unless the work itself surfaces evidence that relevance has changed; the relevance judgment Discovery inherits is the Gate 1 decision.

The flow context. Portfolio Kanban Flow is the flow mechanic within which the capability operates — it defines Triage and Gate 1 as flow elements, the Triage Group as a flow actor, and the Portfolio Leadership Group as the formal Gate 1 decision authority. This capability document describes the substance of the relevance judgment those flow elements carry.

The capability and its container. Strategic Relevance Assessment 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 Triage cadence and facilitation, the structure of a Triage recommendation record, theme-mapping mechanics, and the operational difference between an initial relevance assessment and a continuous reassessment trigger. Not yet authored.
• Practice — Portfolio Ways of Working. The Portfolio Kanban Review, Portfolio Sync, and Strategic Portfolio Review are the forums where relevance assessments are made and revisited. Triage and Gate 1 happen in the Portfolio Kanban Review; the continuous LBC-health check is part of the Portfolio Sync; theme-level shifts that propagate to active initiatives surface at the Strategic Portfolio Review.
• Roles — Portfolio Roles. The Triage Group prepares the recommendation; the Portfolio Leadership Group makes the formal Gate 1 decision and the continuous-reassessment decisions for active initiatives; the Portfolio Office prepares the assessment material. Specific responsibilities are documented there.
• Flow — Portfolio Kanban Flow. The mechanics of Triage, Gate 1, the Discovery Queue, and the continuous flow of active initiatives — including the Triage Group’s role and the three Triage outcomes (proceed, park, stop).
• Principle — Value and Outcomes Focus. The foundational position that portfolio decisions are grounded in direction and outcomes, not in activity or precedent. Strategic Relevance Assessment is the upstream filter through which that orientation reaches investment decisions.
• Metric — gap. Triage cycle time, Gate-1 pass rate, and continuous-reassessment-driven stops are candidate measures; specific metric definitions are not yet documented. Known gap.

Sources

• Donald Reinertsen — Principles of Product Development Flow (2009). The economic case for protecting analytical capacity through deliberate early filtering, and the cost-of-queues argument that motivates continuous re-evaluation rather than fire-and-forget approval.
• David J. Anderson — Kanban: Successful Evolutionary Change for Your Technology Business (2010). Explicit gate decisions and the discipline of refusing to allow work to enter the system without conscious filtering — the basis for treating Gate 1 as an active decision rather than a default-pass.
• Patrick Steyaert — Essential Upstream Kanban (2015). The separation of upstream (option discovery and selection) from downstream (delivery) as distinct systems with different purposes — the pattern that places deliberate relevance filtering in the upstream system, and treats it as a function in its own right rather than a logistics step.