Telling our team "the why" not "the what"

When solving complex problems, those who are directing the work sometimes prescribe solutions. They do this for several reasons:

  • Because they want to help, and if the answer seems obvious to them then it seems the right thing to do
  • Because they feel it will help them get the outcome they want sooner
  • Because that's always been the way they do things—management directs

To some extent, this makes sense if the solution is obvious. However, it may cause unexpected side effects both for our software team and the outcome that we desire. An answer may seem obvious, but simple problems have a knack for hiding complexity. Also, our solution might not be the best.

The New New Product Development Game, Takeuchi ...

Get The Agile Developer's Handbook now with the O’Reilly learning platform.

O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.