Reading through the articles on BSMReview.com,
I started to wonder: "what is the problem?". Is IT
really thàt disconnected from the business? Looking around in my
living room and at the office, I can harldy imagine how life would be
without any Information Technology to support me. And all of this is
provided to me by companies in the form of products and/or services.
Would I buy and/or use them if I didn't know what value they bring to
me? No, of course not. Given that IT has penetrated already so much
into my life, these "IT companies" must be connected to (or better say
integrated within) "my business".
Interestingly some time ago I delivered an ITIL v3 based
Service Portfolio Management workshop within a large Financial
Institution. In preparing for this workshop we agreed to first focus
on the question: "what is a service?". So I started by presenting the
ITIL v3 definition of a service: "A means of delivering value to
customers by facilitating outcomes customers want to achieve without
the ownership of specific costs and risks.". So far, so good. Then we
looked at how to define a service and -more specifically- on how to
define the business value of a service. Now when I asked the question
"what is the busines value of your e-mail service?" the answer I got
is "The e-mail service provides message traffic and storage of e-mail
and e-calendaring". Does this describe a business value? Don't think
so.
Looking at this sample, one might see it as a proof point that
IT is really disconnected from the business and use it to justify a
Business Service Management approach. Personally I wouldn't go that
far. The only thing that it shows to me in this particular case is
that IT is not able to articulate the business value of a service, but
that doesn't mean the service doesn't have value or is not being
used. On the contrary, the e-mail service sample above is one of the
most used and appreciated service in the Financial Institute with an
implicit value. Nevertheless and ultimately as one of the results of
the workshop we came up with the following definition:
E-mail services provide value to the business when cooperative
business communications are conducted without the constraints of
location, device or time-zone. Value is created when IT operates for the
business a store-and-forward messaging system, so that business
employees can compose, send, store and receive e-mails with peers both
inside as well as outside the business and in a manner that
- Is accessible 24 x 7 x 365 across the globe
- Allows only one outage of max. 5 min per 3 months
- Enables messages up to 45Mb and mailboxes up to 100Mb
- Supports protection of business confidential information
- Ensures data availability and archiving within business
policies
Similarly and on a bigger scale, I recently met with another
customer (read: a service catalog manager within IT) who asked me to
review his service catalog and provide feedback. Of course I accepted
this and then found myself reading through a 193 pages thick service
catalog printed on paper. When the guy returned after a few days and
asked me for my opinion, I said: "Imagine that you are entering a
restaurant and ask for a menu card. And when the waiter returns he
delivers to you the cookbook of the chef. How would you feel?". He
immediately got the point that the service catalog contained way too
much information for their business customers. In addition I showed
him that there was also information missing in the service catalog.
And you probably have guessed this one already: it contained no
descriptions of business value whatsoever.
Again also in this situation the reality was that all services
in the catalog already existed and were actively being used by the
business customers. So why then create a service catalog? Good
question. In this particular case the main driver for producing a
service catalog was IT's desire to explain what they deliver, however
the business didn't ask for a service catalog and also was not
involved in the creation. And like Bill Keyworth
rightfully stated in The
Why & What of Business Service Management: "BSM success
is entirely dependent upon the willingness and skill of both IT and
business to have an effective two way conversation ...one party
without the other is doomed to failure.".
Reading through my samples above and several articles on BSMReview.com, I see a number of
very specific issues and symptoms, but am still not sure what the main
problem or need is for which we are trying to find a solution under the
name of Business Service Management. When we define BSM as "the
discipline that aligns the deliverables of IT to the enterprise's
business goals" then I wonder what's the value in doing this? And isn't
this already happening implicitly ? Is it really possible to define
the package of whatever it takes to deliver the expected service to
the business community ...in a way that they can understand and
appreciate that delivery? To me this sounds a little bit similar like
designing the perfect organizational structure, while we all know that
this does not exist (otherwise everybody would have it by now...).
I realize that my statements are provocative, however I believe
that a good understanding of and interactive discussion around the
fundamental problem we are trying to solve should be the starting
point for (m)any article(s) on BSM(Review.com). So let's first address
the question: "Business Service Management: what's the problem?".
Looking forward to your comments.