ITAM Hard Truths: Why are ITSM and ITAM still an opposites-attract problem?

Put an ITSM lead and an IT asset management lead in the same room and they’ll describe the same environment two different ways, and both will be right. That isn’t a personality clash. It’s the shape of the work. Service management is repeatable. Incident, problem, request look the same from one shop to the next, and that portability is a real strength. IT asset management doesn’t travel. You have to work out what the assets are here, who holds them, and how they align to this business before you can manage anything. Two organizations in the same industry won’t have the same answer. Underneath sits the difference that matters. Service management is linear — a ticket opens, moves, closes, and a flat row per device is the right record for that job. IT asset management is relational, and the relationships are the asset. One person: a laptop, two monitors, a phone, a printer shared with the floor. Pull the person out and the records still exist and mean nothing. The same question runs up the stack — this license to this entitlement, to this installation, to this host, to this cluster, to this cost center. So the two disciplines report different numbers, and that’s not a reporting defect. It’s the alignment problem showing up as output. Then there’s the part nobody says out loud. The CIO sees all of this as a service management problem, which is where it goes wrong. Inside IT, IT asset management gets treated as a service rather than something with financial consequence — so executives never see what it’s worth except during budget season. That’s why it has to speak up: in the room where the tool gets chosen, and in the room with finance. In this session of The ITAM Kitchen’s series, ITAM Hard Truths, we get the disciplines aligned before anyone opens a vendor site — why linear and relational are both correct, why repeatable versus not-cookie-cutter is the root of the divergence, and how to make the case to leadership that has only seen IT asset management on a budget line. At Cardinal Trust Financial, service management and IT asset management reported on the same estate and never agreed on its size. Neither was wrong — one counted device records, the other counted the relationships those devices sat in. The argument ended when both teams agreed which shape each report answered. At the Federal Asset Modernization Office, a standard service catalog rolled out across five agencies and worked, because the service side is repeatable. The same approach applied to IT asset data failed in all five, because each agency’s estate aligned to its mission differently and no average described any of them. You’ll leave able to describe your environment in both shapes, name where your two reports diverge and why, and make the case to an executive who has only seen it on a budget line. This was never a technology problem. That’s one more hard truth. 🍳 Bring your two reports to the table. Run this first: “Act as an ITAM/ITSM architect. Service management needs a linear record per device; IT asset management needs parent-child relationships — end user to laptop, monitor, phone, and license to entitlement to installation to host to cost center. Show me where those two shapes force different answers about the same estate, what the relational side loses when the linear shape wins, and how to explain that divergence to a CIO who sees all of this as a service management problem.” 🎯 Built for: ITAM Professionals | SAM Managers | CMDB Administrators | CIOs | CTOs | CFOs 📅 Live: Friday, September 18 | 10:00 AM ET | YouTube & LinkedIn Live