Billy Eline
Jellyvision
I currently work at an interactive software company based in Chicago called Jellyvision. The main product I have worked on the last 6 years is ALEX, a comprehensive online benefits counselor. Due to the sensitive customer info ALEX discusses, I can't actually provide media showcasing my work. However I created an interactive flowchart below highlighting some of the key features and contributions I have made to the ALEX product over my Jellyvision tenure.
Production
Intern
ALEX v6
Customized
ALEX content
One of the most impressive aspects about ALEX is that it’s fully customizable, meaning that if a company bought ALEX, they could purchase content that would only appear for that company’s employees.
I was involved in the scripting, scoping, and creation of this custom content for our customers.
Flowmastered new features
Flowmastery is the act of tying all of the components that make an interactive conversation (voiceover, sound effects, text, art, logic, etc.) into a seamless experience for an end user. The goal is to make all elements “flow” together.
I had mastered the art of flowmastery early on, so I was the
go-to person on the ALEX team to flowmaster any new content or feature sets.
Production
Assistant
ALEX v7
Flowmastered 9 out of 14 ALEX modules
Due to customer and user demands, ALEX needed an extensive overhaul in content. Therefore, we wrote, recorded, and built an entirely new
experience that would better fit our product demands.
I was the primary flowmaster on the majority of the ALEX modules (each module represented an employee benefit – medical, dental, vision, etc.) I collaborated with writers and product owners to ensure every module met our product and end user goals.
Designed progress bars and navigation
Based on user testing, we found that a progress bar and “back & skip buttons” were both highly requested features. I prototyped and built out a working progress bar across all ALEX modules, working closely with our User Research team in order to determine what methods had the
greatest impact on users. I also built some preliminary navigation functionality in our medical module.
Pioneered ALEX in Spanish
Localization in Spanish was a big goal for version 7, but we were limited by our time constraints and resources. We created a version of ALEX that had all of the on-screen text and closed
captioning translated, but kept the English audio.
I brainstormed, troubleshooted, and built the experience with writers, engineers, and product owners.
Flowmaster
ALEX v8
Led Rhino rework
The visual style of ALEX was a mess before version 8. Every module looked different than the other. Project: Rhino was the initiative to streamline the entire design of our visual layouts so there was consistency and polish across the entire experience.
This involved flowmastering all of ALEX again to accommodate the new visual styles. I led a team of producers in the initiative, working with UI designers and engineers along the way.
Initiated Rogue
In the ALEX experience, a user can access HTML webpages that summarize their employee benefits. However, these pages were built with a proprietary flowcharting software which was a nightmare to use.
Rogue was a new tool we created to make these summary pages much easier. I was one of two producers who piloted this project from conception to implementation. I worked with software engineers to
determine what features were needed from Rogue and then used the tool to create our new summary pages.
Iterated on the Spanish experience
Based on user feedback, we knew our Spanish offering needed an overhaul in content. In ALEX v8, we aimed to have a fully voiced Spanish experience. This involved extensive re-records and reflowmastering, but the payoff was extremely rewarding.
I built and maintained the new Spanish offering alongside Spanish-speaking writers, producers, and engineers. The usage of the Spanish experience nearly tripled after this update.
Module manager for medical and tax savings
In ALEX v8, ownership was given to certain producers over modules to help streamline content knowledge.
I was a module manager for the two
biggest modules, Medical and Tax Savings. I acted as a pseudo product owner for my modules, answering any questions, making key decisions on new features based on customer and user demands, and making sure my modules were always functioning.
Senior Interactive
Media Producer
ALEX v9
Introduced Turbo Mode
We had low user engagement for parts of the medical module and I theorized it was due to the modules length and its linear nature.
In response to this problem, I prototyped and developed a feature I called “Turbo Mode”. Turbo Mode was a router built into the existing medical content that would allow a user to jump to certain topics right away. A user could still sit through the linear 10 minute version of the experience, but they also had the option to navigate however they wanted. After this feature was implemented, the completion rate of the medical module increased over 15%.
Developed
Split medical
In the ALEX medical experience, we asked users a series of questions about their medical usage in order to give them a recommendation on what plan they should enroll in. The questions were asked in regards to a user’s whole family, so a user had to provide numbers for the total amount of care their family needed combined.
However due to medical plan designs, we needed a way to collect info from each member of a user’s family. I was tasked with prototyping various methods to collect this info from users in a way that was both technically sound and user-friendly. I then led a team of producers in the development of the feature.
Reworked the retirement module
Saving for retirement is a confusing topic and the ALEX module describing the benefit suffered from its complexity. I led a small team in re-working the existing content to better fit user demands. The focus was to allow users to get to the decisions they care about sooner, while giving them the option to delve into complex topics if they wanted.
The completion rates of the retirement module rose over 20% after this rework.
Built mobile offering
The mobile offering for ALEX was a very simple HTML based slideshow (with no audio or animation), but it had to be maintained by engineers. In developing our new tool for ALEX v10, Talentshow, we decided to remake the mobile experience as our test bed.
I led a team in the creation of the new ALEX mobile offering in the Talentshow tool. I oversaw the design of the experience and its implementation for customers.
ALEX v10
Enter Talentshow
The mobile offering for ALEX was a very simple HTML based slideshow (with no audio or animation), but it had to be maintained by engineers. In developing our new tool for ALEX v10, Talentshow, we decided to remake the mobile experience as our test bed.
I led a team in the creation of the new ALEX mobile offering in the Talentshow tool. I oversaw the design of the experience and its implementation for customers.
Reviewed every module’s content
Since v10 was being written while Talentshow was being built, we needed careful review of what content we were proposing to make. I was one of two producers who reviewed all of the content for the ALEX v10 experience to determine whether or not it was feasible to make in our new tool.
Prototyped around tech limitations
Since Talentshow was a new tool, there were a lot of features on the cutting block in order to get ALEX built in time for customers. Anytime a feature was cut, I prototyped new user flows around the limitation and proposed new solutions to user problems without introducing
unnecessary new tech.
Led the building effort
Using my knowledge of our brand new tool and the new content we had to create, I led a team of producers in building the new HTML ALEX. Together, the entire experience was completed in a few months, well before customer releases.