We removed the pause from design work

I used to think the blank page was just friction. Annoying friction. The kind that makes you open Figma, stare at nothing, move one rectangle around for 14 minutes, then question every career decision that led you to becoming a person who professionally drags pixels for a living.

Lately, I think it was doing more than slowing us down.

It was forcing a pause.

You had to sit with the problem long enough to decide what you were actually trying to make. You had to pace a little. You had to talk yourself into the first move. You had to form an opinion before the work became a thing other people could react to.

That pause was uncomfortable. It was also where a lot of the thinking happened.

Now we have workflows that can remove that pause almost completely.

The cold start is mostly gone now

I use Whisper Flow constantly. I use ChatGPT constantly. I’ll talk through a messy idea like there’s another person in the room. I’ll ramble through the shape of the problem, argue with the first output, sharpen the angle, add more context, remove the weird AI smell, and suddenly I have the bones of something useful.

A PRD.

A piece of product collateral.

A prototype brief.

A set of prompts for Cursor.

A better Slack message.

A rough narrative for a feature that was just fog in my head 20 minutes earlier.

That part is genuinely useful. Getting from zero to 0.5 used to take a stupid amount of energy. Sometimes the hardest part of the work was convincing your brain to put the first ugly version on the page.

Now that first ugly version arrives fast.

Sometimes shockingly fast.

Then the first thing exists, and the machine quietly invites you to make the next thing.

And the next thing.

And the next thing.

Which is great, until you realize you just created a pile of shit your brain now has to carry around.

The physical drag disappeared

Design work used to have more physicality to it. You opened the file. You moved frames around. You dragged pixels. You duplicated sections. You nudged spacing. You clicked into layers. You felt the work through the mouse.

That was slow, and sometimes painfully inefficient.

But it created a pace.

Your hands could only move so fast. The canvas could only get so messy before you had to stop and organize it. The act of making created natural checkpoints because the work had weight. You could feel when the file was getting out of control.

Now a lot of the work happens through voice, prompts, AI-assisted editing, generated artifacts, and rapid iteration loops. Progress is still progress. In a lot of cases, it is better progress. You can explore more directions, pressure-test more ideas, and get farther before the meeting even starts.

The exhaustion just changes shape.

It is no longer only the fatigue of making.

It is the fatigue of holding.

The fatigue moved from your hands to your head

I think people are feeling this, but not naming it yet.

AI did not make the work feel lighter. It made the work multiply faster.

You can talk your way into ten useful artifacts before lunch, then spend the afternoon trying to remember which one actually mattered. Was the prototype direction the point, or was it the narrative that came out of it? Was the PRD the thing, or was it scaffolding for the real decision? Did the prompt make the idea sharper, or did it just make the idea louder?

That is the weird new fatigue.

You can now create more than you can cognitively hold.

And because the output is so easy to generate, it gets harder to tell when you are making progress or creating more inventory for your brain to manage.

That inventory has a cost.

More output means more memory debt

Every artifact asks to be remembered.

Every doc has a reason it exists. Every prototype has a decision hiding inside it. Every prompt creates a branch. Every branch creates a possible direction. Every direction creates another thing someone might need to review, explain, kill, defend, or clean up later.

This is where the rot starts.

Unfinished thinking becomes finished-looking output.

A rough idea can look like a strategy. A half-decision can look like alignment. A prompt can make something feel more resolved than it actually is.

And because it looks real, people start reacting to it like it is real.

Then you are no longer thinking through the work.

You are managing the consequences of the work-looking shit you accidentally created.

That is where the pause matters.

Nick’s story reminded me why digestion matters

This week’s podcast with Nick hit this from a completely different angle.

He talked about losing a job at a startup, then writing about what happened and what he would do differently next time. That writing was not some polished content strategy. It sounded more like self-therapy with a publish button.

Then people started reaching out.

Someone said the article helped them decide whether to join a startup. Someone else asked if they could book his time. Slowly, that thinking became useful to other people. Eventually, it became part of how his freelance work started.

That part stuck with me.

The value came from processing it first. He had to sit with the experience long enough to understand what actually happened. He had to turn the scar tissue into judgment.

I worry we are starting to skip that part.

Everything can become output before it becomes understanding

Bad meeting? Turn it into a post.

Loose thought? Turn it into a strategy doc.

Half-formed product idea? Turn it into a prototype.

