What your designer is actually doing between meetings.

Process · 5 min read

You had a great meeting on Monday. We made decisions, clarified the user flow, and agreed on next steps. The next meeting is Thursday. And now it's Wednesday afternoon and you haven't heard a thing. No update. No email. No Slack message with a progress screenshot. It feels like nothing is happening.

I get it. When you're building something you care about, silence feels uncomfortable. You want to know that progress is being made. But the silence between meetings is actually where most of the real work happens. Let me explain what's going on in the gaps.

The work you don't see

After Monday's meeting, the first thing I do is review everything we discussed. Not just the decisions, but the reasoning behind them. I go back through the product report. I cross-reference what you told me against the user research. I'm looking for contradictions, gaps, and assumptions that need testing. This doesn't produce anything visual. There's no screenshot to send. But it shapes every design decision that follows.

Then I start the competitor analysis. I download apps that operate in your space. I screenshot their onboarding flows, their navigation patterns, their settings screens. I note what they do well and what they do badly. I look at their app store reviews to find the complaints their users have. This takes hours. It's tedious. And it's essential, because I need to understand what your users are already accustomed to before I design something different.

After that comes the actual design work. Mapping user flows. Sketching wireframes. Deciding which screens need to exist and which ones don't. Writing annotations that explain the behaviour behind each element, so the developer doesn't have to guess what happens when someone taps a button or swipes left. Every annotation is a decision. Every decision is based on the research that came before it.

Why the meeting isn't where the design happens

Most clients assume the design happens in the meeting. It doesn't. The meeting is where I present options, where we make decisions together, and where you give feedback that changes the direction. But the thinking, the sketching, the comparing, the discarding of bad ideas and refining of good ones? That all happens before I walk into the room.

Amabile's research at Harvard analysed over 9,000 diary entries from knowledge workers and found that creative cognitive work needs uninterrupted time. Creativity doesn't happen in one-hour blocks squeezed between other commitments. It needs sustained focus. That's why the gaps between meetings matter so much. Those blocks of quiet, uninterrupted time are where the connections get made, where one sketch leads to a better sketch, and where the design starts to actually feel right.

If I sent you updates every few hours, I'd spend half my time context-switching between communication and creation. And the design would suffer for it. The silence isn't neglect. It's concentration.

What Thursday's meeting looks like because of it

By Thursday, I've got something to show you. Not just pretty screens, but considered decisions. I can explain why the navigation works this way instead of that way. I can show you what the competitors do and why I chose differently. I can walk you through the user flow and point out where I've anticipated edge cases you hadn't thought of yet.

That depth only exists because the time between meetings was spent doing the work, not reporting on the work. There's a real tension between keeping clients informed and actually producing quality output. I've found that the best approach is to respect the meeting rhythm. We meet, we decide, I go away and build on those decisions, and I come back with something meaningful. Not half-finished screenshots. Not work-in-progress that needs five minutes of explanation before it makes sense.

So if it's Wednesday and you haven't heard from me, that's a good sign. It means I'm deep in the work. The timeline is on track. The thinking is happening. And Thursday's meeting is going to be worth the wait.

Sources
Creativity Under the Gun (Amabile et al., 2002, Harvard Business Review) - Analysis of 9,000 diary entries showed that creative cognitive work needs uninterrupted time and focus.

Related blog posts:

Your timeline is wrong →

What happens between the prototype and the App Store →

Why I say no to some projects →