Ecosystem-Wide Strategic Visibility
by Designing a Unified Operating Platform
Role & Contribution: Lead Product & Systems Designer — responsible for end-to-end strategic discovery, systems architecture, service blueprinting, and high-fidelity platform design
The Abu Dhabi Department of Health was managing a national healthcare system through disconnected spreadsheets, static presentations, and siloed reporting. I led the design of the Strategy Hub — a unified strategic intelligence platform that connected planning, performance monitoring, risk governance, and benefits realization into a single operating environment for the first time.
Client
Dept. of Health Abu Dhabi
Domain
Healthcare Strategy & Governance
Timeline
6 Months — Discovery to Delivery
My Role
Lead Product & Systems Designer
A National Healthcare System Run on Spreadsheets
Situation
The Department of Health Abu Dhabi oversees a complex ecosystem of public hospitals, regulatory agencies, sector-wide health initiatives, and governance boards. Each entity generated strategic and operational information that was critical to national-level decision making.
Problem
Strategic information was distributed across hundreds of disconnected documents, static slide decks, and isolated spreadsheets. There was no mechanism to understand how a national health directive translated into hospital-level operational actions. Planning teams, execution agencies, and governance boards each operated with a different version of the truth.
Business Impact
Leadership faced a fundamental gap: they could not see the whole system. Decisions about capital allocation, risk escalation, and strategic prioritization were being made on the basis of incomplete, stale, and fragmented information — increasing institutional risk and delaying critical healthcare outcomes for citizens.
Delayed decisions on capital allocation
No visibility across concurrent initiatives
Duplicated effort across planning teams
Increased institutional and clinical risk
Reduced trust in governance reporting
Manual reporting cycles of 6–8 weeks
Beyond Dashboards — Strategy as Systems Design
Initial Ask
"Build a management dashboard that consolidates our KPIs and initiative tracking into a single portal so leadership can see progress."
Observed Reality
The real problem was not visibility of existing data — it was the absence of connected architecture between strategy, execution, risk, and outcomes. Even if all KPIs were visible, leaders would still not understand why performance was degrading or which initiatives were creating dependencies.
Design Reframe
The problem was a systems design challenge. The Department did not lack data — it lacked a common operating model. Our role was not to build a reporting tool but to architect a strategic intelligence environment where every layer of the healthcare system was connected.
Central Design Question
"How might we create a strategic operating environment that enables healthcare leaders to understand, navigate, and govern a national system as an interconnected whole — rather than a collection of isolated reports?"
Mapping the Flow of Ecosystem Strategy
We ran a structured design process across six stages. Each stage was designed to deepen our understanding of how strategy, execution, risk, and performance were connected — or weren't.
Understand
Activities
24 stakeholder interviews across planning leads, clinical directors, governance boards, and operational managers
Stakeholders Involved
PMO, Strategy Division, Clinical Operations, Risk & Compliance
Challenge
Stakeholders had deeply contradictory mental models of what strategy even meant in their context
Mitigation
Used systems-level interview prompts focused on decisions and information flows rather than opinions about tools
Map
Activities
Stakeholder mapping, actor network analysis, strategic information flow diagrams, and current-state service blueprinting
Stakeholders Involved
All functional divisions + external health entities
Challenge
No single person had a complete picture of how information moved across the ecosystem
Mitigation
Assembled composite maps from fragmented interviews and ran validation workshops to surface gaps
Design
Activities
Strategic information architecture, data taxonomy design, platform concept modelling, UX workflow mapping
Stakeholders Involved
Strategy leads, clinical directors, IT architecture team
Challenge
Balancing executive-level simplicity with operational-level depth in the same platform
Mitigation
Designed role-based views with progressive disclosure — executives see aggregated signals, operators see granular detail
Validate
Activities
Interactive prototype testing, structured usability sessions, concept walkthroughs with governance board
Stakeholders Involved
C-suite executives, PMO leads, clinical programme managers
Challenge
Executive users had limited time and low tolerance for abstract design concepts
Mitigation
Used real DoH strategic data to populate prototypes — removing abstraction and making decisions immediate
Implement
Activities
Design system delivery, component library, engineering handoff, sprint review participation
Stakeholders Involved
Development team, product owner, delivery lead
Challenge
Maintaining design intent through rapid development cycles with compressed timelines
Mitigation
Embedded weekly design review checkpoints and maintained annotated spec documentation throughout
Measure
Activities
Adoption tracking, task completion analysis, qualitative feedback interviews, governance outcome review
Stakeholders Involved
All platform users + governance sponsors
Challenge
Defining success metrics for a platform designed to improve strategic decision quality — inherently hard to measure
Mitigation
Co-defined proxy measures: time-to-decision, manual reporting elimination rate, and cross-team data request frequency
Proof of Work
Each artefact below was created to resolve a specific design problem — not to document what we did, but to create shared understanding that moved the work forward.
Stakeholder Actor Network Map
Systems MapThere was no shared understanding of who was making strategic decisions, who was consuming them, and who was responsible for executing them. The actor map made these invisible relationships visible and exposed authority gaps that were causing information to stall at departmental boundaries.
Strategic Information Flow Blueprint
Service BlueprintBefore we could design the platform, we needed to understand how strategy actually moved through the organisation. The blueprint revealed that information passed through seven functional handoffs before reaching a governance board — each handoff was a point of data loss, reinterpretation, or delay.
Current-State Healthcare Ecosystem Map
Systems MappingTo identify where intervention would have the highest systemic leverage. The ecosystem map showed how national health directives connected (or failed to connect) to regional hospital operations and individual programme outcomes.
Executive Mental Model Interviews
Research SynthesisLeadership held contradictory assumptions about what strategic intelligence meant in practice. Capturing these mental models as structured diagrams allowed us to design interfaces that matched how executives actually thought about the system — not how analysts wanted to present data to them.
Platform Information Architecture
IA FrameworkThe system required a taxonomy that could accommodate both macro-level strategic objectives and micro-level operational metrics without losing the traceability between them. The IA framework became the architectural spine of the entire platform.
Prioritisation Matrix — Scope vs. Impact
Design FrameworkSix months was a compressed timeline for a platform of this complexity. The matrix allowed us to make ruthless, defensible prioritisation decisions based on strategic impact to the organisation — not internal team preferences.
Platform Design Slides
Supporting Evidence · 10 SlidesThese high-fidelity platform screens are evidence of the design execution — they are not the story. The thinking that produced them is documented in the sections above and below.
What the Research Revealed
Each insight below shaped a specific design decision in the platform. They are not observations for their own sake — they are the evidence base for every architectural choice we made.
Every department defined "strategic alignment" differently. Finance used fiscal targets, clinical teams used patient outcomes, governance boards used regulatory compliance.
The platform could not assume a single shared language of strategy. Alignment had to be made structurally explicit rather than assumed.
We designed a unified taxonomy — Strategic Objectives → Programmes → Initiatives → KPIs — that forced explicit linkage at every layer. No initiative could exist without a parent objective.
Reporting consumed 60–70% of PMO capacity. Teams were manually compiling performance updates from 12+ data sources every quarter.
The real bottleneck was not decision-making — it was information assembly. Leaders were data-poor not because data didn't exist but because no system aggregated it.
We designed automated data aggregation pipelines with exception-based reporting — surfacing anomalies rather than requiring leaders to read everything.
Risk items were tracked in a separate system to performance indicators. Cross-referencing was done manually, monthly, by a single analyst.
Risk was treated as an afterthought — disconnected from the strategic performance it was supposed to protect. By the time risk was visible, it was too late to mitigate.
We integrated risk registers directly inside the initiative view — every programme showed its active risk posture alongside its performance trajectory.
Senior executives consistently made better decisions when given spatial maps rather than tables. Pattern recognition occurred in seconds; tabular data required minutes of interpretation.
Cognitive format was as important as information content. The same data in a table versus a network map produced fundamentally different decision quality.
We made visual ecosystem maps the primary executive interface — tables and exports were secondary features, not the entry point.
The Strategy Hub Platform
The solution was not a dashboard. It was a strategic operating model made digital — an environment where strategy and execution exist in the same space and inform each other in real time.
Design Principles
One Strategic Source of Truth
A single shared view of strategic objectives, initiatives, and outcomes eliminates version conflicts and ensures all stakeholders make decisions from the same data.
Traceability Across Every Layer
Leaders can move from a national health directive to a regional facility KPI in three clicks — tracing accountability and dependencies without leaving the system.
Risk as a First-Class Signal
Risk is not in a separate register. It lives inside every programme view — visible alongside performance, not filed away in a separate governance portal.
Decisions Over Reports
The platform surfaces anomalies and flags emerging risks before presenting raw data. It is designed to trigger decisions, not just enable data consumption.
Operating Model
The Strategy Hub operates across three layers of organizational intelligence — each layer feeding the next and together forming a closed-loop system from directive to outcome.
Macro Intent
National health strategy directives, sector-wide objectives, SDG and regulatory commitments. This is where the DoH defines what it is trying to achieve and why.
Execution Layer
Programmes, initiatives, capital allocation, and clinical operations. This is where execution teams manage delivery against strategic commitments.
Outcome Harvesting
Benefits realization tracking, performance validation, and governance confirmation. This is where the system measures whether strategy translated into actual healthcare improvement.
Platform Architecture
Platform Architecture — Strategic to Outcomes Flow
Five Interconnected Strategic Workspaces
Each capability was designed because it addressed a specific organisational failure mode — not because it was a standard feature of a healthcare platform.
Strategic Planning
Why This Mattered
Before the platform, strategic plans existed in long Word documents that governance boards could not navigate, compare, or interrogate. Leaders had to be briefed verbally because the plans were not designed to be self-explanatory.
What Was Built
Centralised management of strategic objectives, priorities, initiative registries, and cross-entity alignment. All planning activity feeds into a unified objective tree that every stakeholder can trace.
Measurable Impact
Eliminated verbal briefing dependency. Leaders could review, question, and approve strategic changes directly in the platform.
Performance Monitoring
Why This Mattered
Performance was only reviewed quarterly — at a point when any issues were already months old and mitigation options were limited. Real-time awareness was considered impossible given the manual reporting infrastructure.
What Was Built
Live performance dashboards aggregating KPIs across every programme, initiative, and facility. Anomaly detection surfaces deviations before they become governance issues.
Measurable Impact
Reduced strategic decision latency from 6–8 weeks (manual report cycle) to near-real-time. Enabled proactive rather than reactive governance.
Risk Intelligence
Why This Mattered
Risk registers existed but were isolated from the execution system. A project could be flagged as critical risk in one system while showing green in the performance dashboard — with no mechanism to reconcile them.
What Was Built
Integrated risk registers embedded inside every initiative and programme. Risks are visible alongside the performance data they threaten — with escalation paths, owner accountability, and mitigation timelines.
Measurable Impact
Surfaced 23 previously invisible cross-programme risk dependencies in the initial data migration. Governance board could act on risk before it crystallised into performance failure.
Benefits Realization
Why This Mattered
Healthcare investments were consistently approved based on projected benefits that were never systematically tracked. There was no accountability mechanism for whether promised outcomes were achieved.
What Was Built
A structured benefits tracking environment where every approved initiative declares its expected outcomes at the point of approval — and those outcomes are tracked throughout delivery and post-implementation.
Measurable Impact
Created the first systematic record of health transformation ROI within the Department. Benefit tracking became a condition of capital approval.
Executive Insight Dashboards
Why This Mattered
Executives were spending 3–4 hours per governance meeting reviewing static slide decks. They were passive consumers of information rather than active navigators of it.
What Was Built
Visual-first executive environment with ecosystem maps, portfolio heat maps, cross-programme dependency views, and exception-focused alerts. Designed for 10-minute situational awareness, not 4-hour briefing marathons.
Measurable Impact
Governance meeting preparation time reduced by approximately 65%. Leadership reported significantly higher confidence in strategic decisions made during platform-supported sessions.
What Changed for the Organisation
The platform delivered measurable change at the organisational level — not just functional improvements to a reporting tool.
Governance prep time reduction
Executive meeting preparation reduced from 4-hour brief reviews to 10-minute platform navigation sessions
Decision latency eliminated
Quarterly manual reporting cycles replaced by live performance monitoring with anomaly-triggered alerts
Hidden risk dependencies surfaced
Cross-programme risk linkages identified in initial data migration that had been invisible across siloed registers
Qualitative Outcomes
Greater Strategic Visibility
Leaders gained a consolidated, ecosystem-wide view of all strategic initiatives, risks, performance indicators, and clinical outcomes — simultaneously, for the first time.
Improved Cross-Functional Alignment
Planning units, execution agencies, and governance boards now operate from a shared, consistent framework — eliminating the version conflicts that had previously caused misalignment and duplicated effort.
Standardised Governance Model
The platform enforced a consistent structure for strategic intent, execution risk management, and benefit harvesting — creating institutional process memory that persisted beyond individual personnel changes.
Enhanced Organisational Intelligence
The platform created traceable linkages between national health objectives and clinical impact metrics — making it possible for the first time to answer 'Is our strategy working?' with evidence.
What This Project Taught Me
What I Learned
Strategic transformation is not primarily a technology challenge — it is a systems design challenge. The Department of Health did not lack data, expertise, or strategic intent. What it lacked was a common operating model that allowed all of those elements to work together.
Building the Strategy Hub taught me that the hardest part of platform design in complex organisations is not designing the interface. It is designing the information architecture that makes the interface possible — the taxonomy, the relationships, the data governance model. If the underlying architecture is wrong, the most beautiful interface in the world cannot compensate.
What I Would Improve
We under-invested in change management for front-line operational managers — the people responsible for entering and maintaining data in the platform. The executive layer adopted the platform enthusiastically. The operational layer experienced friction because we had not co-designed the data entry workflows with them early enough.
On the next iteration, I would dedicate a full design sprint specifically to the data stewardship experience — making it as easy and valuable to contribute to the system as it is to consume from it. Platforms like this live or die on data quality, and data quality lives or dies on contributor experience.
How This Changed My Practice
This project permanently changed how I think about what a designer's job actually is on complex enterprise programmes. I no longer believe that a designer's primary responsibility is to design screens. The primary responsibility is to design the mental model — the way stakeholders understand what the system is, what it does, and why they should trust it.
Every system I have designed since has begun not with wireframes but with a systems map — a diagram that shows the relationships between the people, processes, information, and decisions that the platform will need to support. That discipline came directly from the DoH Strategy Hub.