Benevolent AI

Unites AI and cutting-edge science to discover and develop new medicines for complex diseases.

My Role

I collaborated with another designer and engineering team on an internal data-driven, web-based dashboard. I researched the problem space by working very closely with the end users. Finally, I took the lead in delivering the User Interface design of the dashboard.

The challenge

Making complex processes simple

Drug discovery is a highly complex process with many moving pieces. Lately, AI technology has been introduced to the process. We outlined three objectives:

1.

Improve the current workflows by merging different systems, methodologies and technologies under one umbrella.

2.

Unleash the new AI technology and introduce it smoothly into the system so that it can reach its highest potential

3.

Build trust and relationships with the users, and involve them in a process as much as possible.
Evolve together

The Approach

Getting to know each other

Understanding users’ current scenarios, workflows and pain points were crucial for setting the project in the right direction. I was excited to get to know the users, who were also my colleagues. Who are they? How do they work, and what do they struggle with? What do they care about; what is their philosophy? I spent much time discussing those topics directly with the users, brainstorming and exchanging and testing ideas daily. 

The Vision

Relationships

The nature of building an internal product is that you can create a very close relationship with the users. This allowed me to involve the users as much as it was possible. I wanted to ensure that we all share the same vision for the product and evolve together organically.

Design, Test, Repeat

Users were involved in developing the dashboard from the very early stages. As early adaptors, they could give us valuable feedback ‘on the go’. The goal was to be very agile and reactive to users’ feedback and suggestion. I ran usability testing at different stages of design. First, I focused on thoroughly testing the released product but also ran quick tests with users on paper wireframes or click-through, lo-fi prototypes. 

Keep it lean, keep it agile

We were required to move quickly; I wanted to focus on a highly efficient, lean approach allowing us to use different techniques simultaneously. Some parts of the product had to be just technical proof of concept; some were only sketches on a whiteboard. Other sections required high-fidelity UI.

As a team, we worked agilely to put those pieces together.

Outcomes

All good things must come to an end

I had a blast.

This was the most exciting project I worked on. I thrive on close relationships with users and building products that mean something, products that bring intrinsic value. Having an opportunity to work very closely with world-class scientists and technologists was a thrill. I had a blast!

I left something behind.

I finished my contract with benevolent after six months. I was there to introduce culture, vision, strategy and methodologies that allowed the team and product to evolve and take the direction it needed to be successful. I also built a design system and design guidelines, ensuring I am leaving behind solid foundations that can be built upon.

Previous
Previous

Virgin Media