Skip to content
Back to work
Amazon Business 2021–2022

Code-First Prototyping at Global Scale — Amazon Business Telescope

45% reduction in prototyping iteration time. Adopted across 4 global hubs.

RoleUX Engineer Manager
Timeline4 months
Team2 engineers + 1 data analyst
4 Global hubs
45% Faster iteration
Code-first New design workflow

Challenge

Amazon Business needed faster prototyping across 4 global engineering hubs. Traditional design-to-dev handoff was too slow.

Solution

Created "Telescope" — a code-first prototyping tool. Designers prototype in code, not in static mockups. Deployed across 4 global hubs. Integrated with existing CI/CD pipelines.

Architecture

React-based prototyping runtime + shared component kit + CI/CD hooks + analytics.

Technologies

  • React
  • TypeScript
  • Code-First Design
  • Internal Tools
  • Global Scale

The original objection to Telescope, from almost everyone, was predictable: why can’t designers just use Figma. The answer was that Figma was not what slowed us down. The handoff was. Once a designer finished a mockup, it took two days for someone to re-build it in code, another two to wire it into the real data, and by the time a buyer could click on it the design had already moved on. We were iterating on fiction, not on the product.

Telescope was a thin runtime around the existing component library. A designer would write a prototype as a small React file, point it at a real catalogue endpoint, and ship it to a URL in under a minute. The prototype used the real components, the real tokens, the real data. There was no handoff because there was nothing to hand off — the prototype was the same code that would eventually ship to production, minus the analytics.

The fastest handoff is no handoff. The second-fastest handoff is one where the artifact you hand over is the same artifact that runs in production. Everything else is a translation, and every translation loses information.

— Amazon Business design ops retro, 2022

Rolling it out globally was where it got interesting. Four hubs meant four cultures of how design and engineering worked together, each with its own pre-existing opinions about what a prototype should be. Some teams adopted it in a week. Others took three months and a dedicated working group. The tool was identical in every hub; the time to adoption was a function of how much the local design leadership trusted the engineers already.

The Telescope effect

Before: static mockup. After: working code.

Drag the divider →

Figma mockup

Static. Handoff needed. Two days to validate one interaction.

Live prototype

Live. No handoff. Designer ships directly to main.

45% 45% faster iteration