Parties to many divorce proceedings unnecessarily choose litigation instead of settling even when a compromise is possible.
Underlying reason: In divorce proceedings, relationships tend to be acrimonious, and parties will subjectively believe they deserve a greater share of the asset then they actually do.
Lead-on consequences: (1) The parties themselves incur more time and money when embroiled in legal proceedings they unnecessarily received legal services, and (2) the society suffers loss as the judiciary system is unecessarily burdened by such cases.
An outcome simulator that:
Logging in and creating a new matter
Entering matter details and generating report
Viewing Report
Target users of the outcome simulator are lawyers and not the parties to the divorce themselves.
This is because parties would need to engage the lawyers in any case and it would make little sense for parties to learn a new platform for a divorce proceeding which doesn't happen more than a few times at most.
The prediction report shows only the information that are directly relevant to the particular case.
This is because early prototypes which contained charts and showed the data in various alternative scenarios proved a little to complicated for lawyers.
Lawyers spend unnecessarily time reinventing the wheel when developing their own document version control systems based on whichever office suite of technologies their firms are using.
Underlying reasons:
Lead-on Consequences:
A wrapper over GIT is written as a Microsoft Word add-in, where user can:
Editing and saving versions to history
Comparing with previous version
Sending for review
UX is designed to be as transparent as possible (e.g., no confirmation on successful operations)
No feedback is given on successful operation
This is because lawyers are used to using Microsoft suite of office tools, which similarly does not show any confirmation dialog on successful operations (like saving).
The .DOCX is converted to markdown (i.e., plaintext) behind the scenes before committing to GIT. This allows for display of changes on GIT clients
The add-in is really just a wrapper around GIT, Pandoc and TortoiseGIT, with specific workflows crafted around these tools.