(Flatiron School Gif by Jan Cantor)
(Flatiron School Gif by Jan Cantor)
(Flatiron School Gif by Jan Cantor)
Flatiron School
Improving the student enrollment experience
I worked with a team to improve student enrollment in Flatiron School programs
by creating the first student facing experience to get students paid and ready
for day 1 of class faster.
I worked with a team to improve student enrollment in Flatiron School programs
by creating the first student facing experience to get students paid and ready
for day 1 of class faster.
I worked with a team to improve student enrollment in Flatiron School programs by creating the first student facing experience to get students paid and ready for day 1 of class faster.
I worked with a team to improve student enrollment
in Flatiron School programs by creating the first student facing experience to get students paid and ready
for day 1 of class faster.
I worked with a team to improve student enrollment in Flatiron School programs by creating the first student facing experience to get students paid and ready for day 1 of class faster.
Company: WeWork's Flatiron School
Start: July 2019 Handoff: August 2019
Start: July 2019
Handoff: August 2019
Role: Product Design Lead
Team Makeup: PM Lead, Engineering Lead, Engineering team of 4
Flatiron School Mission:
To enable the pursuit of a better life
through education.
To enable the pursuit
of a better life
through education.
To enable the pursuit
of a better life through education.
The Problem:
The Problem:
On Campus enrollment
No existing digital experience.
Takes place over the phone and via email.
No existing digital experience.
Takes place over the phone and via email.
No existing digital experience.
Takes place over the phone and via email.
Online enrollment
Confusing digital experience.
Most students need assistance over the phone and via email
Confusing digital experience.
Most students need assistance over
the phone and via email
Both programs take an average of 14 days to convert to paid.
Both programs take an average of 14 days to convert to paid.
The Goal
The Goal
Get more students paid and ready for day 1 of class earlier!
Get more students paid and ready for day 1
of class earlier!
Get more students paid and ready
for day 1 of class earlier!
On Campus + Online students should take an average of 7 days to convert to paid.
On Campus + Online students should take an average of 7 days
to convert to paid.
On Campus + Online students should take an average
of 7 days to convert to paid.
On Campus + Online students should take an average of 7 days to convert
to paid.
Total project timeline: 3 weeks
Total project timeline: 3 weeks
Total project timeline: 3 weeks
The Outcome
The Outcome
The average student now takes just 1 day to convert to paid and ready for class!
The average student now takes just 1 day to convert to paid
and ready for class!
The average student now takes just 1 day to convert to paid
and ready for class!
The average student now takes just 1 day to convert
to paid and ready for class!
The average student now takes just
1 day to convert to paid and ready
for class!
The new experience was released on October 1st of 2019.
It was first validated with on-campus applicants, then later released to Online applicants.
The new experience was released on October 1st of 2019.
It was first validated with on-campus applicants, then later released
to Online applicants.
The new experience was released
on October 1st of 2019.
It was first validated with on-campus applicants, then later released
to Online applicants.
Hey there, this is the default text for a new paragraph. Feel free to edit this paragraph by clicking on the yellow edit icon. After you are done just click on the yellow checkmark button on the top right. Have Fun!
Demo Build
Process
Understanding the current online experience
Process
Understanding the current online experience
Process
Understanding the current online experience
What did a student see before we improved things?
How did we know we needed to improve?
What did a student see before we improved things?
How did we know we needed to improve?
What did a student see before
we improved things?
How did we know we needed
to improve?
What did an admissions representative need to do manually?
What was their experience like?
What did an admissions representative need to do manually?
What was their experience like?
Some research
I documented the current student journey and sat in on 5 admissions calls to better understand our applicants. I spoke with students and admissions reps one on one, and developed a point of view for
what the experience could be.
Some research
I documented the current student journey and sat in on
5 admissions calls to better understand our applicants.
I spoke with students and admissions reps one on one, and developed a point of view for what the experience could be.
Some research
I documented the current student journey and sat in on 5 admissions
calls to better understand our applicants. I spoke with students and admissions reps one on one, and developed a point of view for what the experience could be.
Wireframe processes
Greyscale sketch files and early concepts. (UI limitations were heavily considered, as I was working within the scope of a first time Bootstrap implementation with the engineering team.)
Wireframe processes
Greyscale sketch files and early concepts. (UI limitations were heavily considered, as I was working within
the scope of a first time Bootstrap implementation with the engineering team.)
High Fidelity
The platform we were going to be building in was powered by Bootstrap 3 (at the time).
We had a conversation around updating to the latest Bootstrap framework and what our MVP scope for the experience should be. Flatiron School's Brand + platform were in the midst of a revamp so we decided it was best to keep a generic UI that fit Flatiron School's look and feel but wouldn't need a heavy custom front-end lift since we knew we would need to make major changes later on.
I created a style guide for my high-fidelity work using Bootstrap guidelines.
This helped for a faster engineering handoff, build and QA process.
High Fidelity
The platform we were going to be building in was powered by Bootstrap 3
(at the time). We had a conversation around updating to the latest Bootstrap framework and what our MVP scope for the experience should be. Flatiron School's Brand + platform were in the midst of a revamp so we decided it was best to keep a generic UI that fit Flatiron School's look and feel but wouldn't
need a heavy custom front-end lift since we knew we would need to make
major changes later on.
I created a style guide for my high-fidelity work using Bootstrap guidelines.
This helped for a faster engineering handoff, build and QA process.
High Fidelity
The platform we were going to be building in was powered by Bootstrap 3 (at the time). We had a conversation around updating
to the latest Bootstrap framework and what our MVP scope for the experience should be. Flatiron School's Brand + platform were in the midst of a revamp so we decided it was best to keep a generic UI
that fit Flatiron School's look and feel but wouldn't need a heavy custom front-end lift since we knew we would need to make major changes later on.
I created a style guide for my high-fidelity work using Bootstrap guidelines.This helped for a faster engineering handoff, build
and QA process.
High Fidelity
The platform we were going to be building in was powered by Bootstrap 3 (at the time). We had a conversation around updating to the latest Bootstrap framework and what our MVP scope for the experience should be. Flatiron School's Brand + platform were in the midst of a revamp so we decided it was best to keep a generic UI that fit Flatiron School's look and feel but wouldn't need a heavy custom front-end lift since we knew we would need to make major changes later on.
I created a style guide for my high-fidelity work using Bootstrap guidelines.
This helped for a faster engineering handoff, build and QA process.
Some hallway testing learnings
After designing and prototyping what I was confident in shipping, I wanted to do some form of user validation, since the timeline didn’t allow for getting in front of real prospective students for more in-depth research. I found 5 Flatiron employees who were not on an admissions team or on the product team and created a scenario to walk through.
Some hallway testing learnings
After designing and prototyping what I was confident in shipping,
I wanted to do some form of user validation, since the timeline didn’t allow for getting in front of real prospective students for more
in-depth research. I found 5 Flatiron employees who were not
on an admissions team or on the product team and created
a scenario to walk through.
Some hallway testing learnings
After designing and prototyping what I was confident
in shipping, I wanted to do some form of user validation, since the timeline didn’t allow for getting in front of real prospective students for more in-depth research. I found 5 Flatiron employees who were not on an admissions team or on the product team and created a scenario
to walk through.
Some hallway testing learnings
After designing and prototyping what I was confident in shipping, I wanted to do some form of user validation, since the timeline didn’t allow for getting in front of real prospective students for more in-depth research. I found 5 Flatiron employees who were not on an admissions team or on the product team and created a scenario to walk through.
I wanted to learn:
Can users navigate between pages in the flow easily?
Are users able to anticipate what will come next based on the information given to them?
Is the content and hierarchy of the page easy to digest?
I wanted to learn:
Can users navigate between pages in the flow easily?
Are users able to anticipate what will come next based on the information given to them?
Is the content and hierarchy of the page easy to digest?
FlatIron School AdmissionsProduct Design
LastMail by LastPassProduct Design
Grasshopper for DesktopProject type
care.meProduct Design
Connect Mobile AppProduct Design
The Four Pillars of CollaborationPublic Speaking
Grasshopper WiFi CallingProduct Design
Homepage Marketing TestRedesign
KodeConnectPrint Design
Building a Cross Product Design SystemDesign Systems
Xively + SalesforceProduct Design