Random frustration? Turn it into a carousel, a prompt, a script, a workflow, a new branch in Cursor, and three Slack messages that make everyone else feel like they are now behind.

I use this stuff every day, so I’m not pretending I’m above it.

But there is a difference between turning thought into progress and turning every unfinished thought into inventory.

The first one moves the work forward.

The second one makes your brain feel like it has 47 browser tabs open and one of them is playing music.

Probably some Drake song you didn’t even choose, but somehow it has been looping in the background while you slowly lose your mind.

The first input is where the judgment lives

The more I use AI in my workflow, the more I think the first input matters.

The voice note. The messy ramble. The context dump. The part where you are not asking for a finished artifact yet, but trying to understand what you actually believe.

That discovery layer is where the creative work still lives.

The machine can help shape it, challenge it, clean it up, and turn it into something usable. But it cannot replace the taste, judgment, business context, and weird pattern recognition that make the artifact worth making in the first place.

This is also why I keep coming back to the fundamentals we built into the Product Design Blueprint. Before the artifact gets shiny, you need to know what problem you are solving, what decision is being shaped, and what would make the work worth doing at all.

A lazy first input becomes fast noise.

A thoughtful first input can become scary useful.

So the question is not whether AI belongs in the workflow. It obviously does. The question is whether we are protecting the thinking before the workflow starts producing.

I’m trying to slow down before the artifact sprint

I’m not trying to use AI less.

That feels like pretending the calculator ruined math.

I’m trying to be more careful about the moment before I ask AI to create another thing. Especially when I’m working on a PRD, a prototype prompt, a collateral piece, or anything that can quickly turn into downstream work.

I try to stop and ask what job the artifact has.

Is it supposed to help engineering scope something? Help sales explain value? Help a PM make a tradeoff? Help leadership understand risk? Help a client believe the experience is real? Help me think through the edge cases before the team burns time building the wrong thing?

When I skip that step, I can still produce a lot.

It just creates more stuff to sort through later.

When I do that step properly, the output tends to be cleaner because the artifact has a job before it has a format.

And if you are too close to the work to see whether the artifact is actually helping or just adding more polished noise, that is exactly the kind of thing Nick and I look for inside the Design Table Audit, because sometimes the problem is not the effort. It is that the effort is aimed at the wrong decision.

Obvious things get bulldozed by speed.

The expensive part is not always making the thing

This is where AI productivity gets weird.

The output looks cheap because the artifact appears quickly. A doc that used to take two hours can show up in 15 minutes. A prototype direction that used to take a day can become a real thing by lunch. A rough narrative can be shaped before the meeting invite even lands.

That is real leverage.

But the thinking, review, alignment, memory, and cleanup still cost something.

Someone has to remember why the thing exists. Someone has to decide which version matters. Someone has to explain what changed. Someone has to kill the branches that were interesting but not useful. Someone has to keep the work from becoming a beautiful landfill of almost-good ideas.

Sometimes the expensive part is not making the thing.

It is keeping track of why the thing exists.

The pause needs to become intentional now

The old workflow gave us pauses by accident.

The blank page. The slow canvas. The annoying first draft. The physical act of moving through the work. None of those were perfect, but they created natural edges.

Now those edges are gone.

So we probably need to add the pause back on purpose.

Not as some heavy process. Not as a new framework. Not as a team ritual with a Miro board and a name that sounds like a consulting firm invented it in an airport lounge.

Just a small moment before the machine starts helping you multiply the work.

And honestly, this is one of the reasons I still think designers need other designers around them. Not just to compliment the work, but to help notice when the work is turning into motion. That is part of what we are trying to create inside the UX and Product Design Community, because most of this stuff gets easier to see when you are not alone in your own file, pretending the 19th variation is still strategy.

What is this thing supposed to change?

What decision does it support?

What will become harder if I create it?

That last question is the one I keep thinking about. Every artifact adds weight, even when it was easy to make.

The episode that made me think about the pause differently

Nick’s episode is not really about AI. It is about the longer arc of a designer trying to get more control over his work, his career, and his judgment.

But the part that stayed with me was how much value came from him processing what happened before turning it into something useful.

That feels connected to the AI moment we are in now.

We can make more than ever, but we still need time to understand what any of it means.

The blank page was annoying. I’m not asking for it back exactly.

I just think we may need to rebuild some version of the pause it gave us.

You can watch the full conversation with Nick here: The Design Table Podcast episode​

Till next week,