Closed lynwilhelm closed 3 weeks ago
@SeanLeRoy @aswallace Not sure who wants to take a stab at providing a bit more info on this ticket, but I created it so we don't lose track of the need:)
@aswallace @SeanLeRoy
This UX ticket is complete. What is contains is design for:
Description
There are various situations where the system does not perform as expected and the user needs to be communicated with. They need to understand what went wrong and steps to resolve if possible. Different affordances and language may be required for each situation. Design just needs a list of all of the situations (with a representative scenario) to get started. We will need to work together on understanding what the system "knows" specifically vs generically and come up with some solutions. (i.e. do we know why something didn't load in certain situations, etc)
Below to be filled out by UX during kickoff Q&A to the best of current understanding
Size
Effort level (xs, sm, m, lg, xl)
Scope
What will we do? What will we NOT do?
User needs statement(s)
As a [type of user], I need/want to [action(s)], so that I can [goal].
Additional notes
Knowns/unknowns, stakeholders, time/dependency considerations, deliverables
One example in current UI: