One of the things that helped us at work was to always create a Jira ticket for these things. Then it exists in the system that "management" sees and we can "bargain" about ticket priorities all together -- and it helps that they understand that each "chunk" of work needs to include both features they want and "features" we developers want too.
Right now, for example, we have backed off adding features to the system while the business folks evaluate the market trends and figure out what's going to be important from a revenue p.o.v. -- and that means that development folks like me can focus on "quality of life" issues. Most of what I've worked on for the past few weeks has been around improving the context reported in errors, making errors easier to read (and problems easier to debug), and streamlining both the dev/test/build pipeline and the observability aspects of the system (in New Relic).
One of the things that helped us at work was to always create a Jira ticket for these things. Then it exists in the system that "management" sees and we can "bargain" about ticket priorities all together -- and it helps that they understand that each "chunk" of work needs to include both features they want and "features" we developers want too.
Right now, for example, we have backed off adding features to the system while the business folks evaluate the market trends and figure out what's going to be important from a revenue p.o.v. -- and that means that development folks like me can focus on "quality of life" issues. Most of what I've worked on for the past few weeks has been around improving the context reported in errors, making errors easier to read (and problems easier to debug), and streamlining both the dev/test/build pipeline and the observability aspects of the system (in New Relic).