Adapt a municipal service to a shared channel
The documented wave-one work spans 11 municipal services, with design activity from 19 July to 31 August 2026. Entry points, dashboard and service flows must fit the shared platform without losing the business journey.
This is one shared-channel integration project. It is separate from Montaji+ product development and DubaiNow Housing Fees.
Compare components and journey assumptions
My original status message describes two approaches: the municipal AS-IS experience using Dubai Trade components, versus adopting the Dubai Trade journey. That comparison makes the trade-off visible before detailed redesign.
The work then redesigns wave-one services following final AS-IS agreement and addresses DDA/business feedback. A shared visual component is useful only when the customer and operational steps remain coherent.
| Decision area | Design concern |
|---|---|
| Entry points and dashboard | Make the relevant municipal task discoverable in the shared platform. |
| Shared components | Maintain a consistent channel while retaining the service logic. |
| Business/DDA comments | Resolve feedback against a defined service flow. |
| Approval and UAT | Track readiness by service rather than claim one blanket launch. |
Report the actual service status
The 4 September update records Ship Sanitation feedback closed and Veterinary comments addressed. Two IRS services await UAT after implementation, while one Waste Disposal approval is pending.
The 1 October update records minor developer support required. These are useful dated delivery statuses; they do not prove every wave-one service is deployed.
Shared-channel quality needs traceability
Each comment should connect to the customer step, business rule and revised design. Approval, implementation and UAT are separate gates.
Post-release task success and support measures would establish customer benefit. The current case is a design/readiness story supported by personal progress correspondence.
Outcomes and learning
Wave-one service design scope
The documented result is a shared-channel design scope, an explicit journey/component comparison and dated comment/readiness coordination. Complete release and customer-impact figures are not claimed.
About the evidence
- Original own Dubai Trade design-status and later task-status messages.
- Original Figma file located; detailed current screen inspection is blocked. No invented shared-channel UI is shown.
