Categories
Affiliate Backend eCommerce Frontend Full-Stack Growth supply-side

Selling More

(Shop It To Me : 6/10-7/12)

Results

  • Iterating with Product to scope, implement (Rails w/MySQL,) and A/B-test pixel-perfect sign-up/refer-a-friend/search/browse/opt-out/profile experiences
  • Drove conversions in the form of signups, virality, and clicks for not only our flagship web and email products (used by 4M+ users) but also eight new product launches
  • Architected company’s newest Ember.js-based product
  • Quickly integrated into a small, fast-moving, startup engineering team
  • Became proficient in all things Rails
  • Ensuring quality through the use of code reviews, TDD, unit, functional, integration, and regression tests under continuous integration, testing plans, and mentoring/pairing to deliver functionality, fix bugs, refactor legacy code, and transfer knowledge
  • Have assumed lead (primarily frontend) responsibilities while reporting directly to CTO
  • Established F2E guidelines and best practices
  • Architected the company’s newest product, an Ember.js-based Single Page Application
  • Leveraged Facebook, Twitter, and Pinterest APIs to increase our social reach (including the use of Facebook Connect and the Like Button during signup and tell-a-friend experiences)
  • Prototyped iPhone app for user to navigate item stream during in-house Hackathon
  • Contributed improvements to our Nokogiri-based data-harvesting framework.
Categories
Architecture Collaboration eCommerce Frontend Innovation Prototyping SPAs supply-side

A New Way To Shop

(Shop It To Me : 1/12-4/12)

Shop It To Me has been a beloved service for years when it comes to finding the best deals across retailers, but we wanted to enable the user finer-grained abilities to find exactly the item(s) of interest for them.

We often had feedback about being able to drilldown by clothing type and brand (e.g. “Rebecca Minkoff handbags”) but our previous tools didn’t enable that kind of granularity.

Enter “Threads.”

As the brainchild of our CEO, project “Threads” has become a way for users to track the specific items of interest to them. We now empower the user with the ability to get as general (e.g. “Black dresses”) or as specific as they want. (e.g. “Rebecca Minkoff handbags under $300.”)

Below, you’ll see the hi-res) mockup we came up with (after having previously white-boarded the idea) in early March (click to view.)

inspiration (as mocked-up in Photoshop)

Over the following two weeks, I ramped up on Ember.js and implemented the first version of the app while the other engineer built out the pseudo-RESTful backend. I won’t claim that the code we produced was the cleanest either one of us ever wrote; while doing the best we could, getting to market was the true driving motivator.

We went live – that is, deployed to production for internal and a select group of test users – on March 27th, 2012, with the following (click to view)

very first landing page

Based on user tester feedback, we decided to bolt-on onboarding and improve the look, so four days later on March 31st, 2012, we deployed the following (click to view)

revised landing page with header and pseudo-onboarding

Based on observations during user testing, we realized the opportunity to incorporate a feed of site-wide activity as that would benefit discovery. We also took a few cycles to flesh out onboarding and a “Things To Do” list given challenges users’ had in making sense of the new product. We also tweaked styling to highlight the very newest items in the users’ results; screenshots follow (click to view.)

onboarding modal on landing page (4/11/2012)
 
1st try: TTD/activity feed on landing page (4/11/2012)
 
2nd try: TTD/activity feed on landing page (4/12/2012)
emphasizing new items (released 4/12/2012)

We brought in more and more user testers. Here’s a screenshot from April 17th, 2012, showing progress we made from our observations

4/17/2012 release of results page

While observing user testers, we discovered that they wanted tastemakers to help them navigate the overwhelming number of apparel items, so we introduced the concept of curation. We also made the assets/images larger by popular demand.

curation (4/23/2012)
results page (4/23/2012)
results page w/larger assets/images (next day : 4/24/2012)

After April 24th, we stepped back to assess how we were doing. I was rotated onto our bread-and-butter projects but the team was augmented with other talent and continued forward, contracting the look-and-feel out to a third party.

The product has since been retired.

Results

  • To revolutionize personalized shopping, a team of three (the CEO as product manager, me as the F2E/architect, another as backend engineer,) created a new shopping experience using Ember.js over two sprints
  • Ramped up quickly on Ember.js
  • Architected frontend as a Single Page Application
  • Worked with backend engineer to agree upon/implement integration between FE and BE
  • Drove development through four major iterations during a two one-month sprints
  • Suggested (though not responsible for implementing) lazy-load as a way to improve performance
  • Picked up design slack when we lost our Graphic Designer
  • Scoped frontend deliverables and managed expectations
  • Worked with CTO to coordinate out-of-cycle releases to production
  • Planned, conducted, and analyzed user testing
Categories
eCommerce Frontend Growth Innovation supply-side

Product Page Improvements

(Shop It To Me : 10/11-11/11)

To keep the user on-network, we created an on-site details page. We explored different MVPs which partially leveraged the metadata already present in our inventory, partially as they were intended to aggregate content from the retailers.

Here are a few concepts we vetted as MVPs

The following screenshot shows that we even tried our hand at soliciting reviews as UGC

… before finally settling on this as the (now retired) final product.

Results

  • created an on-site details page to boost checkout conversion
  • worked 1:1 with Product to prioritize features
  • prototyped MVPs using Photoshop
  • implemented all aspects of the frontend under a sprint schedule
Categories
crm eCommerce Frontend Growth NUX supply-side

Improving the Acquisition Funnel

(Shop It To Me : 2/10-5/10)

Our four-page flow has proven itself time and again, but in order to drive even more signups, I’ve put in experiments on

  • the number and styles of brands a user can choose from (step two)
  • the messaging (copy) and layout (throughout signup)
  • the types and number of mandatory sizes and categories a user must choose (step three)
  • the form fields of the profile creation (step four, final)
  • content and layout of the confirmation email received by the user
  • …and others

Below you’ll find just a sample of these kinds of experiments.

Here are three of the five variations on our final step, the profile page, in a bid to leverage the SSO benefits of FB Connect (click for larger views)

For one experiment in the signup process, we attempted to simplify choosing brands by creating style profiles. The idea was to make it easier for users to signup based on some curated indices (click for a larger view)

Here are a couple of the many landing-page variations we’ve tried when a potential new user is referred from a friend (click for larger view.)

In the following example, we have the original confirmation email as contrasted with a simple design (of my own) I implemented (design and implementation as email in one hour, click for larger assets/images.)

Results

  • Implemented several A/B tests that increased signup conversion by 3-10%
  • Refactored workflow engine while pairing to enable signup for alternative flows used in A/B testing