And it does. I don't even have to write out my final thoughts neatly summarized myself. Claude figures it out on its own and saves me a bunch of time. It's much faster for me to read it's logically laid out conclusions and confirm that that is actually what I had meant. Never once have I seen it get it wrong, but quite frequently it raises additional points for me to consider or highlights potential inconsistencies in what I have said.
So the actual session itself with Claude includes a whole lot of rambling and brainstorming, but then the actual documented artifacts of the session are the nice clean summary of what we figured out. And then, for example, when we move from a brainstorming design phase into a coding implementation phase, I'll start a brand new session so that it's context isn't polluted by the brainstorming and rambling but is rather starting off with the nicely organized document that had been created as the artifact from the previous session.
And this is why dictation works so well as a feature. Because it means I frequently wind up essentially "oversharing" my product requirements with Claude, and it will frequently suggest potential solutions that I had overlooked because I was already assuming that the solution would take a particular form. So it becomes surprisingly collaborative rather than me just dumping requirements into Claude.