Skip to the end
Product Design, Culture+

Designing the Culture+ admin dashboard to help organisations turn team data into action

My Role

  • Product Designer

Scope

  • User Research
  • UX Design
  • User Testing
  • Developer Collaboration

Platform

  • Culture+
  • The Honeycomb Works

Team

  • Research and Impact Lead
  • Data Analyst
  • Client Delivery Manager
  • Developers
Culture+ admin Team overview. Six engagement stage cards for the April to May 2024 feedback cycle, each with a count, a progress bar, the change from last week and an action button, next to an Engagement Center panel. Below are a Welcome to Culture+ panel, an admin checklist, a recruitment action list and a prompt to launch a belonging survey.

Overview

Culture+ is a behaviour change platform built with the Royal Academy of Engineering. It gives people anonymous 360 feedback and helps teams build better habits. The admin dashboard is where an organisation's admin, the "contact person" who manages the platform on behalf of their organisation (usually a founder, co-founder or HR lead), sets up their team, tracks engagement and reads the organisational report. My role covered research, design, testing and working with developers. I built the reporting rules with our research and impact lead, and the engagement patterns with our data analyst and client delivery manager.


The problem

Organisations needed to act on their team's data, but every step ran through our team. Setting up, monitoring engagement and reporting were done by hand: we tracked engagement for a long time with the data analyst and client delivery manager, and we sent each organisation a report ourselves once enough people had received feedback. Admins did not want to work that way. In research with 7 users, three things stood out:

I don't buy into having to ask for a report rather than just go and get it when I need it.

Admin, user research

I don't buy into not being able to onboard my own people.

Admin, user research

I'd assume that I'd be able to see what progress they've made.

Admin, user research

The engagement data showed a second problem. People signed up and then stalled: before we personalised onboarding, 23% of users were in the "signed up but did nothing" group. Emails from us alone did not fix it. Across a series of engagement experiments, several produced 0% engagement and one produced a single signup. The most useful learning was that the founder or CEO engaging was a strong sign the whole team would, which made the admin the person to design for.


The design challenge

How do you let an admin act on their team's data when nobody, including the admin, may be able to identify an individual?

Culture+ promises anonymous feedback, needs at least 4 reviewers before someone can receive a report, and is deliberately designed against surveillance. The question we used for every reporting decision was: does this expose an individual to harm? That created two rules for the design:

01

Everything is aggregate, and actions work without names.

An admin can nudge people who have not acted without ever seeing who they are.

02

Missing data is part of the design.

In small teams, many numbers cannot be reported safely, so those empty states needed to be clear, kind and a little delightful rather than looking broken.


The solution

The dashboard has three parts: a setup flow that starts teams with direction, a team overview built around the six stages of the journey, and an automated organisational report that ends in clear next steps.

1. Setup that starts the team with direction

The admin tells us about their organisation, builds a custom Honeycomb from their company values (typed in, uploaded, or pulled from a web page), then chooses how the team starts: a self-directed survey, a directed survey where the admin picks the focus areas, or a belonging survey. The directed survey is marked as our recommendation. Last, they invite the team by link, pasted emails, or from Google or Microsoft.

Setup screen headed "Tell us about your organisation", asking for the organisation's name, how many people work there, its funding stage or type, and whether it is currently hiring, with a Next button.
Step 1: tell us about your organisation
Setup screen headed "Start Building Your Custom Honeycomb", with three ways to share company values: type them into a text box, upload a PDF, DOCX or CSV document, or paste a link to a web page, then a Generate my custom Honeycomb button.
Step 2: build a custom Honeycomb from company values
Setup screen headed "Get your team started", offering three options as illustrated cards: Self-directed, where individuals choose the cells they want feedback on; Directed survey, tagged "Our recommendation", where the admin chooses the cells; and Belonging survey, to find out how the team feels about the organisation's culture.
Step 3: choose how the team starts
Confirmation screen with a large tick: "Great! You've created a directed survey for your team", showing the two chosen cells, Inclusive Communication and Valuing Feedback, as hexagons, with Continue and Change the cells buttons.
Step 4: the directed survey is set up
Setup screen headed "Invite your team mates to Culture+", with buttons to invite from Google or Microsoft, an invite link with a Copy link button, a box of pasted email addresses, and a Finish setup button.
Step 5: invite the team by link, email, Google or Microsoft

The recommendation comes from the data. When we introduced a personalised onboarding experience that recommends where to start and selects those areas by default, the share of users who signed up but did nothing fell from 23% to 6.7%. The most engaged organisations also tended to start with structure and move to self-directed use later.

23%
Signed up but did nothing, before personalised onboarding
6.7%
Signed up but did nothing, after personalised onboarding

2. A team overview built around six stages

I broke engagement into six stages that map to the product journey and its natural drop-off points: signed up, completed self-reviews, signed up but did nothing, invited reviewers, waiting for feedback, and received feedback. Each shows a count, the change from last week and, where it helps, one action. Each stage tells a different story and calls for a different nudge:

What three engagement stages can signal, and what the admin can do
Stage What it can signal What the admin can do
Signed up but did nothing People are overwhelmed and do not know where to start Send a reminder that recommends where to begin
Finished self-review, no reviewers invited A team too small to find 4 reviewers, not yet ready to ask for feedback, or needing more time to warm up to the platform Send a reminder with guidance matched to the reason
Asked for feedback, few have received it Reviewers are swamped and need a nudge Remind people to give the feedback they were asked for

