Home, Enguerran Avril

Case study · Ogury · 2021–2025

Ogury One

Four years to go from one designer and four legacy platforms to a design team, a design system and one product.

Company
Ogury, advertising technology
Role
Lead Product Designer, then Director of Product Design from January 2023
Period
October 2021 – August 2025
Team
From one designer to a team of three
Scope
B2B SaaS, internal tools and analytics; design system; brand with Marketing

At a glance

The challenge

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.

What I did

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.

The outcome

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.

Impact

  • ÷5time to design a new screen: about two weeks with the old Sketch UI kit, about two days with the design system
  • 500+components and variants in the design system
  • 100%of internal users moved to Ogury One

Orders of magnitude, estimated in hindsight.

Campaigns
Campaigns/Campaigns
Live campaigns
42
Spend this month
$1,284,56071% of planned budget
Impressions this month
214.6M12.4% vs Sep
Average viewability
78.4%1.2 pts vs Sep
Name
Delivered
Booked
Actions
[Deal]204518Rules (2) →FR_Mirevale_Maison Ondine_Noël 2026
Live
On track
102%
5,061,240
18,250,000
$180,000
$48,600
5.06M
54 days
[Deal]204391Rules (2) →FR_Ostrale_Cartaline_Black Friday
Live
Underdelivering
64%
2,592,060
19,100,000
$120,000
$21,600
2.59M
30 days
[Rule]204931FR_Ostrale_Cartaline_Black Friday_Video
Live
On track
98%
1,305,120
4,850,000
$60,000
$16,200
1.31M
30 days
[Rule]204932FR_Ostrale_Cartaline_Black Friday_Display
Live
Underdelivering
31%
1,286,940
14,250,000
$60,000
$5,400
1.29M
30 days
[Line item]311842FR - Corvenne - Velmont - Velmont Auto - TTD - CPM Video - PD - NOV26
Live
On track
106%
3,298,410
6,750,000
$95,000
$45,600
3.30M
29 days
[Deal]204277Rules (2) →FR_Lyrae_Solenne Paris_Winter Collection
Live
Overdelivering
142%
3,907,760
6,800,000
$70,000
$39,900
3.91M
45 days
[Line item]311790FR - Mirevale - Belcour - Fromagerie Belcour - DV360 - CPM Display - OE - Q4
Live
On track
99%
7,218,930
16,500,000
$64,000
$28,160
7.22M
61 days
[Deal]204145Rules (3) →FR_Quai 17_Banque Altière_Q4 Awareness
Paused
—
—
3,621,150
18,300,000
$150,000
$31,500
3.62M
61 days
[Deal]204502Rules (2) →FR_Corvenne_Rivage Mobilité_Launch EV4
Live
On track
103%
3,128,470
9,750,000
$110,000
$36,300
3.13M
22 days
[Line item]311815FR - Lyrae - Kerlys - Kerlys Eau - Xandr - CPM Display - PD - OCT26
Live
Underdelivering
58%
5,548,820
13,500,000
$42,000
$17,220
5.55M
15 days
[Deal]204488Rules (2) →FR_Ostrale_Cimaise Home_Black Week
Live
On track
95%
1,779,560
12,500,000
$88,000
$13,200
1.78M
30 days
[Line item]311768FR - Quai 17 - Optique Lunel - Lunel - TTD - CPM Video - PD - Q4
Live
On track
101%
1,652,380
4,350,000
$56,000
$21,280
1.65M
50 days
[Deal]203960Rules (2) →FR_Mirevale_Pâtisserie Lenoir_Rentrée
Ended
Ended
—
6,917,240
7,100,000
$48,000
$47,040
6.92M
—
[Line item]311856FR - Corvenne - Velmont - Velmont Auto - DV360 - CPM Display - OE - NOV26
Live
On track
104%
2,968,710
8,250,000
$38,000
$13,680
2.97M
29 days
Ogury One’s campaign list, rebuilt for this page from the real screens and filled with fictional campaigns. It works: filter it, sort it, open a deal, pause a line. Then take the tour of its pain points.

