Splunk

McLaren Dashboard

Comparing race telemetry in one view.

My role: Product design · Custom dashboards
Attribution: Splunk project
Platform: Race telemetry
Focus: Telemetry comparison and information hierarchy

01 / Problem

Keep a race comparison connected to the moment on track.

The Splunk McLaren dashboard connects lap and sector selection with braking analysis, track position and paired onboard views.

A race comparison needs to stay attached to its driving context.

02 / What exists today

Laps, sectors, braking and video describe the same drive.

The surviving dashboard contains these different views of a lap. The archive does not include a separate before-screen or a recorded account of the previous workflow.

Several views describe the same drive.

03 / What’s wrong

A number loses meaning when its context is hard to follow.

The design problem is keeping driver, turn and lap context legible across several views. This is the rationale visible in the artifact, not a measured usability finding.

Numbers become harder to read when their context falls away.

04 / What I explored

Use one comparison language across the dashboard.

The design keeps a distinct color for each driver, anchors the data to track position, and places the onboard views together. The surviving material does not document earlier rejected layouts.

Use the same comparison cues across every view.

05 / Low-fi architecture

Connect selection, telemetry and driving context.

This explanatory model follows the relationships visible in the original dashboard. Chart shapes are illustrative and do not report race results.

System flowHow the pieces connect

Inputs

Lap + sector
Selected turn
Driver A / Driver B

The interaction

01Locate the comparison
02Read braking + telemetry
03Inspect paired onboard views

Outputs

Shared comparison context
Location + numerical evidence
Driving context

The same two driver keys connect track position, telemetry, and onboard views.

06 / Wireframes

Move from a lap to the evidence for a difference.

The reconstructed wireframes make the comparison sequence visible without the detail of the original interface.

Wireframe sequenceExplore the sequence

01 / 03

Anchor the comparison to a part of the lap

Race comparisonWireframe

LapSectorTurnDriver ADriver B

Circuit / selected turn

Comparative telemetryIllustrative shape · no measured data

Sector context

Sector 1Sector 2Sector 3

01Lap and sector selection give the numerical comparison a location.

Reconstructed from the documented design; sample content is illustrative.

07 / Solution

Read the metrics and the driving context together.

Consistent driver colors connect summaries and charts; the circuit map and sector timeline locate the comparison. Paired onboard views sit beneath the numerical evidence in the original design.

McLaren race telemetry dashboard comparing lap, sector, braking data, track position and onboard views — A Splunk project for McLaren: lap, sector, and turn comparison in the original dashboard design.

08 / Research

The interface survives; a study record does not.

No participant study or measured task results accompany this archive. A focused evaluation would test whether people can follow the same driver and turn across all views.

Following the comparison across views is the next thing to test.

09 / Outcome

A coherent telemetry comparison, shown in the original work.

The artifact demonstrates the information hierarchy and connected comparison. It does not establish faster analysis or an effect on race performance.

The original artifact shows a connected comparison.

Want to talk through the design decisions?

Next project

ShoppingScout↗

← All selected work