Simplifying legal language- WURRLYedu

The Challenge:

Help teachers collect parent permission to use WURRLYedu and ensure that the product is COPPA friendly.

The Solution:

Update the teacher signup flow to identify who needs parent permissions and develop clear, on-brand language that explains what information is needed and why.

How I helped

• Messaging and copywriting

• User flow development

• User testing

• Collaboration with a designer and front-end engineer
  

Key Skills

• Product writing

• Usability testing

Developing the User Flow

One of the main issues with this project was the need for different information depending on where the teacher taught, the age of their students, and the type of permissions the organization or school collected. If that sounds slightly confusing, it was. To simplify it for our team and support the ideation process I created a user flow that represented the types of users and permissions.

The Previous Design

I also took an audit of what was and wasn’t working for the existing sign up form. I identified 3 main concerns from a content and user experience perspective.

Testing for Clarity

As I developed the copy I ran a few copy tests on Usability Hub to ensure the language was understandable. Some of the original signup questions originated from legal text (and read like it). My goal was to keep the questions clear and consistent with our brand.

Balancing Length and Necessity

I worked with a designer and a front-end engineer to come up with a solution. A key problem that we worked through was balancing the amount of information collected at signup with the length of the process. We knew we had to add more questions to the signup process in order to trigger parent consent emails later on, but we were very wary of long sign up forms because of the drop off rate.

To solve this problem, we decided on the following:

1. Broke the form up into multiple 1-question steps to make it feel as though they were moving through process quickly and making progress

2. Added a visual progress indicator to show the comparison of completed vs to complete to further support this goal

3. Gave the user a “sneak peak” into the product to show the end goal was just around the corner

4. Explained what we were asking for and why in as few words as possible

The Solution - Key Screens