One Tool to Rule Them All

"We shape our tools and, thereafter, our tools shape us".

Design and engineering collaboration is about to undergo another tectonic shift — and this time, it's going to be a bigger shift than what led to Figma.

The Last Big Shift: 1 Designer → N Designers

The previous shift arrived in the mid-2010s, when Figma brought the design canvas—previously locked inside desktop-only apps like Sketch—directly to the browser and unlocked real-time collaboration. Teams could move from one designer working in isolation to N designers working together simultaneously.

That was a massive unlock. The next shift could go one step further.

The Next Shift: N Designers → Everyone

In 2026, I think Figma (for design-first builders) and the IDE (for code-first builders) will increasingly converge into a shared environment. The boundary between "design tool" and "code tool" will become less meaningful.

The promise is a move from N designers collaborating to everyone—designers, engineers, PMs—working in the same environment. Engineers can lean into the design side. Designers can get closer to production code.

Some of today's handoff disappears because design intent and implementation can be inspected and changed in the same place.

One Source of Truth

Today, even on disciplined teams, the design system lives in two places: a Figma master file and the actual code libraries. These can drift apart, creating friction, bugs, and wasted cycles reconciling differences.

A genuinely unified system could reduce this drift. One source of truth for the design system. One place where a component is the component—not a picture of it in one tool and an implementation of it in another.

What This Means for Teams

For teams scaling fast, especially those where design is lean, this matters a lot. Your engineers can contribute to design without switching tools. Your designers can see real implementation constraints in real time. The gap between the two gets smaller.

A shared environment won't erase specialization, review, or ownership. Production code still carries constraints that a canvas doesn't, and design exploration needs room to stay open-ended. What it can erase is the lossy translation between two representations of the same work.

Exactly how this plays out is uncertain. Maybe Figma evolves from within. Maybe a new entrant nails the unified experience first. Figma's Claude Code integration is one sign that the loop is already starting to close.

But the direction is clear: separate tools for separate roles are giving way to environments organized around shared work. Teams that embrace this early can ship faster and with higher fidelity than those still passing mockups over the fence.

The roles are merging, and the tools have to merge.