Case Study: Building a Wiki


Published on

  • Be the first to comment

  • Be the first to like this

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide

Case Study: Building a Wiki

  1. 1. Methodologies Utilized: Online bulletin board/focus group Social media recruitment Usability/UI/UE Quantitative Unique methods/custom user-friendly market research™ CASE STUDY Building a Wiki
  2. 2. user-friendly market researchProject BackgroundA wiki is a collaborative website where anyonewith access can contribute content and modify at will. Perhaps more famous for theireducational applications, wikis have also been used by businesses to create simpleknowledge management systems, or function as a collaborative software. Wikis build relational knowledge databasesystems, capturing the links between isolatedpieces of information. Though this results in anon-linear navigation system, wikis are a more accurate method of structuring informationthan traditional static databases. This organic structure makes for intuitive search.
  3. 3. user-friendly market research Client Objectives One of our clients wanted to create a definitiveresource for third party video game developers, and they already had the qualitative research data to do so. In fact, they had well over 90 different studies worth of data.Having performed some of the initial research for the client, we were asked to combine our own findings with the insights from other usabilitystudies, in order to produce a Game Developers Handbook. After discussing the proposed Handbook with the client, it became clear that what they really wanted was to develop a searchable database of best practices, which could serve as a reference point for game developers, and save a lot of headaches.
  4. 4. user-friendly market research The Challenge Our role was to take this vast collection of assorted findings, and consolidate it into acomprehensive, yet comprehensible catalog. This meant reviewing the research data, identifying the best practices, and then re-organizing 90+ individual reports into a useful tool for the developer community. Due to our familiarity with some of thefindings going in, we knew that this wouldnt be a clean job by any means. Creating neat categories from messy data rarely works; insights interact, and are dependant on relationships between variables.
  5. 5. user-friendly market research Our ApproachWe decided that to structure all of this data, whilecapturing the inter-relationships, we would need to build a wiki. Approaching the project as a wiki meant using the existing research to noterelationships, or affinities, and then come up with headings to describe the major groups of relationships. Instead of organizing information, we created a custom taxonomy to describe the mountain of data we were working with. This processorganically revealed the basic best practices hiding in those 90+ research reports.
  6. 6. user-friendly market research The OutcomeWe identified eight groups, or types of findings tostructure the wiki, and describe the best practices of video game development, as evidenced byprevious research. After pouring the existing datainto this structure, we cross-indexed the contentsof each group to map out all of the relationships.Then we handed the wiki off to the client, so the developers could access the database, and add their own insights where applicable.
  7. 7. user-friendly market research The UpsideThe initial insights were valuable to the client, but they would become even more valuable if they had an infrastructure for ongoing learning. Wedidnt just cut and paste existing research; we laid the foundation for a living resource and useful tool. The relationships established in the wiki makefinding useful information an intuitive process for developers, providing ongoing benefits for the client.
  8. 8. user-friendly market research Thank You!Contact us with questions or to request a proposal 212.660.0110 Follow us on Twitter: @goodmindMR