Recommended
More Related Content
Similar to Real Time Data Collection for High Security Envirnments
Similar to Real Time Data Collection for High Security Envirnments (20)
More from Kristyn Greenwood
More from Kristyn Greenwood (6)
Recently uploaded
Recently uploaded (20)
Real Time Data Collection for High Security Envirnments
- 1. Kristyn Greenwood Role: Researcher & UX Lead Methodology for Real-Time Data Collection for High-Security Environments: Observational Data Logging
- 2. Typical Observational Methodologies Real Time Data Collection for High Security Environments
- 5. The Problem Real Time Data Collection for High Security Environments
- 6. Problem(s) Drawbacks to typical Ethnographic Methodology • Developers: o Prefer Numbers / Statistics o Don’t trust ‘anecdotal’ evidence o Feel that their ‘observations’ have equal validity to researcher’s ‘observations’ • Data Collection • Security Restrictions: No recording (voice or video) allowed. • Volume of data to record is too high for paper and pencil records • Computer users frequently multitask • Computer users frequently use multiple tools simultaneosly
- 7. The Solution Real Time Data Collection for High Security Environments
- 8. Observational Data Logging Real Time Observation Time Data Accurate Logs Coding Scheme
- 12. Data Reporting Options Available Real Time Data Collection for High Security Environments
- 13. Example: Percentage Data • Pie Charts: % of Time
- 14. • Bar Charts: Top 5 Example: Duration Data
- 15. 8 EmailVoicemail Paper Telephone Employee Directory Local Address Book Calendar Informational Web Page Remote Files Local Files 13 12 12 167 9 9 8 8 6 7 Example: Interaction Diagrams
- 17. In Conclusion • Why use this Methodology o Satisfy Number Driven Product Teams o Accommodate Restrictions on recording. o Collect LOTS of data • 3 Attributes of an Observation o Time Data o Accuracy o Components • Data Logging Tool (for a copy contact me: kristyngreenwood@gmail.com
Editor's Notes
- As the name implies the Core of the Methodology is the Observation But – Three Key Attributes to the successTime Data – specifically DurationNot just Frequency Duration is the data that can be turned into graphsExplain more about how we capture duration data and analyze it laterComponent Parts – Observations can be vague. You need a coding scheme that ensure consistency in what is reported for each observation. Accurate Recording: Need to be able to quickly and exactly record Exact Start & Stop Times Unique Observations may be recorded every 5 seconds or the User may multitask.Need to have a high degree of consistency between observations sessions and observersSo how
- PreObservation – Surveys, Interviews & Training. Need to become very familiar with the materials & Setup Observation - Start Time, Components, & Notes (e.g. for asking clarification on an activity later)Post ObservationInterview (for asking about unclear acitvities – what was that script or why did you do that thing with the squiggly)Imporant to interview RIGHT AWAY and Fix items in data log. “(e.g. ‘unclear task’ & ‘unknown tool’ can be replaced by ‘Check System Load’ and ‘personal script’). Collect stuff that illustrates work (screenshots of webpages referenced during job, flow charts from walls, sticky notes)
- ComponentsFor us each observation, information is collected on the task that the user is attempting to accomplish, the specific action that the user is performing, the object to which the action or actions pertain, and the tool used to perform that action. You don’t have to use these 4 component, you don’t even have to use just 4. These are the ones that work best for us.You develop your coding scheme via – Surveys, Interviews & Training. Need to become very familiar with the materials & Setup VALIDATE ITSetup the ToolAnd PRACTICE