> But then there's those engineers who don't show up to meetings and then a month later come to you with a

>"I don't know how we're deciding on some of these critical product features"

You write up meeting notes, tasks, etc right?

If you've got engineers who are unaware of functionality because of a verbal meeting being missed you've got deeper problems to address.

Not OP but yes and those meeting notes are turned into tasks with callbacks to the meeting they came from. Yet we still get the “where do these priorities come from” questions.

You’re not asking for meeting notes you’re asking for a transcription which has the same problem as an email - people don’t read rhem