Portfolio Strategy & Prioritisation
Choosing what to pursue: strategic fit, expected value, evidence requirements, risk, capacity to deliver, interdependencies, real options, and the governance that decides. Portfolio decisions commit regulated capability years ahead of need — and a programme approved without the quality, regulatory and manufacturing capacity to support it does not fail at approval. It fails during scale-up, by which point the alternatives have expired.
What an explainer is not
A topic explainer is SPEQ’s synthesis of what a practice involves, cited to the standards that govern it. It does not reproduce their text, and it does not determine which of them apply to your product or process.
[ POSITION IN THE FRAMEWORK ]
7 DIMENSIONS · 20 LINKSA portfolio is approved against money and people, and fails against capacity nobody counted: the qualification, validation and analytical work every programme needs arrives from the same finite group.
06 · QUALITY MATURITY — PORTFOLIO STRATEGY & PRIORITISATION, REACTIVE TO ADAPTIVE
Programmes are approved individually on their own merits. What they collectively require is discovered during execution.
A portfolio view exists covering spend and milestones, with quality, validation and analytical capacity absent from it.
Constraining capacities are modelled alongside money, so an approval states what it consumes and what it therefore displaces.
Interdependencies between programmes are explicit — shared facilities, methods, people — so a delay in one is visible as a risk to another.
Sequencing is chosen to retire the largest uncertainties first, and an option allowed to expire is a recorded decision rather than a consequence.
SPEQ’s shared five-stage progression, labelled synthesis — not the FDA QMM rating scale. Where does your organization sit? Score your quality system →
07 · REGULATORY & EVIDENCE
GOVERNING STANDARDS · 4
Derived from the 4 standards SPEQ maps to this subject, across 2 regulatory bodies: ICH, ISO.
RECORDS & OBJECTIVE EVIDENCE
- The portfolio view, including quality and validation capacity alongside financial resource
- Approval records stating what capacity each programme consumes
- Interdependency mapping between programmes sharing facilities, methods or people
- Records where a programme was deferred or stopped to protect capacity
- Sequencing rationale, including which uncertainties are retired first
COMMON INSPECTION FINDINGS
- Programmes approved beyond the demonstrable capacity of the quality organisation to support them
- Validation and analytical resource absent from portfolio planning entirely
- Shared facility or method dependencies unmapped, so one delay propagates unseen
- Capacity constraints resolved during execution by shortening qualification
- No record of anything ever being deferred, on a portfolio that is visibly over-committed
Capacity is a portfolio constraint, not a delivery problem
Portfolio decisions are usually evaluated on scientific merit, market opportunity and financial return, with delivery treated as an execution question to be solved later. In regulated industry the binding constraint is frequently capability rather than capital: qualified analytical capacity, validation resource, regulatory affairs bandwidth for the submissions, and manufacturing capacity of the right type.
These do not scale on demand. Qualifying an additional analytical method takes months, a validation team cannot be doubled for a quarter, and manufacturing capacity of a specific type takes years to add. A portfolio approved beyond that envelope does not announce itself — it manifests as every programme slipping slightly, which reads as poor project management rather than as over-commitment.
Interdependency is where portfolio risk actually concentrates
Programmes are assessed individually and share resources, facilities and platform decisions. Three programmes depending on the same pilot plant, the same specialist, or the same novel platform technology are not three independent risks — they are one risk expressed three times, and a portfolio risk assessment that sums individual programme risks will understate it substantially.
The analysis worth running is which single failure would affect the most programmes: a shared platform that does not perform, a facility that does not qualify on schedule, a regulatory precedent that does not go the expected way. Those are the exposures that turn a diversified portfolio into a correlated one, and they are invisible in a programme-by-programme review.
Real options, and the ones that expire quietly
Development portfolios are naturally option-shaped: spend a little to learn whether to spend a lot, and stage-gate governance exists to make that explicit. The regulated version has options that are easy to miss — qualifying a second supplier early, filing a design space wide enough to accommodate a change, running a bridging study while the material is still available.
Each is cheap now and unavailable later, and none appears as an option in a financial model, so each competes badly against near-term spend. Naming them in the portfolio review as options with an expiry date, rather than as optional costs, is what gets them funded — because the expiry is the whole argument.
SPEQ interpretation — quality capacity belongs on the portfolio dashboard
Portfolio governance reviews programme status, spend and milestones. It rarely reviews whether the quality and regulatory organisation supporting those programmes has the capacity the plan assumes — because that capacity is a functional matter, reported through a different line, and usually only when it is already failing.
Putting qualified-coverage and validation-resource load alongside the programme milestones is a small addition to a governance pack, and it moves the conversation from explaining slippage to preventing it. The portfolio decision that most needs this information is the one to add a programme, which is exactly the decision made without it.
FREQUENTLY ASKED
What usually limits a regulated portfolio?
Capability rather than capital: qualified analytical capacity, validation resource, regulatory bandwidth for the submissions, and manufacturing capacity of the right type. None scales on demand, and over-commitment does not announce itself — it appears as every programme slipping slightly, which reads as poor project management.
Why does summing programme risks understate portfolio risk?
Because programmes share resources, facilities and platform decisions. Three programmes depending on the same pilot plant, specialist or novel platform are one risk expressed three times. The useful analysis asks which single failure would affect the most programmes — invisible in a programme-by-programme review.
What are real options in a regulated portfolio?
Cheap actions now that are unavailable later: qualifying a second supplier early, filing a design space wide enough to absorb a change, running a bridging study while the material still exists. None appears as an option in a financial model, so each competes badly against near-term spend unless it is named with its expiry date.
What belongs on a portfolio dashboard that usually is not there?
Whether the quality and regulatory organisation has the capacity the plan assumes — qualified coverage and validation-resource load alongside programme milestones. It is reported through a different line and usually only once it is failing, which means the decision to add a programme is made without it.