Xplanner

The Challenges

Business Challenges

Unified platform

Create one system for experiment planning, execution, and documentation.

Real flexibility

Support diverse research workflows where each experiment is different and protocols constantly evolve.

Effortless adoption

Enable researchers to adopt the tool without adding work to their overloaded schedule.

Design Challenges

Unfamiliar domain

Design for a complex scientific environment where a single experiment spans hours with parallel processes.

Lab conditions

Account for gloves, distance from screen, and high cognitive load during experiments.

Competitive Analysis

Simple pen & Paper

Text-based protocols

Experiments are primarily documented as written text rather than visual workflows.

Common

Documentation and records

Designed to capture protocols, observations, and experiment history.

Common

Linear structure

Experiments are organized as sequential steps, read from top to bottom.

Common

Manual input

Researchers are expected to write and maintain information themselves.

Common

User Research

Key Insights

Design

Building the experiment as a visual flow

Researchers described experiments as processes, not documents.

To support that, I designed the setup as a visual workflow, connecting materials, equipment, and actions in context instead of text.

Closer look: One continuous flow

An experiment is defined by the relationships between materials, equipment, and actions.

I kept them in one visual flow, allowing the protocol to be understood through context instead of text.

Running the experiment in the same flow

During a live experiment, attention is split and hands are busy.

To reduce that load, I kept execution inside the same flow researchers already built, keeping the current step and progress always visible so nothing has to be re-learned mid-task.

Closer look: Stay oriented

Experiments are rarely completed in one uninterrupted session.

To make returning easier, I kept the current step and overall progress visible, so researchers do not have to retrace the protocol after looking away.

Editing without leaving the flow

Protocols rarely stay fixed once work begins.

To support those small adjustments, I kept editing inside the same workspace instead of moving researchers to a separate screen, so the experiment never disappears from view.

Closer look: Adding or editing notes

Not every detail belongs inside a workflow step. I created a space for experiment-wide notes, allowing researchers to keep assumptions and reminders with the protocol.

Closer look: Notes while running

Experiments rarely unfold exactly as planned. I allowed researchers to attach notes to the current step, so observations become part of the protocol while the work is still happening.

Conclusions

1. Planning, execution, and documentation work best as one connected experience.
2. Designing around existing research habits can be more valuable than creating new ones.
3. Experiments rarely go exactly as planned, and the workflow should be able to evolve with them.