Neurobit Hub — Anjani

Introduction · The context

Clinical research involves a lot of moving parts. Researchers work with participants, health devices, questionnaires, tasks and large amounts of data, often across multiple tools. Neurobit Hub was built to bring these workflows together, giving research teams one place to create, manage and analyse clinical trials.

Objective · The goal

A clinical trial can run for weeks or months, with multiple activities happening at different stages. Researchers need to set up the trial, configure devices and questionnaires, assign tasks, collect participant data and analyse the results. Our goal was to bring this entire process into one connected experience, instead of making researchers stitch together multiple platforms.

Research · Understanding trials

I first needed to understand how clinical trials actually work and where researchers struggle today. I combined secondary research with interviews with researchers running active trials. I also worked closely with our co-founders, who came from research backgrounds. This helped us understand the nuances of clinical research and validate what we were learning.

Insights · Key findings

Research was spread across multiple toolsDifferent parts of a trial were managed in different platforms. Researchers constantly moved information between them, making the process tedious and prone to errors.

Devices and questionnaires were manually managedTrials could involve multiple devices, questionnaires and procedures. Keeping track of these often meant relying on documentation and spreadsheets.

Participant tasks needed better managementParticipants had tasks and instructions to complete throughout a trial. Researchers needed an easier way to assign, schedule and track them.

Communication was disconnectedResearchers and participants often relied on separate tools to communicate. This made conversations harder to manage within the context of the trial.

Participant data was manually trackedResearchers manually collected and consolidated participant data into large tables. As trials grew, these became increasingly difficult to manage.

Experience · Existing workflow

We mapped the complete clinical trial journey and the tools used at each stage. This helped us see that the biggest problem wasn't one particular workflow. It was the fragmentation between them.

Ideation · Exploring solutions

The goal was to explore how we could bring these disconnected workflows into one product without losing the flexibility researchers needed. We explored different ways to structure the trial, its participants, tasks, devices, questionnaires and data.

Opportunities · Areas to improve

After exploring different directions, we narrowed the scope around a few key opportunities

Bring the entire trial into one workspace
Make devices and questionnaires part of the trial setup
Simplify participant task management
Improve researcher-participant communication
Centralise participant data and results

Mapping · Opportunity mapping

We mapped these opportunities back onto the existing trial flow. This helped us understand where each feature would fit and gave us a clearer foundation for defining the information architecture and user flows.

Solution · Bringing it together

One place to manage the trial

All trial states could be created, managed and accessed within one unified experience.

A workspace for the entire trial

The trial workspace brings together everything researchers need to monitor and manage a trial.

Built for detailed analysis

Results are presented in a detailed, technical table so researchers can work with large amounts of trial data in one place.

Flexible questionnaires and sessions

Researchers can create and manage questionnaires, as well as configure post-trial participant sessions.

Tasks for participants

Researchers can create, assign and track tasks throughout the trial, giving participants clear instructions and researchers better visibility into progress.

Role · My contribution

I worked across the product experience, from understanding the clinical research workflow to defining the information architecture and designing the core workflows. I also helped establish Neurobit Hub's first design system, creating reusable foundations and components that could scale with the product.

Impact · The outcome

Neurobit Hub brought previously fragmented research workflows into one connected experience. Instead of managing different parts of a trial across multiple tools and spreadsheets, researchers could manage the core trial lifecycle from one place.

I can't fit everything I worked on into one case study. If you'd like to dig a little deeper into the project, feel free to reach out.