Design/Eng walk through pilot mocks together

[kristen101606]

Description

Design is currently working on a set of mockups that will match our vision for the pilot interface. These mocks will also be used in the next round of usability testing. Design and engineering should walk through these mockups and determine if there are any areas that are unfeasible or require further discussion.

Key Questions

• Are there any areas of the mockups that are unclear?
• Are there any aspects of the mockups that don't appear feasible for the pilot?
• If so, what are some feasible alternatives that design should test in the next round of user testing?

Objective

Ensure that engineering and design are on the same page about what the pilot interface will look like and how it will behave.

Resources

Mockups are not yet ready, but will be shared in this Figma file.

Acceptance Criteria

• [ ] Design has shared the finished or near-finished mockups with engineering
• [ ] Design and Engineering have taken an in-depth look at the mockups and the flows
• [ ] Additional tickets are created to resolve un-answered questions, as needed

[kristen101606]

We did a walkthrough of the 21-22 mocks during standup on June 18th. We identified a few areas that are not feasible with the current backend structure. My understanding is that if we move to Vets API, these issues disappear.

Once we land on a decision about using Vets API or not, we should revisit the 21-22 mocks to assess if there are any areas that are not technically feasible to implement, or if there are any improvements we can make.