JULIE HUCHET
PRODUCT DESIGN / HANDS-ON LEADERSHIPCLOUDFLARE · 2026

A small fix.
A bigger opportunity.

Trust starts before you log in.

A customer questioned whether a security login page was legitimate. I took that signal as an opportunity to rethink the experience and build a working answer.

01 / THE SIGNAL

For a security product, looking trustworthy isn’t a nice-to-have.

The message pointed to specific visual inconsistencies: repeated brand marks, different type sizes, and mismatched authentication buttons. Together, these details undermined confidence at the moment of sign-in.

CUSTOMER FEEDBACK · GOOGLE CHAT

“We started using the Zero Trust feature and it’s awesome! I’ve been hit with the login screen a bunch of times and wanted to point out that the design on this page looks really inconsistent (a cloudflare logo at the top and bottom, many font sizes, box size differences between the github and send me a code buttons).

It made me a bit suspicious whether it’s a legit site or not.”

THE ORIGINAL LOGIN EXPERIENCERecreated from the original capture. Account details replaced with examples.
02 / THE EXPERIMENT

Don’t just describe it.
Make it tangible.

Explore the same design across different customer identities, authentication setups and appearances. This is a reconstructed, non-functional design demonstration, rather than a live Cloudflare sign-in.

LIVE PREVIEWDESIGN PROTOTYPE · NOT A REAL LOGIN
GeorgeCorp Incorporated ™

Log in to Hello

Anyone logging into GeorgeCorp Incorporated must adhere to the standards and policies outlined in the company policy of conduct.

Sign in with:
or

We’ll send a 6-digit code to this address.

Disclaimer: GeorgeCorp Incorporated is a fictional organization used to demonstrate customizable customer messaging and policies.
FICTIONAL DATA · NO AUTHENTICATION

CONFIGURATION: WHITE LABEL / DARK4 METHODS ENABLED
03 / HOW I APPROACHED IT

From a Google Chat message
to something real.

01 / NOTICE

Follow the customer signal.

When our CTO shared the feedback, I volunteered to take it on. The problem was small in scope but meaningful in a moment where users need to feel secure.

02 / EXPAND

Ask what else is broken.

I spoke with a product engineer to understand the constraints and adjacent pain points. The goal became a coherent experience that could flex across real authentication configurations.

03 / MAKE

Prototype the answer.

I used AI-assisted coding to create an interactive prototype, then documented the design decisions and reusable implementation guidance for Engineering.

04 / DESIGN DECISIONS
01

One clear hierarchy.

Make the destination, identity and next action immediately legible.

02

Flexible by design.

Support one or several identity providers, email login and different levels of customer branding.

03

Build for the handoff.

Translate a visual direction into an interactive reference and reusable code alongside static screens.

A NOTE ON LEADERSHIP
Being a design leader doesn’t mean stepping away from making things.

I delivered a working prototype and implementation guidance for Engineering. It made the visual decisions and authentication variants concrete enough to discuss and build from. This case study covers that exploration, rather than a verified production rollout.

BACK TO JULIE HUCHET ↗