Archive

Posts Tagged ‘Business Mapping’

Service Management in an as-a-service world – Part 2

August 6th, 2015 Comments off
Reading Time: 4 minutes

This is part 2 of a guest blog I was asked to create for the Service Management Conference. you can find the original here and where it was published completely in the July issue of the itSMF Bulletin.

Why business mapping is critical to effective Service Management and how to get started.

In Part 1 we looked at why the cloud can give IT service management team more control – not less. Now let’s look at how to use business mapping to provide control and visability in a world where applications are offered as subscription services, from a multitude of vendors.

Use Business Mapping To Ensure IT Truly Supports the Business

A map looks at the context of complex systems. We’re familiar with technology roadmaps that match short-term and long-term goals with specific technology solutions to help meet those goals, often presented in a diagram. They are designed to help customers (including internal customers) understand the technology, current and future, that is at work in their business. But the technology view is only one part of the puzzle.

In addition to addressing the business’ immediate and projected needs you need to have a larger view of the product/capability that your organisation provides and the market forces that may impact it. The external forces range from market segment growth, competitive situation and your distribution channels through to political, economic and environmental factors – and more. There are also internal forces including the company, customers, suppliers and other constituents. This view is known as a market audit.

A business map takes this to the next level. It starts with identifying the need that the organisation is addressing with its product or service, the evolution of that product/service from an idea through to a marketable product and eventually a commodity.

Business maps arm the technologist, and business professional, with information that can be used to understand the overall business’ direction and what factors influence the various capabilities that underpin the central need of the value chain. This holistic view of the business gives context for recommendations and decisions. Hint: Get it right and there will be less instances of Shadow IT, as you will be able to understand the emerging needs of the business as it relates to its strategy

Here are six questions to help you start the mapping process:

  1. Where are we now with the business capabilities, supporting processes and technologies?
  2. What is the visibility and value placed on each of these
  3. Where do we want or need to go with these? Ultimately the drive is to head toward commodity, however, that isn’t always the right answer as there are sometimes constraints
  4. How do we get to where we want or need to be?
  5. As the organisation moves from new and novel to commodity, what are your options for sourcing and delivering?
  6. How will we know that we are on track?

If you’d like to know more about business mapping read my blog or go see Simon Wardley’s blog

Transparency across multiple vendors

IDC predicts more than 65 percent of enterprise IT organisations globally will commit to hybrid cloud technologies before 2016. This hybrid environment encompasses everything from applications, to platforms to business services, providing the services the business needs dynamically.

So once you’ve mapped your organisation and selected your solutions how do you track and manage service delivery across multiple delivery modes and suppliers? How do you let the business know what is available to it? And how do you encourage the innovation through the adoption of new services?

Integrating the disparate IT and business systems and providing a clear view of what services are available to the business based on Persona allows everyone to know what is available. Most importantly this provides a way of tracking and measuring the services, both individually and holistically as they underpin key business capabilities.

So there’s no need to fear the cloud. Recognise it for what it is – a different way of delivering services that can actually give you more control, not less, provided you take the effort to jump into the driver’s seat and use your map.

NOTE: Original post included corporate product links, I’ve removed them from here and made specific reference to Simon’s blog (which was found through my blog link in the original)

Service Management in an as-a-service world – Part 1

July 30th, 2015 Comments off
Reading Time: 5 minutes

This is part one of a guest blog I was asked to create for the Service Management Conference. you can find the original here and where it was published completely in the July issue of the itSMF Bulletin.

Screen Shot 2015-08-30 at 12.37.17 pm

Why moving to the cloud can give you more control, not less.

What are the opportunities and challenges for the IT service management team in a world where more applications are moving into the cloud, offered as subscription services, from a multitude of vendors? Can you keep control and visibility?

Recently I led a discussion at an itSMF Special Interest Group meeting about IT service management in an “as-a-Service” world – a world where the way IT is procured, delivered and consumed has fundamentally changed with the advent of cloud computing. Not that cloud computing is new by any means – particularly in smaller organisations, but it is now becoming more and more prevalent in large enterprises. Or it is expected to be…

