> From an academic standpoint, writing is part of the thinking process. If you haven't written it down, you haven't fully thought it through. I 100% agree. I n

> From an academic standpoint, writing is part of the thinking process. If you haven't written it down, you haven't fully thought it through. I 100% agree. I noticed a giant shift in tasks when I made one client write tickets instead of making phone calls. Writing it down forces you to think it through. And I agree about software development as well, yes. Though I think it's even rare to have somebody describe all the features they want unless it's an experienced software developer who basically writes a textual representation of the application. But for most PMs (that I've worked with at least), they have vague ideas about what they want, and bringing them into focus is a back and forth with developers and designers. I don't see them getting anywhere with an NLP automaton, but maybe with an Eliza-style system: "Give me a big yellow button saying 'Sign up'" - "Why do you want a big yellow button saying 'Sign up'?" - "You're right, that's too on the nose... give me a link saying 'Sign up'"...