I work on a product that has been built over 25 years. Lots of the work I did years ago is to ensure the product longevity. Lots of the work I do now is to ensure it lasts another 25 years. Thats good, but its only the start of "my work". It's up to me to "sell" that benefit to upper management. There's no point in assuming they'll figure it out by accident. Part of my job is enumerating the value I add. By all means…
How do you put numbers in there usually? I'm facing an issue at work where an important factor should be done to correct a serious design mistake, but it doesn't get in the way of any feature. It's probably the cause of a lot of loss of development time over the lifetime of the project, but I don physically know how much of a boost will it give to development. I know it will, but I wouldn't feel comfortable without q…
Depending on the stakeholder(s) you're dealing with, approaching it like this (as risk assessment/management) might help to convey the short-term impact of a long-term problem.