I personally think that was a decent use of time - 30 minutes vs a product-lifetime of not pissing off users that little bit will give a lot of goodwill payoff.

I personally think that was a decent use of time - 30 minutes vs a product-lifetime of not pissing off users that little bit will give a lot of goodwill payoff. But I have worked at a place with in-house developers where they probably wouldn't have showed the initiative to do it themselves, and if brought up later as an annoyance I'd be asked for a "business case" which is a complete non-starter, because how do you even begin to quantify this in a way everyone can agree on? I value polish for its own sake highly as I think you do too, a well made tool is more rewarding to use. But the ones forecasting developer effort need a concrete justification. So it's best to just sneak this in if you can and hope other people you work with feel the same, after all it's much quicker to do it up front than to lose context and revisit it later. Asking permission will cost far more than your 30 minutes.