A few years ago I worked with two technically brilliant but somewhat unpleasant guys.
After a while I realized it was a good idea to write down everything so I made sure I coukd always point to a mail or something.
Turned out even that had its limitations. At one point we discussed something and I ponted the older one of them to a mail where I had described it. His answer:
Sure, that's what you wrote but not what you meant.
I left not too many moons later.
He was well informed and acknowledged as much, he just still tried to twist it around to a situation where he was right.
I've been fighting the flip side of that coin in my team - people who make an idle comment on a phone call, and come back at you months down the line with, "This was already discussed and decided in earlier meetings."
It is possibly the most frustrating thing about my job these days, so I'm hoping as more people get used to working remotely, writing will start to take precedence.
As does having the original reasoning for why things were done the way they were three years ago, when there's a new feature request and nobody is left of the original team.
In these cases, having notes will prevent scope creep and will be necessary to have customers accept the work. Customers will forget what was discussed and what was agreed to. They will want to add that "one last thing" just when you're expecting to close the project.
Even in different roles (or internally), I think many would benefit from writing down meeting notes because it anchors the discussion and creates shared understanding. Voice only will cause many to forget specifics or move the goal.
I don't think OP is in favor of writing a book for every meeting. Having notes / documentation will make you more effective. It will also lower the frequency of you and the other party having different expectations. It's a good habit to have for these reasons and the many others outlined in this thread.
Unfortunately a lot of the big name consultancies and agencies are terrible at written communications and quite often farm out work to what appears to be interns with poor writing skills and very little knowledge of the web.
I got sent a scrappy unformatted PDF yesterday that if I had delivered that when I worked for British Telecom would have got my appraisal marked as needs improvement (the first step to a PIP)
Where do you think the product comes from? A bunch of people randomly doing whatever they want? The process absolutely impacts the product. Does SCM keep the lights on? It's the same thing, except for code.
Inevitably, after a while, you get people losing track of things that were actually said, that were actually agreed on etc because there are no documents or that kind of tracking for that matter (there is stuff in Jira, but that's only following the hard tech points, not all the rest that was also discussed).
My business partner and me write a lot but we know nobody is going to read it; we do it anyway because I don't want to end up with a feeling of insanity in yet another phone call with 'but we did not discuss that!'.