We discuss how to go about making decisions for all angles of a software development project, from U/I-U/X to deciding the right technological path to take.

The fundamental idea of tying the "Why?" to all decisions is a basic idea, but often not done. We expound on that and bring some examples demonstrating the mistakes and the result of those mistakes