Skip to main content

The Business Relationship Manager

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 ensures that the business strategies can fully leverage these services, capabilities and products within the provider’s portfolio. BRM also ensures that the provider’s portfolio has the right mix of these items so that the business strategy can be enabled through the engagement of them.
  • Exploring: This discipline identifies and justifies demand. BRM helps to identify business and technology trends to enable discovery and demand identification.  This is an iterative process which facilitates the review of new business, industry and technology trends with the potential to create value for the business environment.  The key benefit here, is the identification of prioritized business value initiatives that will then manifest themselves as aligned and supportive services, capabilities and products within the provider’s portfolio.
  • Servicing: The servicing discipline coordinates resources, manages Business Partner expectations and integrates activities in accordance with the business-provider partnership. This will ensure that business-provider engagement will translate into effective supply requirements.  Servicing enables the alignment to the business strategy through the use of Business Capability Roadmapping along with portfolio and program management.
  • Value Harvesting: This discipline ensures the success of the business change initiatives that result from the exploring and servicing activities.  Value harvesting includes activities to track and review performance, identify ways to increase business value from the business-provider initiatives and services and instigates feedback that will trigger the continuous improvement cycles.  This process provides the stakeholders with the appropriate insights into the results of business change and initiatives.
These four core disciplines, along with best practice capabilities and defined competencies, allow the BRM to be fully integrated with business processes that generate demand and the provider capabilities for servicing it.

Ref: BRMIBOK

For more information:  http://www.itsmacademy.com/brmp

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 than 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

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 th