How do you turn a national smart-city vision into a platform that ministries, sector leads and citizens can actually run on?

Qatar is on a national mission to accelerate digital transformation and build smarter, safer, more resilient cities. TASMU is Qatar's national smart-city program — under the Ministry of Communications & Information Technology (MCIT), it needed to move from a collection of independent digital initiatives into a unified, national platform capable of real-time operations, predictive intelligence and coordinated decision-making across sectors.

• Client — TASMU / MCIT, in collaboration with Ooredoo
• Scope — TASMU 1.0 (platform definition) and TASMU 2.0 (Digital Twin, ICCC, Cognitive AI)
• Role — Product & Experience Design Lead
• Team — strategy, technology and experience disciplines

TASMU 2.0 brought together Smart City OS, Digital Twin, ICCC, Cognitive AI, Connected Assets and the TASMU Data Marketplace into one future-facing ecosystem — but the platform had to move from vision to implementation readiness. Key initiatives like Digital Twin and ICCC were progressing independently, governance was inconsistent across ministries, investment was fragmented, and the strategy hadn't yet been translated into an executable roadmap.

• Independent initiatives with fragmented architectures
• Inconsistent governance across entities
• RFPs advancing without unified standards
• Unclear platform identity and value proposition
• A complex ecosystem with multiple owners and providers

Without a clear product structure, experience direction and governance model, TASMU risked becoming a set of disconnected initiatives rather than Qatar's unified digital backbone.

This wasn't a conventional UI project — it combined product strategy, ecosystem design, stakeholder facilitation, platform definition, concept design and future-state prototyping. The first phase focused on understanding TASMU's current state: its ecosystem, sectors, existing channels, products and future ambition.

• Ecosystem mapping — the relationships between sector leads, service providers, partners, MCIT and the TASMU platform team, surfacing friction, unclear ownership and dependency risk
• Channel and offering audit — the current state spanned multiple channels, account areas, APIs, Azure resources, dashboards and more than 36 products and services
• Benchmarking and inspiration — government-managed G2G/B platforms and public digital platforms, studied for GTM practice, UX patterns, onboarding principles and engagement models

A core exercise in TASMU 1.0 was debating each offering through three questions: what is the value of the offering, what should be inside it, and whether it should be monetized — moving discussion from vague ambition to clear product framing. Offering cards captured what it is, who it's for, what's inside, why it's needed and how it would be provisioned, surfacing ambiguity and dependencies that needed resolving before implementation.

The future user landscape was defined by distinguishing decision-makers, TASMU champions and direct platform users — from sector leaders and transformation managers to developers, operators and data handlers — giving a clearer foundation for role-based journeys. Workshops then explicitly prioritized the hero user flows that would guide visual concepting, so the team wasn't designing generic interfaces but focused experiences tied to real operational value.

TASMU didn't have a technology problem. It had an identity problem.

• Lack of clarity in what the platform was — even within government — was limiting adoption
• The value proposition of core offerings like Smart City OS and Digital Twin was unclear and needed translating into tangible sector benefits
• The ecosystem was structurally complex, spanning ministries, sector leads, service providers, partners and platform operators — complexity that had to be made operable through design
• The platform needed to differentiate itself from hyperscalers and OEM tools by acting as a national enabler with governance, interoperability and sector relevance
• The future platform had to serve both strategic leaders and hands-on users, from government decision-makers to developers and operators

Insights from stakeholder workshops were consolidated with focused research — mapping the as-is experience, identifying gaps across services, and gathering global references to inform direction.

• Experience definition — end-to-end user flows for each service, validated iteratively with product owners and stakeholders before moving forward
• Wireframing & interaction design — validated flows translated into detailed wireframes defining layout, structure and interaction patterns
• Design system foundation — components, patterns, typography and visual guidelines established before high-fidelity design, to support a unified, extensible platform

TASMU 1.0 translated a highly fragmented ecosystem into a cohesive platform experience — making it easier for stakeholders to discover offerings, understand value and interact with the platform. These designs established the foundation for TASMU's product vision, directly influencing the scale-up into TASMU 2.0.

“The success of TASMU 1.0 went beyond delivery — it built trust. The client recognized the value of the platform direction and experience strategy, leading to a direct expansion into TASMU 2.0 to scale the vision into a fully realized, AI-powered national platform.”

• Discovery — deep understanding of the TASMU ecosystem, stakeholder workshops, benchmarking global smart platforms, identifying system gaps
• Define — product vision and platform architecture, structured core offerings, defined user groups and roles, established experience principles
• Prototype — end-to-end product flows, concept-driven interfaces, high-fidelity UI and dashboards, AI-assisted design workflows
• Govern — supported roadmap definition, enabled product scalability, aligned design with engineering and implementation teams

Digital Twin — a real-time, interactive digital replica of the city enabling simulation, monitoring and planning: 3D infrastructure visualization, real-time data integration, scenario simulation for traffic, logistics and environment, and decision-support for planners and operators.

ICCC (Integrated Command & Control Center) — centralized monitoring and operational control across sectors: real-time dashboards, incident monitoring and alerts, cross-system data visualization, multi-sector coordination.

Cognitive AI — bringing intelligence and automation into the platform: AI-driven insights and recommendations, conversational and analytical agents, predictive analytics, decision-support systems.

One of the key innovations in TASMU 2.0 was integrating AI into the design process itself — accelerating ideation and concept exploration, generating multiple design directions quickly, reducing iteration cycles significantly, and enhancing quality and consistency across a very large surface area.

Beyond design, the work supported product roadmap definition, alignment with engineering teams, RFP and implementation support, and long-term scalability planning — ensuring TASMU 2.0 was ready for real-world deployment, not just conceptual.

A showcase of how complex, large-scale systems were transformed into intuitive, scalable product experiences — bringing Digital Twin, ICCC and Cognitive AI together into a unified platform for real-time visibility, data-driven decisions and seamless cross-sector operations.

The work moved TASMU Platform 2.0 from abstract ambition toward operational readiness — clarifying the product suite, translating high-level strategy into platform concepts and prototype experiences, and supporting future implementation through governance alignment and roadmap definition. It gave sector-transformation initiatives across Digital Twin, ICCC and Cognitive AI a much stronger foundation.

• Defined the future-state solution suite
• Prototyped key platform experiences
• Brought product clarity to complex offerings
• Supported RFP and vendor-onboarding readiness
• Helped shape a governance-led implementation path

• National-scale design needs ecosystem clarity before interface polish
• Great platform design starts with value definition, not screen production
• Workshops aren't ceremonies — they're decision-making tools
• AI is most powerful when it increases exploration and strategic clarity, not just output speed
• Design becomes most valuable when it shapes implementation, not only concepts