Hello from Dubai! I arrived a few days ago for customer visits across the region including UAE, Qatar and Bahrain. Although I’ve traveled extensively, this is my first trip to the Middle East.
As a frequent flyer (both in terms of travel and airline loyalty), I looked first to my preferred airlines when I booked my flights to the region. Neither of them (yes, I fly two airlines regularly which suggests that I’m not all that loyal) provided service to my destinations. So, I looked for a partner airline – one that is part of my preferred airlines’ networks. I went with Emirates which not only serves the Gulf States I was planning to visit, but enabled me to stay within network and collect my frequent flier miles. Why do I mention this? Well, I have been thinking about that model of a “Star Alliance” or a “Skyteam,” and how it could apply to service providers of other kinds.
We all know our current paper-based health information process wastes hundreds of billions of dollars annually. Transforming this into a streamlined 21st century electronic system will require moving though stages of maturity from paper charts to the cross provider electronic health record (EHR). And yes, Forrester will be publishing it's maturity model soon which hopefully will be more understandable then the health care bill. Our basic conclusion is that a narrow focus on electronic medical records packaged apps. or paper replacement technologies will fall short of stated goals. Meaningful use - as in qualifying for governement bonuses - will require a process –centric view and a portfolio of technologies including enterprise content management (ECM), business process management (BPM), analytics and Forms Automation. Our three phase maturity model will show how these foundation technologies help move through the phases most providers will transit to get to the 21st century health care system we all need. Stay tuned.
This is not really a new blog post. It's a relatively recent post that didn't manage to make it over from my independent blog. I wanted to be sure it made it to my Forrester blog because I will have lots of publications and posts on information architecture coming up and this was a post on my first piece in this series. So here's the original post:
In January, the lead-off piece that introduces my research thread on information architecture hit our web site. It’s called Topic Overview: Information Architecture. Information architecture (IA) is a huge topic and a hugely important one, but IA is really the worst-performing domain of enterprise architecture. Sure, even fewer EA teams have a mature — or even active — business architecture practice, but somehow I’m inclined to give that domain a break. Many, if not most, organizations have just started with business architecture, and I have a feeling business architecture efforts will hit practical paydirt fairly quickly. I’m expecting to soon hear more and more stories of architects relating business strategy, goals, capabilities, and processes to application and technology strategies, tightly focusing their planning and implementation on areas of critical business value, and ultimately finding their EA programs being recognized for having new relevance, all as a result of smart initial forays into business architecture in some form.
I get a lot of input into my research from speaking with software buyers and sellers, which I analyze and process to come up with firm conclusions and recommendations in my published research and forum speeches. I'm going to use this blog to air some work-in-process analysis, to solicit additional thoughts and information from you. Just recently, Ive been considering why people are talking about 'pay-per-use' a.k.a. 'utility pricing' for software, and to me, the disadvantages to buyers and sellers outweigh the benefits.
Software pricing should be simple but fair, value-based, future-proof and published (see The Five Qualities Of Good Software Pricing). Yes, a one-price-fits-all 'per user' fee isn't fair or value-based, but that doesnt justify the potentially horrendous complexity of tracking detailed usage. Role-based user pricing, such as SAP user categories, is a much better way to reflect diverse usage profiles.
Im not arguing against flexible, on-demand services, particularly for temporary needs, such as renting some CPU power for a few hours. I'm concerned about pay-per-use pricing models for regularly used applications. To me they would be:
"Well, as of this moment, they're on double-secret probation!"
Dean Wormer, Faber College
Recently I have had a number of conversations regarding the role of pre-moderation of internal social networks. Just by way of explanation, pre-moderation would be the approval of all content (posts and comments) prior to posting. Over the past several years and hundreds of conversations with enterprise clients, this has rarely come up.
Just to be clear, there is risk associated with enterprise social networking. There is nothing about social technologies that precludes requirements for privacy, security, maintenance of intellectual capital, regulatory compliance, etc. However, given the right degree of attention, these all are manageable. In fact, over time, social technologies will reduce the risk associated with all of these (more on that later).
OK, so if anyone can say anything at anytime, that's risky right? Well, in thoery, but in reality, not really. Remember, we're talking about internal social networks. Presumably, these are IT sanctioned, authenticated solutions. In other words, everyone knows who you are. And, we can assume that with some degree of planning and education, your users will be aware of the policies that govern the environment. And if you post something not within policy, well you get put on probation (or maybe double-secret probation). Animal House references aside, many a fine internal social networking policy begins with "don't do anything that will get you fired".
There are three key points here:
One, provide a sanctioned solution for your organization because if you don't they may well find something on their own and that could be a whole different kind of trouble.
As I close out my client inquiry records for the quarter, it’s interesting to review some of the common challenges risk management professionals are currently facing. I was impressed to see how closely the issues I deal with were covered in the month’s edition of Risk Management Magazine. In an article entitled, “10 Common ERM Challenges,” KPMG’s Jim Negus called out the following issues:
Assessing ERM’s value
Privilege (of access to risk information)
(Selecting a) risk assessment method
Qualitative versus quantitative (assessment metrics)
Time horizon (for risk assessments)
Multiple possible scenarios
Simulations and stress tests
Negus provides good perspective on these challenges as well as some ideas for solutions. The list is fairly comprehensive, but there are several other challenges that I would have included based on the inquiries I get. First and foremost, the role of technology in risk management – whether for assessments, aggregation, or analytics – comes up very frequently, and vendor selection initiatives have been plentiful since mid-Q4 of last year.
Defining risk management’s role within the business (and vice versa) is also an extremely common topic of conversation. As rules and standards keep changing, this will remain a top challenge. Other frequent issues include event/loss management, building a risk taxonomy, and evaluating vendor/partner risk.
For those of you unable to attend, I will summarize some of the content that I presented on SAP’s overall growth and innovation strategy. SAP has a double-barreled product strategy focused on Growth and Innovation.
The Growth strategy rests heavily on the current Business Suite, which includes the core ERP product that is used by approximately 30,000 companies worldwide. SAP claims that it touches 60 percent of the world’s business transactions, which is hard to validate but not all that hard to believe. The main revenue source today is Support, which comprises 50% of the total revenues of the company at more than 5 billion Euros annually, and it grew by 15% in 2009. Other growth engines include:
Over the weekend I took my daughter to see "Alice in Wonderland" and couldn't resist comparing Johnny Depp's Mad Hatter character to Pega's recent move to acquire Chordiant. For those of you who haven't seen the movie, it's not as weird as the usual Tim Burton movie; but the Mad Hatter character is a little disturbing, with his rhymes and riddles that keep you guessing at his true meaning.
For many process professionals, Pega's recent move was just as confusing as having a conversation with the Mad Hatter. What exactly is he trying to say anyway?
A number of clients ask me "how many people do you think use BI". Not an easy question to answer, will not be an exact science, and will have many caveats. But here we go:
First, let's assume that we are only talking about what we all consider "traditional BI" apps. Let's exclude home grown apps built using spreadsheets and desktop databases. Let's also exclude operational reporting apps that are embedded in ERP, CRM and other applications.
Then, let's cut out everyone who only gets the results of a BI report/analysis in a static form, such as a hardcopy or a non interactive PDF file. So if you're not creating, modifying, viewing via a portal, sorting, filtering, ranking, drilling, etc, you probably do not require a BI product license and I am not counting you.
I'll just attempt to do this for the US for now. If the approach works, we'll try it for other major regions and countries.
Number of businesses with over 100 employees (a reasonable cut off for a business size that would consider using what we define as traditional BI) in the US in 2004 was 107,119
US Dept of Labor provides ranges as in "firms with 500-749 employees". For each range I take a middle number. For the last range "firms with over 10,000" I use an average of 15,000 employees.
This gives us 66 million (66,595,553) workers employed by US firms who could potentially use BI
Next we take the data from our latest BDS numbers on BI which tell us that 54% of the firms are using BI which gives us 35 million (35,961,598) workers employed by US firms that use BI
Inside the BPA Group at Forrester, we conducted a little experiment. I suggested that we should collaborate on a piece about the Pega acquisition of Chordiant. What followed was a large number of email exchanges. I drew the short straw in bringing all these thoughts together into a coherent whole. I prepared a document for Forrester clients to explore the acquisition in detail (probably getting through the editing process next week some time), and this blog post is culled from that document. So while the blog post bears my name, it reflects the collective opinions of Connie Moore, Bill Band, Natalie Petouhoff, John Rymer, Clay Richardson, Craig Le Claire and James Kobielus. Of course, I have put my own interpretation on it too.
Pega definitely wants to be in the customer experience/customer service business, and they want to get there by having a very strong BPM offering. It is not that they are moving away from BPM in favor of Customer Experience – they’re just strengthening their hand in CRM (or CPM as they would call it), more forcefully making the connection. We already knew this, but the Chordiant deal just reinforced that point (see related research doc from Bill Band in 2005 !!). This is not a new direction or change in direction for Pega, it is a strong move that takes them faster in the direction they were already going.
From a product point of view, Pega are adding/strengthening their hand – Choridant’s marketing automation and predictive analytics seem to be of greatest interest. Of course, Pega also values the engineering talent that Chordiant has, and will redirect those people over time to work on integrating these capabilities into the BPM offering. They were also interested in the vertical industry and functional expertise that Chordiant had to offer.