Boosting Success in Engineering Changes
Ever found yourself in engineering departments where tools and practices are adopted and discarded rapidly?
One example that might resonate are companies that try to implement their goals through OKRs. Typically, the first year doesn't yield substantial value, leading to a gradual disregard in the second year. Before the close of year two, a new acronym supersedes the existing goal definition, setting off yet another cycle.

Leads Horizons is a reader-supported publication. To receive new posts and support my work, consider becoming a free or paid subscriber.
Understanding Why New Methodology Implementations Often Fall Short
Whether we're discussing company-wide methodologies like OKRs or team-specific practices like pair programming, it's common to see implementations fall short. Often, methodologies bear the brunt of the blame due to misalignment.
Let's delve into the reasons behind these failures, and assess whether the methodology itself is at fault.
-
Difficulty in Tracking Results: When new methods are introduced, it's often challenging to see immediate results or advantages. This can lead to premature rejection of the new approach.
-
Insufficient Engagement: This covers situations where members aren't entirely on board with the new process. This could stem from inadequate understanding, disagreement with the methodology, or simple resistance to change.
While there are other reasons for failure, they typically fall under or relate closely to these main points.