The challenge

Dell’s customer experience design team once used an internal component system to design and prototype solutions. But it took an entire product team to maintain it. And for a largely “non-technical” team of 50+ folks, it wasn’t what you’d call … friendly.

Tired of fighting this bloated system, the team started looking for something new.

Their needs

In short, the Dell team had a pretty straightforward set of needs:

1. Better communication with developers
2. Web and desktop prototyping — just mobile was not enough
3. A code-free design tool
   ‍

The search

A software evaluation team formed to put the available prototyping tools through their paces. After six months spent evaluating eight different tools, Webflow stood out for the precision and clarity it brought to their communication with engineering, since designers were handing off functional prototypes built with real code — not just pretty looking simulations.

Adopting Webflow

Now, the design team starts every new project from a master Webflow template containing all the brand styles and components. From these raw materials, they build and publish prototypes to share with engineering.

From there, the engineering team can just inspect the code to get all the fine details — no more redlining needed.

Now that we’re building prototypes in Webflow, our design and engineering teams are starting to speak the same language.

– TONDA DYSART · DELL

Now there’s less back and forth between design and engineering, since now the design team can create all the front-end styling — from hover states to transitions to interactions — in Webflow, instead of “faking it” in a merely communicative prototyping tool.

Dell’s customer experience design team once used an internal component system to design and prototype solutions. But it took an entire product team to maintain it. And for a largely “non-technical” team of 50+ folks, it wasn’t what you’d call … friendly.Tired of fighting this bloated system, the team started looking for something new.