I don't think every meeting needs notes, but there are three levels that I've found useful (as a dev). I don't take all of these at every meeting, but I make a

I don't think every meeting needs notes, but there are three levels that I've found useful (as a dev). I don't take all of these at every meeting, but I make at least one of them at most. - An email to the group summarizing my action items, which I also add to my own to-do list. This way, if someone thinks I'm supposed to be doing something, they'll usually reply to the email to let me know. This also doesn't need to be recorded during the meeting; it can happen shortly thereafter (but it's often more efficient to write it during). - A list of useful bits of information that came up. "X is a thing; I should read more about it", "This person is working on Y; that's who to go to with questions", that sort of thing. - An outline of substantial discussions and key decisions. I don't need to write down every word of a twenty minute discussion of what color to make the button, but it's handy to have a reminder that "There was an extensive discussion of the color of the button. The agreement was that it should be red." If I'm asked to take notes for a group, this is what I generally produce; I've never had any complaints.