The Real Cost of a “Finished” Design
When stakeholders see a polished mockup or a clean prototype, they’re looking at the final mile of a long journey. Unless they’ve done design work themselves, they won’t see the research, iteration, or testing that produced that output. That knowledge gap is a common source of unrealistic deadlines: polished deliverables tend to make the production process look much faster than it actually is.
To make matters worse, non-designers often try to measure progress by counting deliverables. But when polished outputs arrive quickly, it reinforces the assumption that the entire process is quick. The real value of design, however, lives in the quality of the process itself, not in the artifacts it produces.
Protecting the Process Without Getting Defensive
Design depends on tightly orchestrated feedback loops between customers, designers, developers, and stakeholders. Cutting corners to meet a deadline breaks those loops. When inputs are poor, outputs follow suit—sometimes in ways that are reversible, but often leading to damage that lingers for years. Defending the process is not just about designer convenience; it’s about protecting the user and the business.
So how do you push back without being defensive? A few straightforward tactics work well:
- Frame it around user value. Never present work as “finished.” Make clear that ongoing testing is intentional and that the design process exists to maximize user value. Business value follows from user value, not the other way around. No productivity tool can automate that value, and there is no later phase to quietly fix a broken design.
- Negotiate for uninterrupted time. Ask for dedicated blocks of heads-down work. If that’s not possible, suggest shifting priorities or reducing the scope of the current cycle.
- Calibrate expectations honestly. Don’t assume stakeholders understand your workflow just because you try to understand theirs. Be explicit about what is needed to reach a shippable state, and you’re more likely to receive support instead of speed demands.
- Show progress early and often. Designers often hide work until it feels respectable. A better approach is to share work in progress frequently—not to solicit subjective opinions, but to ask a direct question: does this help deliver user value?
Proactive reporting also helps keep everyone aligned. A short, two-minute video update shared once a week can be far more effective than a long status meeting.
Visualize the Work: Event Storming
Abstract process diagrams such as the Double-Diamond or Triple-Diamond rarely communicate the true complexity of real UX work. A more effective approach is to visualize the process as what it actually is: messy, interdependent, and full of moving parts.
Running a Session
Gather everyone involved in the project for a two-hour session. On a shared Miro or FigJam board, place orange sticky notes along a timeline, each representing an event required for the project’s success. Cluster related events and organize them into lanes, covering user testing, stakeholder approvals, research tasks, and design initiatives.
The resulting timeline serves as a living reference: a shared record of the work remaining or completed. You can add multiple lanes to map work across different UX activities—research, metrics, and so on—and include any other relevant domains: technical risks, stakeholder engagement, or user testing.
Why It Works
Event storming gives you an honest and real visualization of the design process. It is messy and complex, because real projects are messy and complex. It is also customized to the specifics of a given project, with the actual people who need to be involved for successful delivery.
The biggest payoff is a shared understanding across all teams about what is being done, how it is being done, and what is required from everyone to get to a successful finish. That mutual clarity is a strong defense the next time someone asks why the design “isn’t done yet.”
Design without a deliberate process leads to what Pavel Samsonov calls the “form factor trap”—a fixation on final output over the thinking that produces it. Finding real time for design requires deliberate effort; several practitioners have written practical guides on increasing heads-down time and managing overloaded schedules. These resources are worth reading if your team is feeling the pressure of too much work and too little time.