Around the stages sit an admin checklist, an Engagement Center, a prompt to run a belonging survey, and a "quiet here" empty state that points a new admin to the first step: invite your team.

Team overview for the April to May 2024 feedback cycle. Six stage cards: signed up 6 of 58, completed self-reviews 4 of 6, signed up but did nothing 2 of 6, invited reviewers for feedback 3 of 6, waiting for feedback 2 of 6, and received feedback 1 of 6. Each shows the change from last week and a button such as Invite your team, Send reminders or Remind to re-engage. An Engagement Center panel links to guidance on giving good feedback, and below are an admin checklist with two of six steps done and a prompt to launch a belonging survey.
The team overview: six stages, each with a count, a weekly change and one action
Team overview empty state: an illustration of a small character asleep under a tree, with the heading "It's quiet here", the line "No engagements yet" and an Invite your team button, beside the Engagement Center, the Welcome to Culture+ panel and the admin checklist.
The "It's quiet here" empty state points a new admin to the first step

3. An automated organisational report

The report replaces the manual PDF so decision makers can engage with their team's behaviours themselves. It opens with sign-up and participation figures, the top area for improvement and the top strength, then breaks down into Cell overview, Behaviours, Demographics and Next steps tabs. Behaviours shows scores from self, managers and everyone else, how widely scores vary, and progress over time, each with a short insight.

Organisational report summary for the April to May 2024 feedback cycle. Cards show 24 of 30 users signed up, a participant engagement donut chart, and the most popular cell, Building a feedback culture, with 17 reviews. The area needing most improvement is Building a feedback culture at 72%, with Asking for feedback as the least practised behaviour at 76%. The area of strength is Curious, open, effective communication at 86%, with Using inclusive and respectful language as the most practised behaviour at 89%. Below are the Cell overview, Behaviours, Demographics and Next steps tabs.
The report summary: participation, the top area for improvement and the top strength

Built with our research and impact lead

The rules behind the report

The rules behind it were co-created with our research and impact lead. The report flags when:

  • Self scores differ from others by more than 10 percentage points
  • More than a third of people skip a behaviour
  • Managers score differently from everyone else

Our test for every screen was whether someone with five minutes could understand it.

Behaviours tab of the organisational report. A bar chart compares self, manager and everyone else's scores for four behaviours in the Curious, open and effective communication cell, beside filters and an insight analysis. Cards show the top area for improvement, Asks for feedback at 73%, and the top area of strength at 95%, each with comments. A line chart tracks progress of one behaviour over time for each group, with an insight on how each score changed, and a box plot shows how widely scores vary for each behaviour.
Behaviours: scores by group, progress over time and how widely scores vary

It ends in Next steps rather than a score: link the lowest-scoring behaviour to its habit card for the whole team, focus on the lowest-scoring cell, launch a directed survey as a follow-up, and suggest a belonging survey if the organisation has not run one in six months. The high priority action is a button, so the admin can act in one click.

Next steps tab headed "Here are your next actions". Two ticked points explain why asking the team for feedback is the first step and why leaders should model it. An Actions list links to a habit card challenge for the whole team, an article on bias in engineering, Honeycomb feedback and a belonging survey. A High Priority Action card asks the team to engage with the feedback process, with a Launch a directed survey button.
Next steps, with the high priority action as a one-click button

Where data cannot be reported safely, the report says so plainly. The demographics view, for example, shows "Not enough data to safely report this without identifying certain groups" instead of a chart.

Demographics tab. Donut charts break participants and reviewers down by gender. Below, the demographic breakdown of behaviour scores shows an empty chart reading "Not enough data to report", with an insight explaining there is not enough data to safely report this without identifying certain groups.
Demographics: "Not enough data" instead of a chart that could identify a group

What user testing told me

I tested the dashboard and report with admins and decision makers over several rounds and reviewed the sessions with the team. Five things shaped the design:

01

People wanted to know what to do, not just what the score was.

Next steps were the most valued part of the report, and they only worked when they were specific.

02

Some of our language did not land.

Terms like "other score", "high priority action", "cells" and "directed survey" caused hesitation. These are product words, not the words admins use.

03

Admins wanted more than an average.

They asked how widely scores varied and how things changed over time, which is why the report includes both.

04

Anonymity held, but it created a real tension.

Admins accepted that individuals stay hidden, yet some still asked to see who had not responded. Reminders that reach non-responders without revealing them are the current answer. How much visibility to give an admin against how much accountability they want is still an open question.

05

Inviting people needed to be effortless.

Admins preferred a shareable link, and many organisations work in Google, so inviting from Google or Microsoft mattered.


Outcomes & Impact

Impact on users & business

We saw a marked inprovement in user engagement and business outeomes:

Fewer new sign-ups left stalled after joining, once onboarding was personalised
71%
Of invited people completed their first personalised survey in an early pilot
83%
Of team time saved per organisation report
~12 hrs

What I would do next

01

Simplify the language across the dashboard and report, using the words admins use.

02

Resolve the tension between visibility and anonymity, starting with whether the waiting-for-feedback stage should have its own reminder.

03

Keep checking the six stages against real behaviour, so each nudge stays matched to why people stall.

What I learned

Designing for sensitive, aggregate data means the empty and withheld states carry as much weight as the full ones. Working with our research and impact lead to write the rules first made the screens simpler, because every design decision could point back to one question: does this expose an individual to harm?