Recommended
More Related Content
What's hot
What's hot (20)
Similar to Preso #5
Similar to Preso #5 (20)
Recently uploaded
Recently uploaded (20)
Preso #5
- 1. Event++ PHR: Purva Shanker, Hyewon Kim, Rimi Biswas
- 2. Elevator Pitch ● For recruiting UM EECS students ● Who are dissatisfied with current lack of multi-platform event managers ● Event++ is a event managing chrome extension ● That provides a way to add events to their Google calendar ● Unlike current event managers, our product is quick by allowing minimal user input
- 3. Live Demo
- 4. User Data Feature Importance Satisfaction Multi-platform 3.6 (-1.4) 4.2 (+1.4) Automated Event Listing 4.6 (-0.2) 4.6 (+0.8) One-click add 4.8 (-0.2) 3.8 (-0.8) View added events 3.4 4.0 Customization 4.6 4.6 Average 4.2 (-0.7) 4.24 (+0.54)
- 5. Quotes from Users “It seems like it has plenty of customization, but at the same time it's simple enough to use without tinkering with any of the extra features.”
- 6. “I think you should reduce clicks necessary for the main functionality of the app.” Quotes from Users “Personally I don't know how much I would use the events tab. I feel like I would just look at my google calendar to see what I'd added.”
- 7. Original Hypothesis ● Recruiting EECS students at University of Michigan using Event++ will: ○ Easily manage recruiting events they are interested in ○ Keep life organized better
- 8. Our Findings Users would use Event++ for recruiting and non-recruiting events
- 9. Our Findings Users would use Event++ for recruiting and non-recruiting events
- 10. Lessons Learned ● Know thy users for they are not you ● More concrete planning results in more efficient development
- 11. Questions?
Editor's Notes
- We are PHR and we are developing a product called “event ++”.
- Event++ is for recruiting UM EECS Students who are not satisfied with current multi-platform event managers app / OR who wants to easily keep track of events from multiple platforms Event++ is chrome extension that efficiently adds events to user’s Google calendar so that user can keep track of events they are interested in with Our product is for Recruiting UM EECS Students Who are having a hard time managing recruiting events and are dissatisfied with current event managment applications Our product is a recruiting event management chrome extension That provides recruiting EECS students, that are overwhelmed by the number of recruiting events an easy and fast way to add events they are interested in to their Google calendar Unlike the current event management chrome extensions, our product is uniquely catered to UM EECS Recruiting students who are overwhelmed by recruiting events Our product provides: automated event parsing, an easy one-click option to add to calendars, and the ability to view saved events later on
- Importance scores for all features went down possibly because we tested with diff set of users from MVP1. However satisfaction score went up except One-click add features. It went down because we changed the add buttons into check boxes, so it involves more clicking Satisfaction scores for our new features are pretty high. So overall satisfaction score went up.
- Our original hypothesis is that Event++ users will be able to easily manage recruiting events they are interested in and keep their life organized better. Based on the user testing feedback, most users think that Event++ is helpful to keep track of the recruiting events they are interested in so they would like to use it during recruiting season. In the MVP1 feedback, users said they would also like to use event++ for non recruiting events. As a result, we added facebook in our MVP2. After testing the MVP2, user said they would use our product for more general events.
- Facebook,
- Ex 1) We use piazza calendar to check the recruiting events so we assumed that our users will do the so too. However it turned out that most users do not event notice that piazza calendar exists. So we research on user preference beforehand is really important and can reduce unnecessary work. Ex 2) During our development, we were debating which method to use for front-end. And we ended up doing two versions, react and plain javascript, which resulted in repetitive works. If we planned this out better, we could’ve focus on one version and develop more efficiently.
- Ex 1) We use piazza calendar to check the recruiting events so we assumed that our users will do the so too. However it turned out that most users do not event notice that piazza calendar exists. So we research on user preference beforehand is really important and can reduce unnecessary work. Ex 2) During our development, we were debating which method to use for front-end. And we ended up doing two versions, react and plain javascript, which resulted in repetitive works. If we planned this out better, we could’ve focus on one version and develop more efficiently.