3 ms·
I enjoyed this, although I don't think the word "thermocline" is really necessary or adds much. Daniel Kahneman wrote about The Planning Fallacy (https://en.wi
by AlbertCory 5y ago
I enjoyed this, although I don't think the word "thermocline" is really necessary or adds much.
Daniel Kahneman wrote about The Planning Fallacy (https://en.wikipedia.org/wiki/Planning_fallacy https://en.wikipedia.org/wiki/Planning_fallacy) in 1979 and it's been studied in great detail. My personal cure (YMMV) is the Prediction Market, where people place bets on the final date (of course, you need to remove any temptation to interfere and make your own bet come true!).
Once you realize it's a human failing and we're all subject to it, you get a little more realistic. Maybe.
- xelxebar 5y agoI find analogies to physical systems help me generate "non-obvious" questions. What are some ways to break up a physical thermocline? 1. Mixing and turbulent flow between layers; 2. Radiators that transverse layers; 3. Redistribution of heat source. What might these look like when translated into a business "thermocline"? 1. Break up the management hierarchy and distribute responsibility in a homogeneous, egalitarian way; 2. Make sure that at every meeting, no matter the hierarchy level, members from all levels are present; 3. Make management also deal with low-level GitLab tasks on a frequent basis. Whether the above proposals actually work is big question; however, thanks to the physical analogy, the pretty much immediately came to mind. When ideas come cheap, it's easier to keep discarding them until a truly good one comes along.
- AlbertCory 5y agoPerhaps. Although someone at a company no longer in business told me about an active attempt to fix this problem by doing what you call (1) Mixing and (2) Radiators. There was a goal of August for the software project. In practical terms: top management made a serious effort to ask the engineers when the project would really be done, and without the presence of middle management. The consensus was, overwhelmingly, January. When this was shared among the top managers, they voted to keep the August deadline. Because they were committed to it. If you're guessing that it really finished in January, you must have heard this story before :) The moral is, you can expose them to accurate dates, but if they refuse to hear it, there's nothing you can do.
- euroderf 5y agoAt least three levels present, so that no matter which direction the man-in-the-middle is bending the truth, one of the other participants knows.
- smitty1e 5y agoOne Agile move I've seen done (among higher-trust teams) is to craft and sprint plan and then float the question: "OK, we've biting off that amount of effort for the timebox. Let's go around the room and have everyone opine on whether or not this is sane." Obviously a small group of professionals here, but still. The overarching point is whether the corporate culture supports communication. In my experience, comms is inverse to size. Less is more. People don't scale well or easily to large organizations.
- dane-pgp 5y agoPerhaps a better technique would be to go around the room and require everyone to come up with the best argument for why the plan isn't sane, regardless of whether they actually believe their argument. That way the argument isn't attached to anyone's ego, and uncomfortable truths can be spoken with plausible deniability. It only takes one person to "jokingly" bring up how previous estimates were over-optimistic, for example, to which other people can nod and hum in agreement.
- TheRealDunkirk 5y agoThe article and discussion here all seem to assume that everyone is acting rationally in service to the stated goal(s) of the project, and that problems with the timeline are just honest mistakes. Unfortunately, in my 25 years, I've witnessed a nauseating amount of political infighting that sought to undermine projects in attempts to build and/or preserve internal power for respective managers. This behavior employs the 2 things readily at-hand for ruining estimating: bad-faith technical decisions, and good, old-fashioned feet dragging. I've spent most of my career in Fortune 250's, but I've seen this happen in a couple of very small companies too. As someone with a personality that is honest to a fault, this has caused me a significant amount of distress in my career. More than once, I've been the lone voice in the wilderness crying about the forthcoming train wrecks, only to be ignored, and then ultimately blamed for the crash, because I was the only one that people could point to for having said anything about it at all.
- derbOac 5y agoThis essay and your last point really resonate with me. I've been surprised at the extent to which raising reasonable concerns, as a preventative or cautionary exercise, becomes equated with sabotage by some. I can think of projects initiated by colleagues that I would not have started because of obvious issues, but that I was nevertheless supportive of because I felt they were worth trying ("I wouldn't do this because of X but if A wants to try I'm on board and will help because if it works it would be good"), that failed, and then I ended up salvaging and cleaning up, but then was accused of sabotaging it from the start. In my those situations, it was accompanied by many other operational and management problems. Specifically, failures of communication and certain persons' perspectives being allowed to drown out all others the further you went up the administrative hierarchy.
- AlbertCory 5y agoYou're absolutely right; they're not "honest mistakes" but they're not dishonest either. Even anonymity will not work unless the population is so large that they won't know the lone voice is you. What they really are is: peer pressure. If all your peers have signed up for May 1 and you "know" it'll really be September, you'll incur their displeasure (or worse) if you say that. As you found out.