Skip to content

saurabhr

  • Home
  • Analytics Apps
    • NBA Headshot Plot
    • NBA Player Combos
    • NBA Playoff Matchups
    • NBA Rotation Finder
    • Exploring the EFL Pyramid

project scope

Through North­west­ern’s Inter­ac­tion Design Stu­dio were tasked to con­sult com­pa­nies from North­west­ern’s Start­up Garage on UX/UI design. 

We worked with HearYe,  a mobile appli­ca­tion that is designed to help friends plan casu­al group out­ings. At the time HearYe had not launched their app yet was look­ing for advice on user work­flows and features. 

As a stu­dio, we fol­lowed the Google Ven­tures Design Sprint methodology. 

process

The Prob­lem

HearYe’s core issue was the ten­sion around pro­vid­ing a plat­form for users to plan casu­al events, but events lose their casu­al­ness once they move into tra­di­tion­al plan­ning plat­forms (Face­book, Eventbrite). Con­verse­ly, casu­al plan­ning inter­faces (tex­ting, GroupMe) do not have the nec­es­sary fea­tures to facil­i­tate event planning. 

Ini­tial Research & Insights

We spoke with col­lege stu­dents and young pro­fes­sion­als about how they define casu­al events (e.g. play­ing bas­ket­ball, going to the local bar) and how they go about plan­ning them. 

The com­mon ten­sion with our users was this rela­tion­ship between flak­i­ness and co-depen­den­cy. Poten­tial atten­dees have no accu­rate way to dis­cern whether their friends are attend­ing the event, so won’t com­mit to the events. Their friends act in a sim­i­lar way lead­ing to a lot of “Maybe Attend­ings” where no involved par­ty (host or attendee) has a strong sense of the event. 

Through that insight we were able to map the dif­fer­ent sce­nar­ios of co-depen­dence that lead to com­mit­ment to events.

Sce­nario 1: Co-Depen­dant Mutu­al Attendance

Sce­nario 2: RSVP Change

Sce­nario 3: Co-Depen­dant One Way Absence

Sce­nario 4: RSVP Atten­dance Dis­con­nect I

Sce­nario 5: RSVP Atten­dance Dis­con­nect II

Pro­to­typ­ing & Testing

Ini­tial test­ing was done paper pro­to­types. In ear­li­er sprints, we pre­sent­ed open-end­ed pro­to­types and co-cre­at­ed fea­tures with our users and then test­ed fleshed out ver­sions of those fea­tures in lat­er sprints. 

Through test­ing, we real­ized we can’t elim­i­nate co-depen­dance in event atten­dance, but we can facil­i­tate com­mu­ni­ca­tion among co-depen­dant invi­tees in order to make for an over­all more effi­cient process. 

Since paper pro­to­types would not suf­fice for test­ing fea­tures that are depen­dant on social dynam­ics, we lever­aged the chat plat­form, Slack, and had indi­vid­u­als plan real casu­al out­ings through those chan­nels while our team facil­i­tat­ed their interactions. 

Final Design

chat
HomeScreen
Inviter RSVP
Nudge Response
Nudge
Picture1

Final­ly, we pre­sent­ed our designs in a dig­i­tal medi­um that built upon the visu­al iden­ti­ty that HearYe developed. 

Key take­aways include a fea­ture to afford the min­i­mal co-depen­dence com­mu­ni­ca­tion required, fea­tures that account­ed for the logis­tic flu­id­i­ty of casu­al events, and these fea­tures deliv­ered in a lin­guis­tic and visu­al medi­um that fos­tered the infor­mal plan­ning envi­ron­ment users needed.

select­ed work

  • Email
  • LinkedIn
  • Github
  • Twitter
  • Instagram
Proudly powered by WordPress
×