Originally posted on The AXELOS Blog , March 2021 and written by Solmaz Purser , Project Editor, AXELOS The past year has been tumultuous and unexpected, to say the least. Over a year on from the start of a pandemic that few ever expected, the world has certainly changed. Many people are now working from home . This was expected to be a temporary measure, but in some instances, people have been working from home for nearly a year. It would be fair to say that this is the new normal, where commutes now involve walking to a computer, and work social events are conducted via video conferencing. This brings us to ITIL® 4;: Create, Deliver and Support (CDS) and how it can be used to help you in the new normal. The components of CDS are flexible and adaptable enough to be applied to any situation, such as surviving prolonged periods at home. Relationship management CDS explores the importance of relationship management, where a service manager acts as a point of contact and liaison between

Think slow and hard about that statement; Drive Stakeholder Value ! Sometimes we see and use terminology so much that the power of the statement gets lost. This is one we must hear and ignite if we have any hope of meeting the evolving door of consumer requirements.  The Drive Stakeholder Value (DSV) certification course is available within the ITIL 4 Managing Professional stream of certification.  Therefore, DSV is also a module and one of the focus areas in the Managing Professional Transition (MPT) class.  Confused? Take a look at this graphic : ITIL 4 Managing Professional Transition  is a course that provides ITIL Experts or those that have at least 17 ITIL v3 credits a fast-track way to obtain the ITIL Managing Professional certification. This course excerpts key concepts from ITIL 4 Foundation and from each of the four Managing Professional modules. The Managing Professional stream of certification courses targets IT practitioners working within technolo

The purpose of Portfolio Management, when applied to Provider investments (especially, IT investments), is a central mechanism to an overall Value Management approach by making investment allocation explicit against strategic choices such as how much to invest in potentially high value, but usually risky initiatives versus safe but low-value activities. The Service Portfolio represents the complete set of services that are managed by the service Provider.  It is used to manage the entire lifecycle of all services and is defined by three categories of services.  The service pipeline represents service that is under consideration (purposed) or those that are currently in development but are not yet ready for deployment or consumption by the business partners. The next category is the service catalog which represents all live services or services that are available for deployment to the business partners. The final category is retired services.  This represents the services that are

The purpose of the (IT) Service Provider is to serve the needs of the business.  This is carried out by providing services to the business which are then engaged to provide some form of value to both the business and the Service Provider. Often the value delivered is less than optimal because the Service Provider and the business have different perspectives, culture goals, objectives, and incentives. The Business-Provider Alignment Model (BPAM) provides a framework for being able to analyze and understand these differences between the provider and its business partners. By engaging the BPAM we can begin to surface dialog about the relationship between the provider and the business and begin constructive discussions about the partnership that needs to be created. It does this by allowing each party to exam the four key elements of alignment – business environment within which the business operates, strategic context for the business, provider strategy and the provider portfolio of

In today’s business climate it is imperative that the IT Service Provider not only understand what the business strategy is, but be able to initiate and deliver services that not only support it, but help to shape it.  This can be successfully accomplished by ensuring that the service portfolio remain aligned to the business needs.  Over time these requirements and demand for services change and mature.  The Business / Provider Relationship is integral in keeping the demand and supply of these services and capabilities appropriately and continuously aligned.  One of the tools engaged for this task is the “Business-Provider Maturity Model”. The Business-Provider Maturity Model is a way to help surface and understand the growth in maturity of business demand for Provider services and capabilities, and a Provider organization’s maturity of supply capabilities needed to both satisfy and shape that demand. Many maturity assessments are very IT centric assessing the ability of the Servi

The Business Relationship Maturity Model (BRMM) is a way to help surface and understand the maturity of the relationship between a Provider (internal IT organization) and their Business Partner. This is not about the maturity of the BRM role or process.  This is about the maturity of the Provider/Business Partner relationship and therefore must take into account the perspectives of each party. The BRMM is made up of 5 levels, each with a descriptive tag, and represents a relationship maturity continuum. Level 5 is the highest and described as strategic partnering, Level 4 is trusted advisor, Level 3 is service provider, Level 2 is order taker and Level 1 being the lowest or ad hoc. Level 1 Ad Hoc: From the Business Perspective (BP) it’s, can’t even get my provider's attention, results cost too much, delivers too little and takes too long.   From the Provider’s Perspective (PP) it’s: I’m too busy to think about anything other than I’m too busy.   Characteristics of relati

Historically, many companies have had a single strategy for selecting, deploying and managing applications. They have had a defined structure for classifying applications by value or functionality, but failed to recognize that applications are fundamentally different based on how and when they are engaged by individuals and the organization as a whole and the pace at which these tools need to be changed and updated.   Many organizations are finding themselves with an enterprise application strategy that fails to satisfy the needs of the business community, which has often led to underutilized applications throughout their portfolio. Gartner’s Pace Layered Application Strategy is a methodology for categorizing applications based on how they are used and how fast they change.   This strategy helps IT organizations rationalize the use of DevOps practices that ensure a faster response and a better ROI, without sacrificing integration, integrity or governance requirements.   The

