PINGDOM_CANARY_STRING
documenting user flows

How We Lost $250,000 by Not Documenting User Flows

Reading time: about 4 min

Posted by: Dave Grow

Optimizing the funnel. As marketers (and product managers), we spend countless hours developing and testing new ideas to convert more visitors into customers. Having personally helped run hundreds of A/B tests, I know marketers work hard for the money!

How much time do you spend searching for the big wins? Now, how much time do you spend maintaining the big wins? If you haven’t developed a strong process for maintaining the big wins, it could cost you. And cost you big. In my case, that mistake was worth hundreds of thousands of dollars.

Let me explain.

First, the big win

Several years ago, Lucidchart had two primary paths to register for a free account: (1) a standard pricing page; and (2) an instant demo. The instant demo required no registration to test out the product, but if users wanted to save or print their diagram, they were prompted to register.

In looking at the data of both flows, I realized that users converted to paid subscribers at a much higher rate through our standard pricing page flow. After investigating, I realized that after registering via the pricing page, users were provided a specific onboarding and education flow. On the other hand, when users registered via the instant demo, they were instantly returned to their diagram to continue editing and consequently missed out on this onboarding.

Simple! Why don’t we test redirecting users from the instant demo through the standard onboarding and education flow when they registered? Long story short, the results of the A/B test were outstanding and nearly doubled conversion rates to paid subscriptions via the instant demo.

We celebrated this massive win for the business.

Next, the big loss

Fast forward a year. I was providing a demo of Lucidchart to a peer at another SaaS company because he was interested in how we onboarded users. I clicked into the instant demo, went through the registration process, and was immediately returned to my document for editing. But wait—why wasn’t I redirected to the onboarding and education flow?

I opened an incognito window in Chrome and tried it again. Same results. Something was clearly broken.

Knowing that this was a critical user flow, I immediately sat down with an engineer from our team. He carefully examined the code and realized that a change had accidentally reverted the flow. “Really? When?” I asked. 

He intently reviewed the change log and finally stopped, gulped, and responded, “Six months ago.”

Then, the painful calculations

After speaking with the product manager about getting a fix in place right away, I began to look at our conversion data. Sure enough, there had been a severe drop in conversion rates via the instant demo nearly six months prior. We hadn’t caught it because it had been masked by improving conversion rates via other flows and a number of other factors. Through some back-of-the-envelope math, I came up with the painful estimate of the lower conversion rates over that period:

$250,000.

That was the cost of the mistake.

Finally, the lessons learned

I realized the (costly) irony in all of this. Despite helping lead a team that produces an incredible app for flowcharting and diagramming, I had never formally documented our conversion flows. They lived within my head and for years, that seemed sufficient. Until now. Until I got burned by not taking the time to document and communicate these flows to the broader team -- product, engineering, QA, customer success, and others.

Had I documented the conversion flows, our product team would have known to be incredibly careful when directing changes in the instant demo. Had I documented the conversion flows, our engineering team could have written unit tests or Selenium tests to ensure that the code or flow didn’t change without it triggering an alarm. Had I documented the conversion flows, our top-notch QA team likely would have noticed the change before it was ever released during their regression testing. Had I documented the conversion flows -- and even if it had somehow slipped past product, QA or engineering -- there would have been dozens of others who may have caught that change before I did. 

Over time and via optimization, the funnel can become quite complicated! After all, there are huge wins to be had by segmenting users and tailoring experiences. But here’s my two cents (or perhaps my 250,000,000 cents): Take the time to document your user and conversion flows to ensure that your users are getting the just-right experience you’ve worked hard to create.

Get your teams on the same page today with Lucidchart.

About the author

Dave Grow came on board shortly after the launch of Lucidchart and has worn nearly every hat on the business and product teams. Prior to joining Lucid, Dave worked as a management consultant at Bain & Company. He graduated summa cum laude from Brigham Young University with a B.S. in Business Management. Dave is a political junkie and tries to keep up with the outdoorsy stunts of the rest of the team (with only an occasional trip to the emergency room).

Start diagramming with Lucidchart today—try it for free!

Sign up free

Popular now

what does HR do

What Does HR Actually Do? 11 Key Responsibilities

About Lucidchart

Lucidchart is the intelligent diagramming application that empowers teams to clarify complexity, align their insights, and build the future—faster. With this intuitive, cloud-based solution, everyone can work visually and collaborate in real time while building flowcharts, mockups, UML diagrams, and more.

The most popular online Visio alternative, Lucidchart is utilized in over 180 countries by millions of users, from sales managers mapping out target organizations to IT directors visualizing their network infrastructure.

English
PrivacyLegal
© 2021 Lucid Software Inc.