header-frame

Overview 📌


DASHBOARD

background

inClinico is a platform that provides data about targets, diseases, clinical trials, and scientists involved with the study at the preclinical and clinical stages. This case study will be focused on the database dashboard, the main goal of which is to present information about past clinical trials.

my role

I worked collaboratively in a team with front-end and back-end developers, a product manager, and a test engineer. I contributed as a UX/UI designer and was involved in the whole design process of the dashboard.

challenge

How can we help clinical scientists from the Pharma industry to identify red flags in ongoing clinical trials and suggest corrections to eliminate the red flags before the first patient is enrolled?

goals

• Provide a didactic resource that shows a comprehensive overview of past clinical trials.
• Enable users to search for clinical trials based on specific criteria.
• Make data clear and readable.

Research 🔍

interviews

We conducted a series of interviews with multiple users of the platform to gain insight into their expectations for the database dashboard and their opinions on the current sources they use. The survey comprised a combination of open-ended and closed questions.

In total, 11 participants responded to the surveys. The results we obtained aided in pinpointing potential content and features for the future dashboard with greater precision.

affinity map

Persona 👤

After conducting user research and gathering relevant information from each prospective user, we created a user persona. In developing the persona, we considered factors such as goals, frustrations, activities, and skills to ensure a comprehensive understanding of our target audience.

Ideation 💡

Following the conclusion of the user research phase, the team transitioned to brainstorming ideas. Every member of the product team engaged in this collaborative process, working together to devise potential design solutions aimed at resolving users' issues. Each team member offered input on dashboard features, enabling collective voting to identify the most promising concepts.

Task Flow ⚙️

In order to initiate the dashboard design process, it was crucial to conceptualize the flow initially. The primary objective was centered around a single task for users: searching for clinical trial data, whether with or without the use of filters.

Wireframes ✏️

The subsequent phase involved crafting wireframes to illustrate the placement and approximate appearance of interface elements. This procedure yielded a blueprint outlining the structure, layout, information, and functionalities of the dashboard. Consequently, it afforded us a clear understanding of both the operational aspects and visual depiction of the dashboard.

Styleguide 🎨

brand

type

icons

colors

The style guide for this project embodies a sleek and user-oriented design. Employing a minimalist approach directs attention to essential information and fosters intuitive comprehension of content relationships. Additionally, the design incorporates icons to ensure visual coherence and user-friendliness.

Final UI 🌟

To enhance usability by reducing cognitive load, we developed an interface that prioritizes information through monochromatic elements. This design choice helps users make quicker decisions and emphasizes important content. The layout focuses on minimizing user attention, preventing them from feeling overwhelmed by the information presented.

Usability Testing 📈

For the usability test, we selected 6 research scientists of varying genders and ages. Despite the dashboard primarily serving the purpose of searching for past clinical trials, each participant was assigned a set of tasks with variations in filtering options, such as selecting specific start/end years or choosing a particular therapeutic area.

outcomes

After conducting usability testing with each participant, we identified one minor element that was subsequently removed: the 'high-confidence only' switch in the predictions section. As every research scientist expects the most precise prediction statistics, it became apparent that nobody would be interested in a less informative option, rendering the switch unnecessary.

Before: Useless “high-confidence only” switch

After: “High-confidence only” switch removed

VIEW OTHER CASE STUDIES
footer-frame