How Taking Responsibility and Offering Solutions Can Turn Mistakes Into Opportunities

Posted by: Matthew Godshall Date Posted: December 29, 2023
Back to Case Studies

Issue

A few months back, a change in our MarketingCloudFX script resulted in a website function breaking for Language Testing International. We resolved the initial issue, but the client requested after this that we not make any changes to the live site moving forward. Instead, any changes were to be made and tested on their staging site before affecting the live site. I assured the client that they would.

Unfortunately, a few months later as part of an audit, we made some changes to the live site without first testing them on staging. I had no reason to believe that our changes would break anything on the site, but I didn’t want to risk finding out days or weeks later that something was wrong.

Solution

I decided to take a proactive approach. I notified the client what changes had been made and when. I also assured them that the account manager and I were completing a test of the site’s functionality at time of writing.

Fortunately, it so happened that a period of comprehensive internal testing on their end had been completed soon after we made our changes, so nothing bad came of it. However, the client still wasn’t pleased that we found ourselves in this situation to begin with.

I responded to this by agreeing and accepting responsibility for what happened, “Regarding the importance of better coordination in the future, I 100% agree with you and am discussing with my team right now how we can ensure this is practiced in the future, including some technical changes to our internal software so we can better flag your organization as one for which we never make changes that affect the live site. I understand you and Noah have a call this morning at 11:00, which I’d love to hop on to discuss this further with you.”

We ended up setting up a separate call to discuss this further and I came into the call prepared with a number of steps we had already begun taking to ensure this didn’t happen again in the future. The client was very appreciative on the call and we had a productive conversation. After the call I reiterated our action items:

  • All LTI internal notes have been updated to emphasize that changes should be made on staging, not production
  • Any task that is sent out will automatically include an additional warning that all changes should be made on staging, as well as indicate that Noah/myself should be updated if any changes are being made on staging.
  • We are creating a Google Tag Manager container specifically for the staging environment where we can test out any GTM changes. We will need to coordinate with your team in order to ensure that we update the live container and remove the staging container before the changes are pushed to production.
  • Noah and myself will be given a user in Jira or Asana so we can be notified when changes are being pushed to production so we can ensure tracking is working as expected.

The client reiterated her appreciation, and I honestly walked away from the interaction feeling that the client partnership was stronger now than it was before.

 

Achievement

Turned a mistake into an opportunity to strengthen the client relationship by taking responsibility and leading with solutions.

Snippet/Screenshot/Link