unknown

Engineering leaders often face challenges when past decisions are questioned by new team members or stakeholders. To manage such situations effectively, it's crucial to control your initial reaction, assess whether resolving the disagreement is necessary, find the root cause of the disagreement, and decide whether to stick to or change the decision. Documenting the decision-making process helps prevent future churn and facilitates better communication.

Defending Previously Made Decisions: A Proven Approach

All about Engineering Management, Leadership and Career Growth.

Engineering Leadership

Do you get annoyed when someone challenges decisions that were made many months ago? If yes, you need this post to manage such situations.

Do you get annoyed when someone challenges decisions that were made many months ago? If yes, you need this post to manage such situations.

Sometimes things are fixed poorly because it impacted things outside of the code. Nobody wants to write a poor solution but whenever my seniors do it it’s almost always a situation of “The business (or customers!) cannot wait for 4 months while we resolve this”.
Sometimes the choice was closer to “this is the best we could do” instead of “this is the best we can do”.
I personally prefer discussions of “why should/shouldnt we refactor this” to ‘why is this so awful’.