Portfolio Simulation Model Template

What this template is for

This Portfolio Simulation Model Template helps teams run transparent, repeatable what‑if analyses across portfolios of experiments, pilots, and scaling projects. Use it to compare trade‑offs between exploration and scaling, expose hidden capacity bottlenecks, surface risk concentrations, and translate strategic intent into allocation experiments you can test and revise as evidence arrives.

Why run portfolio simulations?

• Reveal how resource constraints and timing interact with risk and learning value.
• Compare alternative allocation plans (e.g., more pilots vs faster scaling) using consistent assumptions.
• Identify which projects drive portfolio-level outcomes and merit additional learning or governance attention.
• Turn qualitative trade-offs into structured inputs for governance conversations—without mistaking the model for a final answer.

What’s included

• Portfolio Overview: high-level inputs for time horizon, budget, and team capacity.
• Project Register: a sample sheet listing projects with key fields (type: exploration/pilot/scale, expected duration, nominal cost, required FTEs, success criteria, estimated benefit distribution).
• Assumptions & Risk Profiles: suggested probability distributions for outcomes and failure modes (triangular, normal, lognormal examples) and guidance on choosing sensible ranges.
• Monte Carlo Engine: prebuilt scenario engine that samples assumed distributions across many iterations to show outcome percentiles and likelihoods.
• Sensitivity & What‑If: sliders or parameter cells for quick scenario comparison (e.g., change budget, shift capacity, accelerate a timeline).
• Interpretation Guidance: example decision rules, metrics, and questions for governance conversations.

How to use this template (practical steps)

1. Populate the Project Register with the projects you’re considering. For each project, estimate: expected cost, duration, required team capacity per period, estimated benefit range, probability of technical or market failure, and whether the project’s primary value is learning, optionality, or direct financial return.
2. Set portfolio constraints: enter total budget, available FTEs by period, and any hard scheduling constraints (e.g., regulatory windows, seasonal demand).
3. Choose distributions for uncertain inputs. If you aren’t sure, pick conservative ranges and document the source of each assumption.
4. Run Monte Carlo for a baseline allocation. The engine will iterate across sampled inputs and report distributions for portfolio-level outcomes (total cost, realized value, % projects succeeding, resource oversubscription events).
5. Run scenario comparisons: vary allocation rules (e.g., more pilot funding, staged funding with go/no-go gates, or prioritizing projects with high learning value) and compare percentile outcomes and capacity risk.
6. Perform a sensitivity check to discover which assumptions most influence portfolio outcomes—these are high-value learning targets for pilots or additional data collection.
7. Use results to inform decisions, not replace them: present results with clear caveats about assumptions, and combine quantitative outputs with qualitative judgements and governance rules (gates, contingency reserves, stop criteria).

Example metrics and outputs to review

• Median and 10/90 percentile portfolio value over the horizon.
• Probability portfolio stays within budget and capacity constraints.
• Expected number of successful projects and concentration risk (e.g., few projects delivering most value).
• Frequency of resource oversubscription by period (reveals bottlenecks).
• Sensitivity ranking: which project assumptions, costs, or probabilities most change portfolio outcomes.

Interpretation guidance — how to read and act on results

Use the model to expose trade‑offs, not to prescribe a single allocation. Consider these practical decision heuristics:

• If the portfolio median outcome looks attractive but the downside tail is unacceptably large, consider reserving contingency funding or staging rollout with learning gates.
• If sensitivity analysis shows a few uncertain assumptions dominate outcomes, make those the focus of targeted pilots or research to reduce uncertainty quickly.
• If capacity oversubscription is frequent across iterations, revise timing, hire or reassign staff, or reduce the active project count to protect execution quality.
• Use percentiles and scenario comparisons to set governance thresholds (e.g., require additional approval if downside probability exceeds X% or if a single project accounts for >Y% of expected value).

Common pitfalls (Mal Hungers) to avoid

• Do not treat simulation outputs as precise forecasts or as substitutes for qualitative judgement.
• Avoid overfitting to historical data when the future context is different (market, technology, regulation).
• Don’t use the model to justify biased decisions—document assumptions and alternate views explicitly.
• Beware of freezing allocations: treat results as inputs to an adaptive funding process, not a fixed mandate.

Tailoring the template

Customize the template for your context by:

• Changing benefit definitions (revenue, strategic capability, learning value) and mapping them to consistent units where possible.
• Adding organization‑specific constraints (e.g., compliance reviews, manufacturing capacity, or contractor lead times).
• Incorporating staged funding rules and explicit go/no‑go decision points tied to measurable learning criteria.

Suggested next steps

1. Run the template with one recent portfolio to validate assumptions and refine distributions.
2. Share results in a short governance meeting: present assumptions, two contrasting scenarios, and one proposed adaptive funding rule.
3. Use sensitivity results to design 1–2 rapid pilots focused on the highest‑impact uncertainties.
4. Iterate: update assumptions with pilot learnings and rerun the model to see how allocation recommendations shift.

Files & versioning

The downloadable spreadsheet contains named sheets for all sections above and clear cells for assumptions so your team can version, audit, and adapt the model. Keep a copy for each major portfolio review and record the assumptions used for each run.

Final note

This template is a decision‑support tool: it makes trade‑offs and risks visible so teams can act more confidently and learn faster. Use it to structure conversations, prioritize learning, and make conditional commitments that adapt as evidence arrives.