Repositive uxcitymcr
•Als PPTX, PDF herunterladen•
0 gefällt mir•32 views
Slides from Jana and Charlotte presenting about ow we built our User Council at repositive. Presented at UX in the City, Manchester May 5th 2017
Empfohlen
Empfohlen
Weitere ähnliche Inhalte
Ähnlich wie Repositive uxcitymcr
Ähnlich wie Repositive uxcitymcr (20)
Kürzlich hochgeladen
Kürzlich hochgeladen (20)
Repositive uxcitymcr
- 1. What we learnt from building a User Council Jana Grajciarova UX/UI DESIGNER Charlotte Whicher PRODUCT MANAGER
- 2. We are helping researchers find genomic data FRAGMENTED Fragmented in unconnected silos Difficult to discover data
- 3. We are helping researchers find genomic data CONFUSING Inconsistent data structures Overwhelming interfaces
- 4. We are helping researchers find genomic data HIDDEN Data sitting in a hard drives not being used Siloed in different labs and institutions
- 5. We are helping researchers find data ADMIN BURDEN Accessing data can involve lot of formalities The process can take up to 6 months
- 6. We are helping researchers find genomic data Discover and access Search, see related results Find colleagues & their data interests Co-annotate data & community feedback
- 9. Personas Prof William Morgan Head of Computer Biology lab Addenbrookes Hospital PhD Dan Fair Bioinformatician Illumina Elena Watson PhD Researcher University of Cambridge Not so experienced More helpful Active and reliable Skeptical Likes things to be structured Needs evidence Extra cautious Hesitant to share Understands the problem
- 10. UX sessions in the beginning RANDOM SLOW DEV FACE TO FACE LONG SESSIONS
- 11. Irregular user feedback Lacking more information about our users Not enough sources for doing more User Centric design User feedback is not integrated in the product development The problem …
- 13. Solution – Customer Council Taylor Wescoatt @twescoatt Why is the Customer Council a good idea? 1.It reduces the stress of recruiting new users every time you want to test something. 2.Can build a passionate user base, that results in: • A source of valuable information. • A network that can eventually drive revenue.
- 14. What is a Customer Council? Group of people who are actual or potential consumers Willing to give advice in early stages Valuable, qualitative, if somewhat biased feedback
- 15. The Repositive User Council
- 16. Recruitment – How long we would do it for? 6 Months 1 contextual interview At least 2 ‘sessions’ per month 10 – 15 people
- 17. Recruitment – What type of people? Bioinformatician PhD Student Clinician Professor Data scoutLab manager
- 18. Recruitment - How did we reach out to them? People we had met at conferences
- 19. Recruitment - How did we reach out to them? Those who had done UX sessions with us
- 20. Recruitment - How did we reach out to them? Researchers who had given us feedback
- 21. Recruitment - How did we reach out to them? From our current user base
- 22. Recruitment – What were the incentives? PART OF A GROWING STARTUP
- 23. Recruitment – What were the incentives? HELP THEM FIND DATA
- 24. Recruitment – What were the incentives? TO GET AWESOME STASH “Thanks @charlotte! picked up my goodies yesterday ”
- 25. Recruitment – What were the incentives? PART OF BUILDING A PRODUCT
- 26. Message #1 Being involved in a growing start up is a big incentive.
- 27. Recruitment – How do we organise the group? EMAILS usercouncil@repositive.io
- 28. Recruitment – How do we organise the group? SLACK usercouncil.slack.com
- 29. Recruitment – How do we organise the group? SPREADSHEETS Name Email Next UX session Elena Watson elenawatson@tcsg.com 14/03/2017 – 14:30 Dan Fair danfair@gmail.com 18/03/2017 – 14:30 Christina Luckasson Christinaluckas@gmail.com 22/03/2017 – 9:00
- 30. Here they are
- 31. Working with the User Council
- 32. What are we doing with the council? CONTEXTUAL INTERVIEWS
- 33. What are we doing with the council? SURVEYS
- 34. What are we doing with the council? USABILITY TESTING
- 35. What are we doing with the council? EVANGELISING
- 36. 5 Great things
- 37. 5 great things 0 1 2 3 NumberofUsersinteractedwith UX Sessions Contextual Intervieews User council 1 User council 2 RELIABLE
- 38. 5 great things 0 1 2 3 NumberofUsersinteractedwith UX Sessions Contextual Intervieews User council 1 User council 2 RELIABLE Contextual Interviews
- 39. Message #2 Don’t do all the contextual interviews at one time.
- 40. 5 great things “The last half a year went very fast, indeed. I would be interested to stay in the user council :) It is an experience for me personally as well” Jana “When anything comes up just give me a ring” Rob “I would certainly still like to be involved” Jonathan RELATIONSHIP
- 41. 5 great things BACKGROUND & CONTEXT William Sarah ”William didn’t understand the content and wasn’t familiar with the dataset. He isn’t exactly sure what we are after.” Notes from UX session ”This dataset isn't that big so wouldn’t take more than a couple of days to analyse. She would analyse it straight away to see if it's something she could use.” Notes from UX session
- 42. 5 great things UNDERSTAND WORKFLOW CHANGE “Yes thesis submitted and now riding a wave of training programmes” Johnathan “I’m pretty busy at the moment as we are moving office, so I don’t have time to look for data” Jana “We are currently applying for grant money so we aren’t looking for data” Prash
- 43. 5 great things BONUS FEEDBACK “Hi Charlotte, I just have quick idea about the dataset arrangement” Mahantesh “Its another suggestion, you can consider it based on your priorities!” Roy “Hey Charlotte, we do have some ideas so it would be cool to talk with you and your designer. What about next Monday?” Seb
- 44. Message #3 Building a relationship with our user council gave us a better understanding of their workflows.
- 45. UX session BEFORE ….. and NOW RANDOM SLOW DEV FACE TO FACE LONG SESSIONS CONSISTENT FAST DEV ONLINE & REMOTE SHORT SESSIONS
- 47. Message #4 It can be easy to integrate users feedback into the development of a product.
- 52. Main lessons learnt 3# Building a relationship with our user council gave us a better understanding of their workflows. 1# Being involved in a growing start up is a big incentive. 2# Don’t do all the contextual interviews at one time. 4# It can be easy to integrate users feedback into the development of a product.
- 53. This is just the beginning… Charlotte Whicher & Jana Grajciarova
Hinweis der Redaktion
- Data is fragmented in unconnected silos – makes it very difficult to discover data
- Many different sources and repositories around the world. Hard to know where to look.
- People don’t share their data or communicate what they have. It is siloed in different labs and institutions.
- Even if you find the data, hard to get access to it due to ethics around human data and confidentiality.
- Our users are generally people who work with genomic data: genomic researchers, bioinformaticians, clinicians.
- This is our user base, their main traits.
- When I started at Repositive We had a big idea but no product. We knew we want users to be involved in the product development form the beginning. SLOW DEV - The development was slow due the lack of resources and we weren’t sure how we going to build the ‘shit’, what to focus on. RANDOM – Having niche target audience makes difficult to find users for usability testing. FACE TO FACE – the person (potential user) would come to our office and we would show him wireframes on papers. Asking many questions what they thought about designs and and layout. LONG SESSIONS – this sessions took around 1 - 1 ½ hours Random , infrequent users (once every 2 weeks), sporadic Slow development More face to face testing At least 1 hour session PROBLEM Having niche target audience makes difficult to find users for usability testing. In fast development we need to test more often to validate our ideas. Trying to get into our users working environment and understand their current workflow
- Having niche target audience makes difficult to find users for usability testing. We still needed better understanding of our users workflow. Needed more direction from users to make sure????? We needed more feedback from users to validate our ideas
- Risk of building something people wouldn’t like use.
- a group of people who are actual or potential consumers of your product who are willing to give you advice in your early stages. Typically, it’s because they are early adopters and love what you do, and will do it out of the goodness of their heart (think open-source). This is qualitative feedback, even if somewhat biased, but will be valuable to you.
- a group of people who are actual or potential consumers of your product who are willing to give you advice in your early stages. Typically, it’s because they are early adopters and love what you do, and will do it out of the goodness of their heart (think open-source). This is qualitative feedback, even if somewhat biased, but will be valuable to you.
- Add moth to the graphs In firs round of our UC we conducted contextual interviews before. After we had ux sessions layed out in following weeks. CI took lot of our time, and there was gap in dev process.
- In second round we mixed and conducted CI and UX sessions around the same time, so we were getting more insights and testing current features too.
- line up customer pipeline of both data consumer and data provider organisations and
- Context for feedback Means we can tailor ux sessions so don’t get lost in the details Better targetted scenarios in the ux sessions, makes the situation more realistic. Issue with our users is they get caught up in exact content (show a cancer researcher an alzheimer study and they cant complete the task because they cant get over not understanding the data) Give example of sarah alzheimer ux then to william.
- Understanding how needs change over time Affects how we measure activity and what it means to be a retained user Get broader understanding of user as our questions and company direction evolves (asking same people different things over time) Image - puzzle
- Mahantesh Sebi & zsombor Roy IDEAS BUG REPORTS PLATFORM DOWN
- Before Random , infrequent users (once every 2 weeks) Slow development More face to face testing At least 1 hour session NOW: -consistent, frequent (twice a week) Fast development Online - remote 30 minutes sessions
- https://media.giphy.com/media/tXfr3Oy5ugA92/giphy.gif
- This is something we were warned about when we started with UC, but in my opinion when you communicate properly the importance of being honest people get it. Maybe just remind it now and then.
- By testing for 6 months with 10 users there is lack of breadth so we might be missing out on some detail. It’s always good to get some quantitative methods included in your metrics.
- By having templates, and already defined process the seting up UC will get quicker. However managing it still takes significant time and effort.
- Thank youuuuu!