Do.Bono | The “Expert” Project

 

User Challenge

Finding legal help is a costly, timely, and emotionally arduous process. This is particularly true for indigent communities where costs often makes accessing legal help an impossibility.

 

My Design

Do.bono - A responsive application in 3-breakpoints that connects individuals in need of affordable legal assistance to attorneys looking to do pro bono (free) work. 

 

Primary Tools

Adobe XD ∙ Balsamiq ∙ Canva ∙ Figma ∙ FlowMapp ∙ Google Forms ∙ Marvel ∙ OmniGraffle ∙ OptimalSort ∙ Paper ∙ Sketch ∙ Talebook

Timeline

Project Workflow / Timeline

Project Workflow / Timeline

Preliminary Research Findings

 

“The 2017 Justice Gap Report of the Legal Services Corporation found that 86 percent of the civil legal problems reported by low-income Americans received inadequate or no legal help.”

 

72% of attorneys find their Pro bono cases indirectly through a referral program or acquaintance.

“4 out of 5 attorneys would like to do pro bono work, although finding the time and means to provide low-cost legal services to the needy remains a huge problem”

 

74% of Pro bono tasks done in 2016 was giving simple advice.

“A Report on the Pro Bono Work of America’s Lawyers” - Supporting Justice, ABA Standing Committee on Pro Bono & Public Services

Testing Assumptions

 

Research Method

In-person recorded interviews and online survey.
Interview script

Primary Research Questions

  1. How often does the average person not get the legal help they need?

  2. What assumptions about the legal field do average people have that stops them from getting help? What assumptions compel them to get legal help?

  3. What category of legal issues are people least likely to seek help for?

Participants

  • 5 in-person participants

  • 18 survey participants

  • Age range 18-64

Primary Research Findings

  • All interview participants and 80% of survey participants cited a situation when they needed legal help and were unable or extremely hesitant to get it. Very common problem.

  • There is a wide spectrum of emotional and financial concerns that effects peoples decisions to seek legal help. Further research would be required to understand correlation between users situation and their decisions. Often cited concerns included:

    1. Feelings of being overly litigious

    2. Not wanting to deal with emotional burden of dealing with lawsuit

    3. Difficulty finding help

    4. Legal costs

    5. Users personal opinions of the legal field.

  • Cost was a primary concern all participants cited. Non-contingency based legal problems are the most expensive ones so these issues are the most likely to not be served. Analyzed findings

Problems & Solutions

 

It’s too Expensive

Having to miss work, paying for parking and transportation; apart from the cost of the legal services, there are a lot of expenses that add

It Takes too Long

Time is often an important factor in legal situations. Making appointments, visiting different attorney offices, getting their opinions and quotes; it takes too long to get legal help.

It Sucks to Go Through

People are potentially going through the worst experiences of their life when seeking legal help. Having to deal with the emotional burden of the situation in addition to having to shop for an attorney is too miserable an experience.

Lets Make it Cheaper

By making appointments online, a huge amount of cost associated with this process is reduced. There are also programs and attorneys that are available for lower-income individuals; it is just the infrastructure that would connect these two groups that is missing.

Lets Make it Faster

By providing a quicker means of connecting with attorneys and a quicker means of answering client questions, a online platform would significantly reduce the amount of time it takes to get legal help.

Lets Make it Suck Less

By making it cheaper and faster to meet multiple qualified attorneys

User Personas, Journeys, and Flows

 

Persona

Erica - Student / Young professional

Primary Motivation / Frustration

Motivation: Becoming self-sufficient and supporting older family.

Frustrations: Being misunderstood. Ineffective communication is a huge pet peeve and she hates it when attorneys don’t seem to be really listening to her concerns.

Task Flow / Journey Map Objective

Schedule a second meeting with her attorney to go over the outcomes of the last hearing.

Persona

Ruben - Small family business owner

Primary Motivation / Frustration

Motivation: Wants to bring family business in-line with local legal requirements in an attempt to expand.

Frustrations: Hates fluff. Pragmatic person. Finds the air of importance and superiority surrounding legal field to be obnoxious.

Task Flow / Journey Map Objective

Speak to an attorney for an initial consultation regarding his primary motivation.

Other Personas and a closer look Journeys / Flows

