Public Sector Digital Transformation
Designing an AI-Ready Workflow for GOV.OM Design System 2.0
Rethinking the System (The Real Problem)
What we noticed
While building six new components for GOV.OM DS 2.0 (Data Table, Flyout, Add Row, Credit Card Payment, Address, Civil ID), we discovered a deeper workflow issue.
Components were:
• Recreated across ministries
• Duplicated in multiple variants
• Named inconsistently
• Structured manually
• Slow to hand off to development
Complex components like Data Tables required up to:
4 working days in design
5 working days in development
The problem wasn't design quality.
The problem was system architecture.
Deep Dive: Rebuilding the Data Table for Government Scale
The Data Table was the most complex component in this initiative. It needed to support multiple entities, dense operational data, and complex interaction states while remaining adaptable for Arabic-first and RTL environments.
Previously, a component of this scale required:
• 4 working days for design (research, benchmarking, structuring variants)
• 5 working days for front-end implementation
Using ChatGPT, I analysed enterprise-scale data table systems to identify scalable patterns and best practices.
With a cleaned system architecture and structured prompts based on our token documentation, I generated Data Table variants using Figma Make aligned with our naming and design logic. My front-end colleague then used Claude Code to translate the structured output into production-ready components.
The results were significant:
• Design time reduced from 4 days → 3 hours
• Development time reduced from 5 days → 5 hours
More importantly, we established a new collaborative framework:
• AI-compatible naming conventions
• Token-enforced component structure
• Reusable prompt templates
• A documented AI-to-code handoff model
This transformed our workflow from manual component crafting into an AI-accelerated production pipeline.
Rethinking the System (The Real Problem)
What we noticed
While building six new components for GOV.OM DS 2.0 (Data Table, Flyout, Add Row, Credit Card Payment, Address, Civil ID), we discovered a deeper workflow issue.
Components were:
• Recreated across ministries
• Duplicated in multiple variants
• Named inconsistently
• Structured manually
• Slow to hand off to development
Complex components like Data Tables required up to:
4 working days in design
5 working days in development
The problem wasn't design quality.
The problem was system architecture.
Strategic Shift
Instead of “designing faster,” we asked:
How do we design the system so AI can work inside it?
That required cleaning the foundation.