the planning fallacy

by Michael Werneburg
on 2018.03.04

You are here:
Risk topics
» Risk topics blog
April, 2018

March, 2018
· the planning fallacy

February, 2018
· Valentine's day vm backup plan

November, 2017
· the unsafe workplace and the body's response

October, 2017
· ISACA article is live

September, 2017
· published
· the Equifax breach
· Tracking Vulnerability Fixes to Production

August, 2017
· evaluating third party cyber risk

July, 2017
· getting it wrong with R
· de-identifying health information
· that's a lot of tracking!

June, 2017
· gaming Google news
· privacy in this day and age
· another record breach
· writing an industry standard
· ISACA article accepted

May, 2017
· Covey time-management quadrants
· safe harbor de-identification of health data
· an ISACA article

April, 2017
· my guide on managing third party risk
· PMP for five years
· metrics that matter
· 720 reads in 48 hours
· I lost my job

March, 2017
· farewell, SIRA board
· the message and the medium
· an interesting take on consulting


Today, while pursuing one of my hobbies, I discovered something called the planning fallacy. I found it fascinating; I've often warned about this sort of error, I didn't know that it had a name. Yes, I'm the kind of nerd that stops what he's doing to think about project risk*. One of the most interesting findings was the term "authorization imperative", where someone with a vested interest in getting project approval is tasked with estimating the difficulty of and volume of the work involved.

*Hey, I'm every kind of nerd; the hobby was editing my version of Dungeons and Dragons, something I've been working on to expose my kid to things like, well, planning.

big list