Selected workOperating Frameworks
Operating procedures for Digital CX work across four tracks, from new digital requests to life after launch, each with defined review stages, responsibilities, deliverables and timelines.
- Organization
- Ministry of Sport, Riyadh
- My role
- Built the framework and the formal process documentation based on it
- Demonstrates
- Turning cross-functional review work into a clear, repeatable process.
Conceptual illustration. The framework defines review stages, responsibilities, deliverables and service-level timelines. The stage names, functions and path shown here are drawn for this diagram.
1Context
A review only works if everyone knows who does what, and by when.
Digital CX work touches every team that builds a digital product. Requests come from business owners, solutions are built by internal teams and vendors, and national digital-government requirements bring their own deadlines. Every party needed one way of working: when Digital CX is involved, what it checks, who acts on the result and how long each step takes.
2Objective
Define how Digital CX work runs, from the first request to life after launch.
- 1Set out the review stages for each kind of work
- 2Make responsibilities explicit across business, technology and vendor teams
- 3Specify what every stage delivers and the service-level timeline it runs to
- 4Make the unified design system and brand guidelines the reference for design reviews
3My role
I built the framework and turned it into the formal process documentation.
What I did
- Built the Digital CX operating procedures and workflow framework
- Organized the work into four tracks: new requests, pre-launch evaluation, post-launch monitoring and national digital-government requirements
- Defined review stages, cross-functional responsibilities, deliverables and service-level timelines
- Documented the process with flow diagrams and the responsibilities of every party
Working with others
- Developed within the Digital CX team’s wider work on operational documentation
- The responsible department reviewed and approved the process documentation
4Approach
Map the work, define each stage, then write it down formally.
1Map the work
Grouped Digital CX work into four tracks, from new digital requests to national digital-government requirements.
2Define the stages
Set out the review stages in each track, from requirements and prototypes to checks before launch and follow-up after it.
3Assign responsibilities
Made clear what business owners, technology teams, vendors and Digital CX each do at every stage.
4Set deliverables and timelines
Defined what each stage produces and the service-level timeline it runs to.
5Document it formally
Incorporated the framework into formal process documentation, which the responsible department approved.
5Deliverables
A working framework and the formal documentation built from it.
| Deliverable | What it is |
|---|---|
| Digital CX operating procedures and workflow framework | Four tracks of work, each with review stages, responsibilities, deliverables and timelines. |
| Process flows and role descriptions | How work moves between teams at each stage. |
| Formal process documentation | Approved by the responsible department. |
6Outcomes
Outcome
A defined way of working, formally documented.
The framework defines a clear path for Digital CX review, from the first requirements to monitoring after launch. The process documentation built from it was approved by the responsible department.