The measurement frameworks that apply to Project Tulip
Two frameworks define institutional excellence for Project Tulip.
Two established frameworks are used to evaluate institutional excellence for federal entities in the UAE — including federal HR authorities like Project Tulip. The RFP explicitly targets readiness against both — Section 4.1 lists this as a stated procurement objective.
Context: the April 2026 Agentic AI mandate.
UAE Cabinet, 23 April 2026: a national framework to transform 50% of government services to Agentic AI within two years. Federal entity leadership will be assessed on pace of adoption.
This does not appear in the RFP text. It sits above it. Any response strategy has to account for it because it shapes what Project Tulip leadership is being held accountable for during the same period as the mandatory phase and the 2027–2029 roadmap.
What this section is establishing.
Three things need to be true for the response strategy to hold.
- Path to the north star, and how to achieve, sustain, and improve.The mandatory scope is one step on a longer path. Reaching a rating is one problem; sustaining it and improving it in the next 2-year cycle is a different problem. The response strategy has to address both — not just the first assessment, but the mechanism that sustains and improves it over successive cycles.
- Optional packages are not add-ons.They are the mechanisms through which the pillars the mandatory scope cannot fully address get addressed. Section 3 identifies which pillars sit in which bucket.
- The timeline is tighter than the RFP's 2029 horizon implies.The Star Rating reassessment cycle is 2 years; the Agentic AI mandate is 2 years. Both compress the sequencing decisions in the 2027–2029 roadmap.
What the analog tells us
Federal entities have moved fast on this framework.
Three documented cases inform how this framework is being achieved and sustained by federal entities in the UAE.
Two patterns worth naming.
- The pace is precedented.Al Dhafra's 4-to-6-star jump in one cycle and EFQM's 3-to-5-star jump in nine months are examples of what the framework rewards when transformation is correctly executed.
- The likely scoring gap is documentation and evidence structuring, not underlying service quality.The EFQM diagnostic ("doing the right things but documenting them wrong") maps closely to what the RFP asks for in M3, M4, and M5.
Pillar Mapping
The mapping is coverage-and-depth, not a coverage checklist.
| # | GSR Pillar | Coverage | Mandatory workstreams that address it | What is deferred |
|---|---|---|---|---|
| 1 | Strategic Alignment | Foundational | M12 (2027–2029 roadmap), M6 (service design framework aligned to Services 2.0) | Ongoing alignment governance beyond the 6-month phase |
| 2 | Customer Focus | Partial | M7 (segmentation, personas, journeys), M8 (VoE/VoS workshop), M9 (satisfaction survey) | Standing measurement — one-time workshop and baseline survey are not a continuous listening system |
| 3 | Services | Foundational | M3 (service definition methodology), M4 (service manual review), M5 (service structure, taxonomy, catalogue, service cards) | Full service-by-service redesign beyond the catalogue-level rebuild |
| 4 | Service Delivery Channels | Partial | M5 (channel framework, customer interaction principles) | Actual channel rebuild — the mandatory scope produces the framework; O11 delivers the transformation |
| 5 | Customer Experience | Partial | M7 (journeys and blueprints), M8, M9 (voice and survey) | End-to-end experience management, mystery shopper, continuous CX measurement |
| 6 | Service Efficiency and Innovation | Foundational | M2 (maturity assessment and quick wins), M6 (framework and design principles including Zero Bureaucracy) | Continuous improvement engine, service innovation lab, live service pilots |
| 7 | People Empowerment | Deferred | M10 (knowledge transfer, handover, 1 month post-delivery advisory) | Full capability building, training curriculum, communities of practice, sustained institutional capacity |
| 8 | Technology Integration | Deferred | M11 (1–3 Agentic AI use case designs) | Actual Agentic AI implementation, channel integration (Bayanati, NCRM, UAE PASS, Tawasul), full digital transformation |
What this mapping shows.
- Three pillars are addressed foundationally.Strategic Alignment, Services, and Service Efficiency and Innovation.
- Three pillars are addressed partially.Customer Focus, Service Delivery Channels, and Customer Experience.
- Two pillars are deferred by design.People Empowerment and Technology Integration.
Current State
What the RFP explicitly states.
- Missing link: Project Tulip's approved service catalogue may not reflect all real services, channels, service owners, or service-like interactions currently in operation.
- Inconsistent naming: The same underlying services appear with different names, groupings, and detail levels across the four channels — Official Service Catalogue (2022), Project Tulip website, mobile application, and HR AI Agent.
- Misclassified items: Some items in these channels are system features, forms, information content, or process steps rather than true services.
- No governance: Project Tulip does not have a governed method for service definition, classification, ownership, or catalogue maintenance.
- Readiness gap: Readiness against national service excellence expectations requires practical maturity uplift during the engagement.
Working hypothesis (committed as our operating assumption).
What we think
The primary scoring gap is likely definitional and documentation-based, not delivery-quality-based.
What supports this
- RFP-stated challenges are all definitional and structural. None describe service quality failures.
- RFP describes channel inconsistency — a documentation problem manifesting as an experience problem — not channel failure.
- RFP's mandatory scope allocates the largest workstreams (M3, M4, M5) to definitional work.
What we don't yet know
- Project Tulip's operational performance data (SLA adherence, case volumes, resolution times).
- Project Tulip's own diagnostic of where the primary gap sits.
- Whether Project Tulip has an existing self-assessment against Global Star Rating pillars.
What happens if the hypothesis is invalidated
Discovery in the first weeks of the mandatory phase tests the hypothesis. If invalidated, sequencing shifts weight to delivery-layer optional packages (O10, O11, O13) earlier. Risk flagged in Section 10.
Findings & Response
Synthesis of the diagnostic and the approach.
What we found
- Documentation is likely the primary scoring gap.Not delivery quality — service definition, evidence structure, and taxonomy are where the mandatory scope earns its scoring impact.
- The mandatory scope addresses 6 of 8 pillars — 2 are deferred by design.People Empowerment and Technology Integration require optional package activation to reach assessment-grade coverage.
- Peer entities have moved multiple star levels within single cycles.Al Dhafra moved 4-to-6 star in one year. The framework rewards disciplined execution — pace is precedented.
- The real timeline is 2 years, not 3.The Star Rating reassessment cycle and April 2026 Agentic AI mandate both compress the roadmap below the RFP's 2029 horizon.
- Project Tulip's stakeholder ecosystem has more texture than G2E/G2G/G2P suggests.Regulatory guidance, service delivery, procurement governance are distinct relationship types — each with different service design implications.
How we respond
- Anchor to "achieve, sustain, and improve" — not one-time achievement.The north star is cycle-over-cycle progress. Section 7 sequences the mechanism.
- Treat mandatory as foundation, optionals as the pillars that complete the response.Two of eight pillars are structurally dependent on optional package activation.
- Prioritize agentic readiness by service band.Start with high-readiness workflows for M11 (Section 6). Scale to O12 across bands (Section 7).
- Sequence bundles so People Empowerment and Digital Transformation activate in 2027.Deferring either loses the mandatory phase's institutional gains and misses the April 2028 mandate window.
- Structure the partnership so consulting-led and AI-led workstreams are visible, not blended.Domain depth and agentic depth are distinct capabilities — sequenced across the work packages in Section 9.
Framework
Grounded in three established models.
- UK Design Council Double Diamond (2005) — four-phase design process (Discover, Define, Develop, Deliver).
- ITIL Continual Service Improvement (CSI) — service management as a repeating measure-analyze-improve loop.
- Services 2.0 — The Emirati Way in Designing Government Services (UAE Government, May 2023) — four paradigms and five service types; mandated by the RFP.
Four layers that continuously reinforce each other — the mandatory phase builds two, optional packages complete the other two.
| Layer | What it is | Draws from | Where it lives in the RFP |
|---|---|---|---|
| Definition | Service definition, taxonomy, ownership, catalogue, service cards. The structural foundation. | Double Diamond (Define phase), ITIL service catalogue management | M3, M4, M5 (mandatory) |
| Insight | Segmentation, personas, journeys, VoE/VoS, satisfaction measurement. The customer understanding layer. | Double Diamond (Discover phase), voice-of-customer research literature | M7, M8, M9 (mandatory) |
| Experience | Channel design, service delivery, journey execution, single-customer-thread orchestration. The delivered layer. | Double Diamond (Develop/Deliver), omnichannel service design literature, Services 2.0 experiential design paradigm | M5 (partial framework), O10, O11 (optional delivery) |
| Intelligence | Agentic AI, predictive analytics, proactive service triggering, continuous learning loops. The autonomous layer — where services shift from reactive execution to autonomous reasoning against policy, data, and stakeholder context. | Services 2.0 (proactive and predictive services), UAE April 2026 Agentic AI mandate | M11 (design only), O7, O12, O16 (optional implementation) |
Agentic readiness — which services enter first.
The April 2026 mandate requires 50% of government services agentic within two years. For a federal HR authority, not all services carry equal readiness.
High agentic readiness
Medium agentic readiness
Lower agentic readiness for the mandate window
The mandatory phase's M11 (1–3 use case designs) should draw its first use case from the High band to demonstrate mandate-aligned progress within the response window. Subsequent optional package activation (O12) scales across bands.
Sequencing
Bundles across 2027, 2028, 2029.
Bundle 1: Sustain & Raise
Activate the People Empowerment pillar and establish the achieve-sustain-improve mechanism across successive 2-year assessment cycles. This bundle is the mechanism by which Project Tulip moves from achieving a rating to sustaining and improving it.
- O8 — Capability Building and Training Expansion
- O17 — Continuous Improvement Program and Advanced Maturity Re-assessment
- O18 — Standing Voice-of-Stakeholder and Satisfaction Measurement Framework
- O21 — Adoption Compliance Audit and Institutionalization Assurance
Which pillars it activates: People Empowerment (deferred by mandatory scope, per Section 3). Also strengthens Customer Focus and Customer Experience by converting one-time VoE/VoS into standing measurement.
Which layers it activates: Strengthens Insight layer (standing measurement) and creates the loop mechanism across all four layers.
Bundle 2: Digital Transformation
Activate the Experience and Intelligence layers of the framework. This bundle is the substantive delivery layer that turns the mandatory phase's framework work into shipped services and integrated agentic capability. O12's agentic integration must be architected with O11's channel transformation. Sequencing them as separate phases risks rebuilding channels twice.
- O10 — Enterprise Service Redesign (Priority Service Waves)
- O11 — Digital Experience and Channel Transformation
- O12 — Agentic AI Implementation and Channel Integration
Which pillars it activates: Service Delivery Channels (partial by mandatory scope, per Section 3), Customer Experience (partial), Technology Integration (deferred).
Which layers it activates: Experience layer (via O10, O11) and Intelligence layer (via O12). The two layers the mandatory scope minimally addresses.
Bundle 3: Later-stage and opportunistic
Useful capabilities that strengthen the framework but are not structurally required for it to run. These are activated based on Project Tulip's evolving priorities, not on structural necessity.
O1 (Expanded EX-SX Operating Model), O2 (Service-by-Service Deep-Dives), O3 (Mystery Shopper), O4 (Digital Maturity Assessment), O5 (Expanded Governance and KPI Framework), O6 (PMO and Change Enablement), O7 (Agentic AI Expansion — additional use cases), O9 (Roadmap Implementation Support), O13 (Live Service Pilots), O14 (Service Innovation Lab), O15 (Operating Model Transformation), O16 (Advanced Analytics and Predictive Insights), O19 (Service Governance Policies), O20 (Service Design Workshops).
Which pillars it activates: Varied — each supports specific pillars but none is structurally required.
Which layers it activates: Varied — many strengthen existing layers rather than activate new ones.
Year-level sequencing (2027 / 2028 / 2029).
The year framework is grounded — the RFP defines the roadmap horizon as 2027, 2028, 2029 (Section 1, cover page). The Global Star Rating reassessment cycle is 2 years. The April 2026 Agentic AI mandate has a 2-year window.
- Sustain & Raise bundle activates in parallel with Digital Transformation start.
- Sustain & Raise: O8, O17, O18 activate immediately post-mandatory. People Empowerment pillar has been deferred through the mandatory phase; capability transfer without standing capability build risks losing the mandatory phase's institutional gains within 6 months. O21 activates once frameworks have been in use for 6+ months (mid-2027).
- Digital Transformation: O10 begins first (service-by-service redesign waves apply the mandatory phase's institutionalized framework). O11 begins mid-year (channel rebuild requires the redesigned services as inputs).
- Digital Transformation bundle at peak activity. O11 (channel transformation) completes. O12 (Agentic AI implementation and channel integration) activates — where the April 2026 mandate lands.
- Sustain & Raise bundle continues. Reassessment (O17) runs against the first cycle's evidence. Standing measurement (O18) informs the reassessment.
- Selective later-stage activation. O6 (PMO) may activate if parallel workstreams create coordination need.
- Second reassessment cycle begins. O17 reassessment informs targeted improvements.
- Digital Transformation deepens. O12 expands agentic coverage. O7 (Agentic AI expansion) activates if the April 2026 mandate has evolved.
- Later-stage packages activate opportunistically based on Project Tulip's evolving priorities and identified gaps.
Deal Shape
Placeholder — commercial framing to be developed with consulting partner input.
Commercial framing for this response — pricing posture, mandatory and optional package economics, milestone allocation, partner economics split — will be developed with the consulting partner's commercial practice.
The 85% technical / 15% commercial evaluation weight (RFP Section 15) is the anchor. Commercial compliance is table stakes; the technical proposal is where the bid is won. The commercial proposal comes together in the final weeks before submission and depends on inputs currently being assembled (see Section 10, Areas to Address).
Work Packages
If the approach is approved, these are the packages to initiate.
| # | Work Package | Lead | Purpose |
|---|---|---|---|
| WP-1 | Discovery framework — hypothesis testing | Consulting-led with AI-assist | Test the definitional-vs-delivery gap hypothesis in the first weeks of the mandatory phase. |
| WP-2 | Framework alignment | Consulting-led | Validate whether Project Tulip has an existing service architecture to align to. |
| WP-3 | Roadmap validation | Joint | Validate bundle logic and year-level sequencing with Project Tulip. |
| WP-4 | Competitive intelligence | Consulting-led | Gather intelligence on likely competitors and precedents. |
| WP-5 | Bid-readiness financial preparation | Joint | Assemble cost base and pricing options for leadership pricing decision. |
| WP-6 | Technical proposal architecture | Joint | Design chapter structure and content plan for the 85% technical score. |
| WP-7 | L1 and L3 discovery process design | Consulting-led | Sector-specific discovery methodology for the methodology chapter. |
| WP-8 | HR transformation framework | Consulting-led with AI extensions | HR authority-specific frameworks for the technical proposal. |
Areas to Address
Risks, unknowns, and decisions grouped by when they need to be resolved.
| Risk / Unknown / Decision | When it blocks | Owner |
|---|---|---|
| Pricing posture decisions | Bid submission | Leadership |
| Financial modeling inputs | Bid submission | Joint |
| M11 investment strategic tension | Bid submission | Joint |
| Diagnostic hypothesis validation | Discovery phase kick-off | Consulting-led |
| Project Tulip operational performance data request | Discovery phase kick-off | Consulting-led |
| Service adoption and awareness data request | Discovery phase kick-off | Consulting-led |
| Project Tulip's own diagnostic starting point | Discovery phase kick-off | Consulting-led |
| Project Tulip's existing pillar-level self-assessment | Discovery phase kick-off | Consulting-led |
| Project Tulip's existing service architecture framework | Discovery phase kick-off | Joint |
| Project Tulip's current Global Star Rating classification | Roadmap validation | Consulting-led |
| MBRGEA category selection | Roadmap validation | Consulting-led |
| Pillar mapping validation | Roadmap validation | Consulting-led |
| Bundle-to-year sequencing validation | Roadmap validation | Joint |
| Bundle contents preference validation | Roadmap validation | Joint |