Definition of Solution Blueprint

Solution Planning Series

This is the fourth installment in the solution planning series. In the first post on solution planning, we provided an overview of the concept of solution planning as a necessary exercise to be performed before commencing solution implementation. The second post discussed scope confirmation, the first step in the solution planning process. In the third post, we discussed the need to assess capabilities and constraints which involves reviewing the current state of an organization to identify factors that may impact on or influence how a solution will be delivered. This post, the fourth in the series discusses the third step in the solution planning process: definition of solution blueprint.

A solution blueprint lays out the design of the future state of the solution. Taking the outputs of the scope confirmation and capability/ constraint assessment steps as input, the solution blueprint outlines the components of the solution and how they are structured to form a composite whole. A solution blueprint would typically include a business process blueprint, application blueprint and technology blueprint. It is also useful to include a change enablement blueprint because process, applications and technology changes would inevitably result in people-related changes and need to be properly managed in order to successfully implement the solution.

In order to get the best results, it is important to ensure that the right business and technology stakeholders are involved in defining the solution blueprint. A properly defined solution blueprint should contain the following:

• Business Process Blueprint: a depiction of to-be business processes at a high level, highlighting changes to current state

• Application Blueprint: identification of the applications that they future state solution would be composed of and the relationships, integrations, etc. between them

• Technology Blueprint: description of the technical environment that will support the new application landscape

• Change Enablement Blueprint: identifies the high-level approach and tactics that would be employed to enable users of the applications and technology to be implemented as part of the solution

As with all activities performed during solution planning, definition of the solution blueprint should happen at the very beginning of the process, before solution implementation commences.

Benefits of defining a solution blueprint solution implementation commences include:

• A common understanding of the organizational vision for the solution as well as requirements

• Ensures that all solution inputs, dependencies and constraints have been considered and there are no surprises during implementation

• Ensures proper planning and execution which leads to a reduction in time to complete downstream solution implementation phases i.e. plan, design, build, test, etc.

• Provides a plan to ensure that a solution is not just functional but adopted by users

Join us next week for the next post in the series where we continue the discussion on solution planning.

Have you had any experience where there were challenges on a solution implementation project due to poor solutioning? Please share your thoughts and comments below. Follow Virtro on Social Media