Long before any code was committed, we conducted a lengthy series of research exercises, prototypes and client meetings. Conversations centered around project goals, user personas, comparable projects and the kind of site we needed to build.
Technical Architecture
LawHelpMN wanted a legal “triage” application, which users could use for help with specific legal issues. But how would this work? We needed to talk through and visualize the tool first. Our technical architect worked on a series of flowcharts and content models, defining the various taxonomies, paths, and requirements for this complex tool. Thanks to the charitable nature of the project, we were even able to converse with developers of triage tools in other states.
UX and Content Strategy
While technical planning was underway, other members of our team began to work on an improved user experience and content strategy. The first goal was to simplify the site navigation and messaging, making their choices clearer to end users. Unused or redundant links and content was eliminated, while relevant content was presented in easier to understand options alongside specific legal topics.
We emphasized plain-language and clarity for end users, making link choices easy to quickly understand and content easier to scan. Our team studied similar tools and websites in other legal aid websites for ideas and best-practices, and documented results for the client.
With a defined technical architecture and improved information architecture in hand, we moved on to design and development.