What metrics framework do you use to determine the fit of applications or technology platforms to a value stream or business outcome? This is for a current state technology effectiveness analysis, so the question we are seeking to answer is did we make good choices in how we solved for our business needs from a technology perspective. I.e. did we make the right choices between COTS and custom development, are our solutions cost efficient, how well did we satisfy the business in terms of functionality, did we create operationally manageable solutions, etc. Are there useful industry frameworks out there for stuff like this or did you design your own? We will of course need to customize, but I am hoping not to have to start from a blank page.
Sort by:
Thanks Robin, <br><br>This is clear (and helpful!) for an initial implementation. What we are looking at is more a portfolio-level exercise, including apps that might have been implemented quite a long time ago, as well as areas where the business requirements themselves may have evolved over time. So we are trying to do a relatively high level assessment to help identify whether it might be worth taking a new look.
Define Business capability Map for the enterprise and Business Lines atleast until Level 3, Map the Applications, Technology and Tools which meets the need of the business process and other requirements, whichever capability not able to map clearly highlights the GAP. Look for application, Platforms to map with capability, this will start taking the enterprise into Maturity.
I have seen COBIT (Control Objectives for Information and Related Technologies) framework being used to determine if the technology is aligned with business objectives and delivers value. It is a structured framework and covers multiple areas such as IT process management, maturity level, controls, risks , value, governance etc.
You can use a metrics framework to determine the fit of applications or technology platforms to a value stream or business outcome. A metrics framework is a set of quantifiable measures to evaluate how a value stream performs against its business objectives.
For a current state technology effectiveness analysis, you can use a continual improvement lifecycle-based metrics framework to provide process metrics and techniques to help align IT with the business objectives to create value by making processes and services more efficient and effective. This framework helps you determine ways to align IT with business objectives and verify the results.
Another approach is to use Value Stream Key Performance Indicators (KPIs), the quantifiable measures used to evaluate how a value stream performs against its business objectives.
I hope this helps!
I use the three dimensions; people, process (PP) & technology (T). The process and people derive the technology dimension. This is generally where we start. The inputs from the PP give us the information to determine the metrics to evaluate T. T can be a platform recommendation and/or build vs buy decisions.
For technology platform recommendations, we use a weighted average method where each metrics (again depends on PP and the stack in question) are rated against a scale of 1 - 5, and each metric is given a weightage. The top scores are usually a recommended choice.
I would be happy to assist if you are seeking any specific usecase.
Thanks Amit! We previously also used a P/P/T metric that we mainly designed on our own. Can you share a little bit what goes into you Technology dimension? User friendliness? Technical currency? Performance? Security? Something else? There is potentially a lot of factors to consider and I am wondering if you have a view on which ones rise to the top or are the most effective for making decisions?
We do this through a process known as OGSI (Objectives, Goals, Strategy and Initiatives (See Richard Hunter's EXP research 'The 90 Percent Club') We were using that process some time before it was published, we just didn't call it that. This creates the linkage between the Initiative and the business objectives and goals, what you're calling the business outcome.
Once we've determined the Initiative, we start with a Discovery and Scoping phase and the resulting artifact is a Requirements document that outlines the functional and technical requirements. We've used this to go to RFI as well.
When you go to execution and turn to operations, you can now measure what you have done against the requirements before you do final signoff. If you've missed anything in the execution phase, this is where is should show up.
This process (for us anyway) eliminates the need to ask yourself if you've made a good choice since you've mapped the initiative to a business outcome and what you chose (technology/platform etc) meets the functional and technical requirements.
Hope this helps,
Robin