I personally don't have any problems with changing priorities as long as the cost/benefit calculation is done and some things that are easy for management to mi

I personally don't have any problems with changing priorities as long as the cost/benefit calculation is done and some things that are easy for management to miss are considered: * Developer context switches are expensive (both in terms of developer happiness and productivity) * Forks staying off main branch are expensive. * Components/Modules being half-polished due to changing priorities are expensive (both in terms of customer satisfaction and introducing technical debt) So for me, who is in a similar position, it's always a dance between what clients want, what management wants and what would keep my developers productive and happy and my product technical-debt-free. If there's something that my clients ask for and it's really easy to implement, I would often ask my developers to drop other tasks and implement/hotfix it. But I'll try to redirect some good feedback from the customer side to the developer because I know they feel exhausted by changing direction.