JULIE HUCHET
TEAM LEADERSHIP / AI & ENGINEERINGCLOUDFLARE · 2026

Helping designers
turn ideas into
shipped improvements.

QUICK WINS WEEK

We first taught designers to vibe code, then how to submit merge requests. Quick Wins Week gave them a chance to put those skills into practice: improve the Help Page and tackle small projects they already had in mind, with engineers supporting implementation and review.

26UI fixes merged by Cloudflare One
4days · 5 contributing designers
0production incidents reported
96merge requests across the wider PX org

Team delivery and organization-wide contributions are shown separately.

01 / THE OPPORTUNITY

A small surface.
A significant reach.

The Zero Trust Help Page became our shared project for the week, alongside small improvements designers already wanted to tackle. It had gone six years without a major refresh, despite handling approximately 30 million requests every day. That existing traffic made improving it a priority. People relied on it to check their protection status and troubleshoot connectivity, but it predated Kumo, Cloudflare’s current design system.

Legacy components, dense technical data, and weak visual hierarchy made essential information harder to scan. I co-authored the initiative brief with Engineering: modernize this high-traffic surface through focused improvements that designers could help ship.

BEFORE / THE EXISTING HELP PAGE
Original Zero Trust Help Page from the initiative brief, with blue outlined cards, top navigation, and separate DNS and HTTP filtering panels. Organization information is hidden.

Original interface from the project brief. Organization information is masked.

A focused brief

Migrate to Kumo components, improve grouping and hierarchy, refresh spacing and typography, and clean up outdated content. Keep the underlying functionality unchanged.

23 to 25 March 2026 · build days
26 March 2026 · demo day

Approximately 30 millionRequests per day

Six years without a refresh.
An urgent reason to act.

This traffic was already there before Quick Wins Week. A diagnostic page used at this scale needed a clearer, up-to-date experience.

Existing daily traffic, reported in the initiative brief. Requests, not unique users.
02 / MY ROLE

Bring the right people together.
Make execution possible.

I helped turn the learning into a practical team initiative. With engineering leadership, I organized a week where designers could apply their new skills to real work, get support when they needed it, and learn how to take a change through review.

01

Learn, then apply

Connect vibe coding and merge request training to a week of hands-on work on the Help Page and designers’ own improvement ideas.

02

Partner with Engineering

Align with engineering leadership on scope, review expectations, and support before the week began.

03

Share ownership

Let designers and engineers define the practical workflow together, with clear ownership and a route to resolve blockers.

03 / ALIGNMENT BEFORE EXECUTION

Agree on the boundaries.
Then let the team move.

To support that hands-on week, a cross-functional workshop established which fixes were suitable, when to involve engineers, and what reviewers needed to see.

The workshop · 30 to 35 minutes

  1. Define a papercut

    UI-only, small, reversible changes. No API or functionality changes.

    5 min
  2. Map the collaboration loop

    Agree when Design, Product, and Engineering enter the process.

    15 min
  3. Agree on review expectations

    Before/after evidence, self-review, AI checks, and engineering approval.

    5 to 10 min
  4. Close with shared decisions

    Confirm ownership, support, and follow-up.

    5 min

10 people in the room

Workshop participants

Design Manager
1
Design ICs
3
Product
1
Engineering Manager
1
Engineering ICs
4
The workshop group is distinct from the five designers who contributed fixes during the week.
Explore the workshop boards
Workshop board defining eligible UI-only fixes, boundaries, effort, and designer ownership.
Defining what was safe to take on.
Workshop board mapping discovery, implementation, and review responsibilities.
Agreeing who gets involved, and when.
04 / THE OPERATING MODEL

A clearer path
from issue to improvement.

BEFORE

Small UI fixes compete for engineering time.

Before: interface issues rely on engineering capacity to move from design feedback to implementation.
AFTER

Designers contribute directly, within an agreed scope and review process.

After: a shared collaboration workflow connects scope alignment, designer implementation, checks, and engineering review.
How execution worked Tracker · pairing · AI pre-check

Make the work visible before it starts.

Designers submitted candidates to a shared tracker before pairing. Each ticket had to meet the agreed criteria: UI-only, reversible, and without API dependencies. Engineering could see the incoming work and triage scope before implementation.

Selected tracker examples · condensed and anonymized
IssueProposed changeStatus at capture
Access cards used a hardcoded corner radius.Replace the fixed value with the existing radius token. Visual change only.Merged
Secondary text used a fixed gray that did not adapt to dark mode.Use the semantic text color token, with no layout change.In review

A designer and engineer pairing loop

  1. 01

    Align on scope

    Spend five minutes agreeing on the visual issue, the boundaries, and the expected outcome.

  2. 02

    Find the right place

    The designer uses AI to locate relevant components and propose changes. The engineer validates the approach and flags constraints.

  3. 03

    Preview and refine

    The designer checks the interface locally and iterates on details and edge cases. The engineer watches for structural issues.

  4. 04

    Check, then review

    The designer opens a merge request with a clear description. An AI pre-check runs before engineering review and approval.

AI PRE-CHECK / SCOPE ENFORCEMENT

A filter before human review.

The shared pre-check example keeps changes within the UI layer. It flags server or API changes, authentication and access-control changes, new dependencies, and environment-variable changes.

Out-of-scope changes return to the designer with specific feedback before engineering review. The check supports human judgment; engineering retains approval.

05 / THE IMPACT

Better product quality.
Less dependency.

The work reached production, including the refreshed Help Page shown below. Designers contributed implementation alongside their design work, with engineering review and approval.

The team also left with a documented workflow for choosing, implementing, and reviewing small UI fixes. It made the handoff and responsibilities explicit, rather than relying on individual arrangements.

ONE SHIPPED EXAMPLE

Cloudflare One Help Page

The delivered page brings clearer hierarchy, Kumo components, and refreshed content to the same diagnostic tools: device and network status, client guidance, and troubleshooting.

APPEARANCE
Delivered Cloudflare One Help Page in light mode, showing device information, client installation guidance, and network details.

Delivered interface · diagnostic data omitted and protection banner removed for presentation. Select the image to view it at full size.

06 / REFLECTION

The system around the work
made the work possible.

01

Shared agreement made the process usable.

The workshop mattered because Design, Product, and Engineering defined the boundaries together. The tracker and checks gave that agreement a practical form.

02

Clear boundaries created room for autonomy.

Learning to generate code was the first step. Practicing merge requests, reviewing changes, and knowing when to ask an engineer for help connected that skill to the reality of shipping.

03

AI checks helped build confidence.

A first filter gave designers feedback before asking for engineering attention. Its value was also in making the collaboration feel supported, while keeping people accountable for the final decision.

04

Speed still needs judgment.

My responsibility was to create the conditions for useful changes: small enough to understand, safe to reverse, and clear enough to review. That is what I would carry into the next initiative.

07 / LEADING BY DOING

Try it
myself, too.

The Access Login experiment shows another side of my practice: using AI-assisted development myself to explore a customer problem through a working prototype.

SEE THE ACCESS LOGIN EXPERIMENT