All too often, projects start before thought has been put into the project's purpose, its desired results, and ways of evalutation.
They are not accustomed yet to take the standpoint of "user experience" and to do fine/strict/minute/thorough preparation — thinking before acting : clearly stating the objective/scope of the project (what the project does and does not cover), specifying users (diverse individuals), planning, desktop-simulating and testing.
Besides this, they tends to plan huge initiative, while setting a deadline at a short distance. Thus, as a matter of course, planning, desktop simulation and test become perfunctory. This result is : they buy the useless, or they fail to make their initiative (which is exorbitant at scale !) included in the budget.
This serves as an example of how not to behave. What must be done for realizing a system which pay off is : (1) taking a "users (diverse individuals) experience"-based stance, (2) doing minute preparation, and (3) starting small/practival.