Solution delivery by it’s definition focuses on solving problems. It does not focus on methodology or process – although having those 2 components often do solve problems – rather, the purpose of a solution delivery team is to focus on providing a solution that solves business problems and creates business value. Solution delivery means focuses on the WHAT takes priority over the HOW.
The distinction is important because in IT all of us love to be technicians and most of us are masters at our craft… and often times as technicians we like to follow absolutes. We love doing our part/our role the best way we know HOW. But in our comfort zone we can sometimes get mired in the process and lose sight of WHAT problem we are really trying to solve.
When we define ourselves as solution delivery professionals in addition to our traditional project roles, we each take responsibility to ensure we are doing our part to find solutions for the problems that are presented to us within the existing constraints.
An example: An enterprise architect could insist that every design document go through rigorous approval processes to ensure that the product follows all architectural guidelines. This approach makes sense… unless the process is extremely cumbersome and does not support the timeline or the resource availability. As part of the solution delivery team it is the role of the architect to ensure that they are not creating roadblocks unnecessarily… that a degree of flexibility is introduced – while still upholding the responsibility to ensure that the product is structurally sound.
How is solution delivery different than project management? Solution delivery is enabled by project management, and it is each team member’s responsibility to ensure that they are enabling rather than disabling solution delivery. Every person on the team plays a role in ensuring project timeliness, quality and budget.
At PlantoAction we believe that success depends on the team being masters of their own craft while always having responsibility for delivery of the product as a whole. In IT, Nobody is successful if we are not all successful.