Hustle

Shipped and redesigned new features for web and mobile application.

Role: Product Management Intern

Tools: React, Java, Obj. C, CSS, Node.js, Swift, Sketch

Product
Strategy
Design
Data

Image from hustle.com

Overview

Hustle is a peer to peer (1:1) messaging platform to help maintain relationships between the organizations and their contacts. This provides one-to-one engagement, improving effective marketing and efficient communication goals.

During my time at Hustle, I worked with the Product & Design team as a Product Manager Intern. The main focus for the team that summer, or Q2 and Q3 2018, was revamping the “goal creation” process for new and existing users on both the web and mobile app. When I was brought on, I had no specific project assigned to me, so I personally reviewed some of the problems I saw with the product after reading all the help articles and going through the product myself, testing it as if I was one of the three different types of users — org admins, org agents, and contacts.

A few projects I worked on include:

  • Shipping out 2 new features as part of the “goal creation” process with the product and engineering team with React, Java, and Objective C — then following up with QA and the Client Success team to draft support articles to teach users how to use the features.
  • Conducting 500 user research sessions through surveys, phone calls, and in-person interviews to test usability of mobile iOS applications, specifically on the iPad and iPhones — then decking an internal presentation showcasing findings.
  • Creating a machine learning data regression model with the data team to help model spikes and forecast product usage during the election cycle (as many campaigns use Hustle as an outreach tool) — then relaying this information in a report for the Client Success team to be transparent with our customers.

However, I’d like to focus on my contribution to the redesign in the interface workflow of its web texting platform for “goal creation,” drafting a hi-fidelity in Sketch before creating a mockup with CSS and Node.js.

Goal Creation Features

The goal creation process for Hustle is as follows:

  1. Set a measurable goal for a campaign, tracking message impact, event attendance, funding, or re-engagement of contacts.
  2. Create an initial customizable script, making it easier for orgs to talk with contacts.
  3. Start texting contacts.

Some of the features Hustle offers.

A few components that I considered improving on was restructuring the reproducibility of goals, integrating with other apps like Google Calendar to better manage event texting, or creating a script bank that organizations could share across campaigns.

I decided to focus on the last component — creating a script bank. Yet I quickly learned that this feature, while useful, would not be feasible due to time constraints. Thus, a simpler feature to add was an “Additional Response Scripts” that would come at the end of each goal creation.

Additional Response Scripts

At the beginning of each product feature, I would write out a spec, outlining all of my thoughts for how the project would move forward, establishing my motivations, questions, desired outcomes, OKRs, methodology, target audience, and existing data.

This specific project was no different, outlining the thought process admins would have while creating goals and the importance of having an additional response script feature, or an automatic default additional response script.

Due to non-disclosure agreements, I'm unable to share any more details about my work. Please contact me if you'd like to learn more about my process and I’d be more than happy to talk!

Our intern cohort + Hustle employees at Minneapolis for Summer 2018.

Takeaways

Overall, this opportunity gave me a chance to push out real product features that affected a user’s workflow while allowing me the interact with customers to perform user research on how certain key components should be improved, backing that up with data analytics.

It also gave me the chance to accurately work across various teams and the necessary communications required to impact-fully support what one group needed over another. Finally, I also learned how use machine learning to create usage forecasts to help prepare the client success team for high-usage counts, effectively preventing software downtime and overloads.