While there has been a lot of hype around “the cloud”, what became apparent at the meeting is that most information is targeted at the executives in high level overviews, or at techies in great technical detail.

Meanwhile, the IT service management team has been left in the cold. There is little clear direction on “how to” or “where to start” and too much hype versus fact. Yet it is the service management team who often has the responsibility to “make it happen”.

In our discussion, which included IT service management professionals from government, financial services and IT vendors, the concerns/queries about service management in a cloud environment were startlingly consistent across industry sectors:

  •        What is the best way to monitor and report service delivery?
  •        How have other organisations done it?
  •        What is hybrid cloud and how do you manage it?
  •        How do you manage service integration across multiple vendors?

The Australian Government defines cloud computing as a model for enabling ubiquitous, convenient, on-demand network access to a shared pool of configurable computing resources (e.g., networks, servers, storage, applications, and services) that can be rapidly provisioned and released with minimal management effort or service provider interaction.

Interestingly, the itSMF group viewed cloud as a commercial model for delivering IT, rather than a technology. And the overriding concern is that these services are not in their control.

So how does cloud impact the policies, processes and procedures service management uses to plan, deliver, operate and control IT services offered to end-users?

For me it comes down to recognising that while traditional IT procurement has changed, you can still be in control; defining a clear – but flexible – business map for how the technology, processes and people will support the business; and ensuring transparency across multiple vendors.

New Ways of IT Procurement Don’t Have to Mean You Lose Control

Much of the fear of losing control comes from the feeling that IT departments are relinquishing control to IT third parties because they no longer own the IT and can’t see, touch or grab it. Yet in many ways they have more control than ever as it is easier to increase or decrease capacity quickly in response to changes in your organisation or the market in which it operates. And, if you chose the right vendor, they should provide you with regularly updated innovative solutions and contracted service levels rather than you being locked into a technology that will start to age as soon as you implement it.

Of course it’s not simple matter of moving everything into the cloud. Sometimes legislative requirements will dictate where data can be stored or who has access to it which may force an application to be insourced. Or it may depend on the maturity of an organisation’s approach to IT – an immature organisation may refuse to outsource because it is simply fearful of doing so whereas a mature approach is open to pushing risk outside the organisation.

And not all clouds are the same. A private cloud is used by a single organisation. A community cloud is for the exclusive use of a specific community of consumers with shared concerns (eg security requirements or mission). A public cloud is for open use by the general public. And a hybrid cloud is comprised of multiple distinct cloud infrastructures (private, community or public). Whilst the debate over public vs. private cloud services rages on, in the context of the above and the relative organisational needs and maturity, they all have a place.

This feeling of a loss of control can be exacerbated by departments choosing their own systems, easily bought and delivered over the Internet. However this “shadow IT” should not be feared – instead it should be seen as an indicator that the IT department is not delivering what they need. This is why business mapping is so important.

 

Part 2 of this blog will cover why business mapping is critical to ensuring IT and Service Management truly support the business and how to get started.

Waves of innovation

July 25th, 2015 Comments off
Reading Time: 2 minutes

Today I’ve been reading about McNurlin and Sprague’s “Waves of innovation” model (2009) for the changing role of IT within an organisation. It’s essentially made up of 6 waves that have been observed over time, it looks like McNurlin started with 5 and the 6th was added somewhere in 2009.

Waves of Innovation

Wave 1 – Reducing Costs – began in the ’60s with a focus on automation

Wave 2 – Leveraging Investments – began in the ’70s with a focus on reusing corporate assets with systems justified on ROI and cashflow

Wave 3 – Enhancing Products and Services – began in the ’80s with the focus on IT being a revenue source through creating a strategic advantage

Wave 4 – Enhancing Executive Decision Making – began in the late ’80s with the emergence of real-time business management systems

Wave 5 – Reaching the Consumer  – began in the ’90s with using IT to communicate directly with users, completely changing the rules of engagement

