Google - Making a flexible page builder predictable
An internal tool that lets teams build and publish their own pages. Every new setting added flexibility, and also more ways for things to break. I defined how components, settings and layouts behave, so editors get predictable results and engineers get clear rules to build from.
The problem
Teams needed the freedom to shape each page, but every configurable option multiplied the states and edge cases: how a section behaves on mobile, what the published page shows, and what changes when a setting is switched off. Without shared rules, each feature risked behaving differently.
What I did
Designed component settings, layouts and responsive behaviour with product and engineering.
Specified how each editing choice affects the published page, so what editors set is what visitors see.
Defined the component states between editing and publishing, including the in-between and edge cases.
Made consent changes visible within the workflow, not hidden in settings.
Wrote specifications that connected separate workstreams and surfaced delivery risks early.
Key decisions
Shared rules, not one-offs: the same interaction patterns across components, so new features don't invent new behaviour.
Editor linked to outcome: every setting maps to a visible result on the published page.
States designed up front: the in-between states were specified before build, not discovered during it.
Outcome
A defined set of components and interaction rules, handed over as design specifications for the next stage of delivery. Launch results aren't covered here.
My role: Senior UX Designer (contract, 4 months). Interaction design, component specification and responsive behaviour, working with product and engineering.