Showing posts with label ITSM. Show all posts
Showing posts with label ITSM. Show all posts

Tuesday, December 13, 2011

No one wants a Service Oriented business, we want an Outcome oriented business

Why is it that IT experts are so focused on HOW something is achieved and not WHAT is achieved?




I was just reading this article by James Urquhart, VP of Product Strategy at enStratus, "Why it’s so hard to talk about cloud"


Some good points were made between James and Andi Mann, VP of Strategic Solutions at CA.  However, the real gem in this post, as with most posts, were in the comments.   IT at this critical point needs clarity in terms, not confusion.   Unfortunately product companies are perpetuating the confusion.   Why?  Because they are struggling to hang their hat on a differentiation that they can sell.

IT must not embrace these selling points into their value proposition.   It's a value trap.   I'm not saying that as a buyer you should not see value in CLOUD/SaaS/Private, whatever....  You should consider all the key elements of their services and support.   However, do not bring this as a value proposition to management....  THEY DON'T CARE

Services deliver an outcome.  Applications and infrastructure facilitate that outcome.  I think "Service Management" IT people work too hard to shy away from appropriate and fitting terms like applications, infrastructure and systems to use the term service in immature and confusing way.  I.E. Email as a Service.  Email is a system that is part of the employee communication services, like Phone systems, and mail systems, and IM systems, that facilitate the outcome of people sharing information with each other. If the employee communications team was in place instead of the email team, the intranet team, the phone team, the IM team, the portal team, etc..  someone would have realized "Oh our outcome is not very good".  (It also would have marketing and HR staff as part of the team)

STOP THE MADNESS,  this is not that hard.  In order for a Service to exist you must have a clear and present service consumer and a definitive service provider, that delivers an outcome to that consumer.  With out either of these it is a system, and that's is OK, systems are good.  They help us manage smaller components in a meaningful and easy to call out way.  You should also have a Service Owner (the person paying for it, not ITIL's IT self commissioned guardian.)  You also have Service Enablers. Key sourcing relationships (internal and external) that are required to help facilitate that outcome.

So like I've said many times on the ITSMWP podcast, unless you are an IT business, you really don't need IT Services.  You are making more work for yourself, frustrating your culture and breeding confusion.

But if we don't have Services, how can we manage ourselves? You have Services, business Services.  Manage yourself based on the outcomes of those Services.

If the Outcome is bad - your services stink.
If the Outcome is good - your services will do...  for now.
If the Outcome is great - some lied about the metrics...  J/K (sort of)

So if an application, or an infrastructure, or a system is in the cloud, does management really care?  Of course they don't.  They just want the systems in place to ensure speed, security and availability of the overall service they are receiving.  If a cloud provider can be a better Service enabler than internal IT, than an Outcome oriented culture will leverage it.

Wednesday, February 23, 2011

Dazed and Confused - Pink11 revelation

It's 6am Vegas time, and my head is spinning.  I am coming up on day 3 for me of one of my favorite conference venues Pink Elephant IT Service Management.  After years of studying, implementing, consulting and leading ITSM intitiatives and projects I woke feeling like someone had picked my pocket.

WHY IN THE WORLD DO NON-IT COMPANIES HAVE IT SERVICES?
THEY DON'T NEED THEM!
There I said it.  (actually' I've already tweeted it).

Why would I say this?  Me, after standing on soapboxes for so many years.
I don't know if it's the past year of doing the ITSM Weekly Podcast and listening to guests.  Having some gut wrenching discussion internally at Inforonics about our corporate strategy.  Maybe it has been reading the Universal Service Management Body of Knowledge (after reading this post Ian offered users a $50 discount. use Discount code "VigilantGuy" tx Ian) and meeting its author this week Ian Clayton.  I'm sure it's a  bit of all that, but's it's definitely 2 distinct events that have happened in sessions here at Pink.  Which is why this contiues to be one of my favorite venues.

