Pacing
Delivery against time: the volume bar and the time bar side by side. The gap between them sets the situation.
Do
- Show both bars with their percentages.
Don’t
- Show volume without time: 40% means nothing on its own.
Case study · Ogury · 2021–2025
Four years to go from one designer and four legacy platforms to a design team, a design system and one product.
Ogury’s products were spread across four legacy platforms. Design was one person, a web designer by background, and there was no design system, only an old design kit.
Built and led the design team, as Lead then Director: mentoring, sprints, rituals and design QA. Built the design system from scratch, the atomic way, in Figma and Storybook, moved every application onto it, and created a new brand with Marketing. Ran the platform audit, the workshops and the beta tests behind Ogury One, and designed its Persona Builder end to end.
One product, Ogury One, in place of four platforms, on one design system and one brand. Its Persona Builder, shown at Cannes Lions, brought in more than thirty clients. A design team of three with clear ownership, rituals and delivery standards, and design at the table for org-level and roadmap decisions.
Orders of magnitude, estimated in hindsight.
The changes play on the screen above, the problem first and then the fix. Pick one to see it again.
When I joined Ogury in October 2021, its products were spread across four legacy platforms. Design was one person, a web designer by background who had moved into product design, and the previous lead had just left.
Ogury builds advertising technology. There was no design system, only an old design kit. The unified product came last: it was possible because a structured team and a shared design system came first.
My first fifteen months, as Lead Product Designer, went into building the team and its tools.
I started with one designer, a web designer by background who had moved into product design, and mentored this designer to senior level. I brought in two freelancers to help me set everything up, and built a team of two product designers and a motion designer who also did product design. I also worked remotely with three colleagues based in Poland.
When I arrived, I drew up a plan in two streams. For the interface: a first version of the design system, the same look and feel across the platforms, faster mockups, and alignment with Marketing’s brand guidelines. For the experience: review the existing screens, workflows and user stories, prototype, then test with internal users (admins, ad ops) and external ones (agency admins, trader managers), and loop until the friction was gone.
I moved design from Sketch to Figma, and introduced sprints, rituals and roadmap-driven planning with Product and Engineering. Each designer owned product areas, reviewed every half-year: one senior designer the Supply offer, the other several Demand modules. I kept Persona & Insights and the settings, and reviewed key deliverables so both offers stayed consistent.
designer, a web designer by background. The previous lead had just left.
freelancers I brought in at the start.
two product designers, one of them the first designer, mentored to senior level, and a motion designer who also did product design.
From an old design kit to a complete design system, with every application migrated onto it, and a new brand identity built with Marketing.
When I arrived, there was no design system, only an old design kit. I built one from scratch in Figma, documented and automated in Storybook, so that designers and developers worked from the same components, then migrated every application onto it. As Director, I extended it into a complete system, from atoms and molecules up to the navigation, and worked with the marketing team on a new graphic identity and tone of voice. Ogury One was built on both.
The system was built on Ant Design and customised step by step: Ant where possible, an extension only when needed. Its four principles were consistency, scalability, clarity and pragmatism. Figma was the source of truth for design, Storybook for code, Confluence for documentation, and the Figma side lived in three libraries: Foundations, Web and Layouts. Tokens, components and Figma kits were looked after on the design side, Storybook on the front-end side, and I arbitrated shared patterns and priorities. Designers and engineers alike could propose a component.
ogury one
Design system
Red Hat Text
$1,284,560Tabular figures
Fields
Status
Situation
[Deal] 204391FR_Ostrale_Cartaline_Black Friday
Underdelivering10 pts behind
| Name | Status | Situation | Pacing | Budget | Actions |
|---|---|---|---|---|---|
| [Deal] 204391FR_Ostrale_Cartaline_Black Friday | Live | Underdelivering | $120,000 | ||
| [Line item] 311842FR - Corvenne - Velmont - Velmont Auto | Live | On track | $95,000 | ||
| [Deal] 204277FR_Lyrae_Solenne Paris_Winter | Live | Overdelivering | $70,000 |
Pause a line: the status, the counts and the toast follow.
Live campaigns
426 underdelivering
Impressions this month
214.6M12.4% vs Sep
In January 2023 I became Director of Product Design. The job moved from running a team to shaping how design works across the company.
I led and I designed: while managing the team, I kept the most sensitive projects for myself and stepped in when a topic got difficult.
With the team and the system in place, the four platforms could become one B2B product.
We worked in five steps, from understanding what existed to delivery. Ogury One shipped with the new design system, brand identity and tone of voice, and reworked user flows.

