Concept prototype

PMO Strategic Command Center

One executive view of a transformation portfolio — from this week's RAG status up to national strategy.

All data is illustrative. Altair Airways is a fictional Doha-based carrier created for this concept.

The gap

Executive portfolio reporting is usually assembled by hand. Someone pulls delivery status out of Jira, dates out of MS Project, spend out of the finance system, and pastes it into a slide pack the night before the board meets. By the time leadership sees a RAG status, it is weeks old, disconnected from the numbers underneath it, and impossible to interrogate. Ask "why is this amber?" or "which programme actually moves our strategic target?" and the honest answer is another fortnight of analysis.

The bigger gap is strategy. Most portfolio dashboards stop at delivery. They show what is late and what is over budget, but not what any of it is for. In an organisation working to a national vision, that line — from a workstream this week to a 2030 target — is the whole point, and it is almost never drawn.

So I built a concept that draws it.

What it does

A weekly reporting model, not a snapshot. A period selector (Thursday week-endings, the Qatar working week) drives every figure on the screen, and RAG status moves week to week so you see the trend, not just today's colour.
One view, full drill-down. Six programmes, each opening into a weekly status report, milestones with baseline-versus-forecast dates, a workstream-by-week plan on a page, and steering committee decisions and actions.
Attention in one place. Every red, amber, decision-required, and slipping milestone across the portfolio, consolidated — so the meeting opens on what needs a decision, not a tour of what's fine.
Innovation as a governed portfolio. A stage-gate funnel from ideation to scale, where every initiative opens a real business case: problem, benefit model, investment ask, gate criteria, and key risks.
A line to national strategy. The four pillars of Qatar National Vision 2030, mapped to the measurable targets of the Third National Development Strategy, with a matrix showing which initiatives move which goal.
Every number has a source. Each card is tagged to the system it came from, with a panel showing what is automated, what a person maintains, how often it refreshes, and who owns it.

How it's built

The prototype is a single self-contained HTML file — vanilla HTML, CSS, and JavaScript, no framework, no backend, no build step. It opens in any browser and deploys as one static file. That was deliberate: the audience is portfolio leadership, not engineers, and a tool that opens instantly and reads cleanly makes the point better than a build pipeline would.

The architecture it represents is the real one. In production this is a Power BI semantic model sitting over five systems — Jira for delivery, MS Project for schedule, Oracle ERP for finance, Salesforce for stakeholders, SharePoint for governance artefacts — each refreshing on a defined cadence.

The important design decision is the split between what a machine reports and what a person judges. Delivery percentages, dates, and spend are system-fed and never re-keyed. RAG rationale, narrative, risks, and decisions are written by the people accountable for them. That distinction matters: a green schedule carrying a hand-set amber status is not an error, it is a project manager telling you something the raw dates cannot. The dashboard is built to carry judgment, not replace it.

The numbers are real. The airline isn't.

Altair Airways is fictional — named for the navigation star whose Arabic name, an-nasr aṭ-ṭā'ir, means "the flying eagle". That is deliberate. A concept built on a real company's brand can never be published cleanly, and it narrows the work to one employer. A fictional carrier inside a real strategic framework keeps the piece honest, and it makes the method transferable: swap the framework, and the same alignment engine serves any organisation working under a national vision.

What is not fictional is the strategy. The Vision 2030 pillars and the national development targets are researched, not invented — 4% average annual GDP growth, 2% productivity growth, a 46% skilled-worker share of the workforce. A Qatari executive knows these numbers. Make them up and you are caught in the first meeting.

The harder discipline was resisting green. It is easy to build a demo where everything is on track and every bar is full. Nobody trusts that dashboard, because nobody has ever run that portfolio. So the data has real texture: an escalated red programme, amber watch items, milestones slipped between baseline and forecast, a decision sitting unmade. A board pack that is all green is the one the board stops believing.

The honest part

The screen was never the hard problem. The operating model underneath it is.

A command centre does not fix a PMO. It surfaces what the reporting discipline already produces — and if that discipline is weak, the tool just makes weak reporting prettier and faster. Stale inputs, gamed RAG statuses, five teams with five definitions of "done," no clear owner for a number: no dashboard solves any of that. I have seen portfolio tooling fail for exactly these reasons, and never once for a missing feature.

So the point of this prototype is not the software. It is to make "good" concrete — here is what leadership sees, here is the line from a workstream to a national target, here is where every figure comes from — so the real conversation can be about the operating model, the data ownership, and the governance cadence that feed it. The build is the easy part. The reporting culture is the work.

What I'd do next

Wire it to a live Power BI model over the five systems, with role-based security so each viewer sees their slice.
Turn the attention view into push: RAG flips and milestone slips alerted to the owner, not waiting to be noticed.
Add portfolio scenarios: a budget cut, a reprioritisation, a red-programme recovery.
Run it against one real programme's governance data as a pilot.

Built by Shiraz Hussein. Planned and built with Claude, shipped with Claude Code, reviewed and tested by hand.