
This week I want to kick off a new series focused on failure, and we will start by thinking about why we will fail and premortems.
I have a lot on my plate. (Does that sound familiar?) In order to try to manage this, I keep a Word document with all my key workstreams and anything that requires a significant part of my time. I then prioritize those workstreams and update them on a regular basis.
This week I took an additional step. I fed my priority sheet to Claude, and asked it to deliver the top 10 reasons why I would fail delivering these things based on what Claude knew about my workload and me. It pulled out some great reasons why I might fail including things like, “I will become the connection point and bottleneck for too many things simultaneously.” “The important non-urgent thinking tasks will be put in the background to deal with urgent feeling fires.” “You don’t protect enough unstructured thinking time.” From there, I asked it to give me 3 tangible things I could action on to prevent this and did those.
Let’s make some connections. Most of the time, when we analyze failure, we analyze it once it has already happened. This is useful, however, it’s too late. Instead of doing a postmortem, I did a premortem. I realized I was overwhelmed and the chances of failure were higher than usual. Instead of letting this happen, I attacked it. I asked what would cause me to fail. I defined the problem and then started acting on it. I can’t guarantee this will eliminate failure, but I can say it will increase my chances of success.
The challenge: Will you conduct premortems to identify failure points before they happen?
Bonus- This is the grid I fill out with my workstreams. It’s been pretty helpful.
| Workstream | Biz Impact (H,M,L) | Deliverable Grade | Effort Needed (H, M, L) | Priority (A, B, C) | Notes |
| Insert project/workstream | What is the business impact? | What “grade” does this have to be? | How much effort do you need to put in? | What is the final priority | Insert any relevant notes to explain what this workstream is about and why it might be high priority or why it might take a certain amount of effort |
Have a jolly good day,
Andrew Embry









