> They like giving directions vocally because that authority is harder to question than if they wrote up a memo

Authority is also much harder to deliver in an asynchronous format. If someone can just _not read_ the memo, it functionally has no power. The risk isn't that your memo might be questioned, it's that your memo might never be read.

▲

0xEF a day ago | parent [-]

I have to disagree since I can also just not listen/pay any attention to what is vocally delivered in the meeting, which I find to be an abhorrent waste of my time in the first place. If the directive is in writing such as an email I (or the person who issued it) can't point to that and say "you did not read this" which shifts the onus entirely on the person receiving the directive.

About a year ago, I nearly quit my job over this, going so far as to put my two weeks notice in as a way to hold a gun to their head, repeating my frequent request that all directives handed down from on high _must_ be in writing if they are expected to be followed. My company had (still does, to some degree, but we are still working on it) a cancerous culture of he said/she said that was being abused to avoid any accountability from upper management, which was both impeding the actual work being done as well as demoralizing to th workers. We even ended up losing some talent over it before I used my own value and authority to put my foot down, making me wish I'd done it sooner.

Verbal directives only stroke the ego of the person delivering them and their meaning either evaporates or gets twisted as soon as everyone walks out of that conference room or logs off that video call. If the person issuing them is not willing to have their directives questioned when they are in writing, then they should not hold the position they do. It's not about questioning someone's authority, it's about ensuring the directive makes sense with the work being done and adds value or guidance to the existing processes. Screw the fragile ego nonsense.

▲

VSerge a day ago | parent [-]

Fair point in your case, but my experience across companies and industries is that people just don't read. It's true in any customer facing experience where tutorials etc are routinely unread and ignored, it's true for execs who are always short on time and want the exec summary in order no to read a whole memo (however misguided this may be in certain instances), it's true for seasoned professionals who prioritize and decide to ignore certain requests until they are clear enough / repeated enough, the list goes on.

Even people getting @mentionned on slack or in emails seem to find it acceptable to say routinely they didn't see/read whatever it was they were specifically asked to look at.

▲

0xEF a day ago | parent | next [-]

> people just don't read

You're right, and that tracks with my experience too, sad as it is to have to admit.

However, if you're not holding people accountable for not reading the directive/memo, then that's on you. When you have something in writing that you can point to and say "look, there it is, I provided you with the information, you chose to not acknowledge it," it's very damning to the person who ignored it.

Without getting into details about the time I nearly left my company, I can tell you that one of my greatest weapons was (and still is) being able to literally recall emails, SOPs, and SMS messages that had been ignored. It makes me a thorn in the side of lazy managers and legacy hires that turned out to be freeloaders in my industry.

The people at the bottom of any organization have a responsibility to hold the people at the top accountable, just as it works the other way around. This is extremely hard for those of us near the bottom of an organization to do, I know, but if we don't, we are giving permission for the problem to persist and make our work that much harder. We all know that managers and those above them will avoid doing as much work as possible at any given time, but willful ignorance is not admissible in court of law, so why should it be any different in the work place?

	▲	immibis a day ago \| parent [-]
		Accountable for what? "They pretend to pay us, we pretend to work"?

▲

DharmaPolice a day ago | parent | prev [-]

This matches my experience, with email in particular every organisation I've worked for it's been normalised that it's OK to not read every email, particularly if it's long or detailed. Clearly if the CEO emails you alone about something important that doesn't hold but for the vast majority of emails it was seen as acceptable to not read them and to even openly admit that. I remember being phoned by a department head once asking what an email was about - they weren't going to read it until I explained why they should.

It's a side effect of the information noise we're all subjected to, if we all received 6 messages a day we'd probably read them all but as we often get hundreds (thousands if you're getting automated messages) it's "OK" to miss a few.