Becoming an AI-Era PM 10 | High-Fidelity First: I Haven't Drawn a Wireframe in Six Months
Had dinner last week with a friend who does design, and he mentioned his team had cut the whole wireframing step. I froze for half a second, then realized: same here. I went back and checked Figma — that board labeled “low-fi wireframes” hadn’t been opened once in six months.
It’s not that I got more advanced. It’s that drawing them stopped being useful.
Wireframes are cheap, and that’s their only virtue
Why did we draw wireframes in the first place? Because building the real thing was expensive.
Building one actual clickable page meant a designer producing mockups, a front-end dev slicing them up, rounds of back-and-forth — a week or two, minimum. Something that pricey, of course you’d want to align on direction with gray-box sketches before going deeper, to avoid burning it all for nothing. A low-fi wireframe was just a cheap “align early” tool. Cheap was its only virtue.
Building the real thing isn’t expensive anymore. One sentence, and Lovable, v0, Bolt, or Claude Code hands you a page you can actually click in a browser in minutes. n8n’s product team ripped their wireframe flow out entirely; a director at Delivery Hero hand-built a prototype in an hour without pulling in an engineer. By early 2026, industry reports had 67% of design teams already wiring AI generation tools into their day-to-day.
When “building a real one” and “drawing a fake one” cost roughly the same time, the fake one has no reason left to exist.
Gray boxes hide exactly where things go wrong
The most annoying thing about low-fi is that it forces a room full of people to argue over gray boxes.
I’ve paid for this. A wireframe goes up in a review, and everyone stares at a placeholder rectangle debating whether that button should shift two columns to the right. But it’s a gray box — no real data, no loading state, no empty list, not a single error. The places that actually blow up? A wireframe shows none of them. By the time it’s really built, the problems are all hiding in the states it left out: rows break once there’s enough data, the spinner spins into eternity when the network’s slow, a first-time user lands on a blank screen with no idea what to do.
After that one, it clicked for me: instead of making everyone stare at a fake picture and fill in the blanks in their heads, just put the real thing out there and watch it run.
I just build something runnable now
Skip low-fi, go straight to a runnable high-fidelity version. Calling it “high-fidelity” makes it sound like a high bar — it’s really just four things, and I usually go in this order (not some official answer, just the path that comes naturally to me):
One, use real content, not Lorem ipsum. Placeholder text lies to you — a screen of fake Latin looks perfectly tidy, but swap in a real long title, a real dollar amount, a real username, and the layout gives itself away instantly. So when I brief the AI I say it outright:
“Build an order list. Use realistic data: real-sounding product names, a real price range, real timestamps — no Lorem ipsum, no item1/item2. Throw in one absurdly long product name and see if it blows out the layout.”
Two, fill in every state. Loading, empty, error, success — don’t skip a single one. This is where low-fi cuts the most corners and does the most damage. I follow up now with: “Build out what the empty list looks like, what loading looks like, what a failed request looks like — I want to click through each of them.”
Three, actually clickable, not a pretty screenshot. I want to click in, click back, fill out a form and watch how it responds. A lot of problems only surface once a finger actually pokes at the thing.
Four, run it for real where it’s meant to live. Something for phones, I open on a phone — I don’t eyeball a rough version on a laptop and call it done. I’ve been burned more than once by “looked fine on the desktop, button was untappable on the actual device.”
A version takes minutes, so now I build three or four directions at once
Back when a prototype was expensive, I’d narrow the options down to a single “best” one in my head before I lifted a finger — because getting it wrong was costly.
Now a version takes minutes, and I’ve dropped that habit. Once I’m clear on what I’m trying to solve, I just have the AI build three or four directions and put them side by side: one list-style, one card-style, one all-in-one-step, one guided-step-by-step. Lining them up in the browser and clicking around tells me which feels right and which feels off far more clearly than daydreaming ever could. Pick a direction and take it deeper — that beats betting on the right one from the start.
Trying five directions in an afternoon — in the wireframe era that was unthinkable.
The one thing that keeps me on guard: a runnable high-fidelity version is too real — real enough that I’ll look at the first cut and think “that’s it, ship it.” But it’s only “clickable,” and that’s a universe away from “shippable” — with a pile of unhandled edge cases, performance, security, and real data volume still in between. I’ve conflated those two more than a few times, and the next piece happens to be about exactly that.
So I force myself to build two more versions after the first — not because I’m disciplined, but because the first version has fooled me too many times.
Discussion