Skip to content

← Library

The library

Capabilities & futures

What capabilities do we need, and what might change?

Explore the practices, capabilities and tools a portfolio might need, with earlier reading, framework guides and clearly labelled future scenarios.

View of the separate capability, maturity and performance example

Facilitation heuristic

Separate capability, maturity and performance

Use a perceived need to suggest one lead service, then choose the portfolio, programme or project levels to address.

Open the example →
What to try & what it leaves out

Try. Choose Performance and apply its levels, then switch to Capability. Compare keeping those levels with applying the new suggestion.

Limits. A fixed conversation heuristic; it does not diagnose a project, perform a P3M3 assessment or validate a service’s suitability.

Earlier example, repaired and reviewed 2 October 2026. This review checks the stated model and interactions; it does not establish usefulness in practice.

GitHub source (may require access)
View of the review portfolio-office capabilities example

Authored discussion checklist

Review portfolio-office capabilities

Assess an editable hierarchy of portfolio-office capabilities, separating confirmed gaps from unanswered questions.

Open the example →
What to try & what it leaves out

Try. Change a current and target assessment, inspect coverage and gaps, then export and reopen your edited hierarchy.

Limits. A discussion checklist, not P3M3 or a validated maturity assessment.

Earlier example, repaired and reviewed 2 October 2026. This review checks the stated model and interactions; it does not establish usefulness in practice.

GitHub source (may require access)
View of the build a more useful programme conversation example

Conversation guide

Build a more useful programme conversation

Choose questions about alignment, working rhythms and benefits, then assemble a portable run-sheet.

Open the example →
What to try & what it leaves out

Try. Filter by role, add questions from two packs and reorder them. Reopen the run-sheet with its follow-ups and coaching notes.

Limits. Authored facilitation prompts, not a validated diagnostic or causal test. Answers need evidence and alternative explanations.

Earlier example, repaired and reviewed 2 October 2026. This review checks the stated model and interactions; it does not establish usefulness in practice.

GitHub source (may require access)
View of the match a task to a capability example

Historical conceptual map

Match a task to a capability

Explore an earlier proposal for connecting task needs with AI capabilities and model choices.

Open the example →
What to try & what it leaves out

Try. Focus or select a capability, read its description, and follow its connections.

Limits. A historical conceptual map, not a current model ranking, benchmark or proof that the suggested combination works.

Earlier example, repaired and reviewed 2 October 2026. This review checks the stated model and interactions; it does not establish usefulness in practice.

GitHub source (may require access)
View of the explore gaps in a capability map example

Geometric search

Explore gaps in a capability map

Edit six capability scores for five firms, compare six pairwise plots and position an entrant in the empty regions.

Open the example →
What to try & what it leaves out

Try. Raise two scores for one firm to 10, then lower one. Watch the empty upper-right region close and reopen before moving the entrant sliders.

Limits. Supplied scores and a 0.1-grid geometric search. Empty areas do not establish demand, feasibility, competitor capability or a commercial opportunity.

Earlier example, repaired and reviewed 2 October 2026. This review checks the stated model and interactions; it does not establish usefulness in practice.

GitHub source (may require access)
View of the follow the changing project-tool landscape example

Sourced historical timeline

Follow the changing project-tool landscape

Read a sourced software timeline and a corrected 2010–2025 controls comparison, separating interpretation from evidence.

Open the example →
What to try & what it leaves out

Try. Trace a milestone, then compare the controls diagram and inspect its placement assumptions.

Limits. Selected events and an interpretive arrangement; connections are not evidence of product inheritance or a forecast.

Earlier example, repaired and reviewed 3 October 2026. This review checks the stated model and interactions; it does not establish usefulness in practice.

GitHub source (may require access)
View of the imagine different project-services markets example

Authored future scenarios

Imagine different project-services markets

Compare three dated, authored stories about project-services markets, including their archetypes and strategic questions.

Open the example →
What to try & what it leaves out

Try. Choose a story, move through its periods, and compare its assumptions with the alternatives.

Limits. Preserved authored scenario narratives, not forecasts or evidence that a dated AGI, ASI or market event happened.

Earlier example, repaired and reviewed 3 October 2026. This review checks the stated model and interactions; it does not establish usefulness in practice.

GitHub source (may require access)
Compare overlapping scenario pressures diagram

Authored scenario model

Compare overlapping scenario pressures

Place authored policy, market and technology scenarios across time and inspect their signed effects on project constraints.

Open the example →
What to try & what it leaves out

Try. Shift a scenario window and compare pressure at a milestone; inspect the opposing effects behind a small net value.

Limits. Authored triangular activations and signed effects, not probabilities, calibrated forecasts or a robust optimisation method.

Earlier example, repaired and reviewed 3 October 2026. This review checks the stated model and interactions; it does not establish usefulness in practice.

GitHub source (may require access)
Shape a useful project service diagram

Service-design worksheet

Shape a useful project service

Turn a service option or use-case question into a scoped artefact, a human review and a testable measure.

Open the example →
What to try & what it leaves out

Try. Compare an ordinary offer with an AI-assisted option, then inspect the evidence needed to know whether either helps.

Limits. Design prompts and candidate measures, not a vendor catalogue, delivered capability or demonstrated performance.

Earlier example, repaired and reviewed 3 October 2026. This review checks the stated model and interactions; it does not establish usefulness in practice.

GitHub source (may require access)

Browse the other Library subjects →