Skip to main content
Latest news: [[ newestAnnouncement.title ]] Learn more
InVision Support Home Page
Sign in
InVision ambassador ambassador
Ashima Sood
Ashima Sood Updated

Stakeholder and team communication: Less is more

How does one go about speaking to the team about additional features not adding value to the product?

As designers, we are aware of the principle of less is more, Less but better, and so on. But how do we communicate this to the larger team? A team that comprises of individuals who've had a fair amount of experience and feel that they know what works?

Well thought out features have a great impact on the UX of a product, but we need to understand where to stop or what to focus on. I am currently facing a challenge where-

  1. Upper management pushes for design decisions that have no proof of concept and would overwhelm a user instead of adding any value to their experience. 
  2. The larger team is not on the same page when it comes to having an underlying theme for the experience of the product.

Knowing that there may be so many other designers on the same boat as I am I wondered if you all had any tips on communicating effectively with the larger team about this? If yes, how did you tackle it and how was it taken by the team?

Few interesting reads I came across while trying to sole this problem

  • Adam Silver on Medium
  • Fabricio Teixeira, also on Medium via UX Collective. - very relatable, however it doesn't talk about working with a team (non designers) or collaborating. 

This post is associated with a known feature request: [[ problemTicketSubject ]]. Let our Product team know that you’re interested in this feature.

Sign in to add your vote

Thanks for taking the time to share your feedback about making our product better. We’ve let our Product team know that you’re interested in this feature so they can factor that into their product strategy.



Sort by

Rob Whiting
InVision ambassador Rob Whiting , ambassador

Hi Ashima,

A great question and something that happens across a lot of organisations.

For me, the key way to push back on things like un-required features has been to use Research data to support any arguments. Too many Design related discussions end up being more about opinion then evidence but by putting Research data (even lo-fi data) in front of key Stakeholders I've often been able to convince decisions to either go in another direction, or to do additional Research to ensure the feature actually is required.

This has been one of the reasons I've found working with InVision as a tool so useful. The ability to quickly mock up a prototype or user flow (even using very basic, paper prototype style images), put it in front of users or Stakeholders and show people issues rather then just talking about them has been invaluable. 🙂

Angela Millward
InVision ambassador Angela Millward , ambassador

AHH yes the dreaded disconnect! I think this would be a common problem across most organisations. 


Often when people think about adding something in they don't understand the complex thinking which underlies the flow to make something easy which is what makes most products incredibly complicated, but one of the best approaches I have done is to print out my UI and place it over a wall (or a few walls) and connect point to point map it with string. This shows the Larger team the value of the connection points as people often misunderstand how complicated something is, especially when you are doing your job well. You can also invite your Upper Management to come view it, take their suggestion on board of what they what to include and the visually show them how complicated (or easy) the process is.

You can also simplify this down by using a site map. 


I hope this is helpful and GOOD LUCK 




join the conversation

To comment, sign up or sign in.