Most people meet design thinking for the first time inside a workshop: a room papered with sticky notes, a facilitator keeping time, a day that runs from breakfast to happy hour. The trouble starts the following Monday. The sticky notes survive only as photos in a shared drive, and by the next sprint meeting nobody reopens the empathy map or says “How might we” out loud again. Across a string of product design consulting engagements, the pattern has been consistent: design thinking holds up far better as a daily habit than as a special occasion.
1. Why the Insight Evaporates by Monday
The core weakness of workshop-only design thinking is that it’s a one-off. A full day of exercises takes real energy to plan and run, and that effort makes it easy to feel finished the moment the day ends — a kind of psychological full stop. What a workshop produces also tends to sit at the level of big-picture insight, which doesn’t translate cleanly into the specific tasks sitting on tomorrow’s board. It’s usually the first thing dropped the moment a project lead changes or a deadline tightens. Over time, design thinking gets remembered as an event the calendar recorded once, not as a way the organization actually thinks.
2. The Loop Design Thinking Was Built to Close
Understanding why design thinking emerged in the first place makes clear why boxing it into a workshop wastes the point of it. Traditional problem-solving tended to move in one direction — define requirements, design, build, validate — a linear sequence that assumes the problem is already well understood. But for something as slippery as figuring out what users actually need, a looping approach works far better: form a hypothesis, test it quickly, circle back, revise. Design thinking was proposed specifically to embed that iterative loop inside how organizations work, not as a one-time ritual.
That context is exactly why a single workshop can never carry the whole method. Compress a framework whose entire value lies in repetition into a one-day event, and the most important ingredient — the repeating part — is precisely what gets left out.
3. Cutting the Five Stages Down to a Day’s Work
Stanford d.school’s five-stage framework — empathize, define, ideate, prototype, test — was written for a workshop, but every stage also fits inside an ordinary workday without a facilitator or a single sticky note.
Empathize — Spend 20 minutes reading through recent customer inquiries or support logs instead of scheduling a session.
Define — Rewrite one line on this week’s meeting agenda as a single “How might we…” sentence.
Ideate — Drop three alternative directions into a team chat thread before anyone commits to one.
Prototype — Skip the polished mockup; one sketch on paper is enough to start.
Test — Show the screen to a single colleague and watch, rather than ask, how they react.
4. Frequency Beats Intensity — and It’s Not Just for Designers
Habits are built on frequency, not intensity. Adding five minutes at the top of a recurring team meeting — “what did we notice from a user’s point of view this week” — is enough on its own to keep the empathize stage running continuously. The same logic works for ideation: a short ritual of writing down at least three possible solutions every sprint quietly breaks the habit of anchoring on whichever idea arrived first.
The one-day workshop
Delivers one big insight, but the energy it takes to plan and run makes it easy to feel finished the moment it’s over.
The five-minute routine
Small on its own — five minutes in a meeting, three alternatives a sprint — but it reshapes how a whole team thinks, one repetition at a time.
💡 Pro tip — Sharing “what we learned from a user this week” for five minutes before a standing meeting is enough to keep the empathize stage running on its own. One routine like that will outlast a full day of workshopping.
It’s also a common mistake to treat design thinking as a tool that belongs exclusively to the design team. Rewriting an agenda item as “how might we,” or the habit of listing several solutions before choosing one, applies just as well to engineers, product managers, even sales. When only the design team works this way while the rest of the organization keeps its old habits, friction shows up everywhere teams have to collaborate. For the habit to take root across an organization, designers are better positioned as the ones spreading the method — while letting each team translate the practice into the language of its own work, rather than copying design’s process exactly.
Closing thoughts
Design thinking isn’t a special occasion; it’s a way of asking questions, repeated daily. Run through this checklist before your next planning cycle.
Is there a line on this week’s agenda that could be rewritten as “how might we”?
Did you write down at least two alternatives before settling on a solution?
Are you skipping straight to development without any kind of prototype?
Has it been more than a week since you showed a screen to a colleague or user and watched their reaction?
Have you actually referenced the output of your last workshop in a recent decision?
Are colleagues outside the design team using this routine too?
It’s enough to start with one item: rewrite a single upcoming meeting agenda as “how might we.” If there’s no room on the calendar for a workshop, pick just one of the five stages and run it inside today’s work instead.
Design Daily Life · Notes on design, daily