Understanding Online Audiences Bazley Ma Wonder Web 10 Jun09

Loading...

Flash Player 9 (or above) is needed to view presentations.
We have detected that you do not have it on your computer. To install it, go here.

0 comments

Post a comment

    Post a comment
    Embed Video
    Edit your comment Cancel

    Favorites, Groups & Events

    Understanding Online Audiences Bazley Ma Wonder Web 10 Jun09 - Presentation Transcript

    1. Understanding online audiences: How to evaluate your website and why World wide wonder: Museums on the web V&A Sackler Centre 10 June 2009 Martin Bazley Online experience consultant Martin Bazley & Associates
    2. Martin Bazley
      • Science Museum, London, Internet Projects (7yrs)
      • E-Learning Officer, MLA South East (3yrs)
      • Chair of E-Learning Group for Museums
      • Consultancy, websites, training, user testing, evaluation … Martin Bazley & Associates Notes in pack for afterwards
    3.  
    4. www.martinbazley.com
      • Why do we need to research our online audiences?
      • Because otherwise users don’t ‘get’ what we are offering:
      • a real–world example (10 Jun09: 43% of non-users don’t want web at home - even for free)
      • Re value/status of Wikipedia – motivation , then information – anyone involved in any serious research will discover errors very quickly – try and get links into museum content via Wikipedia and other channels
    5. Even a slight difference in viewpoints… … can cause real problems for users
    6.  
    7.  
    8.  
    9.  
    10.  
    11.  
    12. A conflict between visual affordance … … and written instructions visual affordance almost always wins
      • Another example
    13. Hmm… the button is really small… And it’s not green… You can’t push it in… Just push the big green button by the gate
    14. Huge green button
      • How can we get a sense of who our online visitors are and what they do with our online content?  
      • How do we gather data to help us improve what we do?
      • How do we measure success from the user's point of view, and against our own objectives and constraints?
      • For example, how justify investment in social networks etc?
    15. Define audience research goal Analyse data Collect data Use results to guide changes Plan methodology
    16. Define audience research goal Analyse data Collect data Use results to guide changes Plan methodology
    17. Define audience research goal Analyse data Collect data Use results to guide changes Plan methodology
    18. Define audience research goal Analyse data Collect data Use results to guide changes Plan methodology
    19. Define audience research goal Analyse data Collect data Use results to guide changes Plan methodology
    20. Define audience research goal Analyse data Collect data Use results to guide changes Plan methodology
    21. Reasons for doing audience research: Evaluation
      • Did your project/product/service do what you wanted it to do?
      • Provide information for stakeholders
      • Gauge audience satisfaction
    22. Reasons for doing audience research: Promotion
      • Improve your offer for your target audiences
      • Increase usage
      • Widen access
    23. Reasons for doing audience research: Planning
      • Inform development of a new product/service
      • Inform business planning
      • Prove interest in a related activity (e.g. exhibit)
    24. Tools available
      • Qualitative – focus groups, “free text” questions in surveys, interviews
      • Quantitative – web statistics, “multiple choice” questions in surveys, visitor tracking
      • Observational – user testing, ethnographic
    25. When to evaluate or test and why
      • Before funding approval – project planning
      • Post-funding - project development
      • Post-project – summative evaluation
    26. Testing is an iterative process
      • Testing isn’t something you do once
      • Make something
      • => test it
      • => refine it
      • => test it again
    27. Before funding – project planning
      • *Evaluation of other websites
        • Who for? What for? How use it? etc
        • awareness raising: issues, opportunities
        • contributes to market research
        • possible elements, graphic feel etc
      • *Concept testing
        • check idea makes sense with audience
        • reshape project based on user feedback
      Focus group Research
    28.  
    29. Post-funding - project development
      • *Concept testing
        • refine project outcomes based on feedback from intended users
      • Refine website structure
        • does it work for users?
      • *Evaluate initial look and feel
        • graphics,navigation etc
      Focus group Focus group One-to-one tasks
    30.  
    31.  
    32.  
    33.  
    34. Post-funding - project development 2
      • *Full evaluation of a draft working version
        • usability AND content: do activities work, how engaging is it, what else could be offered, etc
      Observation of actual use of website by intended users , using it for intended purpose , in intended context – workplace, classroom, library, home, etc
    35.  
    36.  
    37.  
    38.  
    39.  
    40.  
    41.  
      • Video clip Moving Here key ideas not lesson plans
    42.  
    43.  
    44.  
    45.  
    46. Post-funding - project development 3
      • Acceptance testing of ‘finished’ website
        • last minute check, minor corrections only
        • often offered by web developers
      • Summative evaluation
        • report for funders, etc
        • learn lessons at project level for next time
    47. Website evaluation and testing
      • Need to think ahead a bit:
        • what are you trying to find out?
        • how do you intend to test it?
        • why? what will do you do as a result ?
        • The Why? should drive this process
    48. User test early
      • Testing one user early on in the project…
      • … is better than testing 50 near the end
    49. Two usability testing techniques
      • “ Get it” testing
      • - do they understand the purpose, how it works, etc
      • Key task testing
      • ask the user to do something, watch how well they do
      • Ideally, do a bit of each, in that order
    50.  
    51. User testing – who should do it?
      • The worst person to conduct (or interpret) user testing of your own site is…
        • you!
      • Beware of hearing what you want to hear…
      • Useful to have an external viewpoint
      • First 5mins in a genuine setting tells you 80% of what’s wrong with the site
    52. Extracts from London Museums Hub Online audience research
    53. Data used for different things: Reporting and diagnostics
      • Diagnostics – aimed at improvement of resources, identifying new areas for development, etc
      • Reporting – to DCMS and other funders, internal etc
      • Google Analytics =
      • Most popular web-based web stats tool.
      • But also Piwik, Mint, Clicky etc
      • Also AWstats, HitStats, etc
    54. Stats solutions
      • Exclusion of bots / internal traffic
      • most people aware of need to do so
      • but there is also pressure to provide higher figures…so maybe leave them in?
    55. Issues
      • Browser-based statistics applications (like GA) cannot be installed on the whole of a site because
      • a) no access to the code of the site, or
      • b) there are just too many legacy pages to change
    56. Issues
      • Barriers to effective usage of web stats
      • Subsections of websites or microsites have different statistics packages => separate analysis for each part
      • Perhaps outside supplier controls access to log files or stats package and are unwilling to add Google Analytics etc
    57. Issues
      • Off-website activity not reflected in server stats
      • More of users’ interaction with museum web content is happening away from the museum websites themselves, via blogging, Flickr, YouTube, wikis, etc.
      • Activity via RSS feeds such as blogs or podcasts can be measured…
    58. Issues
      • As museums engage further with web 2.0 services their online identities become fuzzier
      • => May soon not be feasible for museums to measure impact in absolute numbers
    59. Issues
      • Ways to ameliorate:
      • Inbound RSS feeds from those services could be embedded into the museum sites. Strategies to gather statistics from external services can be developed.
      • But a line needs to be drawn to avoid wasting too much effort, following the law of diminishing returns. There is also the copyright-related question of to what extent such content is yours given that it is generated ‘out there’ rather than on your site.
      • Therefore, the precise strategy to adopt should be determined by the ways in which the information will be used. This is one reason for adopting a more universal approach to data collection and interpretation, as outlined below.
    60. Concerns
      • Benchmarks: people want to know what is “good” and what is not when it comes to web statistics >P re Google benchmarks
      • People don’t always know what to do with the results
    61. Geffrye Museum web stats linked with events etc
    62. Key points
      • What we did
        • Online questionnaire
        • Visitor survey
        • Focus groups
      • What we found out
        • Some key findings
      • Recommended next steps
    63. Online questionnaire
      • SurveyMonkey – questions developed with museums then refined following trialling
        • Links to questionnaire added to museum websites
        • Run for several months, 000s responses collected
    64.  
    65.  
    66. EM Online collections research by MHM
    67.  
    68.  
    69.  
    70.  
    71.  
    72. Visitor survey
      • gathered data for comparison with OQs
      • recruitment for focus groups
    73. Focus groups
      • 18-24 / families / adults 25+
    74.  
    75. What we found out
      • Link between websites and physical visits
        • Majority of web use is for planning visits
        • Only about half use the website before visiting the museum
        • Some websites failing to create appropriate impressions of the physical museums, so failing to attract undecided visitors >N
        • Confusion re difference between stored and displayed collections
    76. What we found out
      • Very little use of websites other than for planning the visit, except:
        • Teachers – looking for teaching materials and ideas
        • Families – looking for online games, homework etc
        • Comment re online collection browsing: researching/searching, following, browsing ( MHM)
    77. What we found out
      • Very little interest in ‘user generated content’, but…
        • … this may be because most do not yet understand the possibilities, partly because trends moving so quickly. More research required, based on specific proposals
    78. What we found out
      • Demographic data
      • Motivations for using website
      • Expectations of website
      • etc
    79. Online users
    80.  
    81.  
    82.  
    83.  
    84. Most commonly requested web content relates to visiting
      • The top 4 overall are:
      • information on what the galleries are like
      • information on the museum’s objects
      • details of events and exhibitions
      • information about collections in store
      • what most online users want is more information about the museum visit .
      • Value = Reach x Quality
    85.  
    86.  
    87.  
    88. Metrics
      • Net Promoter may not be appropriate as Quality metric for cultural sector websites
      • Could a single question (or handful of questions) be agreed as standard, and used to assess ‘satisfaction’ via surveys?
      • How could the results be used?
        • Reporting?
        • Internal investment planning?
    89. Defining market share
      • ‘Reach’ may be very small for niche topics / audiences – does this matter?
      • Could use % of total audience instead?
      • This would mean
        • (a) estimating total audience (often part of project plan / funding application anyway)
        • (b) using unique visitors stats or other means to estimate reach
    90. Metrics for reporting
      • Currently ‘visits’ = default metric for reporting
      • Not v meaningful, but does this matter, given that there is no single metric
      • What should we be reporting on?
        • Audience penetration
        • Audience satisfaction
        • Audience engagement
        • Breadth of coverage …?
    91. Metrics for development
      • Use a variety of metrics in combination, based on nature of project issues, future objectives and current sector priorities…
      • No magic bullets on horizon – justifying investment still a ‘creative’ decision
      • Need balance between flexibility between projects, and shareability of data, for successful analysis and skills development
      • ‘ Top tips’ in notes in pack ‘Understanding online audiences’

    + Martin BazleyMartin Bazley, 5 months ago

    custom

    412 views, 0 favs, 0 embeds more stats

    Martin Bazley slides from MA Wonder Web 10 Jun 09 V more

    More info about this document

    © All Rights Reserved

    Go to text version

    • Total Views 412
      • 412 on SlideShare
      • 0 from embeds
    • Comments 0
    • Favorites 0
    • Downloads 8
    Most viewed embeds

    more

    All embeds

    less

    Flagged as inappropriate Flag as inappropriate
    Flag as inappropriate

    Select your reason for flagging this presentation as inappropriate. If needed, use the feedback form to let us know more details.

    Cancel
    File a copyright complaint
    Having problems? Go to our helpdesk?

    Categories