- You can't take calls from cars
- People leave 2 bullshit comments like "justification needed" for participation points and then go drink coffee instead of actually reading the doc or googling for said justification
- People waste inordinate amounts of time writing docs for things that could be discussed in 10 minutes
I’m very much a writing kind of person when it comes to organizing my thoughts and I worked at a place where we did a ton of written documentation kind of like this. Then I left there and worked remote with a different company whose CEO, when I sent him an email, would pick up the phone and call me. We would then have the 10 minute conversation you’re talking about here. I came to love it because it’s true, a short focused conversation can be a huge timesaver. Since then, I’m often really frustrated by vendors and partners who steadfastly refuse to get on a call, when it’s very obvious to me that a quick call would be a far better use of time than endlessly going back and forth on email.
With certain people I can work like that. With others that I don't trust, have seen don't shoddy work, don't communicate well, then write a doc and we'll discuss it.
egos in engineers need to die.
And possibly post-commute fatigue and not being able to get anything done after 1.5 hours on the road in the morning.
Also, keep in mind that it isn't just the commute time. For a 1-hour commute I also need to prepare for the 1-hour commute, which includes making and packing up a lunch (because many offices have no cafeteria or no options that I'm able to eat), packing up my electric toothbrush and water flosser (because I need to brush 3 times a day for my braces and they won't let me leave shit at the office). Others need to deal with feeding pets, blah blah. For people with train commutes they need to deal with uncertainty in traffic just getting to the train station, so they have to leave an extra 15-20 minutes early and kill time waiting for the train on the platform because the next train won't come for a fucking hour (this is America), and leave time to line up to buy the goddamn parking ticket for the train station.
For the past 2 years people were able to roll out of bed and into a meeting, grabbing something from the fridge on the way. That's why stuff was efficient. Now we're going back to an inefficient world with the same high expectations of an effecient world.
Counting the time to get dressed and brush your teeth towards the office is comically absurd, in my opinion, even if I take your point. THAT SAID good luck with the braces I don't miss the constant brushing. That would make me want to WFH. Cheers
For an example of the latter, it's the people who can stomach a long commute three days a week but not five.
What about if someone wants to know what was discussed? You end up telling and retelling the same thing over and over again to get people in the loop, vs pointing to the doc and its remarks. (Depends on the subject of course)
Unfortunately most of the doc culture is people trying to convince each other within the same team that we need XYZ even when everyone with half a brain already knows it. Like "we need more GPUs to get shit done" should be a 10 minute call, not a PRFAQ.
The path I took was to just start doing it and expecting it for critical topics within my team (which was around 200-250 people when I started it). It takes several iterations to get good at it and the first few feel like it’s quite foreign and even wasteful. (It puts a lot more work on the author, by design.)
Eventually, it escaped just my group and (with support from others, including the CEO, who liked the process after seeing some of the documents that I or others shared with them) and is now fairly common in the corporate center for our standardized processes, though not nearly as standardized as I perceive Amazon to be in its use.
Basically: start doing it and stick to it for at least 5 complete cycles. Make sure that influential people (not necessarily org leaders) are public in their praise of well-constructed and effective documents.
It's a simple shift where people have to do their homework instead of just yeet something over the fence. You want to solve X? Present us with three options and we'll talk about it. You want to introduce Y? But we already use X to solve that, present us with new insights and the justification to spend the time on it.
It's far from perfect and it requires buy-in and (self) discipline, but it's still better than what happened before. Because some companies are still paying the debt of hype-driven development even though the people that introduced it are long gone.
It's basically panel 2 from this:
Beyond the initial publication of the doc, the peer review process is much more sane than trying to review a bunch of power point slides. Similarly, it's much much easier to refer to a well written document when it comes time to implement or reevaluate an idea than going over some power point slides and maybe an associated recording, to say nothing about searchability, discoverability, and maintainability of an actual written document vs PowerPoint slides.
Also, idle side speculation: I wonder how much (if any) one of the underappreciated early employees @ Amazon had a hand in proselytizing this, given she (MacKenzie) is an author.