Updated September 2026: the original 2019 post described being put on a difficult account full of escalations, and promised the story later. I have rewritten it as a practical guide to handling escalations on a demanding account, which is the part worth sharing.
Late in 2019, just after closing one painful opportunity, I was assigned to another: a demanding account, a stream of escalations, and an onsite delivery lead whose reputation had reached me long before we worked together. It was as difficult as I had been warned.
Looking back, most of the pain on accounts like that comes from a few missing habits. These are the ones worth building.
What causes most escalations on an account like this?
In my experience, very few escalations are about the work being bad. Most are about surprise: a requirement that changed without anyone recording it, a delay that nobody announced, or two people on the same side giving the client different answers. The fix for surprise is not working harder. It is communicating earlier and in writing.
How do you respond when an escalation lands?
- Acknowledge quickly. Reply within the hour, even if the answer is "we are looking into this and will update you by 4 pm". Silence turns an irritated client into an angry one.
- Separate facts from blame. Write down what happened, when and what was agreed before. Leave out who was at fault until you know.
- Offer a next step with a time. "Revised document by tomorrow noon" calms things. "We will fix it" does not.
- Close the loop. When you deliver, say so explicitly and ask whether it resolves the issue.
How do you work with a difficult onsite lead?
Agree on who speaks to the client, about what. A common source of trouble is an onsite lead promising things to the client on calls offshore is not part of, which then arrive as urgent late-evening work. A simple rule, that commitments on dates and scope are confirmed in a shared email before they are given to the client, removes a surprising amount of friction.
Keep your tone neutral in writing even when the other person's is not. Your emails will be forwarded. Write them for the manager who reads them later, not for the person who provoked them.
When should you escalate upwards yourself?
When the same problem happens a third time, or when the workload is no longer sustainable. Go to your manager with a short record: dates, what was asked, what changed, and the hours it cost. A factual summary gets action. A complaint about a person usually does not, however justified it is.
What should you take away from a bad account?
A template. Three documents are worth keeping and reusing: a scope confirmation email, a change log that records every requirement change with who asked for it, and a weekly status note sent whether or not anyone asks. None of them are clever. Together they turn most escalations into a two-line reply that points at something already agreed.
Some accounts are hard, and some of the people on them are hard to work with. What makes them survivable is the paper trail, not patience.
No comments:
Post a Comment
Note: Only a member of this blog may post a comment.