You're facing pushback from developers on late-stage usability changes. How can you win them over?
Navigating developer pushback on late-stage changes? Share your strategies for turning the tide in your favor.
You're facing pushback from developers on late-stage usability changes. How can you win them over?
Navigating developer pushback on late-stage changes? Share your strategies for turning the tide in your favor.
-
Ever heard the saying, “Teams that talk about WHY together are willing to make late changes together?” Me neither, but we should start using it! :) Growing up as a developer, I know how frustrating this can be. But think about it—if an expert finds a big issue or opportunity right before launch, why wouldn’t the whole team want to make the change? Sure, maybe the change means long hours, and that’s a potential reason for pushback. But the real answer is simple: build a strong, cross-functional team from the start. And always talk about the why when changes come up, whether it’s tech, UX, or anything else. That way, everyone’s on the same page from the beginning. And discussing changes at any point in the project lifecycle is easier!
-
I believe that finding a middle ground or phased approach that addresses both usability improvements and developers' concerns about timelines or complexity can be the right way forward. At the core, clear communication is essential, with nothing to hide. It's important to show empathy and understand the difficulties they face, rather than dismissing their concerns.
-
I try to explain the why and not just the what. I've found if developers are able to understand 'why' late-stage changes are coming in, the pushback lessens/goes away entirely.
-
Facing developer pushback on late-stage usability changes? Start by clearly explaining the user impact and benefits of the changes. Use data or user feedback to highlight the necessity of these adjustments. Acknowledge their concerns about timing and workload, and offer support in finding efficient solutions. Emphasize the long-term value of enhancing usability for the product's success. Collaboration and open communication can help shift the conversation towards a shared goal.
-
When developers push back on late-stage usability changes, I handle it with understanding and clear communication. I acknowledge their concerns about deadlines and extra work, but explain why the changes are important for a better user experience. I use data, like user feedback or test results, to show why the adjustments are necessary. By focusing on how the changes can improve the product and prevent future problems, I try to find a solution that works for both sides. I’m also open to compromise, like smaller changes or phased updates, to make it easier for the developers.
更多相关阅读内容
-
Universal Mobile Telecommunications System (UMTS)How does handover affect the quality of service and user experience in UMTS applications?
-
Gaming IndustryHow can game user research align design with business goals?
-
Usability EngineeringHow do you balance the trade-offs between speed, cost, and quality in a heuristic evaluation?
-
Systems DesignWhat are the best practices for selecting and applying evaluation criteria?