Pain points, before and after

The changes play on the screen above, the problem first and then the fix. Pick one to see it again.

The challenge: Where it started

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.

  • Active Insights
  • Publisher Dashboard
  • Backoffice
  • OCS

Ogury One

  • One design system
  • One brand identity and tone of voice
  • Reworked user flows
Four legacy platforms became one product, Ogury One.

The approach: Building the team

My first fifteen months, as Lead Product Designer, went into building the team and its tools.

Read the detail: Building the team

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.

October 2021
1

designer, a web designer by background. The previous lead had just left.

To set things up
2

freelancers I brought in at the start.

The team
3

two product designers, one of them the first designer, mentored to senior level, and a motion designer who also did product design.

Design at Ogury, besides me: where it started, the freelancers who helped set it up, and the team.

System and brand

From an old design kit to a complete design system, with every application migrated onto it, and a new brand identity built with Marketing.

Read the detail: System and brand

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.

  1. Check what existsIn Figma, Storybook and Ant Design.
  2. Open the discussionWith design and front-end, before drawing anything.
  3. ProposeUse cases, variants, states, dev notes.
  4. Review and sign-offBy design and front-end together.
  5. Ship and announceFigma, Storybook, a documentation page and a changelog entry.
How a component entered the design system, from the team’s contribution guide.

Design system

Foundations and components for every screen of Ogury One

  • Sketch → Figma
  • Storybook
  • Brand, with Marketing
  1. 2021–2022First library, documented and automated in Storybook
  2. 2023–2025A complete system and a new brand identity, with Marketing

Colour

Typography

Red Hat Text

  • Regular 400
  • Medium 500
  • Semibold 600
  • Bold 700

$1,284,560Tabular figures

Buttons and fields

Fields

Status and situation

Status

  • Live
  • Paused
  • Draft
  • Ended

Situation

  • On track
  • Underdelivering
  • Overdelivering
  • Ended

Pacing

[Deal] 204391FR_Ostrale_Cartaline_Black Friday

Vol.18%Time28%

Underdelivering10 pts behind

From components to a screen

NameStatusSituationPacingBudgetActions
[Deal] 204391FR_Ostrale_Cartaline_Black FridayLiveUnderdeliveringVol.18%Time28%$120,000
[Line item] 311842FR - Corvenne - Velmont - Velmont AutoLiveOn trackVol.48%Time46%$95,000
[Deal] 204277FR_Lyrae_Solenne Paris_WinterLiveOverdeliveringVol.57%Time39%$70,000

Pause a line: the status, the counts and the toast follow.

Feedback

Live campaigns

426 underdelivering

Impressions this month

214.6M12.4% vs Sep

Deal 204145 paused
Ogury One’s design system at a glance, recreated for this page from the product: copy a colour, drag the pacing, pause a line.

Leading design

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.

  • Design across squads and business units: B2B SaaS, internal tools and analytics.
  • A UX strategy, a team structure and a collaboration model agreed with Product and Engineering leadership.
  • Clear ownership, rituals and delivery standards, with design principles and design QA.
  • A seat in org-level decisions and roadmap prioritisation.
  • A user-centred culture, built through workshops, research and design-driven metrics.
  • The team trained early on AI tools, starting with Midjourney.

The solution: Ogury One

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.

  1. Analysis of the existing platforms
  2. Workshops with users
  3. Beta testers
  4. Prototypes
  5. Delivery
How Ogury One was built.
Ogury One showing a deal: its advertiser, dates, budget and status, then a table of the rules that deliver it, each marked on track or underdelivering, with pacing bars.
The real screen of a deal in Ogury One, with the rules that deliver it. Each rule says in words whether it is on track, then shows its pacing in volume and in time.

Workshops with users

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.

  • What we saw
  • What got in the way
  • What they asked for

