Solomonic

Find friends for competitive gaming.

Role

Sr. product designer

2021

Teammates

Engineers (2)

Founders (3)

Researcher

Key tasks

Usability testing

Prototyping

Design system

Introduction

Solomonic provides insights into claims that are publicly available but hidden behind numerous complex systems which obscure relationships and data which can help law firms make critical decisions.

When I joined to help them refresh their products usability they were at an inflection point. preparing to build relationships with a number of much larger law firms than they were previously engaged with.

Solomonic was at a pivotal point for their business, after building an operational platform full of rich data and insights they had secured contracts with a number of small to medium sized law firms, but the platform itself was built rapidly and as a result its UX and UI design suffered.

Before injecting new funding and approaching larger clients, the founders needed a designer to lead a full research backed redesign over 12 weeks that improved user satisfaction and increased the number of insights and reports firms would pay to access.

Key Outcomes

New contracts: The new design is industry leading and played key role in Solomonic building relationships and signing deals with major law firms.

Complex data: Solomonic's complex and detailed product now has an intuitive design which serves inexperienced and experienced users alike, reflected in increased user satisfaction and adoption.

Future proof design system: In collaboration with the engineering team I lead the design of their component system which would enable engineers to work quickly and to a high-standard, as well as simplifying future feature design should their make that additional hire.

Jump to solutions→

Journey

Group audit, in-person testing and managing translation.

01.

Reviewing research material, and conducting heuristic review.

Before I joined Solomonic they worked with a user research over two months, the researcher had conducted qualitative and quantitative analysis which I used, in conjunction with a heuristic review, to design a loose requirements document.

02..

Ideating an elegant, data empowered design language.

As I joined Solomonic was also going through a redesign exercise which I was involved in. The primary goal was to deliver a snapshot of what’s to come to investors and the board, to start generating interest for their revitalised platforms.

03..

Aligning on design intent with wireframes.

I systemised design in a simple, approachable way that would suit the needs of Eblitz in the medium term, this was a balance we landed on that allowed us to continue iterating on the product in short time scales.

04..

Taking higher fidelity wireframes to existing customers.

I ran a number of usability tests with existing customers, they were tasked with locating different claims using different methods of search and filtering to assess time to and likelihood of task completion, we also surveyed user sentiment.

Analysis uncovered complexities with search that we hadn’t considered, but the filter and sidebar navigation worked as expected.

05..

Component based design system to create order and finalise visual style.

I ran a principles workshop with the engineering team to promote a sense of ownership over the design system, we also aligned on naming conventions and systematic approach.

We used a simplified version of atomic to organise components, and relied on light annotation (time was thin) to support engineers in delivery after I moved onto my next role.