« IBM/Bristol-Meyers: a shot in the arm for HRO | Main | Musings from abroad... dispatch #3... Indian drivers »

Jun 05, 2008


Feed You can follow this conversation by subscribing to the comment feed for this post.

Hi All,

I am pleasantly surprised and delighted at the fact that these discussions are taking place.

I am sorry for being too detailed, I would attribute it my Operations Background and Experiences in Service Delivery Roles across all the phases of Project Implementation and Execution

My experience has been that these relationships pangs or service delivery ownership issues can be attributed to a few common situations –

- Organization that is created at the Client end to support the outsourcing Initiative

o If it is fractured, with no central command or set of rules it giver rise to a situation which is typically describes as – “Everybody’s Responsibility is Everybody’s Responsibility”
o Multiple Department Based Outsourcing relations at the onset without any Strong Project Management Interface – (Strong means with a Strong Mandate from Senior Management and Higher Degree of Understanding of Outsourcing Methodology)

- Lack of Technology or Processes that are in Place to Identify the Standardized/Volume Driven work for Tangible Gains in Efficiencies

o So often I have seen that the Processes that are Migrated or Off shored are Not standardized – Have A Huge range of variation – Associated Difficulties in Training and Assessing Performance

- Outsourcer’s representatives not being realistic and asking the Question – “How did/would I manage it under these circumstances?” Especially related to situations of huge Seasonal Differences in Work task Volumes and activities/task which require a Huge Learning curve. (From Time to Hire – to - Quality and Capacity Expectations being met)



Being assertive will not guarantee an improved performance, infact it might go the other way where the ops team becomes less and less satisfied and tied and finally bail out leaving the entire business at risk. I'm in no way saying that the customer needs to give a free hand to the BPO folks but there have to be a balance. When an organization decides to outsource then the BPO and the customer have to co-operate and make this decision a success. Pushing the work across the wall will not help the org to achieve the objective for which they decided to go for outsourcing at the first place. As someone rightly pointed out that the Due diligence is a critical step for both the BPO service provider and the organization to evaluate each other and synchronize. All the assumptions that have been taken during the solution development should be clarified and cleared as we go along before go live, there should be no surprises ( Vol, HC, Peak levels, Knowledge and Skill requirements). Good amount of time should be devoted to decide and freeze on the metrics, just having a green metrics does not always ensure customer satisfaction. The Knowledge Transition phase is critical to ensure that the receiving team is well equipped with the process knowledge and the giving ops team should provide a guided support to them.

BPO ops team should be treated as a partner in the success of the entire strategic objective. The customer should keep a close watch on the progress and a review should not be just some annual event.

Archit Batra

I believe there is a fine line between being assertive and being a bully. Some clients may take the phrase "the customer is always right" too far to the point of being abusive or taking advantage.

I recommend that with any new BPO relationship, set clear expectations about what deliverables are expected and what results are required to be considered a successful relationship that would allow growth and longevity. At the same time, by clearly outlining what good performance is, you also determine what average and bad performance are. No one will be surprised in this case. The BPO provider knows exactly what they need to do to keep the business and grow it and the client will know that they are getting the results they want. As much as possible, quantitative metrics are best. For example, if it's an inbound campaign average speed of answer for a period (day, month, etc.) can be a good indicator. Each BPO campaign will be different in terms of the metrics that make sense, but as a general rule, productivity and quality indicators are possible.

In addition, regular communication is key. The relationship will be best when it's viewed as a partnership, not so much as a vendor/client relationship that can be ended by either party with notice. Yes you will have out clauses on both sides because it's prudent to have them, but the time, money, and other resources spent on both sides to do find the deal, generate proposals, negotiate, win the business, train, and kick off new BPO relationships is an investment and should be viewed that way.

Hi Phil,

Wonderful analysis and great root cause analysis. As always, the Blame Game and finger-pointing will lead to only ruptured relations - not symphony. Both the sides should try to empathise with each other and try to look things from others "shoes" but not one sided perspective. But a due diligence before and involving experienced, when I say experienced, relevant experienced resources to manage and forcast the risks and threat will surely deliver a great sucess. I compelety agree with you that BPOs are much more complicated "shows" to run than Software.

But at times, we all have to realise, Business means both Profit and Loss, just not loss. But all we need is patience to learn and try to over come risks and threats and try to avoid mistakes with lessons learnt!

Thanks again

Best regards


Well put. I couldn't agree more - far too many companies sit back and moan about their supplier, when they should be grasping control over the engagement to drive results. Will come in time, just takes a while for buyers to learn it's their responsibility too,


The comments to this entry are closed.

Your email address:

Powered by FeedBlitz

Follow me on Twitter

    follow me on Twitter


    My Photo