Drag the notes, then sort them into themes.Sort the notes into themes.

  1. Is it on track?

    • Compares delivered impressions with the booking, by handWorkshop
    • Finds out a deal is late when it is already lateWorkshop
    • Tell me which deals need me todayBeta test
    • Follows pacing in a spreadsheetWorkshop

    What we took from it

    Say in words whether a deal is on track, then show the numbers behind it.

  2. Four tools, one job

    • Four tabs open to follow one campaignWorkshop
    • Copies IDs from one platform to the nextWorkshop
    • Each platform has its own menusPlatform audit
    • One place for deals, campaigns and reportsBeta test

    What we took from it

    One product, one navigation.

  3. Setting up blind

    • Launches, then waits to see if it spendsBeta test
    • Know the reach before launchingWorkshop
    • Checks every field twice before savingBeta test

    What we took from it

    Show the forecast while the line item is being set up.

  4. Same thing, different names

    • Same button, three different looksPlatform audit
    • One word, two meanings, depending on the toolWorkshop
    • The same words for every teamWorkshop
    • New joiners learn each tool separatelyWorkshop

    What we took from it

    One design system and one vocabulary across the product.

Notes from the workshops, recreated for this page and sorted into the themes that shaped Ogury One. Move them around, then sort them.

Prototypes and beta testers

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.

Add line item
Forecasts are available in Reporting once the line item is live.
Summary
Media typeVideo
Deal typeGuaranteed
Name[Line item] FR - Corvenne - Velmont - Velmont Auto - TTD - CPV Video - PD - DEC26ID : assigned on creation
Flights2026-12-01→2026-12-31
Budget€ 60,000.00
CPV target€ 0.020
EnvironmentsIn-App, Web
CountriesFrance, Belgium
Placement typesInterstitial, Thumbnail, Footer
Creative formats9:16, 16:9
Overview
Media type
Account
Brand
Campaign
Strategy (optional)
Flights
Timezone
Format: year, month, day, as 2026-12-01.
Budget
Budget pacing
Forecasting
No risk of underspendEnough inventory for this budget.
General estimations
Impressions5.22M
Reach2.44M
Estimated performances
CTR0.87%
Viewability84.25%
VTR72.98%
Impressions per environment
  • In-App73%
  • Web27%
Impressions per placement type
Interstitial51%
Thumbnail29%
Footer20%
Header—
In-article—
Based on the last 30 days of inventory
Adding a line item, rebuilt from the real screen with fictional data. Change the budget, the dates, the bid or the targeting: the forecast and the underspend risk follow.

Pain points, before and after

The changes play on the screen above, the problem first and then the fix. Pick one to see it again.

Persona Builder

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.

Read the detail: Persona Builder

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

New persona

Translate your brief into a persona

Build your own persona by simply entering your brief and let the magic happen

Try a sample brief

Expert mode

Build your own persona by leveraging our pre-defined personas, using mix and match

Personas & Insights

My Personas

Access all saved personas for future targeting.

5 personas
IDNameBrandCountryReachLast update
418203KerlysFrance3.5M – 4.3MOct 22, 2026418203 · France · Lyrae · KerlysOct 22, 2026
417966BrightwaterUnited Kingdom1.9M – 2.3MOct 9, 2026417966 · United Kingdom · Mirevale · BrightwaterOct 9, 2026
416540Cimaise HomeFrance7.5M – 9.1MSep 30, 2026416540 · France · Ostrale · Cimaise HomeSep 30, 2026
415872Solenne ParisItaly3.8M – 4.7MSep 18, 2026415872 · Italy · Lyrae · Solenne ParisSep 18, 2026
414309Rivage MobilitéSpain390K – 470KSep 4, 2026414309 · Spain · Corvenne · Rivage MobilitéSep 4, 2026
1–5 of 5

Persona Builder

Summary

Brief

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.

Behavior personas

I want to target

Urban runners or Young professionals or Fitness regulars or City commuters

Socio demo

Gender
Age

Behavior personas

4 of 5 personas

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

And

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.

Not

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.

Reach

Potential monthly user reach

Potential monthly user reach: 12.3M – 15.0M.

Good reach
Gender
Women50%National average 51%
Men50%National average 49%
Age

The dot represents the national average