Event #1) After a 45 minute panel discussion on Service Catalog (of which I had the pleasure of being on) the last question of the day was by a women who was frustrated by the inability to have services defined and asked "Besides Email, what are some other IT services".  I then hear each panelist rattle off System after system,  network, storage, etc..   It was clear this panel of Service Catalog (where you write down what the services are for the business) couldn't agree on what a Service is.

Event #2) In a panel discussion moderated by Rob England (aka The IT Skeptic) the topic was the elusive CMDB.  A source of consternation, frustration, and confusion throughout the ITSM industry.  The major point hit again and again: It has to be Service Aligned....  But wait, we can't define what a service is.
As I sat there and listened to the extremely passionate arguments, emotional lessons learned, and even one person honeslty begging for help.

We are trying to put Round Pegs in Square holes.  We are making up a layer that does not need to be there.  The IT Service layer is fabricated to fill a misconceived whole.  Well there is no whole.

Business Models are supported by Operational Models that are managed through systems and processes.  Business Services are the only services a business needs.  These can be supported through systems layer that correlates and integrates assets (technical or not).

Yet, that is not how ITSM community speaks and talks. In the ITSM community if my Business Model is about Hospitality, we still create this thing called Storage Area Network Services.  When did SAN Services become something people buy to get a hotel room.  They Don't!

So if I follow the current thinking on ITSM, I am supposed build and define the SAN Service, put it in a catalog, map it to a CMDB, and present its value to my CEO and ask him for a seat at the table.

If you were CEO, would ask me to sit down?

I can tell you what Captain Arbrashoff would say: "Beat it buddy"

Please tell me your comments or send me a tweet @vigilantguy  I would love to hear your response and thoughts on this.
On to day 3.

Thursday, January 6, 2011

ITSM Weekly the Podcast (Week36) - Guest Speaker: Ian Clayton

