Chuk Moran

Research & Design

Foundry: Edtech Platform

I joined EVERFI to help research and design a new all-encompassing platform for the company's various lines of business: corporate compliance training, higher education prevention training, financial education for employees, K12 courses, and bank financial literacy volunteer events. Each context has its own needs, but the core is to serve up content (courses, surveys, and videos) to learners with appropriate access controls and logging of learner responses, progress, and policy acknowledgments.

Drawing on my experience as a teacher, I pushed for the project to center around assignments. Most edtech platforms center around the learner browsing for content, but our actual customer was the organization assigning training and nudging learners to explore content on their own.

I was involved for over two years, from early brainstorming to migration and onboarding for hundreds of customers.

  • Role: Research & Design
  • Client: EVERFI
  • Tools: Sketch, Invision, Axure, Interviews, user testing
  • Duration: 2 and a half years
  • Year: 2017-2019

Teaser video for finished product
Assignments screen
Assignment management shows who was assigned what when, from the perspective of the person doing the assigning. I introduced and championed this major shift from legacy platforms and shepderded the feature through complexity that accumulated around it.
Assignment automation whiteboarding
The first few months of this project was constant whiteboarding. Here, we hashed out automation settings for assignments that would include learners by criteria (rather than manual selection) and invite learners by an automated schedule (such as every 1st tuesday or assign learners as they become eligible). Ultimately automation was built in a very different way and the basic design dilemmas here remained unresolved for years. This taught me about the gap between design and implementation, and motivated me to see design as prep work to help the construction crew rather than drawing pretty pictures that will remain forever unrealized.
The system's report on learner progress
Tableau report embedded in the website allows admin users to focus in segments of their training population and get quick answers to key questions. I lead design across several deployed iterations, working closely with the data platform team.
Training reminder email
After working with our visual designer, I implemented and maintained these emails (HTML/CSS with Markdown and Liquid syntax handled by a Notification service written in Ruby). The learner sees this email, but the admin has a great deal of control to edit particular blocks of content and schedule the reminders.
Reminder scheduling
Reminder scheduling went through many iterations, limited mostly by unexpected architectural concerns, and had to meet expectations of customers from our legacy system as well as minimize user confusion for customer support teams.
Ideal analytics
Inventing metrics we'd like from one platform portal and prioritizing them. Ultimately, our web analytics data proved much less accessible and useful than database data, which I got by SQL, data team office hours, and later Tableau.
Support portal
This scheme for a unified support system sat for a long time before it was squashed by an opportunistic political win. The design was simply to route any user asking for help to a single subsystem that would log a few facts about them and send them to the right help documents. Ultimately, product management never made this a high priority, because other leaders did not, and when the company finally did a review of its customer support those in charge lacked familiarity with actual platforms and their use so focused on easier to understand improvements they could more easily represent to their superiors as victories. Very educational, but delivering this would have been fairly easy and I should have made it a priority by shopping it around to the right leads.