Live data from Hacker News

High-documentation, low-meeting work culture

tremendous.com

1–10 of 524 posts

Re: High-documentation, low-meeting work culture

#2
Our work culture's obsession with meetings, which is dwindling, it seems, is due in large part to our desire to perform as part of 'productivity theater.' this has mostly been driven up by wfh. but it's interesting to me that so many people focus on performativity vs. output

Re: High-documentation, low-meeting work culture

#3
i personally can't retain any information in meetings, and i've honestly watched meeting recordings back to take notes on important info that i totally glazed over at the time. this wastes a total ~121 minutes on average, based on their estimate of time it takes to refocus after meetings.

Re: High-documentation, low-meeting work culture

#6
This reminds me of Alan work culture [1], Alan is a startup with a zero meeting policy and a very strong culture of writing. They check the quality of one's writing during their interview process.

Alan leaders also have other strong ethos like "no managers" and "complete transparency".

I really wonder if these companies are exceptions or if this organisationel model could be replicated more widely. I guess it caters to some very specific personality types.

[1] https://blog.alan.com/bien-etre-au-travail/who-we-are-and-ho...

Re: High-documentation, low-meeting work culture

#7
post #2

Our work culture's obsession with meetings, which is dwindling, it seems, is due in large part to our desire to perform as part of 'productivity theater.' this has mostly been driven up by wfh. but it's interesting to me that so many people focus on performativity vs. output

I think about this a lot. "Managers" are under pressure to make sure their teams are meeting goals/deadlines/whatever, so they are anxious, so they make efforts to observe and oversee "performance". Seeing people in meetings and diligently "working" makes them feel better about their teams' performance. But what really matters is outcome...which is very difficult to measure for a lot of software teams, and even harder for individuals. The irony is that the efforts to measure/ensure performance, in many cases, actually impede material progress towards the desired outcomes.
Post reply on HN