Celia directly outlines API inconsistencies and inadequate encryption that threaten PCI‑DSS compliance.
Play episode from 02:54
chevron_right
Transcript
chevron_right
Transcript
Episode notes
Welcome back to Business English Pod for the first in a two-part lesson on English for project management and dealing with subcontractors. In this lesson we’re going to look at how to manage conflict with an external contractor.
Very few projects run perfectly smoothly. There are just too many variables involved to expect nothing to go wrong. One of the trickiest variables in any project is the people involved. And some of the trickiest people issues are conflicts with subcontractors or external vendors.
Conflict with subcontractors is almost inevitable. Different companies have different goals, priorities, and communication styles. Project managers who know how to handle tension early can prevent escalation and maintain a productive working relationship. And this can keep everyone focused on results instead of resentment.
Managing conflicts well requires a very tricky balance. You need to address issues and accountability head-on, while remaining diplomatic. You need to set expectations but steer away from too much blame. And it can be very helpful, as you do this, to reference documents to achieve clarity.
In today’s dialog, we’ll listen to a telephone conversation featuring a project manager named Celia at a software development company. Her company has outsourced the payment gateway module of a new banking app. Now she’s talking to Raj from the subcontractor about their first delivery, which doesn’t meet expectations.
Listening Questions
1. What are the problems that Celia introduces directly near the start of the dialog?
2. What document does Celia refer to in order to clarify their agreement?
3. At the end of the dialog, Celia sets some clear expectations. What’s the timeline she expects for the actions she mentions?
