When it comes to your Technology Management service catalog, are you lost in arguments on what to call certain categories of services? What are your service families and what is the next level of service elements? What are the definitions of the service elements? These questions are just the tip of the iceberg of current projects within I&O organizations in defining the rich and complex world of a technology management service catalogs. I&O teams are struggling to architect foundational service catalogs which will support the standardization and optimization efforts of their service offerings.
With that challenge in mind, Forrester created a I&O Technology Management Service Taxonomy - a collection of many service elements, organized by 13 service families. The research consists of a detailed spreadsheet based tool with a variety of service families, service taxonomies and definitions. The next steps are to understand the business services and capabilities which are enabled through these technology management services. Some business services and capabilities are similar from one vertical to another. Our next endeavor is to capture these services as well.
I’m sitting on my sofa at home (Yes! Home!) on Sunday morning just before Christmas. I’m “shut down” for the holidays now, but of course, I’m watching Twitter and now listening to my brilliant friends Chris Dancy and Troy DuMoulin discussing CMDB (configuration management database) on the Practitioner Radio podcast. It’s a marvelous episode, covering the topic of CMDB in with impressive clarity! I highly recommend you listen to their conversation. It’s full of beautiful gems of wisdom from two people who have a lot of experience here – and it's pretty entertaining too!
I agree with everything these guys discussed. In particular, I love the part where they cover systems thinking and context as the key to linking everything conceptually. I only have one nit about this podcast, and the greater community discussion about CMDB, though. Let’s stop calling this “thing” a CMDB!
I coauthored a book with the great Carlos Casanova (his real name!) called The CMDB Imperative, but we both hate this CMDB term. This isn’t hypocritical. In fact, we make this point clear in the book. Like the vendors, we used CMDB to hit a nerve. We actually struggled with this decision, but we realized we needed to hit those exposed nerves if we were going to sell any books. Our goal is not to fund a new Aston Martin with book proceeds. If so, we failed miserably! We just wanted to get the word out to as many as possible. I hope we've been able to make even a small difference!
Engaging All Service Engineering Folks: Help Forrester Define “Service Engineering” As A New Role Within Infrastructure & Operations (Or Beyond)! A variety of technology trends such as mobility and clouds are empowering consumers and connects employees who all are interacting and collaborating through apps and devices which are changing the way business is conducted. In response, organizations are forced to accelerate business changes which require the need for agility innovating new technology choices, implementation options, and delivery approaches. In this new pace of change the business demands more of IT to help deliver services which enable and support the age of the customer. Some Infrastructure & Operations teams have made the transformation to manage and support BT services which consist of technology, systems, and processes to win, serve and retain customers. Other organizations still manage and support components which range from operating systems, middleware, general purpose components, applications and custom components built all for specific purposes. I&O teams have become good at building components, but it often lacks the engineering discipline to assemble these components into services that meet specific business needs and are relevant in the age of the customer. To stay relevant and transform Infrastructure & Operations in the age of the customer, I&O needs a new role – service engineering. Service engineers mainly “do” three things:
1. Think and act from the outside-in – this means establishing, managing and continually improving services which are critical and essential for business enablement and business success.
2. Participate and support the DevOps journey – business agility in large parts depends on technology today. The DevOps team plays a large role in the quality and speed of technology delivery.
In August this year I am heading down to our nation’s capital to take part in the annual itSMF Australia event – LEADit. I have taken part in this event to a greater or lesser extent over the past few years across Australia – Sydney, Perth, the Gold Coast and now Canberra. As an analyst who broadly covers the Service Management space (as well as a previously ITIL qualified practitioner), this event is the mecca for those interested in service management in Australia.
Year after year at this event, I see a fair amount of change in the content and focus, but little change in the thinking, and little real movement in the implementation or improvement of the processes – a recent survey between itSMF-USA and Forrester displays the current maturity levels of processes in organisations:
Here we are – years (decades?) after the first ITIL books were written, and demand management is STILL immature. Even financial management has barely shifted in maturity over the past few years. Why is this the case?
As I write this, I am in seat 1A of United flight 1607 from Philly to Houston. playing on the screen in front of me is CNBC. I make no secret of my disdain for much of the so called "news media" so I won't launch into my usual rant there (there are some superb journalists out there, but Murrow and Cronkite must be rolling in their graves!). I am bristling over the coverage right now that is focused on the 787's latest woes. As usual, the talking heads are clueless and painting a doomsday scenario for Boeing! It's a bunch of finance people who don't understand the engineering realities. They're smart bean counters, but not engineers. I am an old engineer, so let me shed light on what the Wall Street mouths don't know. There is an important lesson here for I&O leaders!
I was part of a Forrester Team that recently completed a multi-country rollout tour with Emerson Network Power as they formally released their Trellis DCIM product, a comprehensive DCIM environment many years in the building. One of the key takeaways was both an affirmation of our fundamental assertions about DCIM, plus hints about its popularity and attraction for potential customers that in some ways expand on the original value proposition we envisioned. Our audiences were in total approximately 500 selected data center users, most current Emerson customers of some sort, plus various partners.
The audiences uniformly supported the fundamental thesis around DCIM – there exists a strong underlying demand for integrated DCIM products, with a strong proximal emphasis on optimizing power and cooling to save opex and avoid the major disruption and capex of new data center capacity. Additionally, the composition of the audiences supported our contention that these tools would have multiple stakeholders in the enterprise. As expected, the groups were heavy with core Infrastructure & Operations types – the people who have to plan, provision and operate the data center infrastructure to deliver the services needed for their company’s operations. What was heartening was the strong minority presence of facilities people, ranging from 10% to 30% of the attendees, along with a sprinkling of corporate finance and real-estate executives. Informal conversations with a number of these people gave us consistent input that they understood the need, and in some cases were formerly tasked by their executives, to work more closely with the I&O group. All expressed the desire for an integrated tool to help with this.
Here’s the hard truth:IT infrastructure and operations (I&O) teams are becoming less relevant. This will only accelerate now that we are in what Forrester calls “the age of the customer” where bring-your-own-technology policies and “as-a-service” software and infrastructure proliferate.
In this new world, developers still need compute and storage to keep up with growth. And workers need some sort of PC or mobile device to get their jobs done. But they don’t necessarily need you in corporate IT to give it to them. Case and point: employees pay for 70% of the tablets used for work.
At the end of the day, if you can’t deliver on what your workforce and developers care about, they will use whatever and whoever to get their jobs done better, faster and cheaper.
Much of this comes down to customer experience, or how your customers perceive their every interaction with the IT organization, from your staff in the helpdesk to corporate applications they access every day. Here’s a proof point on how much customer experience matters from Forrester’s soon to be published book, Outside In: over a recent five-year period during which the S&P 500 was flat, a stock portfolio of customer experience leaders grew 22% percent.
BMC has a golden opportunity to take a different track with Numara than it has for past mid-market acquisitions (see Magic Solutions), and it must do so if it hopes to build on this one and drive new revenue for the long haul. Numara enjoys a massive installed base of customers with its Track-It and Footprints product lines in the small and mid-market. They have been hard at work rounding out their portfolio to include Client Management (software management, systems management, and OS management), and other areas. Numara has been on a journey to re-invent itself and has been succeeding. Further, we believe that the culture of the Numara organization and BMC's will align well, as long as Numara is given the autonomy and investment they need to grow their portfolio and momentum in the field.
BMC Will Need Time To Work
Numara customers should expect relatively little change in daily operations for the first few months, as BMC aligns the organizations. If history is a reliable guide, BMC will typically give a larger acquisition such as this the opportunity to remain mostly intact, and inject key people and processes to help align the acquired organization with the BMC culture and ways of doing business. If this holds true for Numara, customers should see it as a positive step.
As many of you know, Forrester conducted a joint research study earlier this year, in conjunction with the US chapter of the IT Service Management Forum (itSMF-USA). The report is finally now available to the deserving. Forrester clients can download it using the normal access methods. Members of itSMF-USA will receive their copy from itSMF-USA. If you contributed, but do not fall into either category, Forrester will be sending you your copy.
You can read a few of the finding in my original post announcing the completion of the study. An example of the findings is the level of satisfaction with service desk solutions. While satisfaction in general is higher than one would think, a SaaS model has proven especially satisfactory:
Please let me know if you are having difficulty obtaining your report. Thank you again for all the participation that led us to these findings! We look forward to next year’s study!
There is growing evidence of a harmonic convergence of Infrastructure and Operations (I&O) with Security and it is hardly an accident. We often view them as separate worlds, but it’s obvious that they have more in common than they have differences. I live in the I&O team here at Forrester, but I get pulled into many discussions that would be classified as “security” topics. Examples include compliance analysis of configuration data and process discipline to prevent mistakes. Similarly, our Security analysts get pulled into process discussions and other topics that encroach into Operations territory. This is as it should be.
Some examples of where common DNA between I&O and Security can benefit you and your organization are:
Gain economic benefit by cross-pollinating skills, tools, and organizational entities
Improve service quality AND security with the same actions and strategies
Learn where the two SHOULD remain separate
Combine operational NOC and security SOC monitoring into a unified command center
Develop a plan and the economic and political justifications for intelligent combinations