веб-дизайнер

Customer experience platform | 500+ employees
Customer experience platform | 500+ employees
Customer experience platform | 500+ employees
summary
How Sierra designs with AI
How does a small design team supporting 100+ engineers scale its impact without lowering the bar?
At Sierra, the design team is nearly 20× smaller than the engineering organization it unifies. The company builds a conversational AI platform that enables enterprise brands to deploy autonomous customer experience agents. This operational asymmetry has pushed the team to radically rethink where design creates the highest leverage.
When AI tools can generate, polish, and refine front-end code on demand, a designer's highest-value task is no longer wireframing individual screens. Instead, product designers Wayne Fan and Nick Hiotis have shifted their focus upstream by building the shared structural foundations, data patterns, and flexible components that empower hundreds of engineers to ship high-quality UI independently.
At the same time, they’ve resisted the idea that everything should be automated. While AI has drastically compressed their technical workflows, the team actively resists total automation. They maintain a strict boundary around their craft, intentionally slowing down to sweat the manual details that give a product its personality and soul.
summary
How Sierra designs with AI
How does a small design team supporting 100+ engineers scale its impact without lowering the bar?
At Sierra, the design team is nearly 20× smaller than the engineering organization it unifies. The company builds a conversational AI platform that enables enterprise brands to deploy autonomous customer experience agents. This operational asymmetry has pushed the team to radically rethink where design creates the highest leverage.
When AI tools can generate, polish, and refine front-end code on demand, a designer's highest-value task is no longer wireframing individual screens. Instead, product designers Wayne Fan and Nick Hiotis have shifted their focus upstream by building the shared structural foundations, data patterns, and flexible components that empower hundreds of engineers to ship high-quality UI independently.
At the same time, they’ve resisted the idea that everything should be automated. While AI has drastically compressed their technical workflows, the team actively resists total automation. They maintain a strict boundary around their craft, intentionally slowing down to sweat the manual details that give a product its personality and soul.
summary
How Sierra designs with AI
How does a small design team supporting 100+ engineers scale its impact without lowering the bar?
At Sierra, the design team is nearly 20× smaller than the engineering organization it unifies. The company builds a conversational AI platform that enables enterprise brands to deploy autonomous customer experience agents. This operational asymmetry has pushed the team to radically rethink where design creates the highest leverage.
When AI tools can generate, polish, and refine front-end code on demand, a designer's highest-value task is no longer wireframing individual screens. Instead, product designers Wayne Fan and Nick Hiotis have shifted their focus upstream by building the shared structural foundations, data patterns, and flexible components that empower hundreds of engineers to ship high-quality UI independently.
At the same time, they’ve resisted the idea that everything should be automated. While AI has drastically compressed their technical workflows, the team actively resists total automation. They maintain a strict boundary around their craft, intentionally slowing down to sweat the manual details that give a product its personality and soul.
If we can touch production code more easily with Claude or Cursor, what is a designer's role in trying to empower at scale? Instead of just doing one little pixel at a time, we should build the infrastructure that engineers use to create new features.
Wayne Fan
Product Designer, Sierra
If we can touch production code more easily with Claude or Cursor, what is a designer's role in trying to empower at scale? Instead of just doing one little pixel at a time, we should build the infrastructure that engineers use to create new features.
Wayne Fan
Product Designer, Sierra
If we can touch production code more easily with Claude or Cursor, what is a designer's role in trying to empower at scale? Instead of just doing one little pixel at a time, we should build the infrastructure that engineers use to create new features.
Wayne Fan
Product Designer, Sierra
KEY INSIGHTS
What we learned
01
Small team as an advantage
With zero bureaucratic layers to coordinate through, Sierra's designers align and execute instantly. Sitting shoulder-to-shoulder in the office most days, they run a highly collaborative workflow inspired by engineers: "pair designing". They constantly weave in and out of each other's projects, trading hot takes, handing off tasks seamlessly, and jumping fluidly between Figma components and live Cursor prototypes. While a team this lean naturally has a hard ceiling on how deep it can dive into any single isolated feature, it buys immense horizontal speed and the fluid autonomy to iterate instantly across the entire product ecosystem.
02
From pixels to infrastructure
Early on, the team used Claude to polish production code themselves. It worked, but it didn't scale. As Wayne put it, if a small design team hand-finishes work for a hundred engineers, they've simply added another pair of hands instead of raising the quality bar for everyone. So they shifted their attention upstream: building the components, patterns, and systems engineers assemble from. Rather than fixing quality at the end, they embed it at the start.
03
Shorten the loop between idea and reality
Static canvases often fail when exposed to dense, real-world data. To solve this, Sierra replaced the traditional, multi-day design handoff loop with a continuous prototyping cycle. They now use Figma mainly to communicate high-level concepts or rough wireframes, skipping the need to design every version or edge case. From there, they immediately jump into Cursor to build live prototypes connected to actual product environments. What used to be a days-long round trip of building, breaking, and rebuilding is now compressed into a single morning: Cook, prototype, be wrong, go back—all before lunch.
KEY INSIGHTS
What we learned
01
Small team as an advantage
With zero bureaucratic layers to coordinate through, Sierra's designers align and execute instantly. Sitting shoulder-to-shoulder in the office most days, they run a highly collaborative workflow inspired by engineers: "pair designing". They constantly weave in and out of each other's projects, trading hot takes, handing off tasks seamlessly, and jumping fluidly between Figma components and live Cursor prototypes. While a team this lean naturally has a hard ceiling on how deep it can dive into any single isolated feature, it buys immense horizontal speed and the fluid autonomy to iterate instantly across the entire product ecosystem.
02
From pixels to infrastructure
Early on, the team used Claude to polish production code themselves. It worked, but it didn't scale. As Wayne put it, if a small design team hand-finishes work for a hundred engineers, they've simply added another pair of hands instead of raising the quality bar for everyone. So they shifted their attention upstream: building the components, patterns, and systems engineers assemble from. Rather than fixing quality at the end, they embed it at the start.
03
Shorten the loop between idea and reality
Static canvases often fail when exposed to dense, real-world data. To solve this, Sierra replaced the traditional, multi-day design handoff loop with a continuous prototyping cycle. They now use Figma mainly to communicate high-level concepts or rough wireframes, skipping the need to design every version or