I am always reminded of this story around throughput metrics for Software Engineering: https://www.folklore.org/StoryView.py?story=Negative_2000_Lines_Of_Code.t

I am always reminded of this story around throughput metrics for Software Engineering: https://www.folklore.org/StoryView.py?story=Negative_2000_Lines_Of_Code.txt https://www.folklore.org/StoryView.py?story=Negative_2000_Li... Your suggestion is delightful, and in a former company, one of our PMs, at a time when we were overwhelmed with requests, tried to tame the tied by requiring requesters fill out this simple template along the folloing lines (but I am paraphrasing): - What is the impact on you/your team from this feature/bug not being addressed? - What is the priority of this in comparison to other asks you have from the team? - What is the impact to the business? Even though the team did not like the bureaucratic approach, the number of requests went down dramatically.