Google

User education for a data access platform

A user education strategy for an internal data access platform preparing to onboard many new users.

Problem
Help for the platform was scattered, inconsistent and often out of date. People looked for it only once they were stuck, and new users had no clear path to becoming confident with the tool.
My role
Led the user education strategy over about a year, working with UX research, product, engineering, support and content partners.
Key decisions
  • Audited what already existed before designing anything new.
  • Used a cross-functional workshop to agree on the problem and the learning themes.
  • Made contextual guidance inside the product part of the plan, alongside documentation.
Outcomes
A user education strategy and playbook, designs for onboarding and in-product guidance, and pilots of new resources. The work was designed to raise proficiency and reduce support load; I do not have measured results to report.

Context

Lead Product Designer · Q4 2023–Q4 2024

Services: Design strategy · Research & testing · UX/UI design · Workshop facilitation · Stakeholder communication

This work was on an internal tool, so every screen on this page is a reconstruction with placeholder data. The patterns are real; the names and layout details are not.

The problem

As the platform prepared to bring on a large number of new users, we had to think about how people learn about it, find it and become proficient with it.

What existed wasn't set up for that. Help content was spread across several channels, so people struggled to find what they needed. Years without a shared approach had left it inconsistent in tone, style and quality. Most people only went looking for help when something went wrong, rather than being guided toward good practice from the start. New users had no structured path, and there was no good way to tell whether any of the existing material was working.

My role

  • I drove the overall strategy, including goals, audiences and how we would measure success.
  • I ran a content audit and gap analysis of the existing material.
  • I planned and led workshops with product, support and content partners.
  • I designed wireframes, mockups and prototypes for onboarding, in-product guidance and a new help hub.
  • I set standards for how education content should be written and delivered, and wrote them up as a playbook.
  • I presented strategy, findings and designs to stakeholders and leadership throughout.

I also partnered with the company's central accessibility team on a research study about onboarding for people with cognitive differences and people who use assistive technology.

Process

Discovery and alignment

I started by defining scope and goals with the team, gathering what each group saw as the current problems, and systematically reviewing existing material for strengths, gaps and inconsistencies. I also looked at how other teams approached user education. That produced a first version of the strategy.

The audit found that a large share of the content was out of date or inconsistent in voice, and most of the tasks people most needed to complete had no clear documentation.

Getting user education onto the roadmap took advocacy before it took design. I pushed to start research early enough to shape 2024 planning, then ran a prioritization workshop with PM, engineering and research partners: a problem statement, "what's on your radar," theme grouping, a creative matrix, visual voting and an importance-versus-difficulty matrix. The output became a ticketed backlog the team could actually pull from.

Auditing the request journey

I also went through the access request flow step by step, listing what to fix at each stage and what we still needed to learn. Some of it was language, like a button that didn't make clear it led to a request. Some of it was structure, like a page that showed an error before anyone had done anything, or a hand-off to another tool with no explanation. After submitting, people needed next steps, who had to approve, and where to check status.

data-access-tool / research / request journey

Requesting access, step by step

1Access denied

Fixes

Say clearly why access was denied

Explain the hand-off before sending people to another tool

Open question

How many people use the "More info" button?

2Request page

Fixes

Pare down a visually overwhelming page

Don't show an error before anyone has acted

Open question

Where would people expect the request button to be?

3Confirmation

Fixes

Add next steps and who needs to approve

Explain where to check status

Open question

Can people reopen this after closing it?

4Waiting

Fixes

Send an email at each step, from submitted to expiring

Open question

How do people get back to check their status?

Fixes and open questions at each stage of requesting access. Reconstructed with placeholder content.

Workshop and strategy

I facilitated a cross-functional workshop with persona reviews, journey mapping, "How might we" questions and solution brainstorming. Two findings stood out. The concept people struggled with most was how the underlying data was structured and how that affected finding and requesting it. And people preferred to learn hands-on, through interactive tutorials, over reading.

Themes like just-in-time learning and personalized learning paths came out of the same session. Stakeholders also asked for one organized, central knowledge base and more video.

I pulled the research, workshop output and strategy into one plan covering vision, audience segments and their learning needs, content pillars, formats, channels and tone, and a measurement plan.

Design

From the plan, I designed the first set of interventions.

A central, searchable knowledge hub with clearer navigation and categories.

data-access-tool / help

What do you need help with?

Search guides, tutorials and videos

Getting started

Set up and learn the basics

Finding data

Search, filters and attributes

Requesting access

Choose a role and send a request

Approving requests

Review what a change affects

Managing policies

Create and maintain access rules

Troubleshooting

Fix common problems

Popular:Find the right role·Check a request's status·What attributes mean
The knowledge hub. Reconstructed with placeholder content.

Onboarding paths for different roles and goals, from first setup to core tasks.

data-access-tool / get-started

What brings you here?

I need access to data
I approve requests
I manage data policies
Your pathStep 3 of 5
✓Set up your profile
✓Find your first role
3Send an access requestStart
4Check your request status
5Narrow results with filters
An onboarding path for someone who needs access to data. Reconstructed with placeholder content.

Short, contextual tips inside the product, shown when a person reaches a relevant feature.

data-access-tool / roles
Search roles, descriptions, or data sources
Team ▾Eligible to request

New: narrow your search

×

Filter roles by team or by whether you can request them, so you only see what applies to you.

Not nowTry it
An in-product tip introducing new search filters. Reconstructed with placeholder data.

Templates for tutorials, guides and videos so new content stays consistent.

data-access-tool / help / templates

Content templates

One voice and one structure across every format.

Tutorial

Learning goal

Before you start

Step by step

Try it yourself

What to learn next

Guide

Who this is for

Overview

Key terms

How it works

Related guides

Video

Learning goal

Intro

Walkthrough

Recap

Transcript

Templates for each content format. Reconstructed with placeholder content.

Empty states that explain a concept and prompt the next action, so a blank page still teaches something.

data-access-tool / my access
HomeMy accessApprovalsRolesPolicies

No roles yet

Search for a role and request access. Once you're approved, your roles and their status show up here.

Find a role

Nothing to approve

When a policy is created for your team, it shows up here for your approval.

Learn more

No data registered

Register your data to make it available for new access policies.

Register data
Empty states for three pages. Reconstructed with placeholder content.

What we heard

Research sessions in early 2024 turned up a pattern that reframed the problem. People learned the platform from their teammates, not from us — they used it because their team did, and most didn't know in-tool help existed. They asked for step-by-step instructions with visuals and for a heads-up when features changed.

That shifted the strategy from "write better docs" to "meet people where they already learn": visualizations of workflows, impact explained in context at the moment of a decision, and education that doesn't all have to happen up front.

Execution

In the final phase we worked with partner teams to produce new content from the designs, piloted the first resources to get feedback, and set up tracking so the strategy could be adjusted based on how people actually used it.

We ran two pilots of early resources, partnered with UX engineering on A/B tests and iterations, and tracked each piece of work in the team's ticketing system so it didn't live only in a strategy doc. I presented the findings and direction to the wider UX org and cross-functional partners at our 2024 onsite.

Where it landed

The strategy was designed to help people become proficient faster, cut avoidable support requests through better self-service, and give the team a sustainable way to keep education content current. The playbook was written as a resource other teams could use. These were the goals of the work, and I don't have measured results to report for them.

The components were built and the content standards were in place. In 2025 the program was paused before we could measure results, but the playbook, templates and research stayed with the team.