Discussion about this post

User's avatar
Sourav Bandyopadhyay's avatar

Incentives drive everything. Great perspective on this!

Justin Wilson's avatar

The code-cleanup example raises a useful diagnostic: is the work low-value, or is its value invisible to the people allocating time? For reliability work, I would bring a concrete tradeoff: this recurring failure costs the team X hours, this bounded fix costs Y, and here is how we will check whether it helped. Those numbers need evidence, but the proposal tests whether the incentive problem is a communication gap or a real mismatch. If even an agreed business outcome receives no support or recognition, that is stronger evidence for changing teams than an unsuccessful pitch for cleaner code.

Ready for more?