Research plan for website

[melissamurphy]

Dependencies

#58
#59
#61
#68
#69

Overview

Create a guiding plan for website research outlining goals, research questions, and methods. The plan is a collaborative team effort to align site user research considerations with those of all project stakeholders; and as a living document, it will be periodically revised as research proceeds.

View Research Plan (in Research folder of Access the Data UI/UX Google Drive)

Action Items

Initial Writeup

• Refer to HackforLA guide - Research Plan How-To
• Refer to preexisting Access the Data research plan
• Review research considerations of Design Thinking
• Outline elements of research plan
• Get professional feedback on elements of research plan

Collaboration

• Meet with UX team to collaboratively write details of plan (9/14)
• Make note of working assumptions and research questions from Establishing the Knowns/Unknowns/Assumptions #61
• Confirm with workshop-side on project goals

Sections of Plan

• In Goals section of plan: add stakeholder goals (from FAQ, user persona board)
• In Goals: add site research context based on Framing the Problem #59
• In Methods: add summary of User Interview Script #58

Feedback

• Share plan with rest of project team at Wednesday meeting

Resources/Instructions

• Elements of Research Plan - nn/group
• Checklist for Planning Usability Studies - nn/g for detailing the Methods section
• Design Thinking - Don Norman

[abryant35]

@melissamurphy Please add update using this template (even if you have a pull request)

Progress: "What is the current status of your project? What have you completed and what is left to do?"
Blockers: "Difficulties or errors encountered."
Availability: "How much time will you have this week to work on this issue?"
ETA: "When do you expect this issue to be completed?"
Pictures: "Add any pictures of the visual changes made to the site so far."

If you need help, be sure to either: 1) ask for help at your next meeting, 2) put a "Status: Help Wanted" label on your issue and pull request, or 3) put up a request for assistance on the #access-the-data channel.

Thank you! :)

[abryant35]

@melissamurphy Please add update using this template (even if you have a pull request)

Progress: "What is the current status of your project? What have you completed and what is left to do?"
Blockers: "Difficulties or errors encountered."
Availability: "How much time will you have this week to work on this issue?"
ETA: "When do you expect this issue to be completed?"
Pictures: "Add any pictures of the visual changes made to the site so far."

If you need help, be sure to either: 1) ask for help at your next meeting, 2) put a "Status: Help Wanted" label on your issue and pull request, or 3) put up a request for assistance on the #access-the-data channel.

Thank you! :)

[melissamurphy]

Progress: We need to revisit the main research questions together to reflect our current aims and new roadmap as of yesterday.
The research plan was reviewed and revised with the workshop team 2 weeks ago. It is approved by Bonnie and remains to be seen by Julien (possibly this Friday 10/8).

Blockers: Waiting on card sort and possible further field study (contextual inquiry) issue completion in order to be added to the plan as our Discovery methods.

• Need to confirm at Wednesday 10/6 Meeting the methods we are going forward with (in addition to Survey and User Interviews).

Availability: 8 hours on this issue (*also working on Storyboarding issue and Participant Recruitment issue). Earlier in the plan's development, it took 16 hours/week. So far I have taken 4 hours this week checking over related research issues and doing background reading on methodology, particularly contextual inquiry.

ETA: It can be updated today 10/6 during our meeting based on methodology decisions.

[melissamurphy]

Removing "In Methods: add summary of Competitive Testing Script Create competitive interview questions #69" since issue #69 has been closed as an option.