My dad was a mechanic, he is the farthest thing from a "Computer Guy" as you can get.  Seriously, I have to use Webex to support him because I just don't have the patience to walk him through screen clicks, but that's a whole other blog.  Yet, he was not unlike most of the IT professionals I have worked with.  Let me explain: He owned his on Garage, a Service Station, so it was naturally ingrained into me that when people had problems with their technology (uhm yes, Cars are technology) that they would take it to him to have it "serviced".  This idea of going to professionals to have your problems handled is by no means new.  Yet somewhere along the line service standards changed.  Let me illustrate.  I remember pumping gas as a kid for my dads customers (yeah for real, people didn't actually do it themselves), I would even check the oil, wash the windshields, and even clean the wiper blades.  Also, you could get any type of car repaired, and we did any type of repair. We were a "Full Service" station.  Times have changed we now have "Self Service" stations where you get Gas and typically food goods and other non-automotive related convenience items.  "Full Service" stations you get your gas pumped and that's usually it.  As for car repairs, you go to specialists, Brakes, Mufflers, Transmissions, etc...  The progression has been, as people became more comfortable with their technology, they have become more self sufficient, able to service themselves and look for value added services to their time and convenience.   
I see the IT industry heading down the same path.  IT staff used to be great to help setup network switches, desktops, install applications.  Now an office manager or receptionist won't get hired without knowing these skills.  Thus IT leaders need to look at the trends to help customers be serviced better, more conveniently, enable and empower them to help themselves.  In Episode 36 we have a great guest and legend in the IT Service Management space, Ian Clayton.  Ian is a very forward thinking expert on customer service management and speaks frequently on the concept of "Outside-In".  I hope you enjoy this podcast, as much as I did and I can not recommend his book enough, USMBOK for IT service Management.  Ian has offered a %50 when you enter the code "servicesphere" at check out.


Shownotes and details here: http://www.servicesphere.com/blog/2010/10/11/itsm-weekly-the-podcast-episode-36.html


ITSM Weekly The Podcast (Episode 36) from ServiceSphere on Vimeo.

Special Guest:  Ian Clayton, Ian's Blog Here, See Ian in January 2011Here!
Submit Questions:  Anonymously or Email or Call In: (765) 236-6383 or Twitter Questions/Comments #ITSMWP
Episode 36 Topics:
COOL DEAL:  50%  OFF USMBOK for ITSM Weekly Podcast Listners!  Enter Code "servicesphere" at checkout

Monday, November 8, 2010

ITSM Weekly the Podcast (Week33) - Guest Speaker: Kevin More

In my last blog post I spoke about the human element of actions.  This becomes ever so much more prevalent when your corporation works with deviations from societal norms.  In my life I have worked for almost every type of corporation, marketing, sales, insurance, finance, hospitals, snack goods, education, engineering...  There is a few I haven't worked in by choice, but not many.  The actions of showing up at a desk, walking into a meeting, presenting a topic, evaluating a report, have all been relatively the same for me.  My strength has been FCAPS Fault, Capacity, Availability, Performance, Security, and Change management.  However, my experience for everyone of those actions has been completely different.  FCAPS management to be truly proactive you must understand the business.  What does that mean?  What do the people in the business do, and how do they do it?  You must observe the culture, understand the patterns.  For instance, my first work assignment in insurance I took the opportunity to evaluate when desks would clear out at the end of the day.  I noticed typically around 4pm employees were heading out and by 5pm it was fairly empty.  So before ever running my first system utilization report, I already head the suspicion that between 2-4pm the system was at high-load.  Lifestyle was a cultural element, and sports moms' and dads wanted to be home for 6pm practice. When evaluating network and system traffic, I was spot on. 2-4pm heavy usage.  So I then took that data and evaluated the load testing strategy.  Just as you would have suspected, a ramp load to an avg steady stay for 6 hours and then down again.  In other words, the simulation was emulating traffic and load based on a work-day schedule, not a cultural behavior or pattern.  So what am I getting at?   KNOW YOUR BUSINESS.

This week our special guest is a colleague of mine from Boston SIM, Kevin More.  Kevin is a very impressive proffesional, not just cause he is technical, a savvy business person, or has an iPad.  (Though I am jealous of his iPad).  It's because he knows his business.  He understands what his culture does, how they perform actions, and even more importantly WHY they do it.  Listen in as Kevin More, CIO of May Institute, discusses the delivery of IT services for an organization dedicated behavioral health and development of children and adults with brain dysfunctions and autism.

Enjoy this weeks episode with our special guest Kevin More.


ITSM Weekly The Podcast (Episode 33) from ServiceSphere on Vimeo.

Your Hosts:  Matthew Hooper and Matt Beran(twitter #ITSMWP)

AUTISM, iPADs and SIM-FUSION!
What happens when a CIO, a Service Desk Manager and an Industry Junkie Chat Weekly?!
Special Guest:  Kevin More

Submit Questions:  Anonymously or Email or Call In: (765) 236-6383 or Twitter Questions/Comments #ITSMWP

Friday, October 29, 2010

ITSM Weekly the Podcast (Week32) - Guest Speaker: Philip Neufeld & Matt Neigh

Service Management  - a term that continues to allude people who are in the service industry.  I'm not talking just IT, all be it probably we are the worst to embrace this.  I'm talking about those who just don't get that if you are not fabricating a tangible (electronic or physical) product or good, then you are performing services for your job.  Even if you make a product, say diamond plated dental instruments (something you would be surprised I have learned a lot about),  you still are performing services.  Turning shanks, dipping instruments, packaging, shipping, are all series of actions.  So what's my point?


Service Management is not process.  Processes are not Service Management.  Yet both involve the same series of actions.   You must perform a series of actions in a quality controlled form to produce a result that is consistent, expected, and predictable.  This is where PROCESS kicks in. Processes help you to know which actions to take, when to take them, and what to track about it so you can measure, tune and report on those steps.  SERVICE MANAGEMENT thus is all about the attitude, reflection, interaction, communication, and personalization that surrounds the people performing those actions.  Thus a simple way to think about it in my mind is a PROCESS gets the job done, SERVICE MANAGEMENT satisfies a the requester.  Thus if you spend too much time focusing on either one of these without the other, you will achieve an imbalance of not getting the job done and being a talking head to a requester, or being efficient but a royal pain to work with.  Remember if it's just an action, a robot can do that.  Humans desire a human element, and you must bring that human element to the table when perform actions for other humans.

Enjoy listening to this weeks episode where we speak with Special Guest:  Philip Neufeld Director of Service Management, IT Services State of California and  Matt Neigh from our Higher Education sponsor Cherwell Software

Show notes here: http://www.servicesphere.com/blog/2010/9/13/itsm-weekly-the-podcast-episode-32.html


ITSM Weekly The Podcast (Episode 32) from ServiceSphere on Vimeo.



Your Hosts Chris Dancy, Matthew Hooper and Matt Beran (twitter #ITSMWP)


Mobile Apps, Communication Intelligence and Fusion
What happens when a CIO, a Service Desk Manager and an Industry Junkie Chat Weekly?!
Special Guest:  Matt Neigh
Special Guest:  Philip Neufeld
Series:  ITSM and Higher Education
Submit Questions:  Anonymously or Email or Call In: (765) 236-6383 or Twitter Questions/Comments #ITSMWP
Episode 32 Topics:

Wednesday, September 1, 2010

ITSM Weekly the Podcast (Week27) Special Guest: Patrick Bolger

Being the spokesperson for a Service Desk tool is not an enviable position in my mind at all.  In fact it's probably one of the worst functional areas I would want to support.  It's flooded by vendors, it's selling to a cost focused market place, and it's level of expectation for results is ridiculous.  Unless, your vision and product is game changing, and your are a bullish marketer.  This week we had the pleasure of having on Patrick Bolger, an acquaintance I've come to know through sponsoring at ITSMF and Pink Elephant over the past 5 to 6 years.  My first introduction to Patrick was a continued lesson in never underestimating who you are meeting.  Patrick, in his gruff voice approached me as I went to his booth, "what's ehh ahh Vigilant do?".  Figuring he was a booth bouncer, I said "oh we implement ITSM solutions."  The standard "you wouldn't really know what I'm talking about if I told you".  Then like a sucker punch, Patrick started to unleash on me a vision of  service management and forward thinking I hadn't seen in the industry, especially from a tool vendor.  Long before ITIL V3, Patrick was talking about life-cycles and maturity mapping, integrating strategic vision into tactical execution.  I sat for over an hour punch drunk at the wealth of knowledge from a guy who looked like he just stepped out of the WWE.  That's a compliment Patrick, please don't hurt me. :)


Moral of the story:  Never underestimate the talent in the exhibit halls.  Ask questions, take time to learn, and don't be afraid to say "show me what you got" that's what they are there for.

Enjoy this great episode with Patrick, and thanks again to his company: http://www.hornbill.com/ for sponsoring.

Show notes: http://www.servicesphere.com/blog/2010/8/9/itsm-weekly-the-podcast-week-27.html


ITSM Weekly The Podcast (Week 27) from ServiceSphere on Vimeo.

Your Hosts Chris Dancy, Matthew Hooper and Matt Beran (twitter #ITSMWP)


Sponsor:  Hornbill Software 
Sponsor Special:  You Choose!! 
Week 27 Topics:

Wednesday, August 11, 2010

How to Maximize Outsourcers - Part 3 of 3 - Working the Relationship


This is the 3rd part of a 3-part article on how to get the most out of your outsourcing relationships.  
Now for Part 3 - The Relationship.  Customer, Consumer or Partner 

Part 3 - Us

Congratulations!  
You've taken a big step in evaluating  the mission that your IT organization is on, and have decided that there are core services that you should be focusing on to make a business impact, and that there are services which are not core and that you will partner up to achieve the maximum outcome.  
Phew...  big step.
Next, you have carefully selected outsourcing options and providers that will deliver outcomes aligned with your corporate objectives and business focus.
Great job!... but you're not quite ready to achieve a return on this work.  There are still 2 major hurdles you need to get through in order to start actualizing benefits of this relationship and to start taking advantage of the benefits.

Hurdle 1) Frankenstein Complex
So you have just inked the deal, when you step back to look at your creation and say to yourself - "I now have more complexity, disjointed parts, awkwardness; I've created a Monster!". 
Well, before your peers start running into the data center with pitch forks and torches, you need to be armed and ready.

First, you must make sure that you have clear roles and responsibilities outlined and accepted by your team and the outsourcer.

Next, you must be clear on intellectual rights.  Who owns the IP, the code, and access to your data.  Depending on what you are outsourcing, this can be very complex.  The "Cloud Computing Bill of Rights" by James Urquhart can be a great start.

Finally, you need to show value.  
Ugh... not more presentations.
NOT MORE Presentations...  the last thing that your business peers want to see is a powerpoint of how you've glued body parts together.  (sorry for the graphic image, but that's how non-IT business units look at most of our presos)

I'm talking about real value, demonstrated by outcomes that matter.
So, now that Franky is keeping the lights on and handling daily operations, take this time to setup the following committees
(I recommend in this order):
A) End-User Improvement Steering Committee
 -- A joint effort between IT and departments with the largest or most critical end-user base, focused on improving the end-user experience. 

The output of this committee should be focused on areas of improvement in business operation.  Shy away from look and feel unless it is truly an improvement that will improve business performance.

B) Service Quality Improvement Steering Committee
--Bring together a representative from the top 3 to 5 services within the business 

