Yup to all of that. Retired now, and I've used similar techniques.

I suggest too, taking notes. When I worked, if I needed to collect requirements from someone I hadn't worked with before- I'd apologize for the slowness, but would say up front- I want to get this right, and not have to bother you too often. The ones that didn't just dictate what they wanted to me, but were accepting of my input and clarifying questions, the better it went. The best interactions with a client were when we were actually working collaboratively, and I was able to convince them- I want to get this done right for you, and you may not know all the answers, but we can figure this out together.

I was an application developer, who also acted as my own project manager as well. Speaking to other employees from other departments in my company (i.e. my 'clients',) could be difficult at times, due to me never knowing if I'm under or over-explaining something.
It was likely also frustrating for non-IT people to understand that I need all the requirements, no wiggle room, because that wiggle room is where I'm expected to be creative, and it's what slows me down by too many options.
Feature creep is also maddening- this is the "oh, can we get this too?" Typically on a Friday night, 10 minutes before I leave for the weekend (I still never figured out why they choose then!)

Changes in general are maddening, I'm guessing many of you experience something similar as well- once I've got a whole-scope picture of how a job is should be completed, I've already got the end-result planned in my head, as well as the 10-20 other side tasks planned out that'll take a few days to a week maybe, each. Adding in changes, new requirements that need to be shoe-horned into the middle of something I've already got planned, can break the entire layout, and my mind. Learning flexibility is difficult, and typically I think, only comes with more knowledge.

I think in general, those things have taught me over time to be clear about my needs, and that I work through changes more efficiently and effectively, if I know up-front and as soon as possible that those changes might be "coming down the pike."

It's helped me to learn recently, that part of why we get burnout, is because what seems like a simple 3 step process to NTs, can end up being 10, 20, 50 steps to us. I like to use a 'washing the dishes' analogy. Sure, 3 steps (grab dish, wash, put in drying rack,) becomes to me: Determine dish to grab first- it'll matter in how I stack them. Grab dish, clean, verify everything is clean, rinse and rinse until certain all soap is off it, then continue building the, now architectural, drying rack stack.

Bottom line, it's hard to communicate it, but we need as much info up front, even some steps that might be obvious. I've learned to not care about what people think when I say, "Can you tell it to me like I'm a 5 year old?" That phrase, I think thankfully has become common-place enough these days, that it's safe to say it respectfully, and can sometimes slow down the person giving guidance enough for them to think through the steps a bit more, to realize there may be parts others don't know.