Mari Luukkainen

Main

  • Home
  • Blog
  • Projects
  • About
  • Work with me
  • Resources
  • Now
  • Frameworks
  • GTM30
  • Strategic Growth Hacking

Account

XGitHubLinkedInEmail
  1. Home
  2. /Blog
  3. /Why I don't use static design workflows anymore

Why I don't use static design workflows anymore

September 8, 2025
Vibe Coding

In my vibe coding workshops there’s always at least one person asking about design. Usually it’s something like: “How do I move my Figma design into Cursor?”

I get why people ask. That’s how we were all taught to build: design first, code later. But honestly, I can’t find a reason anymore to include static design workflows in how I build. It just slows everything down.

Static design ≠ product

The idea of spending weeks making pixel-perfect mockups in Figma before you even touch code doesn’t make sense in 2025. A static file isn’t your product. Your product is the live site or app that people actually click on.

Translating static designs into code is double work. First you “design” something, then you rebuild it from scratch in code. For what? To have it look exactly the same? That’s not value creation. That’s just process for the sake of process.

Good enough > perfect pixels

I haven’t designed a single one of my websites. I just put together UI components, tweak where needed, and ship. The results? They look good enough and they convert. And conversion is the metric that matters, not whether a corner radius matches some Figma file.

When you let go of static design, you cut cycle times down to hours instead of weeks. You go from idea → live test without an entire handoff step in the middle.

Where design still matters

I’m not saying design is useless. At some point, some companies do need a lightweight design system or a visual identity to keep things consistent across teams. But that’s an exception, not the default.

And if you bring in designers, they need to be AI-native. Meaning: they’re building directly into code, into components, into production workflows. Adding someone to make static screens for handoff? I can’t justify that anymore.

The bottom line

Static design workflows are a relic. They slow down shipping. They add layers of unnecessary work. For me, coding with components is faster, cleaner, and closer to reality.

If you’re still forcing static design into your product workflow, ask yourself: are you building for speed and outcomes, or are you holding onto a process that doesn’t create value?

Newsletter

Get posts like this delivered to your inbox.

My Account

Access books, resources, and your reading history.

Sign in or create account

Further reading on growth & product

More articles that explore similar topics, frameworks, and playbooks.

I built a mini admin panel so our team could stop asking me to post things

February 2, 2026

Stop buying SaaS for problems you can solve in a morning.

Vibe Coding

I built a tool to automate my vibe coded app's marketing content

January 8, 2026

How I built Yeetpost to automate Femcode's LinkedIn marketing - automatic event reminders and changelog updates via simple API integration with Vercel Cron.

Vibe Coding

CMS as an execution bottleneck in modern GTM systems

December 17, 2025

Why modern GTM systems break under CMS complexity and perform better with code and markdown based architectures.

Vibe Coding
Back to blog