18–2421%National average 11%
25–3440%National average 17%
35–4421%National average 16%
45–5411%National average 17%
55+7%National average 39%

Estimates based on the last 30 days.

Reach

Discard changes!

You will lose all the changes made to this persona.

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.

Ogury One’s Persona Builder, recreated from my Figma file with fictional personas and figures. Try it: translate a sample brief or write your own, or start in Expert mode, then refine the personas, watch the reach and save your persona.

Decisions that shaped it

Three choices made the difference.

  1. Team and system first, the merge second.

    Why
    Four platforms could only become one product with a structured team and a shared design system behind them.
    What it led to
    Fifteen months of foundations as Lead, then Ogury One, built on both.
  2. The same components for design and code.

    Why
    Designers and developers had to work from the same parts, from the smallest atom to the page.
    What it led to
    An atomic design system in Figma, documented and automated in Storybook: change an atom, and the screens that use it follow.
  3. The users of all four platforms in the room.

    Why
    Merging four platforms meant deciding what their users needed from each.
    What it led to
    Workshops, themes that guided the design, then prototypes tested by beta users before delivery.

The result: What it left

  • One product in place of four legacy platforms.
  • The Persona Builder, shown at Cannes Lions, and more than thirty clients brought in.
  • A design team of three, with ownership, rituals and delivery standards.
  • A design system from atoms to navigation, every application migrated onto it, and a brand identity shared across the product.

I left Ogury in 2025 and have been working freelance since.

Go furtherHow the team worked, atoms to pages, tone and microcopy: the detail behind the story above.

How the team worked

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

To do
In progress
Review
Ready for dev
QA
Done

Pick a ritual or a step, or play the two weeks.

Fixed day and time

Design Weekly

Who
All the product designers
When
Twice a week, Monday and Friday, 10:00–10:30
What for
Each designer’s main focus, blockers and async needs, and news for the whole team

Fixed day and time

Design Critique

Who
All the product designers; invited team members can join
When
Every Tuesday, 10:00–11:00: 5–10 min to present, 30–40 min of feedback and discussion, the last 10 min to recap and agree next steps
What for
Peer feedback on early concepts, visual refinements or decisions to align on

Day varies

Squad syncs

Who
The squad’s designer, PM and engineers
When
Weekly or every two weeks; the day depends on the squad
What for
Align priorities and deliveries

Day varies

One-to-ones

Who
Me, with each designer
When
Every week, scheduled individually
What for
Support, feedback, growth and direction

Day varies

QA sync

Who
A designer and a developer
When
When needed
What for
Implementation issues, or the final visual QA

One request, illustrative timing

How a request comes in

Who asks
PMs, engineers or designers
How
A Jira “Design request” with its context, expected outcome or success criteria, deadline and links; never a brief over Slack
Ticket types
Design request, Design audit, Design QA or Visual bug, each tagged Demand or Supply
The board
Its own Product Design Kanban: To do, In progress, Review, Ready for dev, QA, Done, plus Blocked when needed

Step 1 of 6

Brief­ing

Who
The PM and the designer
On the board
To do
What happens
The PM and the designer go through the request together

Step 2 of 6

Exploration and mockups

Who
The designer
On the board
In progress
What happens
Exploration, then mockups built with the design system

Step 3 of 6

Review and iteration

Who
The designer and the PM, with engineers if needed
On the board
Review
What happens
Reviews, async or live, and iterations

Step 4 of 6

Ready for dev

Who
The designer
On the board
Ready for dev
What happens
The design is ready to be built

Step 5 of 6

Hand­off

Who
The designer, for the engineers
On the board
Ready for dev
What happens
Specs and the Figma file, linked in the Jira ticket

Step 6 of 6

QA support

Who
The designer
On the board
QA, then Done
What happens
The designer checks the build. Design QA is mandatory before the ticket closes

Over the half-year

  • Roadmap alignment

    Start of each half

    With the PMs: scope, module focus, team bandwidth

  • Design system review

    Mid-quarter

    With the design-system designer and the front-end lead: component usage, naming, contribution needs

  • Design retro

    End of each half

    Team dynamics, process, collaboration

  • Team health check

    Once a semester

    Informal or by survey: energy, clarity, support

