JULIE HUCHET
STRATEGY / CROSS-FUNCTIONAL LEADERSHIPCLOUDFLARE · JUL 2024 TO JAN 2025

From a workshop.
To an Observatory.

11 JULY 2024 → JANUARY 2025

I initiated a workshop to understand friction across Cloudflare One. With my Design Lead and our partners, we developed it into an Observatory: a shared reference and a process for turning related problems into coordinated work.

01 / WHY I STARTED

Connect the pain points.
Understand the whole.

I could see friction across our products, but struggled to connect the dots: which problems were related, how products affected one another, and where an improvement could make a broader difference.

In the race to innovate, improving the existing experience needed a place, too. I initiated a workshop to build that shared view with roughly 30 product partners across Design, Engineering, Product, and Content.

02 / THE JOURNEY

Gather. Connect.
Align. Deliver.

  1. 11 JULY 2024The workshop

    Bring the perspectives into the room.

    I co-facilitated the workshop with my Design Lead at the Cloudflare One onsite. We combined our partners’ product expertise with a user perspective, asking what worked, what did not, and what would be desirable.

    OUTPUT · A shared set of observations across the existing experience
  2. AFTER THE WORKSHOPThe synthesis

    Connect the dots with my Design Lead.

    We sat down together to connect the observations and identify the larger families of problems. We documented six emerging themes, the user needs behind them, and opportunities to explore.

    OUTPUT · The post-workshop results document
  3. FROM SYNTHESIS TO AGREEMENTPartner alignment

    Discuss what would make a difference, and what was feasible.

    We brought the synthesis to Product, Content, and Engineering to discuss opportunities, constraints, and the path forward. Those conversations connected the shared diagnosis to practical missions.

    OUTPUT · Agreed direction for cross-functional work
  4. FROM AGREEMENT TO EXECUTIONMissions & OKRs

    Give the work a structure and the team a purpose.

    We published the missions and created tickets. I translated that work into OKRs for my team, making the connection between everyday delivery and the product improvements we wanted to achieve explicit.

    OUTPUT · Published missions, tickets, and team objectives
  5. JANUARY 2025Completion

    Complete the missions.

    By January 2025, the missions were complete. What began as a workshop had become a shared reference and a process connecting observations, partner alignment, and execution.

    OUTCOME · Completed missions and a reusable way of working
03 / THE POST-WORKSHOP SYNTHESIS

Six themes.
One connected view.

The post-workshop document connected individual observations to user needs and opportunities. These six themes became the basis for feasibility discussions with our partners.

Condensed from the July 2024 post-workshop results document
ThemesUser needsOpportunities
Use-case-driven workflowsHow do I accomplish what I need to do?Align UI and content around core tasks, with guidance and clearer system signals.
Product consistencyWhy do related solutions work differently?Unify shared patterns, including tables, rules, and policies, across the suite.
NavigationHow do I move between related solutions?Organize products into meaningful areas and connect workflows beyond the side navigation.
Context & overviewsWhere do I start, and how does it fit together?Clarify each product’s purpose and its relationship to the wider solution.
ObservabilityWhat is happening, and what should I do next?Make analytics and reporting more coherent, informative, and actionable.
SettingsWhat does this setting affect?Distinguish suite-wide settings from product-specific configuration and provide contextual help.
04 / WHAT MADE IT AN OBSERVATORY

A shared reference.
A continuing process.

The document gave us a reference; the process gave us a way to use it. The value was in returning to the same view of the problems when discussing priorities, dependencies, and delivery.

01

Keep the whole in view.

Look across products and disciplines to understand related problems and opportunities.

02

Make decisions together.

Discuss user needs, business priorities, and technical feasibility with the partners responsible for the work.

03

Connect insight to action.

Use missions, tickets, and team OKRs to carry the shared direction into execution.

THE OUTCOME

Give improvement a place
alongside innovation.

The missions were complete by January 2025. The Observatory linked improvements to the existing experience with team commitments, giving that work an explicit place alongside new product development.