When discussing BTM a lot of the conversation centers on the technical complexity of business transactions. So for instance we were talking the other week about a simple “bill payment” transaction. Seems such a “simple” payment transaction flows in many cases across as many as ten IT environments: a client service portal (web front ends, security appliances, front end portal servers, portal personalization databases), then crosses over to the payment application (payment system app servers, master payment database and the interfaces to external payment services). There is huge value in exposing this technical flow across the two apps and the eight technical components.

But if we look beyond the technical complexity we’ll see that each and every one of the steps in this flow has a person behind it: from the business user behind the payment itself to the IT people behind the apps and infrastructure pieces. Everyone is focused on making their part of the overall story work well – but they all have very little to go by in terms of aligning their efforts with the overall goal. And the overall goal that really matters is getting that payment thru, without glitches, without holdups, time after time.

Well, transactions, when made visible, provide us the ultimate facility to connect these people, business and IT alike. Transactions expose the “lines between the dots” and provide a meaningful context to the people who participate in planning the systems, creating the apps and operating them. They allow them to focus on their jobs while effectively communicating with their peers. They provide a shared context around which they can all connect.

Think about it :  “Transactions – connecting people”.