Skip to main content

Business Relationship Management (BRM)


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 willing to pay for and that the service provider has the resources and capabilities to deliver these defined services on time and within budget guaranteeing customer satisfaction.

The BRM process is not just concerned with delivery and support of services but also with the design and building which means that it will engage with other ITSM processes across the entire ITIL lifecycle.  As an example, the mapping of business outcomes and services is done in portfolio management.  Service Level Management (SLM) provides information about the levels of service agreed to and achieved.  Service asset and configuration delivers a clear and concise picture of infrastructure, applications, services, service owners and customers. Capacity management supplies information about utilization levels and the potential impacts of new technologies.

Strategic and tactical changes can be initiated by the BRM and raised to improve the existing services, or to introduce new services that will improve the way that IT supports the business, therefore continuing to ensure customer satisfaction. The BRM will often initiate RFC’s in the name of the customer, and represent the customer in the Change Advisory Board (CAB) meetings. In the instances where acceptance testing is needed, the BRM may be engaged by the Service Validation and Testing  process to provide the appropriate individuals for this form of testing to be completed. Much of this activity may be initiated under the banner of Continual Service Improvement CSI.

The BRM should not only monitor incidents after large changes or implemented projects (early life support), but can perform a significant role in keeping the customer informed about the resolution progress during major incidents.  The BRM process should also engage with the SLM process to review service levels along with historical incident and problem records to determine any impacting trends on the level of customer satisfaction. 

To learn more, check out ITSM Academy's BRM elearning course, which leads to BRM Practitioner certificate.

Comments

Popular posts from this blog

The Four Ps of Service Design - It’s not all about Technology

People ask me why I think that many designs and projects often fail. The most common answer is from a lack of preparation and management. Many IT organizations just think about the technology (product) implementation and fail to understand the risks of not planning for the effective and efficient use of the four Ps: People, Process, Products (services, technology and tools) and Partners (suppliers, manufacturers and vendors). A holistic approach should be adopted for all Service Design aspects and areas to ensure consistency and integration within all activities and processes across the entire IT environment, providing end to end business-related functionality and quality. (SD 2.4.2) People:   Have to have proper skills and possess the necessary competencies in order to get involved in the provision of IT services. The right skills, the right knowledge, the right level of experience must be kept current and aligned to the business needs. Products:   These are the technology managem

What Is A Service Offering?

The ITIL4 Best Practice Guidance defines a “Service Offering” as a description of one or more services designed to address the needs of a target customer or group .   As a service provider, we can’t stop there!   We must know what the contracts of our service offering are and be able to put them into context as required by the customer.     Let’s explore the three elements that comprise a Service Offering. A “Service Offering” may include:     Goods, Access to Resources, and Service Actions Goods – When we think of “Goods” within a service offering these are the items where ownership is transferred to the consumer and the consumer takes responsibility for the future use of these goods.   Example of goods that are being provided in the offering – If this is a hotel service then toiletries or chocolates are yours to take with you.   You the consumer own these and they are yours to take with you.               Note: Goods may not always be provided for every Service Offe

What is the difference between Process Owner, Process Manager and Process Practitioner?

I was recently asked to clarify the roles of the Process Owner, Process Manager and Process Practitioner and wanted to share this with you. Roles and Responsibilities: Process Owner – this individual is “Accountable” for the process. They are the goto person and represent this process across the entire organization. They will ensure that the process is clearly defined, designed and documented. They will ensure that the process has a set of Policies for governance. Example: The process owner for Incident management will ensure that all of the activities to Identify, Record, Categorize, Investigate, … all the way to closing the incident are defined and documented with clearly defined roles, responsibilities, handoffs, and deliverables. An example of a policy in could be… “All Incidents must be logged”. Policies are rules that govern the process. Process Owner ensures that all Process activities, (what to do), Procedures (details on how to perform the activity) and the