This should be the easiest thing anyone has to do. Kind of like finding a website on Google, connecting with a friend on Facebook, and downloading an image on Shutterstock. The basics. 

All you have to do here is find yourself on a big Google map, and the nearest eNeighbrs will come right up. You can see what days and weeks they are available to sign for your package, so you do need to do a little thinking ahead of time. But with e-commerce being the way it is today, where you can get the exact date of your delivery, it's really not so bad. 

Normally I prefer user experiences that allow you to undo rather than confirm a decision. However, this is transactional e-commerce where someone will get a real notification and I'd rather not bother people with having to deal with cancellations due to human error. So we ask customers to confirm the date and eNeighbr and make 100% sure this is what they want to do. You click confirm, and away you go. 

Because eNeighbrs do have lives outside of eNeighbr, they've set days they won't be available. So when customers select dates and date ranges for when they expect the package to be delivered, they'll only get valid choices. This manages expectations nicely. 

Here's the confirmation message after you've booked. Clearly this is pretty barebones, but we were under a really tight deadline and this was the best we could do in the time we had. Later iterations of this would be much better, and I should add those to my portfolio here. 

Here's how customers may sign up or sign in with eNeighbr. I tried several different treatments of this. In earlier versions I had placed the registration links on top and the sign in below, but it really didn't look right. Although only .00000000013514% of the population has currently registered with eNeighbr - meaning the more likely use case is to get people registered - the argument for placing those links higher and more prominent is sound. 

However this works for us, too. Note the copy on the calls to action is action and benefit orientated. I don't think Product Designers pay enough attention to copy, which is how 99% of people understand what the intent is. 

There are two kinds of eNeighbr customers: those that are looking to hold packages for people, and those people who want to send their packages to an eNeighbr. 

Let's first take a look at how an eNeighbr onboards. 

Here we have a simple screen that sets up the expectations required for being an eNeighbr. I wanted it to be inviting and friendly. I found some great stock vectors as I'm not much of an illustrator, but I modified them heavily to make them work better for us. 

Once you start the flow, you see you have 4 (or is it 3?) main steps to complete: you, phone, schedule and done! Because most people are at home or on their laptops, I left the password field on so you can see what you are typing. You can easily click to hide the password from prying eyes. 

I will note that in today's world, having just two genders is a bit narrow-minded, but for MVP that's what I went with. Neither of them are automatically selected, but in this particular mockup I wanted you to see the active color treatments. 

Here's the next step. It's easy for you to type, tab, type right through this. Note the ZIP code is first, because when you type it, it fills out the city and selects the state automatically. If the API should fail, you can select these manually. 

Moving right along, we ask the eNeighbr applicant for their phone number, which is a fantastic way of identifying someone. Because these transactions will be face to face, we want to verify they are real people and know we can get a hold of them. 

At this point the text message should be flying to their phone. But if not, it's likely because they fat-fingered it. So we let them fix the phone number if its wrong. If its not, and its taking a while, or never comes, we let them send the code again, which covers 99% of the problems a customer might have. 

They did it! 

This is a bit of an odd step. If you read carefully (yikes, does anyone read on the internet?) it asks you to check off the days you are not available for packages to be sent to your home. But this actually makes sense. If you are clicking too many off, you're not going to be a good customer for us. 

If we had flipped this around and made it so you had to click the days you were available, and you were a good customer, that's just too much clicking. 

Here's what it looks like. This customer isn't available on Mondays, and looks like is going to be out of town the last weekend in August. 

And you're done. You get a nice smiley face. That's it, the customer is onboarded. From there we send them a nice welcoming email and a link to sign in and see their dashboard. 

eNeighbr customers need to be able to pay, change their passwords, and update their personal information. We'd also want them to upload a photograph of themselves, which increases conversion to those eNeighbrs by an astounding amount. 

And besides, do you really want to look like the Pringles guy? 

See? That was easy. We also don't want people to pry or steal this information, so we never show the full card number again. You can delete the card and add another if you need to. 

There are some slim cases where a person wants to be an eNeighbr and also use the service! So we needed to plan for that eventuality. 

All you do is switch between yourself as an eNeighbr or yourself as a customer. Pretty simple. 

And that sums up the eNeighbr desktop experience! I hope you've enjoyed looking through it. Has a blast working on this.