Direct observation

A rich source of insight into how, where, why, when and who uses your products. Is good for both exploring new ideas and also for evaluating product concepts. Excellent for supporting incremental improvement. Provides a deep team understanding of usage issues, but needs careful interpretation.

Unique and professional website templates. Vooweb - Website Templates offers a great variety of Website templates for business and personal use | If there has been no improvement since the beginning of your relationship with your SEO company, they need to explain why. Then you have a great seo Company working for you. If you don't want to do it yourself, an SEO company being paid monthly should detail exactly what they are doing for you. | Any link exchanges promising hundreds or links immediately upon joining should be avoided unless the only search engine you care about is MSN. Using a link exchange as the only way you get links will also not be a path you want to wander down. Exchanging links with every site under the sun is also bad.

Description
In principle, direct observation is an incredibly simple way of gathering data about how users interact with products. However, without planning or structure, it can be difficult to digest and process insights gained. Without care, observation may also affect what people do and the type and number of people observed can bias results. Given these potential difficulties, observation is one of the most powerful tools for gaining user insight. Observation can be applied to: proposed new products - testing product concepts and models, existing products - to help guide improvement for the next generation, competitors products - to determine preference, strengths and weaknesses. As with all user understanding methods, it is important to establish how many users will provide a representative sample - this may be a smaller sample than some other methods due to the richness of information gained and the amount of time it can take.

Structure for recording observations
A useful structure is to have a small team involved in an observation exercise, where each member systematically records insights relating to a specific area of focus (see figure below):

  1. Task Analysis
    Describe the sequence and timing of actions and events. Can tasks be eliminated?

  2. Technical / Performance issues
    Record issues related to technical performance. Was it satisfactory, could it be improved?

  3. Functional issues
    Issues relating to product functionality and features. Were the right features present?

  4. Emotional issues
    How did the user feel? What expressions or comments were made?

  5. User issues
    Did the user require specific skills? Record comfort, ergonomics, physical and ease of use issues.

  6. Environment issues
    Did the location affect use? Were there access, noise, heat or other location issues?

 

observation chart

 

Notes

  • Observation can be time consuming and hence costly
  • Needs careful planning in order to gain maximum benefit
  • Users observed should be representative of user population and the person being observed must be comfortable with the process
  • Best with full team involvement, but this can add to the cost
  • Can be combined with video for data capture
  • Good when combined with traditional interviews

 

Back to index of tools and techniques

Home | GDP Program | Design maturity | Effective product design | Tools and techniques | Contact | Links
Better Product Design Collections