The Quarterly Portfolio Board That Cannot Decide
The Northbridge City Council has a Transformation Portfolio of 28 projects with a three-year budget of £64 million. The Portfolio Board is chaired by the Director of Finance and meets quarterly. The Chief Executive has attended once in 12 months. Project sponsors are middle managers who control neither budget nor staff. In the last quarter, three projects changed scope without board approval; two have overspent, by 12% and 8% respectively. The board agenda is dominated by RAG status reports and exception escalations. A new statutory duty on adult social care arrives with an unfunded £3 million implementation cost. The Head of the Portfolio Office asks whether to add it to the existing portfolio or set up a separate programme, and whether the board needs to change. The council's corporate plan names 'digital and preventative services' as its top priority, but the portfolio contains 11 projects not obviously linked to it.
1. Which MoP principle is most clearly under strain, and what specific actions would you recommend to the Portfolio Board? Justify why other candidate principles are less central.
Read the worked answer
Senior Management Commitment is the principle under most strain. MoP treats it as visible, active and sustained leadership: the CEO attending once in a year, sponsors without budget or staff authority, and a quarterly board focused on RAG all point to commitment that is nominal rather than active. Governance Alignment is also weak, but largely as a consequence: the board's terms of reference and delegated decision rights are unclear, which is why scope changes bypass approval. Strategy Alignment is visible as a symptom in the 11 unlinked projects, not the root cause. Portfolio Office exists but is not the main gap.
Actions: (1) the CEO should chair or co-chair the board and attend at least monthly; (2) redefine the sponsor role so sponsors have explicit budget and resource authority, or move sponsorship up a level; (3) reset the board's terms of reference and decision rights, including a rule that scope changes above a defined threshold require board approval. These are not cosmetic: they change who decides. I would also publish the decision log so the organisation can see that the board is exercising authority.
2. Should the new statutory duty be added to the existing portfolio or managed as a separate programme? What does MoP's Strategy Alignment principle imply?
Read the worked answer
Add it to the portfolio, at least initially, and use the portfolio's prioritisation and balance processes to decide its impact. A separate programme would remove a mandatory £3 million commitment from the portfolio view, making capacity and funding look better than they are. MoP's Strategy Alignment principle requires an explicit line of sight between every initiative and strategic objectives; a statutory duty is a 'must' for prioritisation, but 'must' does not mean 'unfunded and outside the portfolio'. The board should assess the £3 million against existing commitments and decide what is displaced, deferred or stopped. If the duty needs a distinct delivery structure, governance and benefits profile, a programme may be the right delivery vehicle, but it should still sit within portfolio oversight. The 11 projects not linked to the corporate plan should be reviewed at the same time: they are the obvious source of funding and capacity. The test is not 'separate or not' but whether the board can see the whole picture before it decides.
3. The board spends most of its time on RAG reporting. What should a portfolio board focus on, and how would you rebalance its agenda?
Read the worked answer
A portfolio board should spend most of its time on decisions that only it can take: strategic alignment, investment prioritisation, balance, benefits realisation, risk appetite and resource capacity. RAG reporting is a management-control activity for project and programme boards; the portfolio board needs a consolidated view of exceptions and trends, not a project-by-project readout. I would rebalance the agenda to: (1) external and strategic context; (2) portfolio-level performance and benefits dashboard; (3) capacity and constraints; (4) key decisions and trade-offs; (5) risk and assurance; (6) a short consent item for delegated RAG exceptions. Project RAG should be handled at delivery boards and escalated by exception. This change reinforces Senior Management Commitment and Governance Alignment: the board exercises decision rights rather than receiving information. It also reduces the meeting time spent on detail that does not change portfolio value.