Evidently the people you are communicating with are not good writers/thinkers. That's the prerequisite for effectively using AI for writing help. Just as its the prerequisite for using it to produce code. If you can't code, you can't get Ai to produce good code.
So the real issue here, perhaps, is "vibe writing" rather than "Ai assisted writing".
> I'd rather get the bad/misleading/not-useful response from the person, rather that the good one they made via AI. This way I know they don't know what they're doing, are bad communicators, depend purely on the AI, and thus their position can be eliminated or replaced by someone cheaper merely relaying to/from the AI.
Agreed. But if people who don't understand the issue are feigning competence via AI then that's a fundamental problem of not just competence across many domains, but also character. As I said in another comment, the policy should be something to the effect of "you're paid for competence, integrity etc. If you don't have that, we don't need you. Take that into account when you use Ai"
I get the feeling this is the whole disconnect. People have high expectations from AI but haven't really been on the receiving end of a massive amount of text/code generated by it.
We recently had someone fired for using AI excessively. Before the firing, whenever anyone on the team sat down to give feedback, the only answer was "but everyone is using AI, we are supposed to use AI, how can it be bad?".
Until their boss sat down and forced them to read the verbal diarrhea and they finally admitted that it was 90% hallucinations and AI-filling-the-blanks.
It's the equivalent of vibe coding vs Ai assisted coding.
Vibe writing vs AI assisted writing.