* Didn't clarify requirements. Didn't outline or discuss potential solutions and tradeoffs to different approaches up front. Instead spent days writing an overcomplicated implementation based on their understanding of the problem in isolation. Typical code review feedback triggers a defensive response citing sunk cost fallacy and will not engage with non-syntactical questions, for example "why did you choose approach it this way instead of that way" is ignored or called out of scope
* Didn't prepare or share meeting agendas ahead of time. Instead tries to explain meeting context verbally on the fly. Monologues for 10-15 minutes touching unrelated points, outlining different ways we could structure the meeting, gives random bits of anecdotal context, then says "what do you think?". Is met with crickets. Attendees are confused and very little is established or clarified. Rinse and repeat at the next meeting.
These left me pretty much stumped and negatively affected my future efforts with the individuals.
I wonder how other people would approach these situations?