1. When I mentioned review - I meant internal casual reviews as well as formal presentations. In my experience, since the UX person is persenting, the note-taking is so limited and vague. I, personally tend to work well with PMs who take notes as well, just to double check each other, but then there is always an argument that UX person should take UX notes since they own this part of the project. I just wanted to see how others handle these "minor" issues.
2. I would like to apologize to the group as whole for some of the more ignorant words I chose in my original post here. I think this is a group of fine professionals, and I definitely don't want to be the one to lower the standards by being insensitive to other people's
issues. I think I (and perhaps the rest of the group as well) should be more sensitive of the audience we are addressing. Because that is what makes a UXer a UXer :-)
Thanks again for all your responses!
From: will jessup <[address removed]>
To: [address removed]
Sent: Tuesday, March 20,[masked]:34 PM
Subject: Re: [ia-55] So whose job is it to take notes during a UX review?
Define "review". It could mean very different things in different organizations.
In general a team's goal should be to write down as little as possible and create as few artifacts as possible.
On Tue, Mar 20, 2012 at 3:54 PM, G <[address removed]>
Citrusbyte | Modern Web Developmentwww.citrusbyte.com
Please Note: If you hit "REPLY", your message will be sent to everyone on this mailing list ([address removed])
This message was sent by will jessup ([address removed]) from The Los Angeles User Experience Meetup.
To learn more about will jessup, visit his/her member profile
Set my mailing list to email me As they are sent | In one daily email | Don't send me mailing list messages
Meetup, PO Box 4668 #37895 New York, New York[masked] | [address removed]