Drone User-testing Meeting Notes
- Elizabeth Seyler
01-08-2024
Attending: Steven, Mikah, Chris, Marguerite, Elizabeth
Drone Testing Results
Marguerite presented a summary of the drone testing results.
How to prioritize the dev projects? Chris: we can select three categories: yes for sure, gray zone, not feasible. Most are front-end issues that aren’t big lifts. Steven: we should consider the time these will take. Marg: Akshat and Jinam could look at the spreadsheet and select which are feasible.
Next steps:
Chris will take first crack at prioritizing these possible fixes, using the spreadsheet of all responses. Then we can reconvene.
Steven: we also need quick input from Amanda.
WCCC
Steven: met with them today. When will there be a viewable product? Data verification and viewable on the front end. When can we commence user testing? What is the scope/scale of that testing? They’re running lean and one is a bit anxious about workload. We could own the testing and maybe more of the facilitators. Could we provide facils. They’re eager to get this done. Can we have a viewable product in Feb? Mikah: not clear on realistic timeline. Meeting with them tomorrow to figure that out. Steven: can we do user testing this March for six weeks? Then integrate feedback in summer so they have finished product in fall? Marg: we could be avail in March bc VegSpec testing will be done in Feb. Steve: could we do the data verification for the west? We could do it more quickly than WCCC could; Victoria, et al.
12-02-2024
Attending: Attending: Marguerite Dibble, Chris Reberg-Horton, Elizabeth Seyler, Jinam Shah, Akshat Nitin Savla, Mikah Pinegar, Rob Austin
Intro 9:15-9:45
Chris big picture: will explain history and why we’re doing the project.
Jinam and Rob: will give brief overview of the tool, as well as explain App 1 and App 2 pieces; each page of tool and what they do and how.
GT will send us a list of the important things to cover
Break into groups 9:45-10:45
Chris: we have many bio/plant breeder/researcher people (9). A few in the admin category (3). Expert flyers of drones, just a few.
Eliz and Chris avail to lead groups by asking questions and taking notes, in addition to Shannon and Marg.
Two groups of plant breeders, and we could add a third if needed. One group for admin, one group for drone experts. Ceiling of 8-10 people per group.
Marg: really good idea to have people complete a survey at the end for 5 minutes. QR code for each group.
Chris: combine the admin and drone people as long as we don’t have more of them.
We’re emphasizing in-person.
Rob can be a floater to answer subject matter questions as needed in all groups. Groups 1 and 2, Shannon and Marg; Group 3, Chris and Eliz; Group 4 (if any), Eliz.
We’ll connect everyone to the VPN, then they’ll go to the website. People will bring their own laptops so they can explore.
Features/sections: finding the missions, picking your missions, create your grid, your plot
general, non-leading questions during the sessions; more specific multiple choice questions in the survey
Chris: we’ll want to test this again in 2025 bc this will become a national tool.
Rob: people may not even know that they might want vegetative indices, plant classifications. Marg: we’ll include those in the survey.
General questions after the specific pages/sections.
Not necessary to keep track of who says what in the discussions. We can get names and roles in the survey.
Next Steps:
Rob will send GT a list of the kinds of things to include in the survey
GT will draft: one-page agenda, questions for your groups, survey
Meet at the Auditorium at Oval St building on the first floor, down some stairs and a bit to the left.
11-12-2024
Attending: Attending: Marguerite Dibble, Chris Reberg-Horton, Elizabeth Seyler, Heather Darby, Jinam Shah, Anna Morrow, Akshat Nitin Savla, Mikah Pinegar
GT gives feedback on the drone software design. Marguerite’s goals: understand the tool better and see if her ideas make sense.
First page: select the location and dates. She was unsure what she was supposed to do. Put instructions on side and/or a gif of the action of drawing a box. If you don’t enter what’s needed, you get a red outline.
Question: how likely people use mobile for this? Chris: Not likely at all.
Question: is language Ok for the audience? Use consistent words would help: find missions, sort missions, select missions. Jinam: There is no product title now, which limited what we did so far. Marg: we can user-test this question.
Question: How much control do we have on the stylization of the tool itself? Jinam: we have control. Marg: draw button could be more clear. Also, maybe add instructions bar to top of the map to communicate what users can be doing at any moment.
Also, where to put the Next button? Kind of hidden at lower right.
Main page: all flights available within area/date. Display zone. Grid dimensions, other impacts and data points on the grid.
Question: titles could be more descriptive and feel more like buttons
Put all controls for the map together. Map can take up more space.
Present the missions with dates and % cover, but could use whatever’s most useful. Drop-downs could show more information about each mission/flight.
Could add filters at the top.
Jinam: overall, he loves it. We can start adding camera info, too. Esp mutlispectral vs RGB. Marg: we could ask about this in the testing--what to include on this page.
Chris: when do we see the field names? Jinam: at the beginning when choosing the location.
Marg: when you select a mission, it pops to the top, and the map shows up with a tool box that impacts the grid controls. Keeping all things that affect the map together. You can minimize what you don’t want to look at. You can minimize the missions you don’t want to see, and focus on manipulating the map you’re seeing.
Jinam: not sure the grid line choices can go inside the map. Marg: we could move them outside the map. We could even show this kind of thing for testing purposes. Mikah: logic inside the map can be complicated for all the tools. Would be better to keep logic outside. He likes the collapsible options to increase the map dimensions. Better bc it wouldn’t change the logic of the map. Akshat: button could be overlaid on the map but not part of the map itself. That could be an easy solution. Mikah: problem: you’ll overlay on things that are important. You’d have to close the map to use it, though. Marg: we can totally move things to sidebars. Mikah: we can change the dimensions of the map easily.
Final page: see full plot grid on one side, see the mission, but button for “export map.” Edit right next to the plot name.
Question: how much of the output should be visible here, not just when it's exported. Should users be able to compare things on this grid? Jinam: yes, two columns for the RGB or multispectral image info would fit.
Chris: we may want to add more. Have a filter and check off what goes into the export can be helpful. Gray out what’s not available.
Mikah: have check boxes to select the columns you want to see in the grid
GT will clean up these mockups. Want testing feedback on any of these things before we build it in? Chris: yes, now is the time prioritize. Biggest lift is the polygon map parts; we’ve been debating this. We either bring in another developer or we say that’s off the table and check during user testing. Mikah: not sure it makes sense to do the map stuff, maybe better to get the other stuff done. Jinam: some things on the flights page would be easy for us to do.
Next step: GT will integrate this feedback and send new mockups to the team for review. Will also begin putting together proposed agenda items for Dec 9 user testing.