Sitemap Refined with OptimalSort

I conducted card sorts and analyzed my findings using OptimalSort to refine my mobile sitemap.

Sitemap Before

  • Sitemap flow didn’t have enough emphasis on main goal of design which is to get user in contact with someone that can assist them.

  • Pages that would be required in certain user journeys were not accessible in the areas they were required.

Sitemap After

  • Clear emphasis on getting people connected with help.

  • Onboarding changed from static guide to to an interactive feature that funnels into main features being interacted with.

  • Added peripheral “resources” page for miscellaneous information that may be helpful but is not essential to main features.

Prototype Iteration Process

  • With my sitemap refined, I created some wireframes to create a tangible version of my design.

    • 3 main task flows ( Find Attorney, Video with Attorney, Post Your Case)

    • Co-existing hierarchy

    • Tabs used has main navigation pattern to reduce cognitive load

  • Using these wireframes as a guide, I created paper prototypes to create an interactive version of my design I could user test.


    Altered from previous iteration:

    • Navigation tabs located at top

    • Horizontal array grid of 3x3 featuring attorneys with only a picture and minimal information under

    • Menu navigation added to upper left

    • Profile settings added to upper right.

  • User Testing showed multiple points in the design where people struggled.

    Altered from previous iteration:

    • Scrolling date selection —-> Expanding Calendar date selection

    • Visual elements added to tabs to distinguish each one

    • Onboarding incorporated into design

  • Further testing of my mid-fid prototypes lead to other enhancements.

    Altered from previous iteration:

    • Accessibility considerations (color testing, alt text added to images, transcripts to important parts of design, etc.)

    • Color, interactions, and emotional design considerations added to design

    • Fewer featured attorneys with much more information about each one available from home screen

    • Added badges that highlight unique attorney qualifications (children advocate, lgbtq+ friendly, etc.)

High-fid Usability Tests

 

Research Method

Online moderated usability tests.
Usability Test Plan

Primary Research Questions

  1. Will users be able to tell what each tab is for without having to explore the app too much? (I wanted these tabs to be intuitive at a glance as such my design was intended for a wide demographic)

  2. Is the design easy to navigate? What issues are people having when navigating around the app?

Participants

  • 6 participants

  • Age range 18-64

Primary Research Findings

  • All interview participants and 80% of survey participants cited a situation when they needed legal help and were unable or extremely hesitant to get it. Very common problem.n text goes here

  • My older participants had a hard time recognizing what the tabs containing the unique task flows were for without exploring them.

Design System & Handoff

 

Summary

 

Things That Went Well

  • It always surprised me how bountiful the user testing sessions were. Regardless of the small participant pools and my limited experience, I left each session with a clear understanding of somethings that worked and some that didn’t.

  • My initial research and competitive analysis was very convincing of the fact that this was a viable product and a space that people really needed help in. Although some of the typical constraints that a project would normally have were fabricated, the problem and my potential solution were very real to me. 

Things I Would Do Differently

  • I noticed that a lot of the progress being made was from the testing sessions. Once I got past the paper prototypes, I kept ideating features further and always building them out in digital format. I would spend a lot of time fleshing something out only to test it and see something didn’t work. In the future I will spend more time with low-fid prototype testing before moving on to higher resolution designs. 

  • My UI combines material and IOS frameworks and I think it makes the UI look slightly outdated. I kept finding design elements from different frameworks that worked better in regards to UX (Material.io expanding calendar vs IOS scrolling date selector, for example) but I think the overall effect on the UI isn’t positive.

  • I found myself prioritizing unimportant aspects of the design and altering already tested elements in order to get said aspects to work. I would eventually catch on to the fact that I was doing this and had to spend time course-correcting. I spent a long time, for example, trying to get the entire design to have a neumorphic look but it was really not working. 

What I’d Do Next

  • A lot of the constraints I put on this project were focused on the user as the dominate stakeholder. In order to move the project forward, a more developed marketing strategy and development constraints would be required. Armed with a marketing plan and development plan, I would be able to iterate on the design and make other stakeholders key components like I have with user.

  • Testing would be required of the first live version to see if KPIs that were set in the beginning of the project are being met.

  • I would love to develop the UI of the design even further while adding or fixing features that live users brought attention to.