After analysing how the four platforms were built, we ran workshops with their users.
What they said and did went on the wall, then into themes that guided the design of Ogury One.
The research in numbers: at least thirty workshops, with everyone who contributes to a campaign, from the person implementing the tags to sales, by way of business analysts; internal beta testers and three or four clients; at least twelve iterations of the Persona Builder.
Is it on track?
What we took from it
Say in words whether a deal is on track, then show the numbers behind it.
Four tools, one job
What we took from it
One product, one navigation.
Setting up blind
What we took from it
Show the forecast while the line item is being set up.
Same thing, different names
What we took from it
One design system and one vocabulary across the product.
Prototypes went first to internal beta testers, then to three or four clients.
Finding beta testers among clients was hard: their teams already work in Google Ad Manager and are not keen to adopt one more tool. So we tested mostly with internal teams.
After launch, I watched session replays in Datadog, and the team did the same every week: whatever blocked users became the next piece of work.
Adding a line item is a good example of what came out of it: you see what you are setting up, and what it will deliver, before anything goes live.
The changes play on the screen above, the problem first and then the fix. Pick one to see it again.
A big project of its own, which I designed end to end: the Persona Builder.
Ogury targets personas rather than individuals. In Ogury One, the Persona Builder turns a campaign brief, written as plain text or as keywords, into the most relevant personas. The advertiser then refines the audience, combines personas and saves it for their campaigns.
I owned the Persona & Insights module, with Ogury Personas, My Personas and post-campaign insights, and designed the Persona Builder from the first prototypes, which we tested, to delivery. Shown as a demo at Cannes Lions 2024, it launched with Ogury One in April 2025 and brought in more than thirty clients. The trade press covered it.
For Cannes Lions, there were less than two weeks left. I designed a prototype in Figma, polished enough for that demo. It helped win clients. Once the design system was in place, delivery got fast, and we could ship many more projects. The Persona Builder went through at least twelve iterations. On this project I also acted as product manager and carried the business side.
New persona
Personas & Insights
Access all saved personas for future targeting.
| ID | Name | Account | Brand | Country | Reach | Last update | ||
|---|---|---|---|---|---|---|---|---|
| 418203 | Lyrae | Kerlys | France | 3.5M – 4.3M | Oct 22, 2026 | 418203 · France · Lyrae · Kerlys | Oct 22, 2026 | |
Targeting details I want to target Eco-minded parents or New parents | ||||||||
| 417966 | Mirevale | Brightwater | United Kingdom | 1.9M – 2.3M | Oct 9, 2026 | 417966 · United Kingdom · Mirevale · Brightwater | Oct 9, 2026 | |
Targeting details I want to target Frequent flyers or Luxury shoppers | ||||||||
| 416540 | Ostrale | Cimaise Home | France | 7.5M – 9.1M | Sep 30, 2026 | 416540 · France · Ostrale · Cimaise Home | Sep 30, 2026 | |
Targeting details I want to target DIY home improvers or Home cooks but not Students | ||||||||
| 415872 | Lyrae | Solenne Paris | Italy | 3.8M – 4.7M | Sep 18, 2026 | 415872 · Italy · Lyrae · Solenne Paris | Sep 18, 2026 | |
Targeting details I want to target Beauty enthusiasts or Luxury shoppers | ||||||||
| 414309 | Corvenne | Rivage Mobilité | Spain | 390K – 470K | Sep 4, 2026 | 414309 · Spain · Corvenne · Rivage Mobilité | Sep 4, 2026 | |
Targeting details I want to target City commuters or Young professionals and must be Tech early adopters | ||||||||
No persona matches your filters.
Targeted country
France
Launch of our new lightweight running shoe this spring. We want to reach people who run in the city, from regular joggers to marathon finishers, and sporty young professionals aged 25 to 34 who train several times a week.
I want to target
Urban runners or Young professionals or Fitness regulars or City commuters
You can select up to 5 personas to define your final persona.
This list of personas targets the audiences you want to reach. You’ll target either persona #1, persona #2, etc. Note that some audiences may be present in several personas.
Matched in your brief running shoe
, run
, city
, joggers
, sporty
, young professionals
This list of personas will intersect the personas present in OR with those present in this list. This will ensure that you target audiences that are also in the persona below.
You can select up to 1 persona for this section.
The persona in this list will be taken out of your audience. This will ensure that you don’t target the audiences of the persona below.
You can select up to 1 persona for this section.
Potential monthly user reach: 12.3M – 15.0M.
The dot represents the national average
Estimates based on the last 30 days.
The Persona Builder once the brief of a running-shoe launch has been translated: the recommended personas are pre-selected and the reach is estimated.
Three choices made the difference.
I left Ogury in 2025 and have been working freelance since.
Rituals I set up, and a playbook written down for everyone: how work comes in, how it moves, how it gets checked.
Requests came in as Jira tickets with their context, success criteria and deadline, never as a Slack message, and moved through six steps on the design board, from a briefing with the PM to design QA. Twice a week a short Design Weekly, every Tuesday an hour of Design Critique, squad syncs with PMs and engineers, and a weekly one-to-one with each designer. Every half-year, a roadmap alignment at the start and a retro at the end, with a design system review mid-quarter.
Design QA was mandatory: before a ticket could close, the designer went through a checklist in seven parts, from layout and components to microcopy, accessibility and interactions.
Week 1
Week 2
Rituals
Fixed day and time
Day varies
illustrative timing
Steps
Jira column
Pick a ritual or a step, or play the two weeks.
Fixed day and time
Fixed day and time
Day varies
Day varies
Day varies
One request, illustrative timing
Step 1 of 6
Step 2 of 6
Step 3 of 6
Step 4 of 6
Step 5 of 6
Step 6 of 6
Start of each half
With the PMs: scope, module focus, team bandwidth
Mid-quarter
With the design-system designer and the front-end lead: component usage, naming, contribution needs
End of each half
Team dynamics, process, collaboration
Once a semester
Informal or by survey: energy, clarity, support
Seven parts. The first six were required before a ticket could be closed.
We built the system the atomic way: atoms, molecules, organisms, templates, pages.
Each part was designed once, at the smallest level where it made sense, then combined. A dot and a label make a status; a status, a situation and a pacing bar sit in a campaign row; campaign rows fill the list template, and the template becomes the Campaigns page. Change an atom, and every screen that uses it follows.
Atomic design
The Campaigns page of Ogury One, built from these parts: a navigation, a page header, a strip of three KPIs, a filter bar, six campaign rows, a pagination and a toast.
Hover or tap a piece, or point at the page: see what each part is made of, and where it is used.
Ogury One — Design system
The library file of Ogury One’s design system: five pages, from the foundations (colour, type, spacing, elevation) to the atoms, molecules and organisms built as component sets, and the campaign-list template with its slots next to the page it becomes.
The library file of Ogury One’s design system: five pages, from the foundations (colour, type, spacing, elevation) to the atoms, molecules and organisms built as component sets, and the campaign-list template with its slots next to the page it becomes.
Foundations and components shared by the Figma library and Storybook. Every screen of Ogury One is built from them.
Ogury One design system
No match
Delivery against time: the volume bar and the time bar side by side. The gap between them sets the situation.
Ogury One’s users are professionals working fast on complex campaigns. The words had to keep up.
I owned the tone of voice and the microcopy. Four principles, each with what to aim for and what to avoid: clarity, professionalism, helpfulness and consistency. Then a library of ready-to-use wording in thirteen categories, from buttons, placeholders and errors to confirmation modals, empty states, tooltips, toasts, table actions and the way personas are named.
A few of its rules: a confirmation button names the action, as in “Delete campaign”; a tooltip is short and never apologises; no placeholder text ever ships.