What do Enterprise 2.0 and SOA have in common?
Fuzzy metrics, that's what.
SOA has always had a metrics problem. At first, no one knew how to measure SOA or calculate its ROI. Then the list of metrics grew...and grew...and grew. But when it comes to that mother of all metrics - ROI - well, that's still a struggle.
IT departments are notoriously bad with ROI. Oh, sure, IT talks a good game. But as recent research on health management systems shows, sometimes those estimated savings never materialize. And that's certainly been a problem for SOA.
Enterprise 2.0 is in large part about collaboration, and that's not easy to measure either, as Joe McKendrick, an IT consultant and the SOA blogger for ZDNet, says in a recent post.
McKendrick recently participated in a panel discussion for Briefings Direct, hosted by Dana Gardner, another ZDNet blogger and the president and principal analyst at Interarbor Solutions. Officially, the discussion was about the "psychology of project management via Pragmatic Enterpise 2.0 and SOA."
But, as McKendrick points out, the meat of the discussion was exploring the return on investment (ROI) and measuring the success of services. Mind you, they're not talking about services in an IT "little packets of coded functions" sense. They're talking about business services-another concept SOA and Enterprise 2.0, at their best, share in common.
As I mentioned, SOA's measurement challenges are well documented, but perhaps less discussed is the fact that Enterprise 2.0 has a similar problem. Enterprise 2.0 is about collaboration, thus about human relationships-and you know what stinkers we are. How do you measure the human element, asks McKendrick.
I'm sure political scientists could offer some insights, but this is more than a statistics problem. As the panel discussed, part of the problem is that both Enterprise 2.0 and SOA suffer at the hands of another human condition: Mismatched expectations. McKendrick shares this tidbit from the panel:
"... by not being able to effectively measure a technology's benefits in a collaborative way, we're missing out on many of the potential benefits, Dion (Hinchcliffe) said. 'This is the classic technology problem. Technology improves and gets better exponentially, but we, as organizations and as people, improve incrementally. So, there is a growing gap between what's possible and what the technology can do, and what we are ready to do as organizations.' Mismatched expectations are another challenge. People tend to blame software and IT for project failures, but the real failure may be in communications, Michael (Krigsman, president and CEO of Asuret) added."
This failure to align expectations and communicate them-or, put simply, agree on where you're going and how to get there-creates an interesting problem: Often, IT has one set of goals and metrics, while the business has its own separate objectives and measurements.
So guess where both sides find themselves. Back at No IT/Business Alignment-ville, that's where.
How do you get out of that town? Panel member and IT analyst Sandy Rogers suggested that succeeding with SOA and Enterprise 2.0 is to stop focusing on the IT systems and choose metrics and key performance indicators that focus on the business services. I know-it seems so obvious, yet it needed saying. Kudos to Rogers for saying it, and kudos for McKendrick for highlighting her remarks.