CloudBees Website Redesign & Product Catalog Repositioning page hero image
CloudBees Redesign Study

Website & Product Catalog Repositioning

5 pain points .01
5 pain points icon

5 pain points we solved for

  1. Inconsistent messaging and positioning for CloudBees' entire product catalog.

    Solution: Through discovery, we collaborated with product teams to identify customer engagement patterns and tested messaging to find the most effective for our target personas. By addressing customer issues and clearly communicating solutions, we enhance understanding of our products and their benefits.

  2. Lack of product narratives led to gaps in launching new CloudBees products or features.

    Solution: We filled product line gaps by engaging customers in a meaningful dialogue about their challenges. Using component design and refined content, we created a compelling messaging approach with videos, testimonials, and market evidence for an enhanced product narrative and website experience. Improved information architecture and navigation models ensure a lasting and memorable customer experience.

  3. Website UX the was the product of numerous visual uplifts that had no universal design systems approach.

    Solution: Acknowledging past mistakes of focusing solely on certain aspects of our UX and branding layer, we've embraced a holistic design systems approach. This ensures improved consistency and scalability across our entire design framework.

  4. Front-end stack challenges led to a complex rollout of the experience layer.

    Solution: Strengthening our partnership with engineering, we improved collaboration between Design and Code, speeding up delivery, enhancing quality, minimizing testing dependencies, and fostering a better working relationship. Transitioning to standard frameworks allowed us to align design properties with CSS utility classes in a 1:1 system, promoting efficiency.

  5. Brand strategy and limited resources led to a shortage of usable design material.

    Solution: Developing versatile brand tools enhanced our design execution, establishing UX digital design as a core foundation for other teams to build upon.

We gained valuable insights while exploring key areas. Pinpointing the main reasons for past project failures, we made adjustments and collaborated across functions to achieve more lasting and scalable results.
UX tooling for success .02
Patterns & Systems .03

UX design patterns and adopting a design systems approach

Adopting a design systems approach - example

Consolidating patterns enabled the creation of systems for specific surface areas

Over time, the website underwent temporary uplifts, deviating from the central design and component system. Centralizing design in a series of Figma libraries enabled both internal and external teams to collaborate and maintain consistency.


We addressed inconsistencies by aiming for a 1:1 design-to-coded component system, resulting in scalable approaches to our design and brand style libraries, which facilitated efficiencies in collaboration with internal and external teams.

These systems improved speed and quality for engineering teams, UX design, and image asset production, streamlining content, engineering, and page publishing operations at scale.


UX advancements impact other company ecosystems

Strengthening our digital design brand identity influenced both corporate and product identities. We achieved this by standardizing design resources in libraries and providing documentation and support for teams to adopt these principles.

All components, whether designed or coded, maintain a one-to-one relationship in both design tooling and code frameworks

Components and code patterns

Components and code patterns

This speeds up design-to-delivery, fostering a more collaborative design and engineering relationship.

Better partnerships with engineering - example of code

Better partnerships with engineering have better results

Figma variables and attributes are used to ensure all grids, widths, spacing, type rule sets, and colors have 1:1 match with CSS utility classes and all inspectable names are aligned with our front-end frameworks.

Interaction patterns, including animations, transitions, speed, and interaction states, are documented with shared design-to-code relationships.

Branding patterns and operations

example of branding patterns in use
Example of Figma libraries and shared resources

Improving brand design and UX operations

Through shared libraries, centralized design theories, and user research we ensured scalability, accessibility, and usability standards across our entire organization and digital surfaces.

Shared rules and patterns example

Color, contrast, type, and... code, accessibility is very important

Ensuring type and color accessibility is fundamental in every brand standard. We enhance code standards with semantic HTML, ARIA attributes, keyboard navigation, and proper labeling to address issues and promote inclusivity, complying with web accessibility standards through regular testing.

Illustration and brend identify examples

Messaging meets illustration

Defined a new brand and communication theme using illustrations for conceptual messaging, adding personality to our UX work. Instead of stock photography, we used illustrations to articulate messages, providing a broader set of messaging utilities.

CMS operations, publishing, content strategy, and messaging patterns align seamlessly with design

1 - 2 - 3 Systems and patterns working together

Optimizing content and design production by building a closer relationship between content authoring and design

We streamlined content development to resources aligned 1:1 with our component system, design materials, and CMS authoring experience.


Streamlined operations create better results
  1. Design libraries define components and page types, directly ship to Code and CMS models.
  2. Content authoring, revisions, workflows, and tools are orchestrated to align teams and encourage valuable collaboration.
  3. Seamless content authoring across design, content creation, code layer, and CMS tools.
Before and After study .04
End Outcomes Flag icon

End outcomes

The goal was to foster a collaborative environment, combining strong partnerships, streamlined operations, effective tooling, design thinking, team education, and strategic marketing efforts for higher value, scalability, and success.

Transitioning to a product model brings deliberate focus and accountability across teams and disciplines, providing a stronger foundation to build upon.

The strategies paid off by increasing value in production workflows, messaging meets content strategy opportunities, and making infrastructure changes easier to maintain, track, and scale.

Visit the CloudBees site
Who am I .05
Mike Rusczyk - Skateboarder Magazine - Photo - Brian Gaberman
About me

Mike Rusczyk

My product design expertise stems from a skateboarding background, fostering adaptability and turning challenges into innovative opportunities. I prioritize a design process that seamlessly blends functionality, logic, and a distinctive aesthetic to meet technical standards and create emotional connections with users.

Leading design teams with a focus on technical precision and creative insight, I integrate a comprehensive historical perspective into enduring, highly functional designs. In my diverse marketing roles, I've gained a deep understanding of creating successful brand experiences. Focused on navigating the evolving digital communication landscape, I shape compelling narratives that contribute to the overall success of the products I work on.

On Linkedin

Click to dismiss dialog