Blog 17 · UX stakeholder management

The client rejected the design. Good. Now we can start.

Pranjal Chawan
Pranjal ChawanUX leader · LinkedIn

A rejected design hurts. You have put in the hours, and now someone with a title is telling you it will not work.

Here is the reframe that has served me well: a rejection is the first honest thing anyone has said about the project.

Polite silence is much more dangerous. It lets you keep building until launch day. A clear no tells you there is a gap between what you understood and what the business needs. That gap can be found and closed.

A story from the room

Sudhir Rao, an Associate Program Director who managed me, was the Delivery Manager on the GE account at Birlasoft when initial designs were rejected. This is how he described what happened next:

He took immediate ownership of the UX challenge, conducting cross-department user interviews and mapping key pain points. Within two weeks, he presented a revised design flow that secured full client approval.

Notice what did not happen. Nobody needed a better argument. We did not defend the screens. We went and found out what was true across departments, then brought back a flow built on that evidence.

Why stakeholders disagree

Conflicting feedback rarely means someone is being difficult. Each person is usually protecting something real. Sales worries about conversion. Legal worries about risk. Operations worries about the support queue. Your job is to find those concerns.

Tarun Kamra, who worked with me on a chaotic programme and now heads digital for JioBlackRock, wrote that I can "sit in a room full of conflicting feedback, cut through the noise, and turn scattered viewpoints into clean, intuitive UI/UX without losing his cool." I have learned that the calm is half the method. If you get defensive, everybody else does too.

My five-step approach

  1. Listen before you respond. Ask, "What worries you most about this?" Then write the answer down.
  2. Speak to people separately. Individuals are more honest away from the group.
  3. Map the pain points. Put everyone's concerns on one page, with user evidence beside them.
  4. Bring options, not a verdict. Show two or three paths and what each one costs.
  5. Close the loop. Confirm the decision in writing, and explain which feedback changed the design.

That final step matters. People support a decision when they can see that they were heard, even if they did not get their way.

Managing senior executives

Executives have very little time and carry a lot of risk. They usually want to know three things: what is the recommendation, why should I believe it, and what do you need from me?

Start there. Bring the design as evidence for your answer.

When to push back

Stakeholder management is not the art of keeping everyone happy. Sometimes the right response is, "I understand why you want that, and here is what the research suggests it would cost us."

That sentence respects the person, keeps the user in the room, and leaves the decision where it belongs.

Questions people ask

How do you handle stakeholders who reject a design? Stay calm, find the concern behind the feedback, gather evidence, and return with options tied to the business goal.

How do you get stakeholder buy-in for UX? Involve people early, connect design to their goals, show real user evidence, and make the decision easy to understand.

Stuck between opinions?

If your project has become a tug-of-war, I am happy to help you find the thread. You can reach me at pranjal.productmind@gmail.com. I promise to stay calm.

© 2026 Pranjal Chawan. All rights reserved.