The Scenario
A technology services company runs between fifteen and twenty-five active projects at any given time. There is a project management office of three people responsible for portfolio oversight: tracking progress, flagging risks, managing resource conflicts, and reporting to the leadership team.
Each project manager uses the company’s project management tool, but they use it differently. Some maintain detailed task breakdowns with percentage-complete estimates. Others work at a higher level with milestone tracking. A few treat the tool as a task list and track progress in their own spreadsheets. The PMO has tried to standardise usage but has met resistance from project managers who argue that different project types require different approaches.
The PMO lead produces a weekly portfolio status report. It takes her an entire day. She logs into the project management tool, reviews each project, cross-references with the time tracking system, checks the finance system for budget consumption, and compiles everything into a spreadsheet that she colour-codes by status. Red, amber, green. The spreadsheet is emailed to the leadership team every Friday.
The problem is that by Friday, the status is already out of date. And the colour coding is subjective — the PMO lead assigns RAG status based on her interpretation of incomplete data. Two people looking at the same project could reasonably assign different colours.
The Problem
Portfolio visibility is a function of the PMO lead’s time and judgement, not a function of the system. This creates three distinct problems.
The first is speed. The weekly cadence means that a project can move from green to red in the five days between reports. A resource conflict that emerges on Monday is not visible to leadership until Friday. A budget overrun that starts on Tuesday is not flagged until it has had four days to compound.
The second is objectivity. RAG status is assigned by a person, not calculated from data. This means it is influenced by relationship dynamics, optimism bias, and the information the PMO lead happens to have at the time. A project manager who communicates proactively might get a green rating despite being behind schedule, while a quieter project manager with an on-track project might get an amber rating because the PMO lead has not heard from them and assumes the worst.
The third is resource visibility. With twenty projects drawing from a shared pool of developers, designers, and consultants, resource conflicts are inevitable. But they are invisible until they cause a problem. Two projects scheduled the same senior developer for the same week. Neither project manager checked with the other because there is no shared view of resource allocation across the portfolio.
The Approach
Digital Royalty builds a portfolio dashboard that aggregates project data from the existing tools and presents it in a unified, real-time view.
The dashboard connects to the project management platform, the time tracking system, and the financial system. It pulls task progress, logged hours, milestone status, and budget consumption automatically. The PMO lead does not need to compile anything manually.
RAG status is calculated rather than assigned. A set of rules determines the colour: if a project’s budget consumption is more than ten percent ahead of its timeline progress, it moves to amber. If a milestone is overdue by more than five working days, it moves to red. The thresholds are configurable and the PMO lead can override any calculated status with a manual assessment and a note explaining why. But the default is objective.
A portfolio summary screen shows every active project on a single page: name, project manager, current phase, calculated status, budget health, and next milestone. The leadership team can see the shape of the portfolio at a glance without opening a spreadsheet or waiting for a Friday email.
A resource allocation view shows the shared team’s commitments across all projects for the current and next four weeks. Conflicts are highlighted automatically. Project managers can see before they schedule someone whether that person is already committed elsewhere.
A trends view tracks portfolio health over time: how many projects are green, amber, or red each week; average budget variance; milestone adherence rates. This turns the portfolio from a snapshot into a story.
The Outcome
The Friday reporting ritual shrinks from a full day to an hour. The PMO lead still reviews the dashboard, adds context where the data does not tell the full story, and prepares commentary for the leadership meeting. But the mechanical work of data gathering and compilation is gone.
Calculated RAG status proves more reliable than subjective assessment. In the first month, the system flags two projects as amber that the PMO lead would have rated green based on the project managers’ verbal updates. Investigation reveals genuine issues: one is burning budget faster than planned, the other has a critical dependency that has not been actioned. Both are addressed before they escalate.
The resource allocation view prevents three scheduling conflicts in the first six weeks. Project managers start checking the view before committing their team members to new work. The number of “I did not know they were already booked” conversations drops significantly.
Leadership meetings change in character. The portfolio summary is visible on screen during the meeting. Instead of the PMO lead presenting each project in sequence, the leadership team focuses on the amber and red projects and discusses what needs to happen. Green projects are acknowledged and moved past. Meetings that used to run ninety minutes finish in forty-five.
Over a quarter, milestone adherence across the portfolio improves from seventy-two to eighty-six percent. The improvement is attributed to earlier visibility into problems and better resource allocation, not to working harder.
Who This Applies To
This scenario is relevant to any organisation managing more than five concurrent projects with shared resources. It applies to technology companies, professional services firms, agencies, construction businesses, and any operation where a portfolio management function exists — whether formally as a PMO or informally as a person who tries to keep track of everything.
If your portfolio status depends on one person’s weekly compilation effort, or if resource conflicts between projects are a recurring theme, this pattern provides the infrastructure to manage both.