How content design changes cut errors by 43% and doubled feature adoption at DocuSign

Context

DocuSign had shipped a beta feature for real estate agents. To activate it, users had to enter credentials through a validation modal. This was the only way to access the feature, so the modal’s success rate directly controlled adoption.

We weren’t hitting our adoption goals, and an engineer flagged in standup that the volume of failed validation attempts was high. I wanted to understand why, so I jumped into my test account to troubleshoot.

Problem

First thing’s first: there were three versions of the same modal. We consolidated them to one.

But wait, there’s more:

• The terminology was incorrect and inconsistent and incorrect throughout
• The help link for finding your NRDS ID was nowhere near the relevant NRDS ID field
• The “numbers-only” ID field accepted symbols and letters without complaint
• There were zero inline error messages (users got no feedback until a toast appeared)
• The toast itself was wrong: 500 error copy (“Unable to process the request right now”) was appearing for 429 rate limit errors

The 429 errors were the most common failure for this modal, and every one of them was showing 500 copy. Users who’d simply tried too many times were being told to try again because the server was down.

We were rate limiting people, then telling them to try again. We put them in 429 purgatory.

Solution

I pulled the error volume data from the engineer, put together a plan, and pitched it to our product manager. She said yes, the engineer said the scope was easy to manage, and we got to work.

Consolidated three modals into one. Three entry points had drifted into three slightly different modals. I unified them so the header matched the purpose of each CTA, but the content and structure stayed consistent.

Corrected the terminology. “Forms” became “Form Libraries” (the actual product name). I introduced “form source” to prepare for an upcoming release that would add more real estate associations. I verified every term by logging into NAR with my grandfather’s credentials (he’s a licensed realtor). The original modal used names that didn’t match what agents actually see.

Restructured the information hierarchy. Instructions for finding the NRDS ID now sit next to the NRDS ID field. The description leads with what to do and why. A new line under “Associations” clarifies that you need active membership for this to work.

Added inline error messaging. Users now see feedback at the field level instead of waiting for a generic toast.

Rewrote the error messages. I separated the 429 copy from the 500 copy so each error type described the actual problem. Previously, the most common error (429) was using copy meant for server failures (500), which made it look like the product was broken.

Results

Because this modal was the only way to activate the feature, doubling the validation success rate meant doubling adoption. The error message rewrite drove the largest single improvement, a 43% reduction in the highest-volume 429 errors disguised as 500 errors. The terminology corrections, hierarchy changes, and inline feedback closed the remaining gaps.

Before

Before

After

After

1 / 4

Two of three modal variations. The 500 error toast appeared for 429 rate limit errors.

Inconsistent headers and terminology across entry points.

Inline validation replaced generic toast errors. Field-level feedback explains what went wrong.

The rate limit error now describes the actual problem. Unified header across all entry points.

Design details

A few answers to questions folks may have.