I remember reading a quote “Every business today is a technology company” or something close to that. As we move from business-IT alignment to business-IT integration and now convergence, it is becoming more and more critical to understand and manage both the business and IT capabilities so that integration of the business strategy, IT strategy and the IT portfolio are seamless.  In today’s business climate it is imperative that the IT organization not only understand what the business strategy is, but be able to initiate and deliver services that not only support it, but help to shape it.  The Business Relationship role, process and capability is integral in making that happen. One of the tools that can be engaged to help facilitate this convergence is the “Business Capability Roadmap.   It is made up of three key components: Roadmap Business Capabilities: Identifies how business capabilities need to change to achieve defined strategies. Roadmap Enabling Capabilities:

To say that digital technology has changed the world is an understatement. Digital transformations are revolutionizing entire industries and reshaping every aspect of business. To stay competitive, businesses must accelerate the delivery of digital products and services. To meet business demand, IT organizations must accelerate the delivery of secure, high-quality and reliable software features and functionality ( DevOps ). The thing about any transformation, whether it’s the digital transformation affecting the world, or the DevOps transformation affecting IT organizations and their business partners, is that it’s never only about the technology. A successful transformation requires shifts in peoples’ behaviors, mindsets, vocabulary, roles and reporting relationships. It requires changes to processes and to day-to-day operating procedures. Perhaps most importantly, the ability to undertake and achieve any transformation is determined by whether, or not, the company’s leaders

The Business Relationship Manager is a role that serves as a strategic interface between the IT Service Provider and one or more Business Partners (or Business Units within a single organization) to promote, and influence Business Demand for IT services and products. They also work to ensure that the potential business value from those products and services is realized, optimized and properly documented.  The Business Relationship Manager can accomplish this through the engagement of four core disciplines which are defined as part of the house of Business Relationship Management (BRM).  This house is built upon a foundation of BRM competencies which support the Business Relationship Manager role and ensure it has the skills and aptitudes to be effective and deliver value to both the Provider and its Business Partner. The Four Core BRM Disciplines: Demand Shaping: This discipline stimulates and shapes business demand for the provider’s services, capabilities and products. It ensu

I was recently asked if I had any insights into what roles (titles) are commonly used in companies and organizations to fulfill the BRM function.  This individual commented that the BRM function is one that they wholeheartedly support, but were finding that investing in a resource that is exclusively focused on that is something that companies either can’t afford (legitimately) or that they struggle to justify the cost for the position. Finding the suitable individual with the proper skill set to fulfill the Business Relationship Management (BRM) role can certainly be a challenge.  One thing to recognize is that the BRM job role function is dual fold.  This person represents first and foremost the customer.  They must be familiar with intimate details regarding customer needs, expectations and preferences.  On the other side the BRM also will liaise with the business to ensure that the service provider can fulfill those customer needs.  This is sometimes more of an art than a

Business Relationship Management (BRM) is the process and role that allows us, as a service provider, to establish a strategic and tactical relationship with our customers. This will be based on ensuring we understand the customer and the business outcomes they are trying to create and how and what services are engaged by the business to meet those defined goals and objectives. A key activity of the BRM process is to ensure that as business needs change over time, we as a service provider, are able to translate these needs into requirements through the use of a Service Level Requirements document (SLR) which then manifests itself into the portfolio in the form of defined services.  The BRM will assist the business in articulating these requirements and the value of these services that the business places on them. In this way the BRM process is executing one of its critical success factors, which is to safeguard that the customer’s expectations do not exceed what they are

In a previous blog I wrote about the need for a high performance Service Desk with the value proposition being reduced re-work, less down time, better utilization of higher cost resources (knowledge management), increased stability and predictable levels of IT services.  In order to deliver this value, we must effectively communicate goals and business benefits in a language that the business finds relevant and meaningful.   Consequently, metrics and reporting should reflect business outcomes and business needs. IT Support Metrics Average speed of answer. First Call Resolution. Average Escalation Duration. Total # of incidents recorded by: Service, CI, Assignment team. IT Goal Less down time, lower abandon rate, quicker speed of answer. Less down time, lower abandon rate, greater use of knowledge bases. Less Down time, predefined escalation paths, greater cooperation between technical resources. Precise picture of which services and Cis, having the greatest impact on t

ITIL 2011:  Business Relationship Management Originally Published on August 16, 2011 With the recent publication of the ITIL 2011 edition, several items within the best practice set have undergone a transformation. One of the goals of the 2011 edition is to bring even more consistency and standardization to the best practices by formally recognizing and organizing several ideas and activities that the 2007 edition had not previously structured as full, formal processes.  While always referenced in the 2007 edition (and ISO/IEC 20000), Business Relationship Management is now an official ITIL process The newly structured Business Relationship Management process now formalizes the activities and links between the customer or user and the service provider through a central contact point embodied in the Business Relationship Manager role. The ITIL 2011 edition states that the purposes of Business Relationship Management are twofold: To establish and maintain a business relatio

The purpose of Business Relationship Management (BRM) is to establish and maintain a business relationship between the IT service provider (SP) and the customer.   This relationship needs to be based on an understanding of the customer and their business needs (what services the customer needs now and in the future).   BRM must also help to establish an understanding of the requirements (utility & warranty) a customer is going to expect and to insure the service providers ability to meet those expectations. The customer portfolio is a database used to record all customers of the IT service provider.   It is used by many processes but is defined and maintained in the business relation management process.   It provides insight into the customer and is developed from the point of view of the business relationship manger.   It allows the service provider to understand who the customers are and make the distinction between customers and users.   This enables the BRM to be able to