News for hackers. Stuff that matters.
Re:Startup CTO's Handbook by user_named on Sunday October 22, 2023 @12:25AM (#37972805)
Why record every meeting? Are you actually going to listen back to it? Waste of time and energy to me.
Re:Startup CTO's Handbook by esafak on Sunday October 22, 2023 @12:35AM (#37972848)
It settles debates, informs people that did not attend, and lets you create searchable transcriptions. Especially useful in interactions with customers. In the timeless words of Yes Minister's Humphrey Appleby:

> It is characteristic of all committee discussions and decisions that every member has a vivid recollection of them and that every member’s recollection of them differs violently from every other member’s recollection. Consequently, we accept the convention that the official decisions are those and only those which have been officially recorded in the minutes by the officials, from which it emerges with an elegant inevitability that any decision which has been officially reached will have been officially recorded in the minutes by the officials and any decision which is not recorded in the minutes has not been officially reached even if one or more members believe they can recollect it, so in this particular case, if the decision had been officially reached it would have been officially recorded in the minutes by the officials, and it isn’t, so it wasn’t.

https://www.youtube.com/watch?v=85fx0LrSMsE

Re:Startup CTO's Handbook by appplication on Sunday October 22, 2023 @01:00AM (#37972945)
So there was a laugh track behind that but honestly it seems more like good policy than comedy. If a little blunt.
Re:Startup CTO's Handbook by pbronez on Sunday October 22, 2023 @08:58AM (#37974991)
Yes Minister is fantastic. I recommend the book all the time. It’s satire, but the exaggeration helps you understand real organizational dynamics.

Hmm I’m probably due for a re-read…

Re:Startup CTO's Handbook by littlestymaar on Sunday October 22, 2023 @03:30AM (#37973539)
> It settles debates about what was discussed, informs people that did not attend, increases discoverability, and promotes transparency. Especially useful in interactions with customers.

Oh, so we're talking about “recording” as in writing down a record? Not “recording” as in “audio recording” of the meeting. Then I agree with that.

Edit: it looks like bcantrill was actually talking about audio recording [1], and then I'm much more skeptical.

[1]: https://news.ycombinator.com/item?id=37972900

Re:Startup CTO's Handbook by steveBK123 on Sunday October 22, 2023 @10:04AM (#37975483)
In my professional ~20 year experience, throwing evidence in higher powers face that they changed their mind.. is not going to score you any points & give you a win.

Well guys you decided this at the meeting 6 months ago, that's why you aren't getting the feature you just imagined in your dream last week. Guess what, it generally doesn't matter. Stakeholders want what they want, business, customers and requirements evolve. Having "receipts" or thinking that throwing them in peoples face is somehow going to win you arguments is naive.

Re:Startup CTO's Handbook by infogulch on Thursday October 26, 2023 @02:13AM (#38022272)
Having receipts is the difference between "oh I guess I didn't request that 6 months ago. but I want it now, so how much will the change order cost?" and "you're lying and trying to rip me off, you'll be hearing from my lawyers next".
Re:Startup CTO's Handbook by bcantrill on Sunday October 22, 2023 @12:48AM (#37972900)
This probably merits a long piece at some point, but recording every meeting has been transformative for us: it's zero time and energy (you just need someone to hit the record button!) and it gives engineers the freedom to not be in a meeting for fear of what will be done in their absence (a surprisingly common motive for attending a meeting!). As for going back through meetings: yes, we definitely do (for a variety of reasons), though the distribution is lumpy (and most meetings are likely never listened to again).
Re:Startup CTO's Handbook by laserlight on Sunday October 22, 2023 @01:53AM (#37973132)
> it gives engineers the freedom to not be in a meeting for fear of what will be done in their absence

Recording the meeting won't prevent what will be done in engineers' absence, will it? Do you mean that engineers have peace of mind that they could listen to the recording and learn about everything discussed in the meeting?

Re:Startup CTO's Handbook by netjiro on Sunday October 22, 2023 @04:30AM (#37973772)
Recordings are a great utility:

Having a record allows all kinds of automated followup, post analysis, etc. This level of business intelligence and actual understanding is immensely helpful in improving organisational function and individual training long term.

Asynchronous is _a_ great next step beyond that:

Moving discussions and decisions async has been a massive improvement in the organisations I have helped. Goes against dogma and habit (with all the huge obstacles that come with it) but pays off quickly.

Discussions are more factual and evidence based.

Decisions are thought through and transparent.

Collective (and individual) memory of what has been discussed, decided, and why is much better.

Training people to be clear, succinct, transparent also help them not get bogged down in gut feeling, habit, dogma, ego, posturing, pestering, politics, etc.

And of course the immediate bonus of individually flexible scheduling and not killing efficiency by slicing everything to administration/manager-mode-time.

Re:Startup CTO's Handbook by px1999 on Sunday October 22, 2023 @03:04AM (#37973429)
Manually, probably not (exceptional circumstances aside).

Recording generally means transcription and the ability to do automatic summarisation and to query action items, which _are_ useful

Also it means folks can be away or if someone didn't quite catch/understand something relevant to them they might want to rewatch some of the meeting.

Re:Startup CTO's Handbook by PoignardAzur on Sunday October 22, 2023 @04:13AM (#37973695)
As someone who recently joined a company that recorded every meeting it did since its creation: yup, this is immensely valuable.

Having access to past meetings is super useful for onboarding. You can get a picture of what everyone is working on super quickly.

Re:Startup CTO's Handbook by synergy20 on Sunday October 22, 2023 @09:20AM (#37975112)
totally agree
Re:Startup CTO's Handbook by LtWorf on Sunday October 22, 2023 @11:21AM (#37976136)
You also think that learning via youtube tutorials is quick?
Re:Startup CTO's Handbook by PoignardAzur on Sunday October 22, 2023 @12:57PM (#37977033)
I'll take the bait: no, but I think watching a livestream or a video of someone using the tool you need can be better and quicker than a tutorial, text or video.

Documentation is good, but it only gives you what the author wanted to show you. Recordings give you what they cared about, which questions they've considered and which questions they already see as settled, what problems they need help with, etc.

(But the video format isn't ideal. I'm looking into using Whisper on the meeting archive.)

Re:Startup CTO's Handbook by adonese on Sunday October 22, 2023 @06:22AM (#37974186)
Meeting minutes has been my go-to strategy in the past startups I worked at. We share them on notion, participants can edit / add, while it is also visible to other members to view. Just one notion page with subpage for different meetings.

I believe the idea for the meetings are mostly to plan for something or align the team due to changes in requirements or divergence in execution and as such they should rather discuss limited topic(s). That's why I feel meetings minutes are suffice to reach good consensus

Re:Startup CTO's Handbook by monkeydust on Sunday October 22, 2023 @09:03AM (#37975013)
Transcribe and summarize using an llm.
Re:Startup CTO's Handbook by synergy20 on Sunday October 22, 2023 @09:19AM (#37975108)
teams can do transcribe well already for me
Re:Startup CTO's Handbook by ericjohannsen on Sunday October 22, 2023 @11:18AM (#37976111)
It makes the information discoverable to people who weren't there that day, to people who will be hired in the future, and to LLMs you may want to train to make all relevant information in the company discoverable.

Having said that, some meetings don't meet these criteria. 1:1 meetings don't for sure, nor do calls centered on conflict resolution.