The design team’s two weeks, recreated for this page from the team’s playbook: the rituals at their real days and times, those whose day varied shown as such, and one request moving through the six steps and the Jira columns. The request’s timing is illustrative. Pick a ritual or a step, or play the two weeks.

The design QA checklist

Seven parts. The first six were required before a ticket could be closed.

1Visual and layout6 checks
  • The layout matches the latest Figma: spacing, padding, grid
  • Typography follows the design system
  • Colours and visuals comply with the design system
  • Buttons and interactive elements have the right placement, state and hierarchy
  • Icons, tags and illustrations are used and placed consistently
  • Empty states and feedback are styled as defined
2Components and design system5 checks
  • Every element uses Ogury’s version of the Ant Design components
  • New components follow the contribution guidelines
  • No custom styling without a peer’s validation
  • All states are covered: default, hover, disabled, error
  • Forms have the right label position, help text and inline validation
3Content and microcopy5 checks
  • Labels, tooltips, buttons and placeholders follow the tone-of-voice guidelines
  • No placeholder text such as “Lorem ipsum”, “Click here” or “Coming soon”
  • Buttons follow the CTA rules: Create, Add, Edit, Delete…
  • State messages are clear: empty, error, success, loading
  • Tooltips are short, technical if needed, never apologetic
4Responsiveness and accessibility4 checks
  • Tested at the internal standard viewport, 1140 × 750
  • No text overflow, no overlapping components
  • Contrast meets accessibility standards
  • Focus states are visible
5Interaction5 checks
  • Micro-interactions are implemented: hover, transitions, modals
  • Buttons and links do what they should
  • Modals, drawers, dropdowns and tooltips open and close smoothly
  • Errors and edge cases are covered: empty, loading, failure
  • Confirmation modals use action-first copy, such as “Delete campaign”
6Jira, Figma and documentation3 checks
  • The final, reviewed Figma frame is linked in the ticket
  • The ticket is moved to QA
  • The feedback history is summarised in the ticket
7For complex flows3 checks · optional
  • A peer design review
  • A short video walkthrough, attached
  • Reviewed in a Design Critique
The design QA checklist from the team’s handbook: seven parts, the first six required before a ticket could be closed. Open a part to read its checks.

Atoms to pages

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

From atoms to pages

0. Foundations: Colour, type and spacing: the decisions every part inherits.

1. Atoms: The smallest parts: a dot, a label, a track, a button.

2. Molecules: Atoms joined to do one job: a status, a pacing bar.

3. Organisms: Molecules assembled into a section: a campaign row, a filter bar.

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’s design system from atoms to pages, recreated for this page. Hover or tap a piece to see what it is made of and where it is used, point at the page to find its parts, or press Build the page.

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.

  1. FoundationsHeader · Colour · Typography · Spacing · Radius and elevation
  2. AtomsHeader · Button · Icon · Input · Track · Dot · Pill · Label · Figure
  3. MoleculesHeader · Text field · KPI tile · Status · Situation · Pacing · Icon button · Filter tab
  4. OrganismsHeader · Campaign row · KPI strip · Filter tabs · Toast
  5. TemplatesHeader · Template / Campaign list · Campaigns

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 as it lived in Figma, recreated: the same levels, from foundations to templates. Pick a page, select a layer, read its properties.

Foundations and components shared by the Figma library and Storybook. Every screen of Ogury One is built from them.

Ogury One design system

  • Foundations
    • Colours
    • Typography
    • Spacing
  • Atoms
    • Button
  • Molecules
    • Status
    • Situation
    • Pacing
    • Text field
    • KPI tile
  • Organisms
    • Filter tabs
    • Toast

Molecules / Pacing

Situation
Pacing (Volume/
Time Progression)
Underdelivering
Vol.18%Time28%
Controls
18%
28%

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.

The same system in its Storybook, recreated and organised by level: browse the foundations, atoms, molecules and organisms, change their properties, read their rules.

Tone and microcopy

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.