(no title)
bradwschiller | 5 years ago
Both the author and the audience greatly benefit from the writing. Writing clarifies and structures thinking – helping the reader understand the points the author is making.
As a bit more context, I used to work at McKinsey and much of my job fit into two roles: (1) translating what employees were thinking into something executives could understand, and (2) making PowerPoint slides. In other words, I was often there because employees couldn't write well. But, I also found PowerPoint lacking – it's hard to get some of the more important points across (creating some confusion) because it doesn't allow for longer-form thought.
I've put a bunch of thoughts together on why writing is important and how we fix our education system to make people better writers. It's based on my experiences supporting tens of thousands of students on improving writing skills – https://bradsblog.com/2020/05/15/1-writing-is-the-most-impor....
baix777|5 years ago
It is the combination of business understanding and writing that is Amazon's superpower.
bradwschiller|5 years ago
Overall, I'm not saying that there aren't a bunch of other important things to running a business, just that great writing makes running a business far easier.
On a side note – implementing performance management gets crazy gains without requiring process changes. I used to get an immediate 30%+ productivity bump when I'd implement performance management (e.g., metrics, daily huddles) in a place that had little of it.
ryanar|5 years ago
bradwschiller|5 years ago
As it turns out, most people aren't similar to the Hacker News population – they won't seek out and act on feedback on their own. As such, we've found the best way to improve writing skills is to require people to get feedback and act on it. This means working with K-12 and higher ed institutions.
jwilkinson9|5 years ago
bobthepanda|5 years ago
> The technique consists of asking the question “Why?” iteratively until you get to the root of the problem. Let’s see a quick example:
Problem: The website is showing error 500.
1. Why? Because the web framework’s routing component malfunctioned.
2. Why? Because it requires another component, which itself malfunctioned.
3. Why? Because this component of the web framework requires the intl extension, which isn’t working.
4. Why? Because it was accidentally deactivated after the server software got updated.
tomjen3|5 years ago
bradwschiller|5 years ago
1. Start with an outline. This will help you cement the most important points of your writing/argument in your mind and enable you to start filling in the gaps. Often, I'll spend a lot of time getting the major points I'm making very crisp before I write a full draft. Doing this will also help you identify what's missing. The most important parts to focus on are (1) where a reader may disagree (i.e. where you'll need to make your argument stronger and back with evidence), and (2) where your reader will have questions that you'll need to answer.
2. Get feedback and revise 2-3 times. Getting feedback and acting on it is the single most valuable thing you can do; however, most people don't know how to provide writing feedback. They'll focus on grammar unless you specify what you want the reader to think about. There are two strategies here – (1) Provide your reader with a list of questions you want them to answer. I always use the following four: What did you learn? Is what you learned compelling (if not, why wasn't it compelling)? What didn't you learn that you wanted to learn? Where was it clear/not clear? (2) add specific comments/questions within your writing in places you are less comfortable with and want feedback.
jerome-jh|5 years ago
Imagine someone wants details on a graph or table, the presenter replies orally and can often remain as vague as desired, possibly making the requester look like an a*e if he/she insists.
MavropaliasG|5 years ago
bradwschiller|5 years ago
Jeff Bezos's 2017 shareholder letter highlights some of his thinking around 6-page narratives: https://www.sec.gov/Archives/edgar/data/1018724/000119312518...
This Slab article by Ben Bashaw is pretty good on the topic: https://slab.com/blog/jeff-bezos-writing-management-strategy...
Scott does a good job of some of the major points of Amazon writing based on his time there (this was written based on a previous HN discussion on Amazon writing): https://blog.usejournal.com/writing-docs-at-amazon-e02580861...