When attorneys begin looking at case documents in Reader, they want to see annotation suggestions so they can organize and mark items faster for prioritization.
When attorneys are in Reader in document view mode, they want to see tips and suggestions on document to point them towards potential places to leave critical comments and verify document types.
Problem statement
Provisional
Attorneys are required to view 1-1,000+ documents for a case and they arrive with no order or organization. Filtering and sorting aren't helpful until they've manually annotated parts of each document which can take a lot of time. This is potentially a large bottleneck for the appeals decision writing and reviewing process.
What is out of scope?
Background/context
Attorneys (to ask Dustin or John Gosnell)
Not only just power users, but also normal users as well. We don't know the distribution. We want to appease the masses
What are the unknowns?
For research tickets only: What questions do we hope to answer? What are our learning goals?
How much time do you spend in Reader? Do you use the functions? Why/why not?
Do you still do it manually? Why?
What do you like or not like about it?
If Caseflow suggested categories, tags, what do you think about that idea? How much do you want these changes?
Identify any pain points? (slide in these ideas for suggestions)
What do you wish you could change about it?
Do attorneys on the same judge teams have the same habits and behavior patterns?
Existing design and content
Success criteria
Attorneys reviewing documents faster
Attorneys drafting decisions faster
Judges finding critical information faster
Reduced number of items overlooked or inaccurate data
Job story
Provisional Job Stories
Problem statement
Provisional
Attorneys are required to view 1-1,000+ documents for a case and they arrive with no order or organization. Filtering and sorting aren't helpful until they've manually annotated parts of each document which can take a lot of time. This is potentially a large bottleneck for the appeals decision writing and reviewing process.
What is out of scope?
Background/context
What are the unknowns?
For research tickets only: What questions do we hope to answer? What are our learning goals?
Existing design and content
Success criteria
Technical/logistical constraints (if known)