Incident Management in a SaaS environment

Integrating your incident management process using a SaaS toolset provides dividends to the organisation.

An unplanned event happens in everything we do in life. Whether it is spilling your drink in a packed bar or a child announcing they need the potty while driving to a Sunday lunch meeting with their grandparents, life throws you curve balls. How we react to them is in our genes. So why do we have problems dealing with these curve balls when it comes to Incident Management in a SaaS environment?

John Kenneth Galbraith used the term Conventional Wisdom to identify obstacles to newly acquired information. Conventional Wisdom sees Incident Management purely through the prism of firefighting. It is not until we integrate other data and processes with Incident Management that the organisation can add value. Driving down costs per incident, reducing the number of incidents and increasing average revenue per user.

Software as a Service is not new, but now an accepted mode to deliver business solutions. It is time to change the way we think about it. Even large enterprises are depending utilising SaaS. The example of Salesforce is but one.

Salesforce offers an organisation integration of Customer Relationship Management in a virtual solution. Specific to Incident Management, Salesforce allows for rapid sharing of information, insights based on the customer profile, behaviour and previous incidents and resource collaboration when finding a solution. All actions are tracked and stored for future reference.

Salesforce is not without its challenges. For instance if you want to integrate with your legacy billing platform the organisation needs to be on the Enterprise version of the Service Cloud. The impact here is a direct cost implication of a per seat license increase in excess of two-fold. The shortcut of buying the Web Services API module will not give the organisation the benefits in my experience; you end up finding you have to buy more modules that eventually add up to the same price.

There are indirect costs too when it comes to integration. In my experience with one such Salesforce integration house, Appirio, development was on time and to budget. Appirio, or saaspoint as they were previously branded, were also able to leverage off functionality already in the license bundle I had. Great when you are looking at building integration with other service solutions such as Splunk, Qualys or Smartsheet.com.

The power provided by Salesforce is that you have integration and sharing. The shortcut is to use single purpose call tracking tools to do the same job. Long term this is going to cause problems. Without integration, all you are doing is being effective, but you are not bringing efficiency in to the loop. The organisation will end up expending the same effort in five years time to bring a solution to a problem. Efficiency in that case will only be achieved by experience built up by the user and that is efficiency that never truly vests in the organisation.

Collaboration without integration is not a sustainable service improvement cycle. All organisations are better served investing in what creates vested wealth than achieving short term wins.

To find out more email letstalk@tavne.com.

Supporting SaaS

Everything changes, but nothing changes.

clare sign post

Service Management in the a SaaS environment is in a state a flux. Practitioners are told on a daily basis competing and contradictory tales on how Service Level Management is dead or central to their business. Tales of how Apple delivers value with little or no service. Or a SaaS solution only succeeds if it excites the customer base.

In essence, everyone is right and everyone is wrong. The stories are rationalisations of a historic reimagining of what has happened.

The days of long delivery lead times are dead. SaaS is more akin to baking cupcakes than building aircraft carriers. The short lead times mean PRINCE2 and heavy metal ITIL processes strangle SaaS innovation. In the time it takes you to think of writing up your Request for Change (RfC), your competitor has already delivered a killer feature. A Change Advisory Board meeting will take longer to organise than the programmer takes to write the code.

Mr magoo

The flip side is if you mess up in an unstructured environment the results can be devastating. We are all waiting to see what will be the long term effects on Snapchat, but there are some pointers we can identify now. Turning down the Facebook offer seems a trifle rash. The arrogance/ignorance of not reacting to a threat you were made aware of my a third party has to ask questions of IT governance. The simplicity of the hack has to ask questions of the testing rigor performed. Do you see a theme?

The British Computing Society put in place structures in order to manage just the dangers that have beset Snapchat. ‘IT is the business’ is my favourite. The idea that the business always comes first. Safeguarding the investment is what IT governance is all about.

toolbox

A risk board, a release management process and rigorous testing would all have gone a long way to mitigating Snapchat’s exposure.

Risk Board
This just needs to perform. Give it an owner. Give that owner a spreadsheet with risks and issues laid out. Plug the owner in to the entire business (so much easier in a SaaS company with low employee numbers). Then support and motivate that owner tackle the business head on.

Release Management
Again, cut away all the fat out of the change and release processes you see in ITIL. Distill it down to the bare bones. Every change to the system needs to be tracked, but only the big ones need an RfC. Get your users involved. Empower them to do the process management – in the long run it is in their interest. Get the adage across “do it right once and never look at it again”. Kanban is great, but it depends on motivated staff – motivate your staff. One rule, always separate the developer from the release.

Testing
This follows on from release management; test the hell out of your product. Employ people to do it. Again this is a step change from the huddle of desks making up the Operational Acceptance Testing team. Use internal resources. Involve all staff members in this. It’s a great way of explaining what the business does, training sales people and giving ownership to those on the periphery of the toolset. If you can’t explain it to your colleagues, what chance do your customers have.

One bug means every product you have sold has a bug in it. If Toyota are sending out all their cars with a design flaw where the gas pedal gets stuck they will not hold on to the moniker of the best build cars in the world for long. It happened on just a few cars and it was world wide news. SaaS means a bug in one product is guaranteed to be in all products.

I’m going to try and make a weekly buzz out of this. All comments are appreciated (so long as they are nice).

New offices

We now have new offices!

Ennis Innovation Age Park has become the new home to our fast growing team. It is great to have these state of the art facilities at our disposal.

photo 1

It is a striking building in the Clare and really inviting. The SDC staff have really gone out of their way to make us feel welcome.

photo 4

We have the stocks in for visitors.

photo 3

The chair is waiting for work to be done.

photo 2

And the view from the window is not half bad.

Be sure to pop in and have a cuppa if you are in the area.