back
Templated Guide
Problem Statement
Process of creating an obligation description may be hard to follow if each analyst writes it in their own way. There needs to be a way to provide a more structured guidance.
User Personas
Analysis of publications and definition of obligations was given to internal staff. In most cases all staff would be co-located but for larger jurisdictions we had to consider them to be in different time zones.
Empathy Map
Through qualitativbe user interview with analysts and managers, I have created an empathy map that has provided us with guidance on ways to improve current process.
Process Flow
In order for users to create obligations in a uniform fashion, product leadership has identified a need for templatizing the process. Analysts would choose from available templates to create obligation. If no appropriate template was created, analyst would have to request one to be created.
Key Research Findings
After conducting several user interviews we've gathered some key goals and frustrations. It helped us with guidance for our design decisions.
Rough Wireframes
Discoveries + Iterations
Initial designs proposed by the team proved to have several heuristic issues. We have observed that affordances was not easily observed and some tasks proved tedious to accomplish.
1
Interaction was designed around dragging and dropping each parameter in place. This functionality was highlighted in design reviews as a potential problem in terms of accessibility.
2
List of available parameters were below the fold and were not easy to access for a reference when building a template. 3
This approach was also considered inflexible. If more parameters were to be added, finding a reference would become increasingly difficult.
Improvements
We have introduced a template list view to help administrators manage templates. They would be able to see how many templates are in use. To help users find what they were looking for, we have introduced pages that would assist in narrowing down results. They would be able to see the structure of each template and adjust it as they see fit.
After several rounds of iterations and peer reviews, I've arrived at design that has addressed all of user's goals and eliminated frustrations.
1
Instead of drag and drop interaction, I have suggested that we convert hash tag text into parameters. This has addressed the accessibility issue and has made the interaction faster and more intuitive.
In order to provide some guidance 2
we've included a short guidance for the user. 3
Parameter values would be readily available and relevant to template content.
During usability workshops we've noticed that some users were not confident if template they created would make sense to analysts.
4
In order to eliminate issue, template preview was introduced. User would be able to test their work to ensure it is structured as intended.
Once template was created, analyst would be able to
5
select it from list of relevant templates.
Analyst would not have to worry about format of the description as the structure would already be provided. For each clause that required an obligation they would have a clear guidance of format they needed to follow in order to provide data that clause has described.
6
Depending on how each paramater was set up by administrator, analyst would see only relevant values and be able to either make a single selection, multi selection or provide free text input.
Responsive + Dark Theme
Although app was not intended to be used on mobile devices, it became quite apparent from user interviews that many analysts had multiple windows open as they were multitasking. We started to produce version of key screens in dark theme with intention to reduce eye strain.
Outcome and Takeaways
Feature has enabled clients to create custom templates that follow guidance and standards which are compliant in their industry. Improved experience has reduced training and document analysis dramatically.
Dribbble
Behance
Art Store