The document discusses building a process framework for managed IT services. It begins by establishing the value proposition, outlining customer needs like resolving outages quickly and keeping systems updated. It then designs the service architecture, mapping needs to processes like reactive support, proactive management, and strategic consulting. Finally, it discusses engineering process modules and deploying the processes using tools like service blueprints. The overall goal is to take a structured approach to developing managed services processes that link value to delivery and achieve required results.
Good afternoon everyone and thank your for joining our webinar on “Building the Process Framework for Managed Services”. The great turnout that we are experiencing for these webinars is testimony to the importance of well defined processes for a successful Managed Services practice.
3 objectives today:{BUILD} Give you a step by step approach to develop your processes, starting with a solid foundation of requirements{BUILD} Ensure that the service delivery model aligns with the expectations that you set with your customers for the service value proposition. If service delivery and expectations are not aligned, the result is unhappy customers{BUILD} (in just a few slides) Introduce a concept for deploying these processes in a modular approach that facilitates adoption
We hope you receive two benefits from the approach we are reviewing today:{BUILD} More sales – because your Managed Services represent greater value to your market{BUILD} Higher profitability – because you can deliver your managed services consistently, with less rework and reduced non-value-add effort
There’s a lot of buzz around about clouds these days.I would like to suggest that there’s one cloud that’s not getting as much publicity as it should.That’s the dust cloud raised by all of the backstage activities that many MSPs juggle in delivering their services to their customers.Unfortunately, without consistent processes in place, many MSPs are successful due solely to the heroic efforts of their staff.
In some cases, MSPs have developed processes for isolated areas. Areas like…While performance has improved in these areas, the cloud remains. There are still problems with waste, rework, and handoffs in other areas.
Unfortunately, heroic efforts don’t scale very well. You can maintain customer satisfaction for a limited number of customers, but at some point, as you add customers, your service levels begin to break down.
The underlying premise in this presentation is that services must be designed, just like products.Service delivery processes are a critical element of the design. You must design value – outcomes that satisfy specific customer needs – into the service in order to satisfy customers and achieve your business objectives for growth and profitability.
This afternoon, we’re going to look at the four steps required to institute a solid process foundation for Managed Services.At the end of today’s webinar we’ll review AntFarm’s offerings for a completed process framework for Managed Services.
All too often, “Value Proposition” for a service is confused with the top level messaging used to capture the prospect’s attention.[build]While this messaging is clearly an important part of the go-to-market strategy for a service, it doesn’t provide the necessary foundation for service design. It doesn’t explain the business problems you’re solving or how you’re going to solve them.
We’re going to take a three step approach to defining the in-depthvalue proposition for a service:a) Define the business problems you are going to address with a service – stated as business objectives. These will be sources of pain or benefit for the customer. They are the reason the customer will spend money with you.Increased revenue, reduced cost, reduced or managed risk, increase competitivenessb) Determine the underlying requirements – or needs- that must be addressed to solve the problemc) Identify the outcomes your service must provide to satisfy these requirements[build] Let’s start with a couple of examples for business objectives... As you write them, always finish with “so that you can…”
Now lest look at some examples of requirements that must be met so that the objectives are achieved.We’ll focus on the availability element in the first objectiveMake sure you include the non-technical requirements to be satisfied: No downtime because of changes that went wrong Client understands service delivery procedures Proper notifications Periodic review of service levels provided
Finally, determine the service outcomes you will delivery to satisfy the needsFor those of you familiar with Six Sigma, this thought process should look very similar to the Critical To Quality (or CTQ) Flowdown
Make this a comprehensive exercise.[build] The deeper that you understand the needs, the more value in the service.This is where you begin to differentiate your services competitively from those of your competition.(approx 140 needs addressed by 60 – 70 specific outcomes)
Once you’ve completed the Customer Needs Analysis, you can develop your top level messaging to match.You will be able to articulate:Specific business problems you are addressing – why they should spend money on you They underlying needs that contribute to solving these business problems The service outcomes you will provide that satisfy the needsYou will be able to establish credibility with your prospects that you understand the full scope of the business problems they face related to IT management and that you have and answer for those problems.
Typically 3 levels to a process framework as shown here…> Top level view> Process or workflow view>Detailed technical procedures (you probably have these already) process ties them together to create the serviceIn this presentation, we will be focusing on the top two layers in this framework.
Service Episodes – episodes of customer engagement
If the concept of an architecture or life cycle is still a little fuzzy for you…Common example of a life cycle for a project. All of you have one of these. You call it a methodology.For a project, relatively linear.Be sure to define entry and exit points or boundary conditions for each phase. Serve as: triggers, handoff points, contract milestones.
For managed services, the architecture has a number of parallel phases once you onboard the customer.This architectural model provides the broad framework for the life cycle of the relationship with the customer and for service delivery.(yours may not match exactly)
Next step is to define the process modules included in each phase.This is done by grouping the service outcomes into logical sets – based on common teams, tools, technology, place in the lifecycleNot as hard as it may seem. You know many of these already – perhaps just not all of the outcomes to include.Use affinity diagramming.
This is the AntFarm view of a Managed Service architecture.Yours may vary.Now you can explain your service methodology to both your employees and your clients.And, you know where in the process framework the various outcomes are delivered that satisfy customer needs > the value proposition has a direct tie to the service methodology and process framework.Although your diagram may not include all of these areas yet. As you mature your offering over time, they can be added.
Each module drills down to a process map, or Service Blueprint – discussed next.All of the modules connect together to form the service offering.Within the service architecture, you can prioritize where you want to start in process development or improvement.
This is the AntFarm view of a Managed Service architecture.Yours may vary.Now you can explain your service methodology to both your employees and your clients.And, you know where in the process framework the various outcomes are delivered that satisfy customer needs > the value proposition has a direct tie to the service methodology and process framework.Although your diagram may not include all of these areas yet. As you mature your offering over time, they can be added.
Process design begins with understanding the objectives and desired outcomes.
Kaizen is Japanese for “Change for the Better” or continuous, incremental process improvement. The Kaizen approach was developed as part of the Toyota Production System in the 1950’s and 1960’s. It spread to the United States in the 1970’s and 1980’s, where it has become established as the leading method for fast-paced business process improvement.The focus of Kaizen is incremental process change, as opposed to sweeping change, that improves customer satisfaction, eliminates wasted effort and reduces process delay.Some key tenets of Kaizen are shown here: First, understand value from the customer’s perspective: improve service delivery elements that represent business value for them and reduce or eliminate the rest Second, improve process performance by reducing service failures (whether for the customer or for the provider) and improving productivity Next, take an evolutionary approach rather than a revolutionary approach to process change. Institute an ongoing, repetitive process to improve service delivery that achieves results one step at a time. Finally, involve the workgroup as part of a team focused on achieving results. With everyone’s input, the situation is more thoroughly understood and solutions have stakeholder buy-in.
The foundation for Kaizen is the “Deming Improvement Cycle” introduced into Japan during the 1950’s by Dr. Edwards Deming, a renowned quality consultant. Since it’s initial introduction, the Deming Improvement Cycle has become the cornerstone of many process improvement disciplines.The cycle has four steps as shown on this slide – PLAN, DO, CHECK, and ACTLet’s review the steps:[build] PLAN: Seek to understand the current state of the process: how is value created for the customer of the process, how well is the process performing. Then determine how to improve the process: what steps must be optimized, what steps must be eliminated. Design the future state of the process. Prioritize the potential improvements. (You will not be able to implement all of them in a single Kaizen event)[build] DO: Implement the proposed process improvements: develop the tools, templates, standard work processes. Pilot the changes to make sure they are practical and don’t have unintended consequences. Roll the changes out to the work group.[build] CHECK: Determine the resulting process performance: is your team complying with the process; are metrics moving in the right direction. Verify that the improvements were as expected, or explain why not.[build] ACT: Fix the root cause of any variation from the expected results. Lock-in the new process to ensure sustained performance.This simple four-step cycle occurs at two levels for Kaizen events. We’ll explore this more in succeeding slides.