Attendee List for Toolbox Talks Version 2.0

Attendee List for Toolbox Talks Version 2.0

Attendee List for Toolbox Talks Version 2.0

An attendee list that's as easy to create as a Spotify playlist

Role

Solo Product Designer

Feature Type

Feature

0 to 1

Platform

ISN's Empower App, Toolbox Talks v2.0

Empower App, Toolbox Talks v2.0

Status

Shipped Apr 2025

Duration

3-4 weeks

Team

PM, Dev Lead and other developers

CONTEXT

Designed this because the users asked for it

In April 2024, we launched Toolbox Talks in the Empower app, ISN’s mobile product for contractors. Toolbox Talks, are safety guidelines for different tasks, which were made easily accessible through this AI-powered feature. (Prototype on the right.)



During beta testing, users frequently asked, "How do I see who attended or read the Toolbox Talk?"

Based on this feedback, the PM and CTO planned to include this feature in Toolbox Talk v2.0.

PROBLEM

How might we help a contractor see who attended or read the Toolbox Talk?

FINAL SOLUTION

We shipped 'Create an Attendee List' feature

The solution enables users to easily create and manage attendee lists for Toolbox Talks. They can add attendees by typing their names or selecting from recent entries, link the list to a company, and generate a shareable PDF for their team.

IMPACT

73% of feature visitors completed the flow and created a list; 39% went on to share it.
Sped up design-development collaboration
Sped up design-development collaboration
Sped up design-development collaboration

Created a Teams chat for immediate responses to developer queries and ran 1:1 calls to resolve issues in the moment, simulating an in-person experience instead of having developers upload screenshots to a portal for me to answer later.

Created a Teams chat for immediate responses to developer queries and ran 1:1 calls to resolve issues in the moment, simulating an in-person experience instead of having developers upload screenshots to a portal for me to answer later.

Redefined design workflow with end-to-end ownership
Redefined design workflow with end-to-end ownership
Redefined design workflow with end-to-end ownership

Single-handedly designed the feature from low-fi to hi-fi and expanded the design system with new components. Proposed this to replace the older model where separate designers handled low-fi and hi-fi, cutting handoff communication.

Single-handedly designed the feature from low-fi to hi-fi and expanded the design system with new components. Proposed this to replace the older model where separate designers handled low-fi and hi-fi, cutting handoff communication.

Redesigned feature launch to boost engagement
Redesigned feature launch to boost engagement
Redesigned feature launch to boost engagement

Partnered with the PM to design a single Pendo modal for 'new feature' messages with a 'Try Now' button that brings users straight into the feature, replacing multiple CTA-less modals and reducing drop-offs.

Partnered with the PM to design a single Pendo modal for 'new feature' messages with a 'Try Now' button that brings users straight into the feature, replacing multiple CTA-less modals and reducing drop-offs.

Accelerated marketing by bringing production in-house
Accelerated marketing by bringing production in-house
Accelerated marketing by bringing production in-house

Spotted the chance to speed up marketing production by bringing it in-house instead of using an external agency. Created the materials and secured leadership approval within 3 hours.

Spotted the chance to speed up marketing production by bringing it in-house instead of using an external agency. Created the materials and secured leadership approval within 3 hours.

DESIGN PROCESS

To begin with, I mapped the actions of the user sub-groups

I tried to understand the actions different user sub-groups will need to take to have an attendee list created, after having read the Toolbox Talk.

Next, I mapped the user actions to basic UI for a quick discussion

Considering we would have the same interface for both the Toolbox Talk host and attendees, I sketched out a basic UI for attendee list creation.

Created a manual version, but found it too effort-intensive

Weaving in the feedback, I created a quick sketch of the most manual way of creating an attendee list - the host types out all the attendees’ names in the attendance sheet. But, I felt this was quite effort-intensive for the host to manually type out all the names.

Added 'Recents' to reduce user effort

To make it easier for the Toolbox Talk host to add attendees, I added a list of 'recent' names. The host types the name for the first time, then makes use of the 'recent' names second time onwards.

Flow for the first time user

Flow for the first time user

Flow for the first time user

Flow for the second time user (makes use of 'Recents' list)

Flow for the second time user (makes use of 'Recents' list)

Flow for the second time user (makes use of 'Recents' list)

But the user wasn't able to see the list they were creating

The attendee list that the user is creating, is hidden behind the ‘View attendees’ button. I wanted them to be able to see the list they were creating.

So I brought the list to the forefront.

The user is now easily able to see the list they are creating on the same page.

Flow for the first time user

Flow for the first time user

Flow for the first time user

Flow for the second time user

Flow for the second time user.

Flow for the second time user

As the 'Recent' names get pushed out of the view, as the attendee list gets longer, I added 'Add from recent' button at the top, which would open up a bottom sheet of recent attendees

As the 'Recent' names get pushed out of the view, as the attendee list gets longer, I added 'Add from recent' button at the top, which would open up a bottom sheet of recent attendees

As the 'Recent' names get pushed out of the view, as the attendee list gets longer, I added 'Add from recent' button at the top, which would open up a bottom sheet of recent attendees

PM shared a new need, but I was on a week long PTO

After we had closed high-fidelity designs, the PM shared a new requirement to allow users to link the attendee list to a company. Unfortunately, at that time I was on a week-long PTO. Below is how that requirement was added in the flow by other team members.

Issue 1. : An API error could waste the user's effort of creating a list
Issue 1. : An API error could waste the user's effort of creating a list

The ‘Link a Company’ step was added toward the end of the flow. The user might run into an API error of ‘Unable to show companies’,  after having put in the effort of creating a list at this point. Moving the 'Choose Company' step towards the beginning would save the user from the wasted effort (as shown below).

Issue 2. : Share button leading to 'Link a Company' page didn't feel right.
Issue 2. : Share button leading to 'Link a Company' page didn't feel right.

As shown in the screens below.

Issue 3. : Metadata not useful for the user could be removed.
Issue 3. : Metadata not useful for the user could be removed.

Metadata as shown under company name (Knox Construction) in the screen below.

Discussed the issues with the PM, fixed them, and shipped the solution

a) I moved the 'link company' step to the start of the flow to prevent API errors after list creation.



b) Replaced the separate page for ‘link a company’ with a dropdown and bottom sheet for seamless company linking.

c) Removed unnecessary metadata under the company name to simplify the UI.



d) Enabled users to change the linked company anytime during the flow.

And that’s almost a wrap.

We introduced automatic search suggestions, snack bars for actions like adding or removing attendees, and addressed numerous edge cases. Along the way, I designed several new components that are now part of the design system.

For more details, feel free to contact me at sonaljaiswal.design@gmail.com. I would love to share the full story. Thanks for reading. :)

Let's connect
A good chat is nothing short of serendipity.
Let's connect
A good chat is nothing short of serendipity.