Skip to content
Jon GiffordCXMind / Product design
All product work
Wripple / Client dashboard engagement

The talent was good. The dashboard needed work.

I redesigned the client dashboard and talent-pool workflow as the sole designer. The job was to make a complex marketplace easier to operate, while giving the team reusable parts for the next release.

My role
Sole designer
Time
Multi-sprint engagement
Scope
Requirements, user flows, dashboard, design system, illustration, microcopy
Redesigned marketplace dashboard: talent discovery and team-building in the client’s working environment.
01

Good service, awkward controls.

Wripple connects clients with premium creative talent. After working with the company for a couple of years, I was brought in to design a client dashboard with new features. The navigation, filters, and progress indicator were confusing. The talent was already good; the dashboard was the weak point.

I handled requirements, flows, interface design, the design system, illustration, and microcopy on my own. Each sprint, I worked with the client to define features and carried those decisions through the screens and supporting language.

The existing product also lacked a usable atomic design system. Nested components and variants were not part of the working toolkit, so new features repeatedly started from scratch. Improving a screen without fixing that foundation would leave the same problem for the next sprint.

Dashboard and talent-pool screens: a shared workspace for finding people, reviewing options, and building a team.
02

Make team assembly one continuous task.

Clients needed to create talent pools from scratch or bring in teams they already worked with. Their own notes, documents, and rates belonged with those people. The product had to support a working relationship, not simply a search result.

The old flow separated search, filters, role selection, and team assembly into different screens. I worked to fold those steps into one continuous flow. Filtering became a core feature, with controls and supporting copy that explained what changed in the results.

For each sprint, I mapped detailed requirements into the existing system. The complexity made edge cases worth resolving early. Thumbnails led to cards, tiles, modals, and screens built from shared elements.

Three views of one task: find people, review the options, keep the team together.

1. Find the right people

1Keep filters beside the results they change.

2. Compare and select

2Keep the selection visible while reviewing other candidates.

3. Keep the team together

3Keep working details with the people they describe.

Reconstructed flow diagrams based on the delivered screens and documented talent-pool flow.

Talent-pool flow

Open in Figma
03

A system the team could adopt while shipping.

I organized existing colors and fonts into an atomic toolkit, with nested components, variants, and instructions for staged adoption. The team still needed to release features. Requiring a complete rebuild before the system could be useful would have made it less useful.

Table views supported the different ways clients reviewed talent and maintained their teams. Navigation, filtering, project status, and talent pools needed to work together, not behave like separate products.

Budget also shaped the explanatory content. The client retained the Humaaans illustration library, so I built larger illustrations with the same method and paired them with short microcopy. The aim was to explain unfamiliar concepts within the workflow, without adding another layer of instructions.

Table and portfolio views retain the detail clients need when comparing talent and maintaining team information.
04

Built for the next release.

The dashboard gave clients a way to assemble talent pools, bring in existing teams, and keep notes, documents, and rates attached to the people they worked with. Search, filtering, and role selection became part of a continuous team-building flow.

The atomic toolkit gave Wripple reusable components and a practical path to adopting them. An existing product, a sprint schedule, and a budget were all part of the brief. The system had to help the team ship the next feature, not become another project standing in its way.