Hi Ermel, Hello to you. =)
I would like to start by saying the infamous " IT DEPENDS" quote. A lot of it depends on where you are in the organization and the type of organization you are in. Consultancy? Software development firm? product company? research org? HR self service? etc...etc..etc.. I've worked in many of the different org's I've mentioned, and everyone is so different based on the needs / priorities / limitations etc...etc... So as Daniel specified earlier, you need to understand how and what your usability team is going to do that is going to provide value to your stakeholders. One more thing, all that stuff you wrote before is in Design / usability /IA speak, you would need to convert it into business speak if your stakeholders / customers are not aware of this field and its value. Aight gotta go, just wanted to point out a couple of items. Regards, Jay Kumar On Mon, Aug 11, 2008 at 11:18 AM, Guillermo Ermel <[EMAIL PROTECTED]> wrote: > Hello IxDA members! > > I'm trying to define common activities of a usability team... So I've made a > list. > > Maybe there are some activities I haven't thought of, or maybe there are > some that you think shouldn't be part of a usability team duties. > > > Would you add/remove any items to this list? I'd greatly appreciate your > help. > > > *Evaluations without users* > Informal evaluations (by intuition, cognitive walkthrough) > Heuristic evaluations (several evaluators, using guidelines) > Recommend changes > > *User recruiting > *Define user profiles > Create Personas > Create screening scripts > Filter out users from database > Maintain database > Recruit users on the phone > Schedule users > Schedule observers > Reconfirm users > > *Usability testing with users > *Plan usability test / Design experiment > Define test goals (purpose of test, how results will be used) > Define research questions > Write test script (introduction, tasks, questionnaires) > Revise script using prototype or product > Determine equipment needs for test > Prepare and operate equipment > Interview users > Moderate tests > Observe tests (taking notes) > Take special notes (data collection, time on task, success, etc.) > Play Computer in tests with paper prototypes > Debrief users > Transcript notes (to digital format) > Consolidate data gathered during tests to make analysis easier (tables, > graphics) > Analyze videos, notes and other date to infer problems > Recommend changes to interface > Make highlight videos – choose segments, make script for video > Make highlight videos – edit, operate video software > > *Interface design* > Create / analyze design options with development team > Create flow diagrams > Create paper prototypes > Create software prototypes (e.g. Axure) > Revise designs made by others > > *Other activities* > Analyze other sources of information (surveys, access logs, search logs) > Create User Profiles / Personas > Conduct contextual enquiries (at users' home/work) > Moderate participatory design sessions > Conduct Focus Groups > Train other team members in usability matters > > *Information Architecture* > Design taxonomies, organization criteria, labeling systems, controlled > vocabularies. > > > Thanks! > -- > Guillermo Ermel > ________________________________________________________________ > Welcome to the Interaction Design Association (IxDA)! > To post to this list ....... [EMAIL PROTECTED] > Unsubscribe ................ http://www.ixda.org/unsubscribe > List Guidelines ............ http://www.ixda.org/guidelines > List Help .................. http://www.ixda.org/help > ________________________________________________________________ Welcome to the Interaction Design Association (IxDA)! To post to this list ....... [EMAIL PROTECTED] Unsubscribe ................ http://www.ixda.org/unsubscribe List Guidelines ............ http://www.ixda.org/guidelines List Help .................. http://www.ixda.org/help
