Digital Services Playbook • Client Project • 2026

Digital Services Playbook

Role

UX Researcher
UX Designer

Timeline

Jan 2026 - Apr 2026

Team

7 people

Scope

User research
Service design
Information architecture

Overview

Making the Region’s service strategy easy for every staff member to use

The Region of Waterloo had a plan to improve its services, but it was too long and technical for the staff who needed it most.

Challenge

Guidance for delivering services was hard to find and harder to use. Staff juggled Excel, Teams, SharePoint, and email to get their work done.

Approach

We started by reviewing six government playbooks, then ran a staff survey and interviewed our client. Those findings shaped a Figma prototype, which we tested with staff in 4 interviews and improved based on their feedback.

Result

A Digital Services Playbook for the staff intranet, with checklists, templates, and search, presented to the Region at our final presentation.

My contribution

I reviewed British Columbia’s playbook for our comparative analysis, contributed to the staff survey questions, and was also in charge of writing our milestone reports, turning our research into clear updates for the client. On the design side, I helped make sure the playbook screens reflected what staff told us they needed, bringing our research findings into the team’s Figma designs.

Problem

The main issue

The Region of Waterloo is growing, and so is the demand for its services. Its Services Transformation Strategy set out how services should improve, but it was long and technical, and hard for staff without a UX background to apply. Without clear, shared guidance, services were delivered inconsistently.

Research

How might we create a service design playbook that is clear and easy to use, and helps employees understand their digital tools, work across teams, and find the right resources while delivering services?

13 •

Staff surveyed

6 •

Playbooks compared

1 •

Client interview

4 •

Testing interviews

1. Comparative analysis

We compared six government playbooks: Toronto, the UK, Ontario, British Columbia, the US Digital Service, and Vancouver. We looked at their structure, usability, level of detail, and practicality. Web-based playbooks were easier to navigate, scan, and keep updated than PDFs.

My review

British Columbia. It was very detailed, and the clickable table of contents and side links to templates and examples made it easy to find related tools. But being a PDF held it back. Some links led to error pages, there was no way to jump back to the table of contents, and opening an external link sent me back to the start of the document when I returned. It was also packed with text, and the few images were blurry.

2. Staff survey

We surveyed 13 employees. I helped author the survey questions, which asked about the tools they use, the difficulties they run into, and what they’d want from a playbook.

3. Client interview

Two of my teammates conducted the client interview, which set the direction. The Region had never had a playbook before, so it needed to reflect Waterloo’s own needs, and its language had to work for both technical and non-technical staff.

Insights

01

Checklists were the top pick for a future guide (11 of 13), followed by visual examples (8) and templates (7).

02

For requests that span departments, not knowing who to contact was the biggest roadblock (5 of 13).

03

No one felt very confident their services were accessible and equitable. 7 of 13 were unsure or not confident at all.

Process

Decisions we made

Web, not a PDF

We considered a downloadable PDF, like British Columbia’s. We chose web because the web playbooks we reviewed were easier to navigate, scan, and keep updated. We gave up offline use and being able to Ctrl+F the whole playbook at once, so we leaned on search to make up for it.

Inside the intranet, not a separate site

IT wanted it staff-only, and staff didn’t want another platform to learn. The tradeoff: no one outside the Region can see it.

Modules, not one long guide

Staff wanted tools they could use on the job, and checklists were their top pick. Without one start-to-finish read, navigation mattered more.

A module grid with a sidebar

We sketched five layouts and chose a grid for the overview, with a sidebar and quick links inside each module. To keep it simple, we kept the layout minimal and added search.

Search that suggests as you type

Our Accessibility Specialist suggested search should work more like Google. So we added suggestions that match existing headings as staff type.

Solution

Our proposed solution

The playbook turns the Region’s strategy into tools staff can use day to day. Modules are organized by topic, and each one has checklists, templates and step-by-step guides. Since 7 of 13 staff weren’t confident their services were accessible, one module covers AODA and WCAG 2.1 AA standards. A sidebar, quick links and search help staff find what they need fast. Anyone on staff can browse, but only logged-in staff can edit.

Deliverables to the client

Interactive prototype

A clickable Figma prototype of the playbook.

Project summary

Our research and the reasoning behind each design decision.

Modular structure

Built to grow, so the Region can add new modules without starting over.

We presented this to the Region at our final presentation.

Reflection

The open-ended questions told us the most

Asking what tools staff use didn’t tell us much new, since all 13 use email. The real problems showed up when people answered in their own words. Staff kept describing waiting: on approvals, on back-and-forth emails, and on finding the right person. One respondent pointed out that “client” means different things across the Region, since for some staff it’s a partner organization. Multiple-choice questions alone would have missed that.

Using BC’s playbook showed me what to fix

Reviewing British Columbia’s playbook meant actually using it, and running into its problems myself. That made the issues feel real in a way a checklist wouldn’t have. Those frustrations backed up two of our decisions: making the playbook web-based, and adding a sidebar table of contents with quick links to checklists and templates.