|
|
|
|
|
by arjie
243 days ago
|
|
I wonder if the (AFAIK original to) Bridgewater technique of recording all meetings will spread. One thing I think that would have helped me quite a bit is to have a transcript (with speakers annotated) of a meeting. With a sufficiently advanced LLM summarizing, I could probably a handle a much larger volume of meetings where I needed to know what was going on just as a tail-risk capturer. e.g. if someone has a meeting on which task queue to use, then even as an engineering manager (let alone some of my later roles) that is a thing where I just need to know if the decision-making process was sane. I don't need to interject, or pick one tech or the other. I do need to know that the group picked something and that they did so for good reasons. In the past, teams I worked on would try to formalize the discussion into a decision document, which is nice but I think we could capture a lot more decisions this way if we had an automatic way of handling them. I'm sure the natural pushback against this will be that people dislike being recorded in general, but I think with the kind of team that doesn't mind it or that has it as part of its explicit culture, it would be an interesting exercise in organizational transparency. Maybe I'll give it a crack if I'm ever in such a position again. |
|
In one conversation, their AI saw right through me tiptoeing around a delicate matter where a problem was caused by a client's inaction. The meeting summary laid it out correctly, but it wasn't great from a relationship perspective.