Design Thinking Workshop: Priortization Grid

Date: 13th May 2020

Following the discussion of Assumptions & Questions, we "prioritized" the features we thought of on the basis of its feasibility and its value to users.

We classified the features in the following categories

High Feasibility & High Value to User

Value to user - 😍 and won't be very time-consuming.

1. A way to edit templates.
   1. The structure should be editable.
   2. A form should be there to assign the contract variables value.
2. Data of the contract is saved in the Word document itself. In simpler words, the data related to the contract shouldn't be stored in the writer's local disk instead, cloud storage should be integrated.
3. Ability to create templates for lawyers to use. At least one should be able to write the template and specify the variables for it. Writing Ergo logic isn't in the scope of this project yet.
4. The addition of an already created template to a doc should be feasible too.
5. A guided tour of the add-in on start-up which will aim to walk through a user about the functionalities of the add-in.
6. A way to make the creation of templates compatible with MS Word and VSCode simultaneously.

Utilities

Not much value to the user and is a little time-consuming for developers.

1. Export and Import of template CTAs in and out of the Word document.

Unwise

Features that have negligible value to the user and are also time-consuming to implement.

1. Integration of Outlook to notify either party of the reviewing or drafting of a contract.
2. Import templates from online legal resources.

Value to user - 😐 Not at all time-consuming for developers.

1. Add support for uploading logo in the contract.

Not much value to the user and is time-consuming for developers.

1. Adding a support from "Definition & Interpretation clauses" in contracts. (This is more of a cicero issue although.)