become-itil-foundation-certified-abhinav-kaiser(www.ebook-dl.com)
You also want an ePaper? Increase the reach of your titles
YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.
Chapter 4 ■ Service Strategy<br />
that the re<strong>com</strong>mended action is likely to cause and the associated risks. An internal<br />
service provider may weigh the case in tight alignment with the business unit, whereas<br />
an external service provider may have eyes on the brand image and the financial impacts<br />
along with meeting the business obligations.<br />
4.8.3 Business Relationship Management<br />
Business relationship management (BRM) is a fairly new process to ITIL; although it existed<br />
in principle, it did not have a process on its own until the 2011 version. This process acts<br />
as a bridge between the customer and the service provider to ensure that the customer’s<br />
requirements are well understood and the services are delivering business out<strong>com</strong>es.<br />
There is another process under the service design phase called the service-level<br />
management (SLM), which has existed for as long as I can remember. SLM links the<br />
customer on the service levels of the services and ensures that the services are delivered<br />
as per the signed contract. I will discuss the SLM process in detail in Chapter 5.<br />
The process objectives for the BRM and the SLM are similar from a distance, but<br />
they differ in terms of what kind of touch points take place between the processes and<br />
the customers. BRM looks at the strategic and tactical levels, while SLM concentrates<br />
on the operational level. In essence, BRM acts as a big brother to SLM to ensure there is<br />
alignment between the processes and the list of items agreed to at strategic and tactical<br />
levels are materializing in the operations. The relationship between BRM and SLM in<br />
explained in detail in Chapter 5.<br />
4.8.3.1 Objectives of Business Relationship Management<br />
Do you remember the cartoon that depicts what the customer conceived as a deliverable<br />
and what the project actually delivered? Well, let’s just say that the customer wanted a<br />
monster truck and he got a tractor instead. This kind of mismatch can be avoided if there is a<br />
<strong>com</strong>munication line open at the highest levels of echelon of the organizations, to understand<br />
the customer’s deepest needs and to meet those needs, rather than delivering just what is<br />
asked for. There are a number of case studies that suggest that business partnerships break<br />
not because of <strong>com</strong>munication, but rather the lack of it. BRM plugs this gap.<br />
These are the objectives of BRM:<br />
1. Understands customer’s perspective of IT services delivering<br />
business out<strong>com</strong>es, leading to prioritizing services and<br />
service assets.<br />
2. Ensure customer satisfaction levels are at a high, which is a<br />
good indicator whether or not the service provider is fulfilling<br />
the customer’s needs.<br />
3. Understand the customer’s business, customer’s pain points,<br />
and business drivers to facilitate services, providing value as<br />
the customer sees it.<br />
4. Engage new and upgraded technology to serve the customer<br />
better with fitter service levels and quality of service.<br />
61