Next, I get into the solution.

The theme of this section is to tell a story.

How did you reach your solution?

Walk the audience through it.

Include everything, from rough sketches to high fidelity mockups, as well as anything

that sparked inspiration including mood boards or screen shots from other apps.

I start by stating my hypothesis.

I believe that bringing the recruitment experience in app for

prospective apprentices, will result in a more streamlined user experience,

that gives them access to the starter track more quickly, provides more clarity

in regards to next steps, and frees up time for Treehouse staff.

We all know this to be true when we see more prospective apprentices being active

on the starter track, less support tickets relating to recruitment confusion,

and a reduction in Treehouse staff time spent on recruiting.

That states my intention for how I want to solve the problem.

Next, I show how I improved the user flow.

Here I have some updated user flows that show the new experience I'm creating.

My plan is to bring the recruitment landing page into the Treehouse app and

have it auto generate based on a template.

Then I want to streamline the interest forum so

that when people want to join, they can automatically get access.

Then I start showing the mockups for the new flow.

The interest form went through a couple of iterations, so

I start with the first iteration.

Depending on the purpose of the presentation and the time you have to

present, consider including the iterations that ultimately got scrapped.

Explaining what worked and

didn't work, will inform them about why you landed on the solution.

In an early iteration,

I redesigned the interest form while keeping the questions intact.

Later on, you'll see I drastically simplified the form after learning from

the team that several questions actually weren't used to vet

candidates in the early phase of the process.

Here's my first pass at building an a sign up flow after the interest form is

filled out.

There's a special variation here for

when someone with an existing organization account signs up.

That kind of transfer requires customer support help.

I also included this idea I had for

a review queue in our internal admin dashboard.

We ultimately decided to not go this route, but

basically the idea was to display the candidates on a dashboard and

allow admins to review their interests form responses.

Then admins could accept or deny access.

We ultimately decided to automatically give new users

access without putting up a gate.

I recap the pros and cons of my first iteration here.

Then I showed my second iteration, starting with the interest flow.

I builds off the usual tree house sign up form.

I included the various steps as there are different screens shown to those with

existing Treehouse accounts and those who do not have a Treehouse account yet.

Here's the email that's sent us students after they submit the interest form.

It clearly communicates it's related to the apprenticeship program and

includes the next steps.

That wraps up the student facing experience.

Next is the admin experience within an internal staff only dashboard.

I start by showing the updates to the admin dashboard.

This shows the Cohort page, which includes the Generate Landing Page button.

That leads to another internal page where the landing page template is defined.

This part of the dashboard is older and not as freshly designed, but

still works just fine, redesigning it was not in the scope of this project.

Here Treehouse staff can create a new landing page for a given cohort, and

customize specific fields such as city and employer name.

Here are the improvements.

There are several assets to choose from to personalize the landing page.

Here are just a few.

Now, here's the updated landing page design.

As you can see, it's difficult to read a long web page within a small space on

a slide, so I've layered a couple of sections of the page here.

And in the next few slides I've zoomed into each section.

Here I show that I made the location more prominent.

The hero image can easily be swapped out in the template.

I also introduced the program and provided a place to explain

the partnership, and I clarified the key dates and program timeline.

I included some extra goodies such as a page that displays the cities we're

currently recruiting in.

This wasn't part of the original project goals but

now that the recruitment is automated, it's easy to automatically generate

a page that gives everyone transparency into where we're recruiting.

That covers the project walk through.

In the next video, I'll show you how I talk about the project plan.