That's a good one! If the way things were done or have always been done is causing more problems, it is a great skill to be able to identify that and make it better for everyone.
I'd also add when to not solve an issue that was identified. If there is code that is considered "bad" by objective measures, but works and isn't costing any development time to support it, leave it alone.
We're a place where coders share, stay up-to-date and grow their careers.
We strive for transparency and don't collect excess data.