≡ Menu

dougmcclure.net

thoughts on business, service and technology operations and management in the digital transformation era

links for 2007-02-03

in General
  • When you consider the traditional closed loop BPM Lifecycle, as illustrated below, the emphasis has always been very much on using analytics about how processes have performed in the past, in order that we can modify the actual process definition in order
    (tags: soa bpm bam events)
  • The Open Group Service Integration Maturity Model (OSIMM) is the industry’s first collaborative maturity model for SOA adoption. Spearheaded by members of The Open Group, including IBM, BEA, HP, EDS, and Capgemini, the initiative is working to provide a
0 comments

Stan from Sharp Analytics has a good post on trying to make sense of how dashboards, reports, etc. are used (or not).

I’ve seen this happen a lot as well, especially when there isn’t a full lifecycle of review, support and upkeep associated with dashboards and reports. I recommend frequent review and sign off with stakeholders and audiences after initial release and then at least quarterly once you’ve got something that’s pretty much perfect. Remember, it’ll never stay perfect – and if you let it get stale, outdated or incorrect, you’ll quickly loose your audience and any confidence they had in the dashboard or report in the first place.

-snip-

“Why do some reports get used often, while others are viewed only once? Why do some report users login once and never return, while others return often?

Every time I build a report, dashboard, or ad-hoc query environment I wonder if it will ever be used. And every time I setup a user account for a new user, I wonder if they really want and need it. Everyone involved in an IT project from a business standpoint knows that they should need the data, and they devote hours of meetings providing input and money. So why don’t many of them ever return to take a look at the results?”

2 comments

links for 2007-02-02

in General
0 comments