Wave 6 – Partnership Supply-Chain Management – looks at integration of partners into the supply chain.

The premise is that these are observed waves and that IT is appearing to loosing some of it’s traditional responsibilities. I think that this is because the view painted treats IT capability as a uniform blob and not as discrete functions and capabilities. It doesn’t take into account that you have a spectrum of bleeding edge capabilities through to commoditised offerings at the far end and the value that each capability or service delivers sits somewhere on the “value” spectrum too.

Delivering value with IT systems requires clear understanding of the business, the services and capabilities that make it up and how IT can then support those individual pieces. This one dimensional view of IT is what holds business back from making smart decisions.

/rant

Bits or pieces?: An introduction to Wardley (Value Chain) Mapping

February 8th, 2015 Comments off
Reading Time: 2 minutes

15817131058_5acabc4677As those reading this blog will know, I’m a fan of the work of Simon Wardley, specifically his mapping technique for business landscape understanding. His most recent blog: Bits or pieces?: An introduction to Wardley (Value Chain) Mapping is the most concise step by step explanation to date.

I’ve watched as Simon’s model has matured of the years and it only gets better. When I think I’ve got a great tweak or variation on his work, he releases another explanation that has it and more.

The most recent of these are the aggregate view, overlay of provision or consumption and gameplay.

  • Aggregate view – when you take multiple views of the same map and overlay to get a holistic view of the organisation
  • Provision vs. consumption – are you consuming a service and as such what is it’s value, are you providing the services to higher-order components and are there smarter ways to obtain them.
  • Overlaying outsource/COTS/build your own with the provision/consumption to get a clear view of what you should be doing – working with market moves toward the right (commoditisation) when and where should you get the service you need.

My favourite is the use of the Kanban technique when implementing changes. I’ve been using this myself for several years (though I didn’t know it was called that) and found Trello to be an amazing tool to help.

I suggest you take the time to check out Simon’s blog, as it is well worth it to pick up on the concepts to develop your own tactics to strategy development.

How to build a roadmap in 7 steps

January 2nd, 2015 Comments off
Reading Time: 7 minutes

RoadMapMoving Information Technology (IT) into the sphere of “the business” is still a challenge in a lot of organisations. How to move up requires that the IT/ICT teams demonstrate value (showing how you can support the business achieve its goals) to more senior executives within the business, where to start is always a hard question. Whilst there are many ways to approach this, the roadmap is one of the simplest ways of getting started.

 

Over the years I’ve noticed that there is little consistency in the generation and development of roadmaps; Infrastructure, Application or even Business structure. This can be for various reasons including:

 

  • There isn’t visibility of the full picture, but you have to show some degree of thought
  • Enterprise Architects are now really Technology Architects so the views are skewed towards a technology, conversely there are consultants posing as Enterprise Architects who have nothing more than an MBA and no experience or exposure
  • Businesses don’t truly understand what they are doing with ICT or why they need to be planned and not reactive
  • It’s a contract deliverable and come hell or high-water you’ll deliver something.
  • Newly minted TOGAF, SABSA or other practitioners attack this discipline with too much vigour that they get quickly shutdown by the business.

 

Regardless of the reason, it is important to be able to show those needing to invest in ICT services, what they are going to invest in and why they are going to invest. I’ve found that providing clear traceability between business objectives, ICT strategies (where available) and the roadmap help you as the architect understand WHY better which helps when presenting up higher the the organisation; communicating in the business’ terms and not techno-speak.

It can also help the CIO/Director of ICT/etc. understand how their organisation is supporting the wider business and its initiatives.

Remember a roadmap is generally for inside an ICT organisation. it requires distilling into bite-sized chunks for management to absorb

So let’s get to it. Building a roadmap can be broken into 7 stages

  1. Confirm the business’ priorities
  2. Current State
  3. Define End state
  4. Identify the measures
  5. Gap analysis!
  6. Sequence the events
  7. Publish the end goal

Read more…