Accelerating User Onboarding

Redesigning Bynder's onboarding from a 12-week professional services dependency into a self-serve flow completable in hours, without losing enterprise-grade quality.

Overview

Bynder's onboarding took up to 12 weeks from purchase to first use, long enough to lose deals to competitors and frustrate customers before they ever experienced the product's value. I led the end-to-end design of a self-serve onboarding system that reduced time to value from 12 weeks to 4–5 hours, freed the onboarding team to focus on enterprise consultation, and drove a 30% increase in new partner bookings.

The solution did not require new technology, it required the right UI on top of what already existed.

Outcomes

12 weeks → 4–5 hrsTime to value

50–60%Reduction in time to value

72%Decrease in hours spent on onboarding projects

50%Increase in onboarding team focus on enterprise customers

30%Increase in new partner bookings

The Problem

From the moment a customer purchased Bynder to the moment they could actually use it, 12 weeks passed. That window was filled with back-and-forth emails, Excel sheets, professional services requests, and setup tasks that customers had no way to complete themselves. For enterprise customers, this level of care was expected. For smaller customers, it was a barrier that slowed adoption and created frustration before the product had delivered any value.

The onboarding team was so consumed by implementation work that they had no capacity left for proactive guidance or strategic consultation. Every minor change, a portal background, a font, an SSO configuration, required a request to professional services. This was not a resource problem. It was a design problem.

Research across 18 existing customer interviews, observation of 8 new customers mid-onboarding, and step-by-step timeline mapping across both sides of the process revealed two things. Taxonomy setup was by far the longest stage, a back-and-forth process of defining metadata structures that could stretch for weeks. And almost every other onboarding step was bottlenecked not by complexity, but by the absence of a UI that allowed customers to do it themselves.

Phases of the onboarding flow and where time was lost

Solution

Industry-based taxonomy templates

The biggest bottleneck in onboarding was taxonomy definition. Pre-built industry templates with eight essential meta properties gave smaller customers an immediate baseline, while enterprise customers retained tailored support.

Progress saving on a non-linear flow

Users could pause and return at any point. Because onboarding is inherently non-linear, customers jump between steps as they gather information, progress was saved at every stage so nothing was lost.

Previews before go-live

Customers had never used Bynder before setting it up. Module previews let them see exactly what they were configuring, reducing confusion and building confidence before they ever went live.

Branding & fonts setup

Login screen configuration

Taxonomy setup

Key Product Decisions

Separating what needed to be self-service from what needed to be enhancedThe research revealed a clear split. Most onboarding steps, creating a profile, setting up teaming, configuring a domain, enabling login, setting permissions, were straightforward tasks the technology already supported but lacked a proper UI. These were the self-service opportunity. Taxonomy was genuinely complex, essential for every customer, and the source of the most back-and-forth. This needed to be redesigned, not just surfaced.

Industry-based taxonomy templates as the unlockRather than asking every customer to define their taxonomy from scratch, we introduced industry-based templates that provided at least eight essential meta properties as a starting baseline. Smaller customers could get started immediately and modify properties within seconds. Enterprise customers still received dedicated support, but the onboarding team was no longer spending that time on customers who did not need it.

A five-step guided flow, not a settings pageThe redesigned flow was structured around five clear steps: portal creation, admin invitation, user login, guided configuration, covering branding, fonts, colours, favicons, taxonomy, videos, and survey inputs, and portal unlock. Every section had to be completed before submission, ensuring customers arrived at a fully functional DAM rather than a half-configured one.

Progress saving and previews as trust mechanismsEarly prototype testing revealed two consistent user anxieties: customers were afraid to start because they did not know if they could stop, and they did not understand what they were configuring because they had never seen the product. Progress saving let users pause and return at any time. Module previews let customers see each part of Bynder as they set it up, reducing confusion and building confidence before go-live.

An internal dashboard for proactive supportAlongside the customer-facing flow, we built an internal dashboard for the onboarding team that tracked where each new customer was in the process and flagged when someone appeared stuck. This shifted the team's mode from reactive to proactive, they could identify a struggling customer and reach out before frustration escalated, and manage multiple onboarding customers simultaneously.

What Almost Killed It

The hardest part of the launch was not the design, it was migration. Existing customers had taxonomies, settings, and configurations built inside the old system that needed to move into the new one. This required extensive cross-department collaboration and created significant pressure on both engineering and professional services.

Post-launch, the change management required across the onboarding team was equally demanding, the team's entire way of working shifted from implementation to consultation, and that transition needed process documentation, training, and ongoing communication to stick.

What I Learned

"Empowering users early pays off"Customers who set up their own environment understand it better, adopt it faster, and need less ongoing support. Self-service is not a cost-cutting measure, it is a better experience.

"Small changes have big impact"The technology for self-serve onboarding already existed inside Bynder. No new infrastructure was required. The entire shift, from 12 weeks to 4–5 hours, came from putting the right UI in front of the right steps at the right moment. The design was the product.

"Onboarding is itself a product"It has users, flows, success metrics, and failure states. Treating it as a handoff process rather than a designed experience was the root cause of the problem. Once we designed it with the same rigour as any other product surface, the results followed.