Mike Morgan presented a method called visual data collection for taking structured notes during user research. It involves creating visual guides with screenshots of prototypes and predefined annotation symbols to log participant actions and feedback. Data from multiple participants is aggregated into a tally sheet using visual connectors to identify patterns. The method aims to help researchers stay focused on goals and analyze data faster. Attendees watched a demo then tried annotating a prototype themselves to experience the benefits of visual structuring for note-taking.
This document summarizes a student's computing research project on remote working tools. It outlines the student's research process, including setting the project vision to improve the Discord online meeting platform. The student defined requirements by comparing Discord to other tools and surveying users. The roles of literature review and importance of project planning are discussed. Primary and secondary research methods were used, each with merits and limitations. Research results were presented through online survey figures and analysis of advantages, disadvantages, and needed improvements to Discord.
Research: Developing an Interactive Web Information Retrieval and Visualizati...Roman Atachiants
The document describes developing an interactive web information retrieval and visualization system. The system aims to make information searching and presentation easier and more efficient. It does this through speech recognition, keyword extraction from text, query construction and expansion using concepts, filtering and summarizing search results, and visualization. The system architecture includes these main components and was tested with satisfactory results. However, some challenges remain in creating a smooth presentation experience.
The document discusses key considerations for designing questionnaires, including:
1. The format of questions will affect the answers, so questions should be short (under 25 words), understandable, and avoid double negatives.
2. Choosing an appropriate question format is important so responses are understandable and analyzable. Questions types include single answers, multiple choices, scales, and grids.
3. Pilot testing the questionnaire is essential to check that the data can be analyzed as intended and to refine ambiguous, leading, or poorly structured questions. Feedback from pilot participants should be solicited.
4. Generally, questionnaires should be limited to around 20 likert-scale questions to maintain participant interest and engagement. A variety of
Improving Your Surveys and Questionnaires with Cognitive InterviewingUXPA International
Do you use surveys or questionnaires in your work? If so, it is important to be sure you are collecting the data you need. Too often, we write surveys without much attention to how participants will understand and respond to our questions. Just like forms, instructions, websites, or any other product, users often have their own interpretations of our content.
We can improve our survey questions with a method called cognitive interviewing. This method was developed to improve questionnaires for large survey companies and government organizations. The method is similar to usability testing, as it evaluates how a user experiences a survey, but there are also some critical differences between the methods. In this session, we will describe cognitive interviewing, and show how it is similar to and different from usability testing. We will discuss how to conduct cognitive interviews, what data to collect, and how to analyze the results.
Presented by Jean Fox, Jennifer Edgar and Scott S. Fricker
Understanding User Experience Workshop - Interlink Conference 2012Lynne Polischuik
The document discusses user experience design and provides guidance on conducting user research and design. It recommends starting with discovery activities like interviews and empathy mapping to understand users. Personas should then be created to represent different user types. Guerrilla user research methods are suggested to validate assumptions and identify opportunities. Design principles informed by research can guide the design process. A design studio approach engages the team in sketching and combining ideas. Prototypes should be tested with users early through methods like guerrilla testing to iterate on the design.
The document summarizes different low-cost methods for conducting user research on web products with limited resources. It discusses using heatmapping and analytics tools to evaluate existing use, as well as virtual usability testing, guerrilla testing, and microfeedback forms to gather user experience feedback during the design process. Specific tools mentioned include CrazyEgg, Google Analytics, Usabilla, and building your own microfeedback forms. Examples are provided from a case study of redesigning a university library website.
This document summarizes a student's computing research project on remote working tools. It outlines the student's research process, including setting the project vision to improve the Discord online meeting platform. The student defined requirements by comparing Discord to other tools and surveying users. The roles of literature review and importance of project planning are discussed. Primary and secondary research methods were used, each with merits and limitations. Research results were presented through online survey figures and analysis of advantages, disadvantages, and needed improvements to Discord.
Research: Developing an Interactive Web Information Retrieval and Visualizati...Roman Atachiants
The document describes developing an interactive web information retrieval and visualization system. The system aims to make information searching and presentation easier and more efficient. It does this through speech recognition, keyword extraction from text, query construction and expansion using concepts, filtering and summarizing search results, and visualization. The system architecture includes these main components and was tested with satisfactory results. However, some challenges remain in creating a smooth presentation experience.
The document discusses key considerations for designing questionnaires, including:
1. The format of questions will affect the answers, so questions should be short (under 25 words), understandable, and avoid double negatives.
2. Choosing an appropriate question format is important so responses are understandable and analyzable. Questions types include single answers, multiple choices, scales, and grids.
3. Pilot testing the questionnaire is essential to check that the data can be analyzed as intended and to refine ambiguous, leading, or poorly structured questions. Feedback from pilot participants should be solicited.
4. Generally, questionnaires should be limited to around 20 likert-scale questions to maintain participant interest and engagement. A variety of
Improving Your Surveys and Questionnaires with Cognitive InterviewingUXPA International
Do you use surveys or questionnaires in your work? If so, it is important to be sure you are collecting the data you need. Too often, we write surveys without much attention to how participants will understand and respond to our questions. Just like forms, instructions, websites, or any other product, users often have their own interpretations of our content.
We can improve our survey questions with a method called cognitive interviewing. This method was developed to improve questionnaires for large survey companies and government organizations. The method is similar to usability testing, as it evaluates how a user experiences a survey, but there are also some critical differences between the methods. In this session, we will describe cognitive interviewing, and show how it is similar to and different from usability testing. We will discuss how to conduct cognitive interviews, what data to collect, and how to analyze the results.
Presented by Jean Fox, Jennifer Edgar and Scott S. Fricker
Understanding User Experience Workshop - Interlink Conference 2012Lynne Polischuik
The document discusses user experience design and provides guidance on conducting user research and design. It recommends starting with discovery activities like interviews and empathy mapping to understand users. Personas should then be created to represent different user types. Guerrilla user research methods are suggested to validate assumptions and identify opportunities. Design principles informed by research can guide the design process. A design studio approach engages the team in sketching and combining ideas. Prototypes should be tested with users early through methods like guerrilla testing to iterate on the design.
The document summarizes different low-cost methods for conducting user research on web products with limited resources. It discusses using heatmapping and analytics tools to evaluate existing use, as well as virtual usability testing, guerrilla testing, and microfeedback forms to gather user experience feedback during the design process. Specific tools mentioned include CrazyEgg, Google Analytics, Usabilla, and building your own microfeedback forms. Examples are provided from a case study of redesigning a university library website.
The document provides tips for making websites user-friendly during the web development process. It recommends thinking about the intended audience and taking aspects from other appealing websites. Key steps include ensuring logical page connections and navigation cues, using templates for consistency, and testing pages before completion. Organization through a directory structure and promotion are also emphasized. Continually evaluating ways to improve the site over time is advised.
The document outlines the steps for conducting user research through a usability study. It discusses planning the study, including defining goals, questions, metrics, methodology, participants and script. For the study, participants are asked to complete tasks with a prototype and provide feedback. Moderated studies involve a moderator guiding participants, while unmoderated are self-guided. The goals are to understand usability issues and identify areas for improvement prior to product launch.
Essay On Importance Of Reading Habits. Online assignment writing service.Diana Jordan
The document discusses the themes of friendship and war in the novel A Separate Peace by John Knowles. It provides examples of how the friendship between the main characters Gene and Phineas changes and strains as their competitiveness and jealousy increases. Their friendship represents the inner war they experience with each other as Gene feels inferior to Phineas and wants to be more like him. The themes of friendship and inner war are crucial to understanding the story.
Design and Data Processes Unified - 3rd Corner ViewJulian Jordan
In this presentation (given in early 2020) I explain that to build digital products, data analysts/scientists and designers need to leverage each other’s processes and work as a unit.
I introduce the problem solving approach of data analysts/scientists and designers as well as how to combine these approaches. Additionally, I explain how mental models and algorithms, while associated with design and data science, respectively, are similar ways to represent phenomena and questions about them.
1Dr. LaMar D. Brown PhD, MBAExecutive MSITUnivEttaBenton28
1
Dr. LaMar D. Brown PhD, MBA
Executive MSIT
University of the Cumberlands
Course: 2019-SPR-IG-ITS530-21: 2019_SPR_IG_Analyzing and Visualizing Data_21
Chapter Readings Reflections Journal
Chapter 1: Defining Data Visualization
Summary
In Chapter 1, the author Mr. Kirk describes about the concept of Data Visualization. Data visualization was defined as the visual analysis and communication of data. The chapter also included the historical background survey definition of data visualization by various other authors.
Also, in the book was a set of fascinating recipes that of the components in that involve in the definition. The type of data that is required to be visually analyzed is important before it is being subjected to further processing before visualization.
Mr. Kirk also emphasized the significance of the art and science of making data analysis a fun filled technical and an analytical reading that encourages the use of human perception to make decisions in assistance of visual treats that come in the form of graphs, pie charts among others. The science of data visualization is defined with the implication of truth, evidence and rules that govern the process of visualizing a set of data that can be quintessential in determining the path of an enterprise or an organization.
Highlights:
Upon reading the chapter 1 in this book that was in depth into data visualization, I was able to grasp essential technical and analytical definitions and can say they are quiet telling in terms of the importance on the concept and visual representation of the definitions. The use of some of the citations was a key indicator that data visualization can be defined in various ways and can assist in technical improvements if used in way that is beneficial to all parties.
Ideas and thoughts:
The chapter was a thorough analysis of the concept. However, I was also keen on looking for live examples of visual tools or results of analysis inculcated in this defining place of the book. The big positive is the use of the concept of science and art that can be implemented in the day to day activities to introduce data visualization in any area and can help in making decisions that can set a trend for the growth of an organization. In terms of the course, it was a great read to write this review journal and can hopefully add a firm base to the things to come.
Application:
The concept of data visualization can be implemented in my current work environment. As an IT personnel, I deal with the network infrastructure and constantly come across large chunk of data that will need to be analyzed for its usage stats, bandwidth, performance and benefits of choosing the hardware or software accordingly. To best impact this, the monitoring tools such a s NetFlow helps us in verifying bandwidth over utilization or underutilization to perform a set of tasks before troubleshooting any related issues. Now, the concept of data visualization can be implemented here ...
"Open" includes users - Leverage their inputRandy Earl
This document discusses various user research methods that can be used to improve open source software and ensure diversity. It begins by explaining the importance of intentionally including a diverse user base to drive innovation. It then provides an overview of common user research methods such as interviews, usability testing, card sorting, and analytics reviews. Specific examples are given around label testing and task-based navigation that resulted in improved user experiences and outcomes. The overall message is that proactively involving and understanding users is critical for the success of any software, including open source projects.
"A scenario is a description of a person’s interaction with a system.
Scenarios help focus design efforts on the user’s requirements, which are distinct from technical or business requirements.
Scenarios may be related to ‘use cases’, which describe interactions at a technical level. Unlike use cases, however, scenarios can be understood by people who do not have any technical background. They are therefore suitable for use during participatory design activities." http://infodesign.com.au/usabilityresources/scenarios/
This document provides an overview of various universal principles and methods of design. It discusses key design principles such as affordance, closure, immersion, and Ockham's razor. It also outlines several user experience design methods including contextual inquiry, affinity diagramming, heuristic evaluation, think-aloud protocol, and usability testing. The document aims to explain these principles and methods to help teams make informed design decisions and evaluate designs effectively.
This document discusses planning usability testing by defining goals and metrics. It recommends categorizing goals into questions about the product, users, success metrics, competitors, needed research, and timing. Goals should be simple statements that can be measured, like "Can visitors find needed information?". The type of data collected, like qualitative user feedback or quantitative metrics, should depend on the goal and who will use the results. Common metrics include success rates, error rates, and task completion times. Planning goals and metrics upfront helps focus the testing and ensure it provides useful results.
1. This document provides a step-by-step guide to implementing Outcome Driven Innovation (ODI) for a new product development project. It outlines 12 steps, including understanding the ODI method, defining the job to be done, conducting customer interviews, designing and launching an online survey, analyzing the results, and using the findings throughout the development process.
2. Some of the key lessons learned are to practice ODI interviews, do a mock analysis with sample data before launching the real survey, and make the survey as easy to complete as possible while still capturing important outcomes. It also emphasizes continuously referring back to the customer research findings as the product takes shape.
3. An example ODI project outlined in
This document discusses combining web analytics and user testing methods to provide more comprehensive insights. It outlines how each method has limitations on its own but provides complementary quantitative and qualitative data when used together. Specific examples show how web analytics can help focus user research activities like participant recruitment and test scenarios, while qualitative findings from user testing help interpret web analytics metrics. The overall message is that combining these methods allows telling a stronger story backed by both data and insights.
Information architecture for websites and intranetsContent Formula
A quick introduction to the art and science of information architecture and how we apply it at Content Formula to build effective websites and intranets
This document discusses various UX tools and methods that can help software developers integrate user experience best practices into their development process. It outlines the typical software development phases of analyze, design, develop/implement, and test, and provides examples of UX tools that can be used at each phase, such as mind maps and personas for analysis, wireframes and user flows for design, feature files for development, and heatmaps and analytics for testing. The overall goal is to help developers better understand users and build software that meets users' needs.
Usability testing (or user testing) involves measuring the ease with which users can complete common tasks on your website. The results of the analysis are a huge eye-opener and their implementation often leads to:
Increased sales and task completion and a high rate of return site visitors
A greatly improved understanding of your customers’ needs
A significant reduction in call centre enquiries
A much more user-focused in-house development team Source: http://www.wbcsoftwarelab.com/wbcblog/read-basics-of-usability-testing
This presentation will examine the purpose and application of information architecture for the so-called ‘next generation’ of information tools, including blogs and wikis. We will introduce ‘needs based’ information architecture, the methodology used for organising and designing information-rich environments in a way that allows people to use them more easily. We will then look at how the best practice principles behind this approach apply equally well to emerging technologies.
Presented at Open Publish 2007, by Patrick Kennedy of Step Two Designs.
Everything You Always Wanted to Know About Bad UX Research But Were Afraid to...Valsplat
This document summarizes an Amsterdam meetup on March 16th, 2016 about user experience (UX) research presented by Miel de Zwart. The presentation discussed different types of UX research methods like user interviews, usability testing, and analytics. It highlighted both good practices for moderating interviews and observing users without influencing them, as well as common pitfalls to avoid. Miel also provided suggestions for how to shift from reactive UX research to more proactive research that drives design changes, such as conducting frequent user tests and integrating UX insights directly into development processes.
Requirements Engineering for the HumanitiesShawn Day
This workshop explores how requirements engineering can be employed by digital and non-digital humanities scholars (and others) to conceptualise and communicate a research project.
requirementsEngineeringAs the field of digital humanities has evolved, one of the biggest challenges has been getting the marrying technical expertise with humanities scholarly practice to successfully deliver sustainable and sound digital projects. At its core this is a communications exercise. However, to communicate effectively demands an ability to effectively translate, define and find clarity in your own mind.
World Usability Day 2014 - UX Toolbelt for DevelopersSarah Dutkiewicz
The document discusses user experience (UX) tools and methods that are useful for software developers. It covers techniques for analyzing user needs like mind maps and personas, designing interfaces with wireframes and user flows, implementing features tracked in code via behavior-driven development, testing with analytics and heat maps, and iterating based on user research. The goal is to incorporate UX best practices into each phase of development to build intuitive, user-centered products.
This document outlines 8 principles for making user research lean:
1. Just do it - Conduct research in real world locations like coffee shops and airports.
2. It's a collective effort - Research should involve the whole product team to surface assumptions and gaps.
3. Know your assumptions - Sketching helps reveal assumptions.
4. Mix discovery and validation - Blend new ideas generation with improving existing products.
5. Go beyond listening, watch what they do - Observation provides important insights beyond interviews.
6. Quality over quantity - Look for patterns rather than large samples.
7. Go beyond interviews and observations - Methods like phone tours, diaries and concept comparisons provide additional insights.
8.
Connect Conference 2022: Passive House - Economic and Environmental Solution...TE Studio
Passive House: The Economic and Environmental Solution for Sustainable Real Estate. Lecture by Tim Eian of TE Studio Passive House Design in November 2022 in Minneapolis.
- The Built Environment
- Let's imagine the perfect building
- The Passive House standard
- Why Passive House targets
- Clean Energy Plans?!
- How does Passive House compare and fit in?
- The business case for Passive House real estate
- Tools to quantify the value of Passive House
- What can I do?
- Resources
PDF SubmissionDigital Marketing Institute in NoidaPoojaSaini954651
https://www.safalta.com/online-digital-marketing/advance-digital-marketing-training-in-noidaTop Digital Marketing Institute in Noida: Boost Your Career Fast
[3:29 am, 30/05/2024] +91 83818 43552: Safalta Digital Marketing Institute in Noida also provides advanced classes for individuals seeking to develop their expertise and skills in this field. These classes, led by industry experts with vast experience, focus on specific aspects of digital marketing such as advanced SEO strategies, sophisticated content creation techniques, and data-driven analytics.
More Related Content
Similar to Visual Data Collection - Mike Morgan - REcon 18
The document provides tips for making websites user-friendly during the web development process. It recommends thinking about the intended audience and taking aspects from other appealing websites. Key steps include ensuring logical page connections and navigation cues, using templates for consistency, and testing pages before completion. Organization through a directory structure and promotion are also emphasized. Continually evaluating ways to improve the site over time is advised.
The document outlines the steps for conducting user research through a usability study. It discusses planning the study, including defining goals, questions, metrics, methodology, participants and script. For the study, participants are asked to complete tasks with a prototype and provide feedback. Moderated studies involve a moderator guiding participants, while unmoderated are self-guided. The goals are to understand usability issues and identify areas for improvement prior to product launch.
Essay On Importance Of Reading Habits. Online assignment writing service.Diana Jordan
The document discusses the themes of friendship and war in the novel A Separate Peace by John Knowles. It provides examples of how the friendship between the main characters Gene and Phineas changes and strains as their competitiveness and jealousy increases. Their friendship represents the inner war they experience with each other as Gene feels inferior to Phineas and wants to be more like him. The themes of friendship and inner war are crucial to understanding the story.
Design and Data Processes Unified - 3rd Corner ViewJulian Jordan
In this presentation (given in early 2020) I explain that to build digital products, data analysts/scientists and designers need to leverage each other’s processes and work as a unit.
I introduce the problem solving approach of data analysts/scientists and designers as well as how to combine these approaches. Additionally, I explain how mental models and algorithms, while associated with design and data science, respectively, are similar ways to represent phenomena and questions about them.
1Dr. LaMar D. Brown PhD, MBAExecutive MSITUnivEttaBenton28
1
Dr. LaMar D. Brown PhD, MBA
Executive MSIT
University of the Cumberlands
Course: 2019-SPR-IG-ITS530-21: 2019_SPR_IG_Analyzing and Visualizing Data_21
Chapter Readings Reflections Journal
Chapter 1: Defining Data Visualization
Summary
In Chapter 1, the author Mr. Kirk describes about the concept of Data Visualization. Data visualization was defined as the visual analysis and communication of data. The chapter also included the historical background survey definition of data visualization by various other authors.
Also, in the book was a set of fascinating recipes that of the components in that involve in the definition. The type of data that is required to be visually analyzed is important before it is being subjected to further processing before visualization.
Mr. Kirk also emphasized the significance of the art and science of making data analysis a fun filled technical and an analytical reading that encourages the use of human perception to make decisions in assistance of visual treats that come in the form of graphs, pie charts among others. The science of data visualization is defined with the implication of truth, evidence and rules that govern the process of visualizing a set of data that can be quintessential in determining the path of an enterprise or an organization.
Highlights:
Upon reading the chapter 1 in this book that was in depth into data visualization, I was able to grasp essential technical and analytical definitions and can say they are quiet telling in terms of the importance on the concept and visual representation of the definitions. The use of some of the citations was a key indicator that data visualization can be defined in various ways and can assist in technical improvements if used in way that is beneficial to all parties.
Ideas and thoughts:
The chapter was a thorough analysis of the concept. However, I was also keen on looking for live examples of visual tools or results of analysis inculcated in this defining place of the book. The big positive is the use of the concept of science and art that can be implemented in the day to day activities to introduce data visualization in any area and can help in making decisions that can set a trend for the growth of an organization. In terms of the course, it was a great read to write this review journal and can hopefully add a firm base to the things to come.
Application:
The concept of data visualization can be implemented in my current work environment. As an IT personnel, I deal with the network infrastructure and constantly come across large chunk of data that will need to be analyzed for its usage stats, bandwidth, performance and benefits of choosing the hardware or software accordingly. To best impact this, the monitoring tools such a s NetFlow helps us in verifying bandwidth over utilization or underutilization to perform a set of tasks before troubleshooting any related issues. Now, the concept of data visualization can be implemented here ...
"Open" includes users - Leverage their inputRandy Earl
This document discusses various user research methods that can be used to improve open source software and ensure diversity. It begins by explaining the importance of intentionally including a diverse user base to drive innovation. It then provides an overview of common user research methods such as interviews, usability testing, card sorting, and analytics reviews. Specific examples are given around label testing and task-based navigation that resulted in improved user experiences and outcomes. The overall message is that proactively involving and understanding users is critical for the success of any software, including open source projects.
"A scenario is a description of a person’s interaction with a system.
Scenarios help focus design efforts on the user’s requirements, which are distinct from technical or business requirements.
Scenarios may be related to ‘use cases’, which describe interactions at a technical level. Unlike use cases, however, scenarios can be understood by people who do not have any technical background. They are therefore suitable for use during participatory design activities." http://infodesign.com.au/usabilityresources/scenarios/
This document provides an overview of various universal principles and methods of design. It discusses key design principles such as affordance, closure, immersion, and Ockham's razor. It also outlines several user experience design methods including contextual inquiry, affinity diagramming, heuristic evaluation, think-aloud protocol, and usability testing. The document aims to explain these principles and methods to help teams make informed design decisions and evaluate designs effectively.
This document discusses planning usability testing by defining goals and metrics. It recommends categorizing goals into questions about the product, users, success metrics, competitors, needed research, and timing. Goals should be simple statements that can be measured, like "Can visitors find needed information?". The type of data collected, like qualitative user feedback or quantitative metrics, should depend on the goal and who will use the results. Common metrics include success rates, error rates, and task completion times. Planning goals and metrics upfront helps focus the testing and ensure it provides useful results.
1. This document provides a step-by-step guide to implementing Outcome Driven Innovation (ODI) for a new product development project. It outlines 12 steps, including understanding the ODI method, defining the job to be done, conducting customer interviews, designing and launching an online survey, analyzing the results, and using the findings throughout the development process.
2. Some of the key lessons learned are to practice ODI interviews, do a mock analysis with sample data before launching the real survey, and make the survey as easy to complete as possible while still capturing important outcomes. It also emphasizes continuously referring back to the customer research findings as the product takes shape.
3. An example ODI project outlined in
This document discusses combining web analytics and user testing methods to provide more comprehensive insights. It outlines how each method has limitations on its own but provides complementary quantitative and qualitative data when used together. Specific examples show how web analytics can help focus user research activities like participant recruitment and test scenarios, while qualitative findings from user testing help interpret web analytics metrics. The overall message is that combining these methods allows telling a stronger story backed by both data and insights.
Information architecture for websites and intranetsContent Formula
A quick introduction to the art and science of information architecture and how we apply it at Content Formula to build effective websites and intranets
This document discusses various UX tools and methods that can help software developers integrate user experience best practices into their development process. It outlines the typical software development phases of analyze, design, develop/implement, and test, and provides examples of UX tools that can be used at each phase, such as mind maps and personas for analysis, wireframes and user flows for design, feature files for development, and heatmaps and analytics for testing. The overall goal is to help developers better understand users and build software that meets users' needs.
Usability testing (or user testing) involves measuring the ease with which users can complete common tasks on your website. The results of the analysis are a huge eye-opener and their implementation often leads to:
Increased sales and task completion and a high rate of return site visitors
A greatly improved understanding of your customers’ needs
A significant reduction in call centre enquiries
A much more user-focused in-house development team Source: http://www.wbcsoftwarelab.com/wbcblog/read-basics-of-usability-testing
This presentation will examine the purpose and application of information architecture for the so-called ‘next generation’ of information tools, including blogs and wikis. We will introduce ‘needs based’ information architecture, the methodology used for organising and designing information-rich environments in a way that allows people to use them more easily. We will then look at how the best practice principles behind this approach apply equally well to emerging technologies.
Presented at Open Publish 2007, by Patrick Kennedy of Step Two Designs.
Everything You Always Wanted to Know About Bad UX Research But Were Afraid to...Valsplat
This document summarizes an Amsterdam meetup on March 16th, 2016 about user experience (UX) research presented by Miel de Zwart. The presentation discussed different types of UX research methods like user interviews, usability testing, and analytics. It highlighted both good practices for moderating interviews and observing users without influencing them, as well as common pitfalls to avoid. Miel also provided suggestions for how to shift from reactive UX research to more proactive research that drives design changes, such as conducting frequent user tests and integrating UX insights directly into development processes.
Requirements Engineering for the HumanitiesShawn Day
This workshop explores how requirements engineering can be employed by digital and non-digital humanities scholars (and others) to conceptualise and communicate a research project.
requirementsEngineeringAs the field of digital humanities has evolved, one of the biggest challenges has been getting the marrying technical expertise with humanities scholarly practice to successfully deliver sustainable and sound digital projects. At its core this is a communications exercise. However, to communicate effectively demands an ability to effectively translate, define and find clarity in your own mind.
World Usability Day 2014 - UX Toolbelt for DevelopersSarah Dutkiewicz
The document discusses user experience (UX) tools and methods that are useful for software developers. It covers techniques for analyzing user needs like mind maps and personas, designing interfaces with wireframes and user flows, implementing features tracked in code via behavior-driven development, testing with analytics and heat maps, and iterating based on user research. The goal is to incorporate UX best practices into each phase of development to build intuitive, user-centered products.
This document outlines 8 principles for making user research lean:
1. Just do it - Conduct research in real world locations like coffee shops and airports.
2. It's a collective effort - Research should involve the whole product team to surface assumptions and gaps.
3. Know your assumptions - Sketching helps reveal assumptions.
4. Mix discovery and validation - Blend new ideas generation with improving existing products.
5. Go beyond listening, watch what they do - Observation provides important insights beyond interviews.
6. Quality over quantity - Look for patterns rather than large samples.
7. Go beyond interviews and observations - Methods like phone tours, diaries and concept comparisons provide additional insights.
8.
Similar to Visual Data Collection - Mike Morgan - REcon 18 (20)
Connect Conference 2022: Passive House - Economic and Environmental Solution...TE Studio
Passive House: The Economic and Environmental Solution for Sustainable Real Estate. Lecture by Tim Eian of TE Studio Passive House Design in November 2022 in Minneapolis.
- The Built Environment
- Let's imagine the perfect building
- The Passive House standard
- Why Passive House targets
- Clean Energy Plans?!
- How does Passive House compare and fit in?
- The business case for Passive House real estate
- Tools to quantify the value of Passive House
- What can I do?
- Resources
PDF SubmissionDigital Marketing Institute in NoidaPoojaSaini954651
https://www.safalta.com/online-digital-marketing/advance-digital-marketing-training-in-noidaTop Digital Marketing Institute in Noida: Boost Your Career Fast
[3:29 am, 30/05/2024] +91 83818 43552: Safalta Digital Marketing Institute in Noida also provides advanced classes for individuals seeking to develop their expertise and skills in this field. These classes, led by industry experts with vast experience, focus on specific aspects of digital marketing such as advanced SEO strategies, sophisticated content creation techniques, and data-driven analytics.
Storytelling For The Web: Integrate Storytelling in your Design ProcessChiara Aliotta
In this slides I explain how I have used storytelling techniques to elevate websites and brands and create memorable user experiences. You can discover practical tips as I showcase the elements of good storytelling and its applied to some examples of diverse brands/projects..
EASY TUTORIAL OF HOW TO USE CAPCUT BY: FEBLESS HERNANEFebless Hernane
CapCut is an easy-to-use video editing app perfect for beginners. To start, download and open CapCut on your phone. Tap "New Project" and select the videos or photos you want to edit. You can trim clips by dragging the edges, add text by tapping "Text," and include music by selecting "Audio." Enhance your video with filters and effects from the "Effects" menu. When you're happy with your video, tap the export button to save and share it. CapCut makes video editing simple and fun for everyone!
Architectural and constructions management experience since 2003 including 18 years located in UAE.
Coordinate and oversee all technical activities relating to architectural and construction projects,
including directing the design team, reviewing drafts and computer models, and approving design
changes.
Organize and typically develop, and review building plans, ensuring that a project meets all safety and
environmental standards.
Prepare feasibility studies, construction contracts, and tender documents with specifications and
tender analyses.
Consulting with clients, work on formulating equipment and labor cost estimates, ensuring a project
meets environmental, safety, structural, zoning, and aesthetic standards.
Monitoring the progress of a project to assess whether or not it is in compliance with building plans
and project deadlines.
Attention to detail, exceptional time management, and strong problem-solving and communication
skills are required for this role.
Practical eLearning Makeovers for EveryoneBianca Woods
Welcome to Practical eLearning Makeovers for Everyone. In this presentation, we’ll take a look at a bunch of easy-to-use visual design tips and tricks. And we’ll do this by using them to spruce up some eLearning screens that are in dire need of a new look.
International Upcycling Research Network advisory board meeting 4Kyungeun Sung
Slides used for the International Upcycling Research Network advisory board 4 (last one). The project is based at De Montfort University in Leicester, UK, and funded by the Arts and Humanities Research Council.
ARENA - Young adults in the workplace (Knight Moves).pdfKnight Moves
Presentations of Bavo Raeymaekers (Project lead youth unemployment at the City of Antwerp), Suzan Martens (Service designer at Knight Moves) and Adriaan De Keersmaeker (Community manager at Talk to C)
during the 'Arena • Young adults in the workplace' conference hosted by Knight Moves.
Revolutionizing the Digital Landscape: Web Development Companies in Indiaamrsoftec1
Discover unparalleled creativity and technical prowess with India's leading web development companies. From custom solutions to e-commerce platforms, harness the expertise of skilled developers at competitive prices. Transform your digital presence, enhance the user experience, and propel your business to new heights with innovative solutions tailored to your needs, all from the heart of India's tech industry.
UNIT V ACTIONS AND COMMANDS, FORMS AND CONTROLS.pptx
Visual Data Collection - Mike Morgan - REcon 18
1. Good afternoon everyone! It’s great to be here at ReCon 2018. My name is Mike Morgan. I
am a UX Researcher with Bloomberg.
Today we’re going to have some fun with straws! Just kidding.
Actually, today I am going to show you a method of data collection I have been using over
the past few years during mostly early-phase prototype research that I thought would be
interesting to share with you all.
It’s something I call visual data collection. You could also call it visual note-taking.
2. Here’s the agenda. I’ll briefly talk about the problem we’re trying to solve.
I’ll give an overview of some common note-taking tools and techniques used in the field
Then I’ll show you the method details for visual data collection.
We’ll save the best for last and do a fun data collection exercise where you’ll first watch a
play-by-play using the technique, then you’ll get to try it out yourself.
But first a little bit about myself.
3. I’ve been in working in the IT industry for about 20 years in various roles. I like to say that I
sort of backed into the field of UX research not realizing at the time that what I was doing
had a name to it.
I’ve worked in financial services for most of my career.
First as an engineer, then a business analyst, and ultimately as a UX researcher.
I also worked at ADP’s Innovation Lab for 4+ years doing UX research for their next
generation HCM software solutions.
Like many people in our field, I have a motley educational background.
I earned my Bachelor’s degree in English and Creative Writing from Binghamton University.
I also have an MBA in Finance/Strategy from NYU Stern and an M.S. in HCI from Iowa
State University.
I enjoy writing about UX research methods as well as UX strategy and innovation.
I have a column called Discovery on UX Matters which focuses on insights learned about
UX research for early-phase concept testing studies.
I’ve also written for some other publications as well.
But enough about me. Let’s talk about the problem we’re trying to solve.
4. We collect LOTS of data when we do UX research. Why shouldn’t we? It’s OUR job, right?
We hope to learn something new with each participant. Or identify a pattern of behavior that
may yield some insights, some design implications.
Much of what we collect during sessions might be useful and actionable but does it always
align with our initial research goals?
The problem is we don’t always know at the time whether or not we may need a piece of
data. So what do we do. We collect it “just in case.” Then what happens? We start to collect
more and more “just in case” data.
6. [person at desk]
Then when it comes time to analyze the data we may end up analyzing things beyond the
initial scope of our research goals.
[clock]
With an unlimited amount of time to do UX research having more data is not a bad problem
to have. After all, we will learn things we did not know before about our product and our
users.
The more data we can collect the more we can learn about our users, right?
But the reality is projects DO have limited amounts of time to get things done.
Deadlines need to be met so that designers can get their changes to engineers in time
before their sprints start.
Researchers need to ensure they stay focused on the original research goals or risk
[show dog]
stakeholder frustration and disengagement.
7. The note-taking approach I am going to show you today which I call visual data
collection will allow you to:
-Stay focused on your research goals
-Deliver reporting faster
-Will make your notes easily traceable in case you need to revisit them
[dog]
Ultimately you’ll end up with more satisfied stakeholders
Before I show you the method and we do a fun interactive note-taking exercise, I want to
do a brief review of note-taking tools and approaches that are currently being used in the
field.
8. According to UX researcher Whitney Quesenberry, most note-taking techniques have little
structure in place. There’s the less structured physical tools we use like post-its, notepads
and whiteboards. As you move along this line data contains a little more structure in the
guise of spreadsheets like Microsoft Excel and cloud-based solutions like Air Table. There
are solutions that utilize tagging of free-form data like Evernote or digital brainstorming tools
like Mural. And then along the far right you have power tools that log tasks like Ovo or tools
like Nvivo that can analyze large amounts of qualitative data in various formats.
To collect all of this data, we may gravitate towards using our own tools and techniques for
note-taking. I’m sure everyone has their favorite tool for taking notes.
9. There is no universal manner in which to take notes. According to UX Consultant and UX
Matters columnist Jim Ross, what note-taking approach we use really depends on
factors like the subject matter of your research, or, the research method being used,
among other things.
I think the note-taking approach we decide on is usually an after-thought or a given when
undertaking a research effort.
We already have in our minds the note-taking approach we’d like to use.
Ultimately, the way you record and organize the data should allow you and your teams to
make sense of it.
10. Techniques to make sense of your data as suggested by consultancies like Nielsen
Norman Group include topical notes-- recording observations and coding on post-its, then
affinity mapping the data to identify the main issues and themes.
11. Chronological logs is a more structured method for taking notes. It involves coding and
timestamping of events while logging observations.
Path analysis is a more visual method for taking notes. It allows us to to analyze the flow a
user takes within an experience to identify problems. We can analyze patterns across all
users in a more visual fashion with path analysis.
The Visual Data Collection method is similar to each of these-- it involves recording events
and tagging them. Similar to path analysis, visuals are an integral part of the note-taking
process.
12. So what is visual data collection? Here is a definition which sums it up. [read the slide]
In order to conserve paper I typically collect data using a digital tablet and stylus. The only
paper I end up printing out is when I am ready to do my final analysis.
I’ll show that to you as a part of this working example.
13. In a moment I’ll explain to you what these mean.
14. So what does it look when we put all of these components together?
Here is a snapshot of a visual data collection guide for a user study involving a fictional
search engine site.
In the visual data collection guide you will see a series of screenshots of the prototype that
depict the flow that a user would experience.
This is what you would call “the happy path.” Here you see the initial search screen then
the ensuing search results screen.
Along the right hand side are corresponding questions that relate to the visuals.
For easy reference I put the annotation key used for this study along the right hand side.
These are the shorthand symbols recorded during the sessions that allow for datasets to be
consistent across participants within a study.
For the sake of simplicity there are only 5 annotations listed here.
The annotations here include: the sequence of actions, elements the participant did or did
not understand as was intended by the design (or conceptual model), what the participant
selected in the prototype, participant feedback or suggestions and user expectations.
So if we were to interpret this user’s data, it appears that they first selected the text box,
entered in “Bruce Willis” then hit search. They expected after selecting the search button to
view a list of results. This participation did not understand what the “Roll the Dice” button
meant.
After being told in the session what it was, the participant suggested calling the button
16. So imagine you’ve logged all of your data into their respective visual data collection
interview guides. Now you have to aggregate them into one guide so you can analyze
them for patterns and themes.
Since we consistently applied annotations across the participants, analyzing the results
should be much easier.
The tally sheet is a master document which should include all of your participant’s data.
The annotations for the tally sheet are slightly different than the individual VDC guides.
Responses for each of the questions and annotations will include the participant’s number
as denoted by a “P” and their number enclosed in a circle.
This enables you to trace back any data directly to that participant.
Also, connectors are used to link together similar findings.
Connectors can include participant-to-response (orange). So in this case we see that two
participants did not understand the Roll the dice feature and one did.
There’s also participant-to-participant (blue) which suggests that participants exhibited the
same behaviors. In this example all 3 participants’ first action was to select the search box.
And lastly there’s participant-to-action sequence (purple). So in this case the first
participant’s second action was to select the search button.
With this very basic example you can see how easy it becomes to analyze data.
17. I do want to acknowledge that this method is not without its challenges.
-Websites that have many ways to accomplish the same task become difficult to design
data collection guides for. The number of pre-defined responses could become
overwhelming.
Rather than crafting questions with pre-defined responses, it might be worth considering
leaving open-ended questions then documenting the path they took.
-Another challenge is space. As you have more and more participants, space within the
tally sheet becomes a challenge.
Typically I’ve used this method successfully for up to 10 participants. Beyond that, the
increasing density of annotations becomes harder to discern.
-Lastly, subject matter without a UI may not benefit from this method. Questions which
are more exploratory in nature might require further detail, transcription and coding.
18.
19. Now it's time to watch it in action.
Pay attention: because you’re going to be trying this out in a minute!
We're going to do this in two parts:
First, you’re going to watch the annotations in a scripted, play-by-play mode alongside the
screen share of the prototype.
Then, for the rest of the video you’re going to try it yourself!
So here’s the scenario…[read the scenario on the slide then play the video]
As an observer and note-taker you should be clued into what the “happy path” is before
seeing the scripted portion of the video.
So I’ll walk you through that now.
22. Now at your table are handouts of the visual data collection guides as well as the
annotation key for reference during the session.
Use the annotation key when recording your observations. Observe the participant’s
actions and their corresponding sequence.
Watch for what they do and do not understand.
Answer the pre-defined questions.
23. Now that you’ve experienced the method, I’d like you to pair off with someone else and
compare results.
Try to interpret each others annotations. Then answer these questions
Then afterwards, I’m going to ask a volunteer to share their experience with the audience.
24. Before I conclude this presentation I just want to highlight potential areas for future research
using visual data collection.
This method has proven useful for early-phase prototypes. It has served as a useful way to
collect lots of interaction data and impressions from participants for early-phase prototypes.
Could it prove useful for collecting data for summative studies like usability testing?
How about products that don’t have a UI? How would this method capture notes without
any screenshots of UIs to annotate? Things to explore for sure.
And lastly, I’ve been using digital tools like pencils and tablets to collect data saving much
in terms of using paper up.
If we all used digital methods for collecting data as opposed to paper printouts how much
could we save in terms of $$ and trees?
25. If anyone wants to discuss this method further or has any ideas about extending this
method to other applications I’d love to chat.
Here’s my info. Thanks for listening and the opportunity to present this method. Enjoy the
rest of your conference!