3.6 KiB
3.6 KiB
eFiling — UX Analysis: E-Filing_in_Filevine_2min.mp4
| Field | Value |
|---|---|
| Source video | E-Filing_in_Filevine_2min.mp4 |
| Duration | 2m 0s |
| Analysis date | 2026-05-13 18:35 UTC |
| Model | ~google/gemini-flash-latest |
Sure! Here is a UX research analysis of the screen recording:
1. Overall Workflow Summary
The user is performing a legal e-filing process within the Filevine platform. The workflow involves selecting the filing type (E-File, Initial), checking off required document types, and then manually attaching corresponding PDF files from a project repository. The user experiences several interruptions due to validation errors and a non-intuitive document-matching process.
2. Friction Timeline
- 0:34 - 0:40: User navigates to "File and Serve" and clicks "Add Action."
- 0:41 - 0:47: Initial hesitation while selecting "Order Type" and "Filing Type."
- 0:48 - 0:58: User checks multiple document types (Summons, Complaint, etc.).
- 1:00 - 1:10: Major Friction Point: User attempts to "Create" but is blocked by a red validation message: "We cannot save because you are missing required fields or have invalid data." The user scrolls up and down, clearly confused about which field is missing.
- 1:11 - 1:20: User realizes "Filing Status" is required and selects "Unknown."
- 1:21 - 1:50: Inefficient Workflow: User must manually search and attach each document they previously checked off. They accidentally attach the wrong file at 1:42 and have to delete it.
- 1:51 - 2:00: Continued manual searching for the "Complaint" file.
3. Inferred User Intent
The user wants to quickly submit a set of standardized legal documents for a specific case. They expect the system to understand which files are needed based on the checkboxes and ideally "auto-map" them if they already exist in the project folder.
4. UX Issues Ranked by Severity
| Severity | Issue | Description |
|---|---|---|
| High | Vague Validation Errors | The error message at 1:05 doesn't highlight the specific missing field ("Filing Status"), forcing the user to hunt for the mistake. |
| High | Redundant Data Entry | The user checks "Complaint" in the list, then has to manually find and upload "Complaint.pdf." This is a double-entry task. |
| Medium | Poor UI Discoverability | The "Filing Status" dropdown is located far below the primary action area, making it easy to miss. |
| Medium | Lack of File Mapping | The system doesn't suggest files from the project folder that match the checked document types. |
| Low | Confusing Terminology | "Order Type" vs. "Filing Type" caused a brief moment of hesitation at the start. |
5. Suggested Improvements
- Inline Validation: Instead of a generic error message at the top, highlight the "Filing Status" field in red with the text "This field is required" as soon as the user tries to save.
- Smart File Suggestions: When a user checks "Summons," the "Add Docs" area should automatically suggest files named "Summons" or "Summons.pdf" from the current project folder.
- Workflow Consolidation: Combine the document checklist and the file upload area. Instead of two separate steps, provide an "Upload" button directly next to each document type (e.g., [x] Summons -> [Upload File]).
- Default Values: If "Initial" filing is selected, the system could default "Filing Status" to a logical starting state to reduce clicks.
- Visual Feedback: Use a "Progress Bar" or "Step Indicator" (1. Details, 2. Documents, 3. Review) to help the user understand where they are in the filing process.