Products, Solution Frameworks, and Development Tools are too often touted by vendors and development teams as solutions to customer business problems. Why do development teams, customers, and users seek products to fill this gap? When solutions fail is it too easy to blame a given platform than for those really responsible to take responsibility? It more often has to do with one's level of problem solving skills, planning, and ability to align technology with business strategy. This session introduces proven field architectural practices in leadership, communication, and some strategy tools that will assist stakeholders in becoming owners of their solutions--taking responsibility for their outcomes. This results in greater customer satisfaction, as the focus is all about enabling problem solvers (not expecting products) to deliver successful solutions.