Hide Notes 

Slide 1: USER RESEARCH AND ANALYSIS Purpose The User Analysis tools provide the designer with perspectives on the different categories of people who will play some role in the product’s use. The term used to describe these different groups of people is stakeholder – derived from the notion that these people will have a certain ‘stake’ or vested interest in the product A stakeholder is someone who has a vested interest in a product. Examples: manufacture, stockiest, retailer, end user, occasional user, service providers ,end disposing mechanism. The most obvious stakeholder is the end user The purpose is to record detailed information about the target users of a proposed product. The User Analysis comprises 3 tools: Stakeholder Overview; Stakeholder Attributes; and Requirements Summary. The purpose of these tools is to record detailed information about the target users of a proposed product. Through this three–stage process users are identified; their stake in the product specified; their attributes or characteristics described; and finally their requirements specified. These tools lead designers through a process of identifying users and classifying them according to the kind of use they will make of the product.
Slide 2: Methodology User Analysis Stakeholder Overview • 0. Source material Methodology: Activity Analysis Tools &Techniques: User Mapping tool Any background information on use attributes 1. Product title and description First, give the product a title and record the basic information about the product idea.  To design an aid for the children aged 8 years to 15 years to enable them draw the circles in A4 sized notebooks with the help of a pencil. 2. Stakeholder Category List the stakeholder groups identified in the User Mapping data gathering exercise.  The target user of a product,  Occasional users  Service providers.  Manufacture  Vendors  Stockiest  Retailers 3. Role in product For each group of stakeholder, identify what they are trying to do with the product, why the need it and what their responsibility might be to other stakeholders.
Slide 3: 4. Design Implications Based on the information and on any background research carried out, decide on whether any of your stakeholders have any special requirements or characteristics which, from the onset, must be taken into consideration in the design process. For example, if your target end user population are children it is worth bearing in mind that children are naughty and hasty. The product you are designing should therefore pay greater attention to the safety measures. 5. Actions Needed At the end one needs to summaries the research and also list the actions which are needed. For example one might realize that the full range of possible users is not known, and an action may be to try and obtain such information by contacting experts working in the area.
Slide 4: 0. Source material Methodology User Analysis Stakeholder Methodology: User Analysis Tools & Techniques: Interviews; direct observation; group discussions; questionnaires. 1. Stakeholder title and description  First, identify and describe briefly the stakeholder group under consideration. To design an aid for the children aged 8 years to 15 years to enable them draw the circles in A4 sized notebooks with the help of a pencil. 2. Attribute Stakeholders are described in detail in this under the headings in this column: capacities, name, age gender; qualification ,economic class religion, context, community, occupation (Demographic data) The information needed to complete this table is therefore, of necessity, detailed and extensive. The anthropometric data is also documented 3. Functional implications  Against each of the attributes listed, note down what you feel the bearing each particular attribute may have on the design of this product. For example: If the target end user population will vary widely in terms of sensory abilities (e.g. hearing and sight) then no feature of the product should be reliant on a single sense for operation. Another example: Similarly if the target end user population will vary widely in terms of their educational range and literacy,then written material for the product should be simple and minimal. 
Slide 5: 4. Desired product characteristics Based on information arrived at ,the design team should now consider how the product might be designed in order to address the issues raised. For example, if the product is not to rely on a single sense for operation then a desired product characteristic might be that an alarm should be both a flashing light and a tone or buzzer, not one or the other. Similarly, with users of varying reading abilities, a desired product characteristic would be that the machine should be a ‘walk up and use’ product and that instructional material for the product should be pictorial, and so not in written form, where possible. This column acts to document any practical ideas for the design of the product, and can be seen as the suggested features of the product needed to satisfy user needs. 5. Actions At the end one needs to summaries the discussion in this column and also list the actions which are needed. Pay special attention to issues which you feel may need to be considered in more detail at a later stage of the design process. Areas where different views emerged should be noted, all views again being recorded.
Slide 6: Methodology User Analysis Requirements Summary. Activity Analysis (AA) Purpose The Activity Analysis comprises 3 tools: Stakeholder Scenario List; Activity Elements Summary; and Requirements Summary. The Stakeholder Scenario List (AA1) summarizes the usage scenarios or main activities for each of the relevant stakeholder groups identified in the User Analysis. A usage scenario is a collective name for a set of actions that need to be performed. In order to understand activity–based requirements it is important to understand the context in which a product will be used, and what it will be used for. The functional implications of these activities are then examined and from these the design team can consider how certain design features can be incorporated into the product to meet the demands of those activities. One will note that this is a very similar procedure to that carried out in Stakeholder Attributes .This time, however, we are considering requirements arising from the attributes of activities as opposed to the attributes of users.
Slide 7: Activity Analysis 1 Stakeholder Scenario List 0. Source material User Analysis Methodology: Task analysis; group discussions; interviews; direct observation. Tools & Techniques: Any background information on user activities. 1. Product title and description Record the basic information about the product Next, identify and briefly describe the stakeholder group under Consideration List of Scenarios List all the usage scenarios you can think of for the stakeholder group under consideration. A usage scenario is defined as a set of activities which logically belong together to perform a task. For example: using the hand shower at the start of the bathing activity is one scenario. Another scenario is using the hand shower with the soapy hands. For general products with a wide range of usage this can be difficult however, and in this case it will be better to list a representative set of scenarios i.e. common or important groups of activities rather than trying to list everything. For Example in case of cell phone basic functions of calling, messaging, alarm. 1.
Slide 8: Use whatever data from analysis, customer contacts etc. that you can but do not be reluctant to use your imagination where data is missing. Mark such assumptions so that you remember which are assumptions and which are based on factual information. 3. Attributes of scenarios Describe as best you can each of the usage scenarios that have been identified for this particular stakeholder in detail.  For example :  The bathroom admeasuring 4’6”x7’6” with the granite tiled flooring has the hand shower placed on the wall opposite to the door opening next to the mixer at the height of 600mm above the finished floor level. The stool used for bathing is of 230 mm in height. The bucket is placed below the tap of 350mm diameter and height 450mm .The soap case and shampoo are placed on the floor next to the stool on the left hand side at the time of bathing. 4. Activities in Scenario In this column, list all the activities you can think of that go to make up the usage scenario under consideration. By observation list all the body interface with the product with the help of sketches and identify the areas of concern .also make intense observation of the product communication with the user (semantics)
Slide 9: 5.Functional Implications. Note down the implications that you think the activities identified may have for the design of the product. At this stage of analysis you are interested in identifying the design issues that need to be resolved rather than in how they will be solved in practice Functional implications for design can cover a wide variety of issues and be developed from formal analysis e.g. surveys of users’ needs, or come from designers’ intuitions It may be better to think of them as problems or difficulties in the performance of the activities being considered, and to then move towards considering how these may be solved. 6. Desired Product Characteristics Based on information arrived at, the design team should now consider how the product may possess certain design features that will address the emerging support needs for the activities to be performed. In addition to considering desired product characteristics in isolation, it is also important to explore any conflicts that may occur due to different design features being incompatible with each other
Slide 10: 7. Priorities for development Having identified possible conflicting product features, the next step will be to seek a resolution of the anticipated difficulties and formulate the priority listing to enable formulate a detailed design brief. 8. Actions Needed At the end one need to summaries the discussion and list the actions which have arisen through the completion of this tool. This analysis should synthesize in the articulation of a detailed design brief with a clearly identified user group, context, Scenarios with clear mention of the essential features and the desired features.
Slide 11: Product Analysis (PA) Purpose Up to this point we have described the design process as one which isi nhierently user-centred And which promotes significant levels of user involvement throughout. This approach helps designers form an understanding of the users, their needs and the activities they wish the product to perform. From that, designers can begin to formulate a Matrix of USERfit, this information will form the row Headings and thus become one axis of the Matrix. With the Product Analysis tool we now turn to the functional aspects of the proposed product in terms of design objectives and its broad specification and how these rest with issues such as: standards conformance; available technology; market considerations; and functional comparisons with competing products or services. The Product Analysis Summary will serve to summarise design information about the product which includes the creation of a list of detailed operational features, along with a summary of any actions that needed to be taken. These detailed operational features will be used to complete the Product Attribut Matrix and form the column headings. Procedure 0. Source material • Tools & Techniques: Task analysis; brainstorming; user trials. • Any background information on the product.
Slide 12: 1. Product title and description First, give the product a title and record the basic information about the product idea. This serves as a guide for other considerations 2. Design objectives and Detailed operational features In this column, list all items of product specification that have so far been identified The task now is to describe these in terms of concrete operational features. For example, in the design of the intelligent washing machine a design objective would be for the machine to allow easy access for the loading and unloading of washing. A possible operational feature to support that requirement would be a large door with an easy open and close mechanism. You may even specify the exact measurements of the door if that can be known at this stage. 3. Actions Needed At the end one need to summaries the discussion and list the actions which have arisen through the completion of this tool. This analysis should synthesize in the articulation of a detailed design brief with a clearly identified user group, context, Scenarios with clear mention of the essential features and the desired features.
Slide 13: This column contains a series of questions These questions are basically the who, what, why, where and when of the products use and are largey self–explanatory. What is the product/service? Why is there a need for the product/service? Where did the idea for the product originate? Who will purchase this product/service? Who are the primary end users? How and when will this service be used? Where will this product/service beused ? How will the development of thisproduct/service be Purpose This tool considers in more detail what is known about the environment in which the product will operate, and any implications that this may have for design. This tool reminds developers to consider the wider implications of how the product will be supported, and also documents • some of the likely implications of these decisions. • Training needs • Documentation • Installation • Maintenance • Support Environmental context and Product Environment
Slide 14: 0. Source Material Methodology: Product Analysis, Activity Analysis 3, User Analysis 3. 1. Preparing the Matrix Step 1. Across the row marked ‘Product Specification’ enter all items of product specification These items will now act as individual column headings along the Matrix. Step 2. Down the left hand column, desired attributes are entered from the Requirements Summaries of the User and Activity Analyses tools (UA3 and AA3). These items will now act as individual row headings down the Matrix. Step 3. Assessments are made for each desired attribute in terms of their perceived importance to the user. 2. Completing the Matrix Step 4. A simple tick is placed in a cell if the desired attribute is supported by an element Step 5. In the right hand Summary column, an assessment is now made of the degree to which each desired attribute is being adequately met by all of the elements in the product specification, and as before ticks, crosses and question marks should be used Step 6. Along the bottom row, a summary assessment is also made of the degree to which items in the product specification satisfy desired attributes The Product Attribute Matrix (PAM)
Slide 15: Design Summary Thus the Product Analysis is largely used to document an axisting product’s specification, whilst the Design Summary documents any design decisions made during the process of using the USERfit methodology. Usability Evaluation With the Usability Evaluation Planning tool, outputs from the Requirement and Design Summaries are used to identify usability goals and associated activities which are then enacted, tested, observed and measured during the course of the evaluation procedures.