The project

Overview

Biosignals Studio is a software created to acquire data for research, mainly in the health area. It connects to different devices and biosensors for acquisition, filtering, processes data and creates visual charts and reports for analysis, both in real time or not.

This project involved both redesigning an existing product and creating something new. Using older software as a foundation, I designed an entirely new user experience for this health sensor reader initially called OpenSignals. Intended to be a desktop software, the project underwent many changes. This resulted in the release of a mobile app first, with a desktop version currently in progress.

The company

Plux Biosignals provides biosignals engineering tools & services to build biosignals products & medical devices that can be used for research, on the health area and even sports, all that while meeting all industry standards and beyond.

Research

Strategy

To gain a better understanding of the product, customers, and their needs, it was necessary to conduct user interviews, learn about the software, and deepen my understanding of data acquisition and the devices used. I also needed to explore how the software could be utilised in various contexts.

Stakeholders and the team

The meeting started by defining the project’s scope, timeline, and expectations. I learned about health data acquisition, company devices, and the previous software version. Collaborating with various teams helped me understand the full scenario and present solutions. We held many similar meetings with developers and stakeholders throughout the project.

Benchmarking

In order to understand what could be done and what are Plux strengths, I studied a few competitors and similar products in the market. It helped me to see their best features, weak points and define how to designer features that can help differentiate our product.

The personas

Rick the Researcher

Morty the Researcher

This persona represents the user who is responsible for data acquisition, organisation, and analysis in the research area. They hold significant control and authority within labs.

Morty the Researcher

The objective of this persona is to embody the individual responsible for software development. This includes the integration of devices and algorithm development, such as data processing, within the research area.

Jerry the Professor

Morty the Researcher

Jerry the Professor

This persona embodies a typical college professor who specializes in Human Cognition and Biosignals analysis and processing. He represents our users in the education sector, introducing our software to a new generation.

💡Iconography

Some of the buttons and icons used on the original software are not clear and confuses users a lot, specially when they use the software for the first time.

💡Settings

💡Iconography

The settings are not organized in an intuitive way and sometimes users need to search a lot to find something that should be simple.

💡Plugins

💡Iconography

💡Connections

Using plugins can be a little tricky and the space dedicated to that on the acquisition screen is too small, specially for plugins with graphs.

💡Connections

💡Data analysis

💡Connections

Connecting and setting up devices is not only complicated as there can be a lot of information, but is also affected by a few bugs and bluetooth problems.

💡Data analysis

While other companies can have complicated softwares, their graphs and information are showed in more clear ways.

💡Dark mode

💡Data analysis

Not having dark mode can be a problem when the tests are made in dark spaces where too much light can be a problem.

Tests and prototypes

First usability tests

High-fidelity prototype

For the initial usability tests, I experimented with different menus and icons, addressing issues from the legacy software. We decided to use labels for buttons and menus due to the specificity of the information. I also tested wireframes internally to ensure we were on the right track.

High-fidelity prototype

After the first round of tests, I created the main prototype that would be used for more usability tests and later to help the developers on their work. I created a prototype that would cover most of the features and the main user journey and later created a few more pages to include some details that needed more attention.

Final usability tests insights

📌 Plugins size

Some users automatically tried to change the plugins screen size. We decided to make it adaptable.

📌 View modes

📌 Plugins size

Users wanted to view the acquistion graphs in a “dashboard” view. Now we offer 3 different view modes.

📌 Device channels

📌 Confirmation screen

Users got confused choosing the device channels on the device settings. We can show the device illustration on that screen.

📌 Confirmation screen

People wanted to confirm information before starting an acquisition. It is possible to add a confirmation screen before that.

The project

Overview

The company

Research

Strategy

Stakeholders and the team

Benchmarking

The personas

Rick the Researcher

Morty the Researcher

Morty the Researcher

Morty the Researcher

Morty the Researcher

Morty the Researcher

Jerry the Professor

Morty the Researcher

Jerry the Professor

User interviews

💡Iconography

💡Iconography

💡Iconography

💡Settings

💡Iconography

💡Iconography

💡Plugins

💡Iconography

💡Connections

💡Connections

💡Data analysis

💡Connections

💡Data analysis

💡Data analysis

💡Data analysis

💡Dark mode

💡Data analysis

💡Data analysis

Information architecture

Wireframing

Tests and prototypes

First usability tests

High-fidelity prototype

High-fidelity prototype

High-fidelity prototype

High-fidelity prototype

High-fidelity prototype

Final usability tests insights

📌 Plugins size

📌 Plugins size

📌 Plugins size

📌 View modes

📌 Plugins size

📌 Plugins size

📌 Device channels

📌 Confirmation screen

📌 Confirmation screen

📌 Confirmation screen

📌 Confirmation screen

📌 Confirmation screen

The final product

Thank you!

This website uses cookies.