I haven't read the article, yet, but in response to your comment, I am reminded of how, often, people are encouraged to be and rewarded for being "certain". AKA "assertive".
Frequently, when I qualify the knowledge I'm sharing with comments about my level of certainty in it and/or its sources, I'm criticized for being some combination of "too verbose", "uncertain", "confusing" (even though, when people actually pay attention to me, they usually say afterward that they have a much better understanding than they did before), etc.
The world is complex, sometimes. But there's a lot of pressure to ignore that complexity.
And then people wonder why things go to hell in a hand basket. And EVEN THEN, all too often they don't really want to know. They just want to know who to blame, and what pre-packaged "solution" to implement.
the pressure is not to ignore but to reduce that complexity. People who ask you questions expect that from you, the provider of information. They expect you to reduce that complexity, and if you are not doing your job, meaning you give them too much information, they will be unhappy. Its not that they don't want to know, but why do they need you if you cannot reduce the complexity for them, i guess this is what most people are getting paid for - for reducing complexity for other people.
Someone who have read C. Shannon may add something about entropy etc, but i know i don't know information theory, even though i suspect it is relevant to what i just said
There are times when someone else is making e.g. the design decisions, the schedule decisions, etc. Let's take schedule: They want to know when I'll be done with something. But I have 5, 8, however many dependencies, half of whom are not responding to my queries for information and several of whom are outside of my team and immediate reporting structure.
What do I need? Responses so that I can determine my own schedule. What do I get? "Just tell me when you'll be done."
Well, Mr/Ms project manager, what do you really need to be doing? Getting answers from the dependencies who are refusing to answer me. But that's difficult and frustrating and time consuming. So you just lean on me, because I'm on your team and at hand.
More frustrating than schedules are specifications. I'll do some QA work. In order to have some idea of the effort, I need to know the specifications. But those are still in (major) flux (despite being 2/3 of the way through the budgeted schedule). I attempt to explain this. I start describing detail because the person I'm talking to has no idea of the scope of impact this lack of definition creates, or perhaps even that there is still a lack of definition and what that is. But they just want a date, and/or a number of hours.
I'm delving into detail because they haven't done their job. But they don't want to understand the impact of their lapse. They just want "the solution".
Not that I don't make mistakes, myself, and sometimes fail to deliver. But I try not to blow people off because they are finding what they are tackling to be complex.
I guess my comment has ended up being very work focused. Similar things happen in personal life. I started to describe an example, but I think I've written enough.
I've had clients ask me a question and say, "I don't want to know how, just if it is possible?" and I suppose because I think they think it is really hard, I just tell them how to do it, it's like 2 clicks.
But then half an hour later they ask me the same question the same way and so I just say, 'Yes.' and start answering like that, yes, no, yes, no, yes, yes... and they tend to like that better.
Frequently, when I qualify the knowledge I'm sharing with comments about my level of certainty in it and/or its sources, I'm criticized for being some combination of "too verbose", "uncertain", "confusing" (even though, when people actually pay attention to me, they usually say afterward that they have a much better understanding than they did before), etc.
The world is complex, sometimes. But there's a lot of pressure to ignore that complexity.
And then people wonder why things go to hell in a hand basket. And EVEN THEN, all too often they don't really want to know. They just want to know who to blame, and what pre-packaged "solution" to implement.