Create a Service Quality initiative that is based on verifying value-add (yes the old VVA stuff for those with manufacturing backgrounds, hey it works) of the services that the company delivers.

The output, from an IT perspective, should be to start labeling and documenting the business services relationships to IT services and the IT Service providers.
-WAIT!  don't you mean IT assets?
No, I don't.  You need to trust your service providers, and trust that they will create that level of documentation.  Trying to micro-manage the outsourcer is a losing proposition.

With that said, let them do a lot of the work for you.  By providing them the service relationship model, you can have them provide the reporting to you in a format that the business wants to see, along with the reporting on their performance.

Now, you can start to change how IT is perceived.  Yet, beware... you’re still not there.

Hurdle 2) Extreme Makeover Complex
This new look for IT is very exciting to the business.  They really like some of the new-found attention that they are getting.  Yet, without maintaining certain disciplines, the glitter and glam will fade quite fast.  

Here are some personality checks to keep the relationship strong.  
Don't forget where you came from.  
In other words, don't forget the difficulty and complexity of the services you have outsourced.  This is not your chance to finally be the "Customer" and unleash all these years of pentup frustration from being beat down by the business.  Your outsourcer is your partner, a partner who will best serve by making you look like a hero.  

It's not cheating to multi-source.  
(I know this is sound more and more like a Cosmo article...)
But seriously, it's business.  Single-sourcing is not always your best option.  Be open and honest with your provider.  Dictate your requirements and reasons for sourcing alternatives.  If you feel that your current provider is over-stretched or over-committed - tell them.  It will give them the opportunity to focus on the services that they are delivering, plus it will create an opportunity for them to compete in the future.  
Of course, you may be surprised and find out that they are more mature in this offering than you think; that they can provide great credentials and references to back that up. , In this case, it's a WIN either way.  Remember from Part 2, this is a competitive marketplace, and you have every right to keep providers earning your business.

Finally, don't play games.  
Sad but true, there are many who feel that all the resources of an outsourcer are at their beck and call.  Be warned!  Outsourcers with whom you can play games, play games as well.  You are fooling yourself if you think you are getting more than you paid for or bargained for.  Enter the relationship with honesty and integrity and expect the same back.  View the outsource partner as an extension of your organization, while remembering that they are NOT your organization.  
So when dealing and interacting with them avoid internal politics and keep them focused on delivering for your team.