When the Process Holds You Hostage
Every UX designer loves the process. Research, define, ideate, prototype, test, iterate. It looks beautiful on a slide and it absolutely matters. But here is the reality: sometimes you do not get the luxury of the full textbook cycle, and clinging to it like dogma can tank your credibility, stall momentum, and burn bridges with the teams you rely on.
I watched a colleague refuse to deviate from the correct process. Research had to happen before anything. Wireframes had to precede prototypes. User surveys were mandatory. On paper, ideal. In our actual working environment, not realistic. We already had a design system, clear requirements, and the business needed screens fast.
That designer insisted on writing user surveys and waiting on feedback before moving forward. It caused sprint delays, created friction with PMs, developers, and BAs. The work was technically right according to the UX playbook, but completely wrong for the moment we were in.
Protecting UX is not about following a checklist. It is about supporting delivery while improving the product. Sometimes you have to read the room and prioritize velocity over ritual.
What Actually Matters
Here is what that designer should have done: Use the time and tools you already have. Get just enough validation from accessible stakeholders. Move. Deliver. Then adjust if needed.
This is not about abandoning principles. It is about knowing when to stand firm and when to adapt. Because in the real world of product delivery, timing, customer expectations, and internal relationships matter just as much as the perfect flow diagram.
The Meeting That Made the Difference
We were tasked with presenting prototypes to customers in person. We drove out to their site, sat in their conference room, and walked them through the experience live. Not traditional. But it worked.
When it was my turn, I went a step further. I had alternate screens ready and made small adjustments in real time based on their feedback. The room lit up. Instant buy-in. The customer felt seen. The BAs felt supported. Everyone walked away energized.
One UX teammate hated the approach. He thought live changes broke process discipline. He sat stiff in the room, showed his screens, refused to adjust anything on the spot. The customer noticed. The BA really noticed. He was pulled from future customer sessions. I was asked to take them back.
That is the consequence of valuing purity of process over outcomes and relationships.
The Real Lesson
You do not win by being the UX purist in the corner who grumbles about how things are supposed to be done. You win by understanding the environment, the constraints, and the players in the room.
Yes, protect UX. Yes, speak up for the user. But also recognize when the biggest UX value you can bring is flexibility, momentum, and the confidence you give your team and your customer.
Being a UX designer is not just about advocating for ideal design. It is about being practical, adaptable, and professional enough to know which hills are worth dying on, and which ones are not even worth climbing.
How to Know Which Hills Matter
Ask yourself these questions when you feel the urge to push back:
- Is this blocking users from completing a task?
- Does this create genuine confusion or unnecessary friction?
- Does it break consistency in a way users will notice?
- Does it expose users to risk or data loss?
- Is this about principle or preference?
If the answer to the first four is yes, push. Make your case, back it with logic, and be ready to defend it. But if it is mostly about how you think things should be done, let it go.
Read the room. Deliver. Then improve.
This is real-world UX.