< Back to Project Home
GR1 - User and Task Analysis
User Analysis
Analyst’s Notebook (ANB) has an extremely wide range of users. The representative users that we interviewed are from the sectors of academia (MIT), industry (IBM), and military (U.S. Army), but all were working on problems related to government and international development. These problems include:
- Criminal investigations (FBI): tracking down people responsible for very elaborate, massive-scale fraud/scams; crime/drug rings, Russian mobs, etc.
- National security & diplomacy: figuring out relationships between international leaders, particularly "who is influencing who." People-centric analysis, social networks.
- Civil affairs: making predictions based on many different factors and data sets. Events-based analysis.
Within the scope of government-related users, we learned that ANB has two main classes of users that use the program in very different ways:
- Senior Analysts
- Age: 30-40 years old
- Experience: ~15 years, very highly experienced in their field and in using ANB
- Education: most have Bachelor's degrees, many have at least one Master’s, some have PhD’s. Fields of study are mostly social sciences (i.e. sociology, anthropology, psychology). For those with two Master’s degrees, one of them is usually technical (i.e. engineering, math).
- Usage: “use it like they’ve always used it.” Senior analysts are expert users of ANB and have become very familiar with it over the years, so they are not accustomed to changes in UI. They tend to prefer seeing relationships as text data fields or in tabular format, and frequently use queries to search within the data.
- Entry-level government contractors, enlisted military, or researchers
- Age: early- to mid-20’s
- Experience: not much experience with data analysis and ANB, if any
- Education: recent college graduates. Bachelor’s degrees.
- Usage: very visual. These users have a fast learning curve, and often rely on intuition to navigate the UI. Rather than see data as tables or text fields, they prefer to visualize relationships, i.e. as “honeycombs of influence” in a social network (people with influential relationships will be close to each other in a honeycomb visualization). Big emphasis on visualization of data and intuitive GUI.
Both of these user groups share the following characteristics:
- Frequency of use: daily. They "live it.”
- Hardware: high-end laptops with plenty of memory and processing power. Usually Dell Precision workstations.
Lessons learned:
The users emphasized that efficiency is the most important aspect of UI design for them. They complained that ANB's UI requires too many clicks and mouse movements to perform simple, common tasks. Users were very enthusiastic about the use of sliders (rather than buttons) to adjust parameters, such as time or resources. The overall movement is toward a more efficient, intuitive, slick design with primary emphasis on visualization. In other words, the ANB interface is shifting toward the younger class of users.
Task Analysis
With the back-end and database support provided by IBM, we will focus on designing effective ways to visualize data in a way that allows users to see relationships between large amounts of data efficiently. The user should be able to change the values of one datapoint, and see how that affects the entire visualization in a meaningful way. Our users have expressed a need for this to replace the tedious methods of querying and optimization that they currently use. Standard data visualization tools are available from open-source libraries such as processing.js. We will select a few visualization methods (e.g. web, map, graph) to focus on, geared toward understanding the data sets for WiFi in Africa. The users' main high-level tasks include:
- Optimization: The overarching common goal among users of ANB is to discern and understand complex relationships within data sets. This is one of the users' main goals in analyzing data. Users want to optimize and manipulate certain data given certain restraints. It is similar to querying a database, but expressed in a more visual way.
- Manipulation: It should be easy for users to modify one aspect of the visualization and see the effects in realtime. Users need to see information in the most efficient way, and thus need the ability to manipulate and interact with data visualizations.
- This can include tasks like dragging and dropping, zooming, and panning, as well as changing the method of visualization (e.g. web, map, graphic).
- Collaborating: Currently, users described collaboration in ANB as clumsy. This user task is one of the main motivations behind creating a web-based application. Users often need to annotate data, making notes both for themselves and to share with others. They will need the ability to insert text comments, highlight parts of the visualization, etc.
- Sharing: Analysts would like to be able to share their data and visualizations with superiors and co-workers.
- Data Sharing: It should be easy for users to choose the source of data for a given visualization, as well as to share their data sets with other users.
- Visualization Sharing: Users should be able to share their visualizations easily without having to export and import large amounts of information.
Throughout the semester, we will be in communication with our representative users to pinpoint the UI features that will be most useful to them.
1 Comment
Unknown User (juhokim@mit.edu)
Problem Statement
Although the general problem statement on visualization was a bit vague, the problem domain introduced is unique and specific. One thing that was not clear before the feedback meeting was what exactly is the problem that this project is trying to solve: is it the lack of interactive visualization tool or is it a specific problem Boingo struggles with involving WiFi towers in Africa?
User Analysis
The user analysis should describe specific user classes that are affected by the problem. The scope that the current write-up covers is too broad. When the scope is too broad, what you can learn from this exercise is also limited.
Task Analysis
The task breakdown is reasonable, and they are all significant tasks people perform. But maybe too significant! I wish the write-up had a more thorough analysis of sub-tasks that each of the main tasks contains.