If You Build It, Will They Come Back?
A cost model only becomes useful when it can be understood, defended, and operated by more than the person who built it. Clear logic, visible structure, and sustainable design determine whether people return to it, whether it survives turnover, and whether it supports the broader goals of cost transparency.
Seeing labor more clearly through modeling
Effective cost modeling brings clarity to how labor is sourced, deployed and measured across different arrangements, and gives practitioners the structure they need to build more specific views when a use case requires more than finance‑level precision. Clearer labor insights support stronger, more reliable investment decisions.
The Many Meanings of “Asset” in Technology Costing
When teams come together to build a technology cost story, familiar words can take on very different meanings. The term “asset” is one of the most common sources of cross‑functional confusion, especially when Finance, ITAM, and ServiceNow each bring their own definition into the conversation.
How to Socialize Cost Pools and Why It Even Matters
Cost pools offer a simple way to describe what an organization buys, but their real value comes from how they’re socialized. When people can see their own work in the structure and imperfections are part of the conversation, cost pools become a shared foundation for clarity, accountability, and cost transparency.
Start With Structure, Not Software
Before software can help, structure must exist. Cost pools are the first layer of any cost model, turning abstract accounting data into categories people can understand. They are a first step in creating the consistency that allows a model to scale into more advanced capabilities later on.
A Practitioner’s Introduction to Job Order Costing (JOC)
If Activity‑Based Costing explains why cost happens, Job Order Costing shows us exactly how it accumulates to the work we do every day. By following cost from resources to activities and into individual jobs, we start to see how requests, deployments, and even model inferences carry different costs, and why that matters for real-world decision making in cloud, platforms, and AI.
Breaking Through the Wall
The implementation wall is the moment when an ITFM or TBM initiative loses momentum and the work stops moving. It isn’t caused by tools but by misaligned expectations, collaboration gaps, and process debt. Breaking through requires governance, clarity, and practitioner leadership — not more configuration.
It’s Not the Framework
Frameworks don’t create cost transparency, organizations do. A framework is only as effective as your ability to implement it, align it to how your teams actually work, and sustain it over time.