Concept prototype
Group Transformation Command Center
One command centre that turns transformation reporting into transformation decisions.
Qhorvane Energy is a fictional Saudi energy company created for this concept. All portfolio data is illustrative. Originally explored with a real operator's branding, then rebuilt around a fictional company so the work could be published cleanly.
The gap
Most transformation dashboards report. They show you 42 initiatives, a budget number, a RAG status, and leave you exactly where you started: knowing the state of things, but not what to do about them.
The people running a multi-billion-dollar transformation portfolio don't have a visibility problem. They have a decision problem. Which initiative do we fund, and which do we kill? What's about to slip, and who needs to intervene? Where is capital sitting that would work harder somewhere else? A status report answers none of that. It hands you the data and makes the connections your job.
So I built a concept of the opposite: a command centre where the strategy, the risk, and the money all resolve into decisions someone can actually act on.
What it does
- Executive command view. The landing surface leads with the six metrics that matter at portfolio level — Vision 2030 alignment, portfolio value, at-risk initiatives, digital maturity, projected ROI, AI adoption — each one a live tile rather than a static number.
- Strategy-to-delivery line of sight. Vision 2030 pillars cascade down through programmes to initiatives, so the connection most organisations lose between "the strategy" and "the work" is on screen. Economic Diversification, Digital Infrastructure, Innovation, Talent Localization, Sustainability — each with its own alignment score and status.
- Investment prioritisation. Every initiative mapped by strategic value against execution risk, so the fund-or-kill conversation becomes visual instead of political.
- Market intelligence and benchmarking. The portfolio set against sector peers, so performance is framed in context rather than in isolation.
- Change readiness and accountability. Who owns what, where the resource conflicts are, and whether the organisation can absorb the change it's committed to.
- A working AI assistant. A chat surface that answers questions about the portfolio in natural language — illustrative here, but shaped like the real thing.
How it's built
Plain HTML, CSS, and vanilla JavaScript. Chart.js for the visualisations, Feather for the iconography, Inter and JetBrains Mono for the type. No framework, no build step — a single file that opens in any browser and deploys as a static asset on Cloudflare.
The intelligence layer is deliberately narrow. The AI assistant's answers and the recommendations you see are illustrative, written to show the shape of the decision support — not to pass off scripted responses as a live model. The structural work underneath (the cascade logic, the benchmarking, the charts) is deterministic. That split matters: a real version would let a model draft the narrative, but the numbers it reasons over would come from source systems, not from the model.
The honest part
The software was never the hard problem. The data pipes are.
A dashboard like this is only as good as what feeds it, and what feeds it lives in a dozen systems that don't talk: the ERP for spend, the PPM tool for schedule, the planning platform for OKRs, the HR system for capability and localisation numbers, the GRC platform for risk. The interface is the easy 20%. The integration — and the governance to keep the numbers trustworthy — is the 80%.
Which is the point of building the concept. It makes a hard-to-fund conversation concrete: here is what a decision-first command centre feels like, from the executive summary down to initiative-level accountability. The interesting question was never "can this be built" — it's "is a transformation office ready to make its decisions this legible."
Why a fictional company
This started as a themed concept built around a real energy operator's brand, the way a designer might mock up a redesign of a well-known product. That's a legitimate way to make a portfolio piece feel real — but it invites confusion about what's official and what isn't, and it puts someone else's trademarks on work that's entirely my own.
So I rebuilt it around Qhorvane Energy, a fictional Saudi energy company. The frameworks are the part that matters, and they're real. The company is invented so the work can stand on its own and be published cleanly. The numbers are illustrative; the thinking is not.
What I'd do next
- Wire one real source first — most likely the PPM tool — so schedule and status are live rather than illustrative.
- Make the assistant real: a model drafting over governed data, with the deterministic logic kept separate so nothing can be hallucinated into a decision.
- Persist decisions — an audit trail of what was approved, by whom, on what evidence.
- Pilot with one transformation office and one portfolio, and see whether the decision-first framing survives contact with real politics.
Built by Shiraz Hussein. Planned with Claude, built with Claude Code, reviewed and tested by hand.