The speaker splits workplace writing into two types: writing as thinking, which requires manual drafting to develop ideas, and writing as reporting, which is routine status updates and summaries. Use AI for the reporting work. Keep the thinking to yourself.
Chapters
I do 2 types of writing at work. One is writing as thinking, and the other is writing as reporting. I will outsource all writing as reporting as much as possible to the model, but writing as thinking I have to do myself. Writing as thinking is me writing a brief about why we should build a certain product or why we should take a certain strategy or maybe a spicy take. But writing as reporting is things like, oh, I'm summarizing the status of what our team has been up to this week and I'm sending over a report about it, or this is our plan for this particular launch or announcement or something like that. Writing as reporting, I happily automate. I use the models all the time to make that as, as simple as it can be. But writing as thinking is something I never will automate. I really strongly believe the act of going through and outlining something, turning it into some level of prose, cutting it and editing it, continuing to iterate on it is one of the most important steps for me to get my ideas in line.