Hello William,
That is potentially a mighty big question! :-). There are some fundamental capabilities and outcomes early adopters typically begin with, and others that companies mature into. I'll list a few below, and recommend you ask the community additional follow up questions around those you feel address your highest priorities and/or pains.
1. Defensible showback / chargeback for IT Towers, and potentially Solutions (applications / product / services): Consumption-based views that can be drilled into for self-service interrogation by business units, legal entities, product entities and/or practice types. This ability to provide consumption volumes and accurate unit costs, built up from a standard taxonomy, goes a long way toward stopping any disbelief in "the numbers". It also enables IT to expose consumption levers business units can pull to impact their own costs, and allows IT to shape Demand using strategic rate setting. It is a prerequisite for informing transfer pricing if it is needed.
2. Solution (Product / Service / Application / Platform) TCO, based on specific underlying infrastructures and related metadata (location, type, CPUs, volumes etc.), plus software license costs, so you capture both "Run" and "Change" the business. Proper application TCO helps inform your journey to cloud, TCO optimization, portfolio rationalization, and use cases like investment decisions related to cost-performance, M&A, modernization, and risk. It is also the first big step toward understanding the cost-to-serve for your customers. We have healthcare organizations that have pushed beyond this, to show IT's contribution to every hospital bed, to certain outpatient service, and patient registrations.
Both of the above can address fixed/variable, direct/indirect, OpEx/CapEx, discretionary / non-discretionary spend, depending on your need. The community is here for you, but we have no idea what problems you're attempting to solve, or the type of IT organization you are (e.g. central IT? heavily outsourced? owning all applications or only shared corporate apps?). There are an enormous number of people in the community to speak with, to understand how they started, and to help you understand where a good starting point for you might be.
3. Cloud cost management is another option, perhaps using FinOps (depending on how large your overall tech spend is vs. your cloud spend). This to help you optimize your cloud costs, ensure efficient consumption, and manage/reflect business unit economics.
There are so many other use cases for TBM that we would have to write a small book here. If I've hit on something that resonates above please ask more about it so the community can chime in. If not, let us know what you're interested in solving for, that way we can come back to you with more specific detail. I've uploaded an introductory file from the Council from years past that may help as well.
Great to see you participate in the community forum - good luck!!
Jack Bischof
VP, EMEA
Technology Business Management Council, Ltd.
1234567
Original Message:
Sent: 10-20-2022 15:55
From: William Cox
Subject: Practical Examples of using TBM
I would appreciate any feedback on practical, specific examples of applying TBM. This would be helpful for me to wrap my mind around what I think is a good concept, and to better explain it to our IT senior leadership.
Thank you.
------------------------------
William Cox
IT Finance Manager
Ballad Health
TN
14233020248
------------------------------