Analytics for workspace admins

Workspace Analytics

One place for workspace admins to see how their team uses events and sessions.

Context

Professional · Pigeonhole Live

Timeline

Jan to Apr 2025

Team

With product managers & developers

Role

Lead Designer

Workspace Analytics dashboard with overview totals and charts for participants, sessions, interactions and Pigeonholes created
Overview

What it is

An analytics dashboard inside each Pigeonhole Live workspace. It shows participants, sessions, interactions and events created over a chosen period, and the data can be exported. It was released as a paid add-on.

Who it’s for

Workspace admins and organizers who need to track how their team uses the platform, for example to justify the cost at budget time or to give seats to the people who use them most.

What I did

As lead designer, I worked out which data to show and how to organise it, then designed the overview, the charts, the date filters and the export. I worked with product managers and developers throughout.

Focus Areas

Information Architecture, Data Visualization, Enterprise UX

Design Methods

Support-ticket review, data audit with developers, sketching, colour-vision checks

The problem

The data existed. Admins had no way to see it.

Pigeonhole Live is an audience engagement tool for events, meetings and conferences. The company held data for every event in a workspace, but organizers had no way to view it across all the events they had created.

Companies using Pigeonhole Live usually have several workspaces, one per team, with different events running at the same time. Without a dashboard, admins couldn’t monitor that activity or measure it accurately. Four things stood out.

01 Prove the value

Some admins have to justify their usage when budgets are reviewed.

02 Assign seats well

Admins want to give seats to the people who use the platform most.

03 See every event together

One view across all the events in a workspace, not one event at a time.

04 A standard SaaS feature

Users increasingly expect an analytics dashboard as a basic part of the product.

Research

Starting from what clients were already asking

There was no existing feature to build on. I had two things to work from: a record of client requests, and the company’s Data Retention Audit. To understand what admins wanted, we listed the most common support tickets from clients who had used Pigeonhole Live for at least two years.

Nine sticky notes with common client questions, such as which event performed best and whether team members are using the platform

The most common questions in support tickets from long-term clients.

01 The answers were already there

About 90% of these questions could be answered with data the company already held. It needed a way to be displayed.

02 The audit as a base

I started from the data points in the Data Retention Audit, then picked out the ones specific to a workspace: events created, sessions, polls used and user activity.

03 From data points to insights

We looked for more useful readings of the same data, such as the month-on-month change in events created.

Working with developers on the data

I worked with a few developers to find out what data we actually had and how it could be shown. Some of it was clear and easy to use. Other parts were missing or not detailed enough. We talked through what was possible and what users needed most, and made sure everything on the dashboard was accurate and useful.

Design decisions

Three decisions that shaped the dashboard

Each one comes from the questions admins were asking.

01

Totals first, then the breakdown

The page opens with an Overview of four totals: participants, sessions, interactions and Pigeonholes (events) created. A Breakdown section below gives each metric its own chart.

The date range and the Export Report button sit at the top of the page, next to the time the data was last updated. Changing the date range updates every figure and chart on the page.

What it enabled

One place for admins to keep track of how their workspace is being used.

Top of the Analytics page: date range selector, Export Report button and four overview totals

The top of the Analytics page: date range, export and the four overview totals. Shown with sample data.

02

Date filters that match how people think about time

Filter options follow the way people talk about time, like “last 30 days” or “this quarter”. They were based on what users wanted and what we found in research, not only on what was technically possible.

I sketched how the time axis should change with the length of the range, from months up to five-year steps. I also mapped which events fall inside a selected range, including the cases where the dashboard has nothing to show.

What it enabled

With the date filters, admins could see trends in event participation and session use.

Hand sketches of line charts showing how the time axis changes for ranges under 12 months, over one year, 1 to 12 years and 13 years or more

Sketches of the time axis for different range lengths.

Five diagrams of event timelines against a selected date range, showing when the dashboard is empty and when events are included

