Deadlines and lists. What I mean is your project has a deadline for when it has to get done. You set that deadline. Once set, you've only got so much time you can put into the project for features. You are more than happy to accommodate as many requests as you can, but you're limited by the time. You're not saying no to them, the deadline is saying "not right now." That takes the pressure off you and focuses it where it needs to be -- on getting this project done.
The list... is a list of all the requests you get. You can track them all, but don't need to do anything with any of them (necessarily). Triage them, clean them up so it's clear what they want, and put them somewhere people can see. Let them vote for them. The things that get more votes probably require your consideration. And the votes eliminates the loudest person syndrome because they only get one vote.
And again, it removes you from making the decision to the system. The system says this feature is wanted by 30 users. This other feature is wanted by 1.
Now that all said.. if your the one doing the design you may do the less rated feature because you know it's necessary, but IMHO all this helps put things in a spot where people can easily see the constraints competition for the time left.
Focused on creating wonderful user experiences by attending to folks needs with empathy and creating spaces of safety. Senior Frontend Developer/Tech Lead at Dolittle.
I like the idea of making the backlog public and something that can be voted on. Uservoice is a great service for this. I’m a fan of how Microsoft Teams does theirs. Don’t know if there’s a private version, Or possibly alternatives.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Deadlines and lists. What I mean is your project has a deadline for when it has to get done. You set that deadline. Once set, you've only got so much time you can put into the project for features. You are more than happy to accommodate as many requests as you can, but you're limited by the time. You're not saying no to them, the deadline is saying "not right now." That takes the pressure off you and focuses it where it needs to be -- on getting this project done.
The list... is a list of all the requests you get. You can track them all, but don't need to do anything with any of them (necessarily). Triage them, clean them up so it's clear what they want, and put them somewhere people can see. Let them vote for them. The things that get more votes probably require your consideration. And the votes eliminates the loudest person syndrome because they only get one vote.
And again, it removes you from making the decision to the system. The system says this feature is wanted by 30 users. This other feature is wanted by 1.
Now that all said.. if your the one doing the design you may do the less rated feature because you know it's necessary, but IMHO all this helps put things in a spot where people can easily see the constraints competition for the time left.
Good luck!
I like the idea of making the backlog public and something that can be voted on. Uservoice is a great service for this. I’m a fan of how Microsoft Teams does theirs. Don’t know if there’s a private version, Or possibly alternatives.