Teams are building. Replit, Claude, Figma, Cursor — the tools are extraordinary, the speed is intoxicating, and the distance between an idea and something that looks like a product has never been shorter. What used to take months now takes days. Sometimes hours.
And then it ships.
Not to users. To buyers. To leadership. To the board deck. Sometimes directly to production. (You should really call me, if this is your org.)
The users — the actual humans who will open this thing, try to understand it, and decide in the first thirty seconds whether it earns a place in their workflow — often don't see it until it's already live. In some organizations, this is also true for the ever-dwindling design team.
I've watched this happen at enterprise scale. I've sat in rooms where a prototype got green-lit because a VP liked the demo. Where a product (read: prototype) got sold because the buyer was satisfied and the deadline was real. Where "we'll iterate based on feedback" became the plan, because iteration sounds humble and scientific and nothing like what it actually is: releasing something untested and hoping the fallout is manageable.
But that’s not iteration. That's just shipping and hoping.
And even in some of the best orgs, where we are working with limited resources, it SEEMS like the best option because “If we don’t sell something now, there will be no company later.”
The Figma bill nobody saw coming
Let me give you a concrete example of what happens when you skip the humans who actually use your product.
When Figma shifted its token pricing model — moving from not charging designers and PMs for Dev Mode access to charging — some organizations discovered overnight that their annual Figma bill had quadrupled. Quadrupled, in just the two months they’d been using it.
Why? Because no one had actually mapped how the tool was being used across the organization. AND, Figma wasn’t charging in those first few months to give people the chance to learn it—so how could we even know what the work we were doing COULD cost?
The buyers had made a decision based on the the mandate to use AI for design in order to de-centralize/democratize/speed up the design process. I get it.
This is not a story about Figma. This is a story about what happens when you optimize for the buyer experience and treat the user experience as a downstream concern. The bill comes due. Sometimes it's financial. Sometimes it's adoption. Sometimes it's trust.
"But testing delays release"
I’ve heard this a lot, and even more in the past 3 months.
Yes. Sometimes it does.
It also delays releasing something that doesn't work. It delays releasing something confusing. It delays releasing something that solves the problem you assumed users had, rather than the one they actually have.
There is a version of speed that is genuinely valuable — getting something real in front of real people quickly, learning fast, adjusting. That's good. The prototyping tools we have now make that kind of speed more achievable than ever, and I think that's genuinely exciting.
But there's another version of speed that is just anxiety in a hoodie. Ship fast, fix later, move on. That version doesn't save time. It borrows it, at interest, from the future.
Not everything needs to be released. Some things need to be tested, learned from, and shelved. Some things are gold with garbage attached and need thirty minutes with five users to figure out which is which. Some things are genuinely not ready, and releasing them anyway doesn't make them ready — it just makes them your users' problem.
What's actually being skipped
When we skip user research and testing, we're not just skipping a process. We're skipping the only reliable source of truth about whether something works for the people it's supposed to work for.
Buyers buy. Users use. These are not the same act, they are not performed by the same people, and they do not require the same thing from a product. A buyer needs to believe in the value proposition. A user needs the thing to actually work in the context of their real life, with their real constraints, on a Tuesday afternoon when they're already behind on something else.
We've always known this. What's new is that the gap between ideation and production has collapsed so dramatically that it's now possible — it's easy — to skip the step where you find out if you've built the right thing. The tools don't enforce a pause. So the pause doesn't happen.
That's not a tools problem. It's a culture problem. It's a leadership problem. It's a problem that will look, for a while, like speed — until it doesn't.
A note on AI
None of this is an argument against the tools. I work with these tools. I think they're remarkable. The ability to prototype an idea in an afternoon and put something tangible in front of a real user is a genuinely powerful thing — if you use that speed to get to users faster, not to replace the step where users are involved at all.
AI should compress the distance between idea and learning. And even from learning to iterating. But it should not replace the part where actual humans validate that what we have built will improve their lives before we build it, incorporate it into existing products and platforms, and ship it.
Strategic Creations Studio helps organizations integrate AI and design thinking without losing the humans in the middle. If this resonated, I'd love to hear what you're seeing inside your organization.