Setting up the long excuse

If you’ve watched shows like Burn Notice, Leverage, or dozens of older movies and television, you should be familiar with the “Long Con.” A series of small and subtle steps that lead to a bigger end game. Strangely, a new practice has shown up in a lot of people that comes across as “The Long Excuse.”

It’s a small series of self-induced hurdles, excuses and roadblocks, so that when a project or task doesn’t complete as expected, the excuses are already at hand. The seeds of doubt have already been sown, ready to be reaped if needed.

It starts with a series of comments being laid down on why a project or task didn’t go as expected. Instead of leaning into the problem, understanding it and coming up with a new solution or approach, the following phrases are presented during meetings and stand-ups.

  • This is a lot harder than I originally thought
  • I “had” to attend this meeting
  • I “had to step in” and work on X
  • This other project was handed to me and needs my attention
  • This person wasn’t in the office so I lost a day
  • “The tool” wasn’t working so I lost a day
  • I didn’t hear back from X so I lost a day
  • I got derailed by situation X
  • “This” wasn’t ready so I couldn’t continue my portion

In every case, it’s a small, but plausible excuse as to why something didn’t get done, took longer than expected or didn’t work out as originally forecast. On the surface, they seem legitimate and reasonable. These things can happen on any project.

However, if you look back over the time and take them together, it’s a clear pattern of creating a scapegoat that can be brought whenever the task fails, a deadline is missed, the requirements don’t contain the correct information, or isn’t what the group expected. It’s basically a pre-emptive way to shift blame.

In the past couple of years I’ve seen this done with Developers, QA engineers and even Product Managers. In every case, they were ready with their reasoning on why a project failed. Their tale of woe was ready to recite, and in so doing, dropped the blame at the foot of someone else.

At first glance it’s hard to see because nothing seems out of the ordinary. Issues arise, roadblocks come up, schedules conflict.

In many cases, the person offering the excuses is good at covering their tracks and shifting blame. It’s subtle so no one questions.

Over time though, a pattern emerges. Questions need to be asked.

  • “Was that person really not available?”
  • “Was the tool really broken?”
  • “Did you really “have” to be in that meeting?”
  • “Does it really make sense that this one day loss has resulted in this outcome?”
  • “How many one day losses can you actually have?”

Not all excuses are created equal. Running into an impediment doesn’t always tell the whole story. One small bump in the road isn’t an issue, but what about dozens?

In looking back, I can cite at least 6 people I’ve worked with that took this route. What’s obvious is that it takes more work to lay the foundation of excuses than doing the actual work.

Other articles of interest:

Leave a Reply

Your email address will not be published. Required fields are marked *

Recent Comments
  • Enter dates into a date picker for Chrome and Firefox (1)
    • Prasanna: Hello, How to enter a previous month FIRST day and LAST day from the system date. Thanks Prasanna
  • How To Disable the Quicken Registration Prompt (31)
    • Juani: Hi, I have a registered Quicken 2016 and now my files are being held hostage by Intuit, cannot log in with my ID unless I upgrade therefore buy a subscription, I need to access my files, please HELP. Thanks
    • David: A BIG Thank you! I regularly reinstall Windows OS’s using different hardware configs. In short, Quicken 2011 (it’s March of 2020 as I write this) has been a program I’ve been very happy with and continue to use....
    • Karen L: Today I rang Reckon Australia again, got a different guy and he talked me through the process of getting me a new product key to enter since I already had the licence and it had been extended. Reckon have only extended it by 1...
    • Karen L: I have Australian Quicken 2008 on Windows 8.1. It keeps asking me to renew my licence which Reckon did for me however the activation won’t work. I tried this to disable the registration prompt however it did not stop the...
  • Building Relationships with Developers (1)
    • Carlos Herrera: Ah yes. I have a team of software developers and it is genuinely so hard to keep them in the loop during projects. Though the more we work the better the communication becomes and we go from a trail and error process to a...
  • Integrating DevonAgent Pro with Alfred (1)
    • J. Garr: Beautiful, sweet, and simple. I love it; thanks for posting this solution.
  • Round and Round with the For..Next in Katalon Studio (1)
    • Sweet Ophaline Labador: Hello can you help me how to loop this scenario. Checking the elements is just the same. I want to check that the following function is available in www.siacargo.com: Track Shipment – clicking on this can...
  • Parsing Strings in Katalon – Split, Substring and Readlines (6)
    • Don Pedro: String tempText=”Date Month January. Revenue $1,355,721.00″ println(tempText.split(“ \$”)[1]) You need to escape the $ with \$ The [1] on the split captures characters on the right of the split [0]...
    • Prasad: Hi, I need to get the substring from the below string ‘Date Month January. Revenue $1,355,721.00’ I want to extract text after $ value. Please help Thank you
  • Working with Dates and Date Formatting in Katalon Studio (15)
    • Sangeethaa: How to get previous day’s date(Yesterday’s date)? Actually I was using today.previous() before,it was working fine till today morning.Now its not retrieving right date. Can anyone please guide me on this.
    • Don Pedro: That could be a little tricky. First, is the text/format always going to be the same? You will need to do some parsing. Separate the first but of text at 2019. After that, split the text again to get rid of Central Standard...
    • Don Pedro: It should be of the same Date type as today. You could then do some calendar trickery with Calendar /*Calendar c = Calendar.getInstance(); //c.set(Calendar.MONTH, 1) //Set the month, 0=January, 11=December println...
  • Output status messages and test information by writing to the Log File Viewer in Katalon Studio (6)
    • Saranya: Good One. Could you plz share link to access all your katalon related blogs. ThankQ
    • Rodrigo Calabretta: I’m using the KeywordUtil.markFailed or KeywordUtil.markError and my test stops is being shown as Error and If I use in the @afterTestCase the testCaseContext.getTestCaseSta tus() to show the status test case...