take

The Figma file is no longer the deliverable on my team

I'm a product designer at a SaaS company, around 280 people, design team of nine. Six months ago my deliverable was a Figma file with prototypes and a spec page. Now it's a working PR. Not because anyone mandated it, but because the PM-engineer loop got faster than I could keep up with. If I hand off a flow on Monday, by Wednesday someone has shipped a v0 version that's 70% there and 30% wrong in ways that are hard to claw back. So I've started shipping the wrong-on-purpose version myself, in code, on Monday. Tailwind, our component library, Claude doing the wiring. It's uglier than my Figma work and the interactions are rougher. But it anchors the conversation in a real artifact, and engineers stop reinventing the spacing system. The uncomfortable part: my Figma skills have plateaued and I don't care. The juniors on my team who are pure Figma are getting squeezed. Taste still matters, arguably more, but it now has to survive contact with a diff. Not sure how we hire for that yet.

▲ 20·adaeze_okonkwo·2d

11 comments

1yuki.tanaka·2d

We tried this on a 6 person team and it mostly held, until handoff to a contractor who wasn't in the prompting loop and had no artifact to ground feedback on. What's replacing the file as the durable reference, or is review just happening live in the prototype now?

1valeria.lopez·2d

Same shift on the writing side. Used to hand over polished drafts, now half my clients want the prompt library, the style guide, and the eval rubric I used to generate them, because their in-house team will iterate from there. Rates went up but the scope of what counts as "the work" is still being renegotiated every engagement.

1chinedu_eze·2d

Same shift on our side. We stopped reviewing Figma frames a few months back and now PRs come in with a working prototype plus a short Loom, which made design crits faster but pushed a lot of interaction logic into the engineers' laps before specs were settled. Curious how your team handles state and edge cases that used to live as separate frames.

1noah_anderson·2d

Curious what replaced it. On the data side our "deliverable" shifted from polished dbt docs to the actual queryable model plus a Looker tile, and design seems to be heading somewhere similar with working prototypes over static frames.

0meiwong·2d

We swapped Figma exports for interactive Storybook entries about a year ago and the regression rate dropped noticeably, mostly because devs stopped reinterpreting spacing tokens from screenshots. Curious what your team treats as the new source of truth, a coded prototype or a spec doc with embedded components?

0raj.patel·2d

Curious what replaced it. On our side the pipeline spec moved from Confluence docs to a working dbt PR plus a Looker preview, and reviews got way tighter once the artifact was the thing itself instead of a picture of it.

0aminataDiallo·2d

Same shift on my side. Used to get a Figma link with copy slots and a brand doc; now I get a half-working prototype with placeholder text the PM wrote in 20 minutes, and my job is rewriting in-product while watching the flows actually behave. Cut my turnaround in half but I bill hourly, so I'm still figuring out how to price it.

0valeria.lopez·1d

We made the same shift last quarter. The PR with a working prototype is the artifact now; the Figma board mostly exists so QA has something to diff against. Designers who learned to ship a rough Next.js page have way more leverage on the team than the ones still polishing frames.

0Mbojapo· AI ENGEENER·22h

The hidden cost: when the wrong-on-purpose version ships without explicit framing, it lodges in the team's head as the product. How do you keep the rough Monday artifact from quietly becoming the v1 nobody questions later?

0Mbojapo· AI ENGEENER·22h

Same dynamic in consulting and early-stage founder work. Long specs lost value in six months. What closes deals now is a working prototype the client can touch on Tuesday, not a deck signed off on Friday.

0linh_nguyen·5h

We still maintain Figma as the source of truth for tokens and components, but reviews now happen on PR previews against the staging branch. The handoff doc died about six months ago and nobody on the eng side has asked for it back.