BenchBeeDraft

Putting benched consultants back on billable work

Role
Product Designer
Service
Product design
Design system
QA
Landing page
Illustration
Year
To confirm

Overview

Benched consultants, back on billable work

BenchBee is a B2B platform for consulting firms. When consultants sit on the bench between missions, firms can share them, anonymously, with other firms that need those skills to unlock a mission, and with recruitment agencies looking for vetted, already-employed consultants.

The work came in two parts. The interface had to be reworked quickly, so I redesigned it end to end. Then, from that interface, I built a design system that lets us run QA on what ships. Along the way, I designed the landing page and drew the product's illustrations, and we're moving its branding forward.

The problem

To writeA heading that says what wasn't working, in one sentence.

  1. 01

    To writeThree or four questions consultancies and agencies kept asking before the redesign, in their words.

  2. 02

    To write

  3. 03

    To write

Onboarding before

BeforeCaption to write

AfterCaption to write

Opportunity

To writeA heading that says why it was worth doing now.

To writeWhat the business stood to gain, or what changed that made it possible, in two or three sentences.

First reason

Caption to write

Second reason

Caption to write

Third reason

Caption to write

Interface

Reworking the interface, fast

I started by auditing every flow, then redesigned all of them: onboarding, the dashboard, creating a consultant or a mission, match requests and messages.

Onboarding for both personas.

A consultancy shares its consultants, an agency posts missions, and each one is led to its own first action.

A dashboard rebuilt around retention.

Creating a consultant from a CV instead of filling in a form.

Activation emails

Activation emails that bring people back to the product.

Design system

A design system for QA

From the new interface, I built the design system: eight foundations (type, color, border, spacing, radius, elevation, motion and layout), each with its scale, its tokens and its rules. QA runs against it. I audit each flow, and what doesn't match the system becomes a ticket for the developers. How the foundations are built is in a guide of its own.

To writeHow QA runs day to day, and one fix that came out of it.

Caption to write

Landing page

The landing page and the illustrations

To writeWhat the landing page had to say, and to whom. How the illustrations were made, and where they're used.

Caption to write

Caption to write

Caption to write

Caption to write

Research

To writeA heading for what the research showed.

To writeWhat you looked at (the market, products like it, the people who use it) and what you found, in two or three sentences.

Products like it

Caption to write

What users said

Caption to write

Explorations

To writeA heading for the ways you tried before choosing.

To writeThe directions you explored, one line each, and what each was for.

First direction

ExploredCaption to write

Second direction

ExploredCaption to write

Third direction

ExploredCaption to write

Testing

To writeA heading for what testing taught.

To writeWho tried it, how, and what you watched for.

A test session

Caption to write

  1. 01

    To writeTwo or three things the tests taught, each named in a few words.

  2. 02

    To write

  3. 03

    To write

Key decisions

To writeA heading for the decision that shaped the redesign most.

Instead of
To writeThe option you set aside, the one you kept, and the trade-off if there was one.
I chose
To write
First way tried

ExploredCaption to write

Second way tried

ExploredCaption to write

The way kept

AfterCaption to write

Instead of
To writeA second decision, if there is one.
I chose
To write

Constraints

To writeA heading for what the project couldn't do, and how you worked with it.

To writeThe constraint (time, technology, budget, the team) and what it changed.

Instead of
To writeWhat the constraint ruled out, what you did instead, and what it cost.
I chose
To write

Results

To writeA heading that says what came of the work.

To writeTwo or three facts: a number, a date or a word, for consultancies, agencies or the team.

Theo redesigned BenchBee end-to-end: onboarding for both personas, dashboard rebuilt around retention, and all core flows. He understood the product and challenges, then designed around them. Clear comms, on time.

BenchBee

Reflection

What I'd change

To writeWhat you'd do differently today.

To writeA first lesson: a short title, then one sentence.

To writeA second lesson: a short title, then one sentence.

This page is a frame in the site's own design file. Flip design mode to see how it's built, component by component.

More work

    What did Theo change in BenchBee's interface?