Modla recently put forward a proposal to an electricity distribution utility, to justify an investment in our data to decision making platform.
When justifying the addition of another software solution to your architecture, a common pitfall is to ignore the strategic context, and focus solely on the problem and needs.
Here there are two viewpoints:
The strategic is what sets the boarder requirements and direction from the business, while the problem represents the current pain points.
Starting with the strategic view, it is important to be honest in the self reflection of the current business state. Below is an example of such an assessment:
It's important to note that this table describes the broader direction of this utility with regards to an Asset Analytics function, and the benefits described are as a result of adoption of an approach, rather than a specific solution or resolving a need.
Once the strategic view is understood, then we can dive into the specific needs or the immediate problem. Again here is an example of such an assessment:
This is where the more tangible benefits can be quantified for solving a perticular business problem.
When selecting a solution (In particular a software solution), it should be able to address the immediate need, while also fitting within the strategic view of the business.
Failure to account for the strategic direction, in this case could result in:
Just food for thought.....