Cases for events inside and outside a selected range, including empty states.

03

Colours that stay readable for every vision type

The session and interaction charts use a wide range of colours, one for each type. I applied an inclusive, colour-blind safe palette, so the charts stay clear and readable for every vision type.

This matters because each colour stands for a variable: one session type or one interaction type. If two colours look alike to someone, they can no longer tell which type a segment belongs to. I checked the palette against eight simulated types of colour vision, shown below.

Both palettes follow the idea behind Viridis: sessions run from dark navy through teal and green to yellow, interactions from purple through pink and orange to yellow, with lightness rising along the way. So types differ in lightness as well as hue, and neither palette depends on telling red from green. Because these are categories, not a low-to-high scale, I kept the steps clearly separate, the principle behind the Okabe-Ito palette.

What it enabled

Charts that stay clear and readable for all vision types.

Session and interaction colour palettes and charts shown under normal vision and eight simulated colour vision types

The session and interaction palettes under normal vision and eight simulated colour vision types. Click to enlarge.

The dashboard

A chart for each question

The Breakdown section gives each metric its own chart. Each one was designed around something admins wanted to know. The charts below are animated: click one to replay it.

Participants

This chart compares signed-in and non-signed-in participants. The bar chart shows the totals, and the line chart breaks them down by month, with details on hover. I designed it to help admins find peak participation periods across events.

I paired a bar chart with a line chart because admins ask two different things: how many people in total, and when. The bars put the signed-in and non-signed-in totals side by side. The line shows each month in order, so the busiest months stand out.

Participants: totals on the left, the monthly trend on the right.

Sessions

This chart shows total sessions by type within the selected time range. Each type is colour-coded, so organizers can compare usage over the period and see which session types are used most and which are used least.

I chose stacked bars because each month has two readings: how many sessions ran, and which types they were. The height of a bar is the total, and its coloured segments are the types. A line across the top traces the total, so the trend stays clear even when the mix changes.

Sessions by type. Hover a column to focus on one month.

Interactions

This chart shows how participants interacted during events, with each interaction type colour-coded for comparison. It helps organizers see what engages their audience most, such as Q&A, and plan their events around it.

It uses the same stacked form as the Sessions chart, so the two can be read the same way. Each colour is one interaction type, and the legend on the left gives the total for each.

Interactions by type. Hover a column to focus on one month.

Pigeonholes created

This chart shows how many Pigeonholes (events) were created in the workspace each month. Admins can use it to spot their busiest periods and to judge whether their current plan still fits their usage.

I used a single line with a filled area because there is only one thing to follow here: how the number of events changes over time.

Pigeonholes created per month.

Pigeonholes table

Below the charts, a table lists every Pigeonhole within the selected period, with its sessions, participants and interactions.

It lets admins compare events side by side, for example two similar sessions held at different times of day.

Pigeonholes table listing each event with its status, date, sessions, participants and interactions

The Pigeonholes table, shown with sample data. Click to enlarge.

Results

What shipped

Workspace Analytics shipped as a curated analytics board in each workspace, for paid users.

01

Four totals up front

Participants, sessions, interactions and Pigeonholes created for the selected period.

02

A chart for each metric

Breakdowns by sign-in status, session type and interaction type.

03

Date filters

Ranges that follow how people think about time.

04

Data export

Organizers can export the data to Excel for further analysis, or share it as a PDF report.

How it was received

The dashboard was well received, especially by admins who had often sent feedback tickets asking for a way to keep track of how their workspace was being used. The date filters and charts made trends in event participation and session use simple to see, and organizers valued being able to export the data.

What I learned

A tight scope kept the structure clean

What worked

Scoping the feature to session groups kept the architecture clean, and aligning with existing insight structures reduced the risk of technical debt.

What was hard

Handling changes in session hierarchy, such as moving sessions between parents, was more complex than expected. We had to account for edge cases where the UI and data visibility didn’t align.

© 2026
© 2026
© 2026