Portfolio Review Cascade¶
Planning and allocation review — instantiates Layered Coordination Oversight
Reconciles local plans against shared capacity through staged tier-by-tier review — rolling dependencies and cumulative risk upward, pushing funded allocations back down, and deciding only the tradeoffs that truly need a wider tier.
When local units each plan their own portfolio but all draw on the same limited capacity, someone has to reconcile the plans without re-deciding every project. A Portfolio Review Cascade does this in stages: local portfolios roll up into a system view that aggregates dependencies and cumulative risk, the wider tier resolves only the tradeoffs that genuinely cross boundaries, and funded allocations with their rationale flow back down. Its defining job is to allocate shared capacity across competing plans — to decide what gets funded and in what order — while leaving in-scope choices with the local tier. That capacity-allocation purpose is what separates it from the interface that translates a single policy downward and the dashboard that surfaces live operational exceptions.
Example¶
An enterprise runs its annual IT capital planning as a cascade. Teams submit project portfolios with cost, expected benefit, and uncertainty. Business units aggregate their teams' submissions, de-duplicate overlapping proposals, and pass up a consolidated view. Regions surface the cross-unit dependencies and shared-platform contention that no single team could see — three units independently bidding to expand the same data center. Enterprise governance then resolves only those cross-boundary tradeoffs, funds the winning bids, and returns the decisions with rationale and constraints attached. Teams keep authority over their within-budget project choices; nothing forces every project up to the top. The review is deliberately timeboxed so it does not sprawl into a permanent committee. The result is fewer duplicated initiatives, visible tradeoffs, and allocations that arrive in time to act on.
How it works¶
- Collect local priorities before revealing central rankings, where independence matters, so upward evidence is not gamed to match an expected answer.
- Aggregate dependencies and constrained resources into a system view that preserves the exceptions and tail risks a simple total would hide.
- Resolve only cross-boundary tradeoffs at the wider tier, leaving decisions the local tier can own with the local tier.
- Disaggregate and return funded decisions with rationale, constraints, and an appeal path.
- Timebox the review so it fits the capacity budget and does not become an endless allocation ritual.
Tuning parameters¶
- Subsidiarity threshold — how large or cross-cutting a tradeoff must be before it rises; set too low and everything centralizes, too high and cumulative risk hides.
- Aggregation basis — how local plans are combined and normalized; the wrong basis averages away the outlier that mattered.
- Reserved local domain — how much each unit decides without review; wider reserves speed local action but weaken system coherence.
- Review timebox — how long each stage runs; short timeboxes force decisions, long ones invite re-litigation.
- Appeal path — how a unit contests an allocation; a real appeal protects local voice, a nominal one launders central rankings.
When it helps, and when it misleads¶
The cascade fits when local portfolios compete for shared capacity and cumulative risk or dependency emerges only at broader scale, so central allocation needs local feasibility evidence without re-deciding every project.
Its failures cluster around distortion and drag: central rank laundering, where a predetermined central ranking is dressed up as bottom-up review; metric gaming, where units inflate benefits to win funding; local voice loss, where aggregation erases the context that justified a project; and endless review, where the cascade becomes its own bureaucracy. The sharpest technical trap is the aggregate that hides its own variance — the flaw of averages, where planning to the mean of an uncertain portfolio systematically misleads.[1] The guarding discipline is a genuine reserved local domain, sensitivity analysis on the aggregates, a recorded rationale for each allocation, and a firm timebox.
How it implements the components¶
aggregation_and_disaggregation_rule— it rolls local plans, dependencies, and risk into a system view and pushes allocations back down, keeping totals reconcilable to local records.subsidiarity_and_lowest_competent_level_rule— it lifts only genuinely cross-boundary tradeoffs to the wider tier and leaves in-scope choices local.oversight_scope_and_capacity_budget— the staged, timeboxed review matches scrutiny to available attention rather than reviewing every project everywhere.
The cascade allocates capacity across plans; it does not define the exception signals that surface live variance for attention (cross_tier_information_contract — the Management-by-Exception Dashboard) or translate a single policy into local procedure (vertical_coordination_interface — the Policy-to-Practice Translation Chain). Its nearest twin is the Dashboard: the cascade decides how shared capacity is allocated among competing plans, whereas the dashboard decides which live signals deserve a higher tier's attention.
Related¶
- Instantiates: Layered Coordination Oversight — the cascade supplies the staged aggregation-and-allocation loop the architecture uses to reconcile local plans with system capacity.
- Consumes: Multi-Tier Governance Charter — the charter's decision rights fix which tradeoffs are reserved local and which rise for review.
- Sibling mechanisms: Multi-Tier Governance Charter · Federated Coordination Council · Intergovernmental Coordination Compact · Policy-to-Practice Translation Chain · Management-by-Exception Dashboard · Risk-Based Tiered Assurance · Escalation and Return Matrix · Nested Incident Command · Cross-Tier Learning Review
Editorial Notes¶
Form Classification¶
Form family: Protocol, Workflow & Routine
Rationale: The mechanism enacts tiered collection, aggregation, cross-boundary trade-off resolution, and disaggregation of funded decisions with appeal.
Nearest alternative: Decision, Gate & Allocation — Wider tiers make decisions, but the staged review-and-handoff lifecycle is the defining form.
Review outcome: Adjudicated after independent review; high confidence.
Origin Attribution¶
Primary origin: Organizational & Management Science
Origin pattern: Cross-disciplinary synthesis
Present-day reach: Multi-domain
Rationale: Tiered reconciliation of local plans against shared capacity is an organizational planning and governance practice.
Related originating lineages:
- Operations Research — Operations research contributes cumulative resource, dependency, and risk aggregation.
Review resolution: Both blind reviewers agree that organizational management is the primary origin. Reconciliation resolves encyclopedia synthesis disagreement. Formative alternate lineages are retained as operations_research; later breadth of use is recorded separately as domain_reach=multi_domain, while origin_mode=cross_disciplinary_synthesis describes the relationship among origin lineages.
Encyclopedia synthesis: The exact catalogued form synthesizes established practice rather than reproducing a single standard historical label.
Review outcome: Reconciled after independent review; high confidence.
References¶
[1] Savage, S. L. The Flaw of Averages: Why We Underestimate Risk in the Face of Uncertainty. Wiley (2009). Defines the flaw of averages as the planning error produced by replacing uncertain variation with average assumptions. registry ↩