Monthly Archives: May 2017

May wrap-up: Working with User Research

Posted on by
Reply

WOW! What a fantastic evening! If you’re interested in user research, I hope you were there! Otherwise read on for the summary.

Big thanks to Fiona Knight, one of our volunteers, for taking great notes!

Using Experience Sampling for Rapid Insights into User Needs

George Cockerill started the evening off with a discussion about how his team approached gathering user research in a project building a smart assistant for students at Deakin University.

The team decided to use the Experience Sampling method. Other methods like interviews & diary studies have participants recall their past whereas experience sampling gave them access to detailed immediate needs.

With experience sampling, you ask short, easy to answer questions throughout the day. For this project, the same two questions were sent to participants eight times a day over a week. Occasionally the team would add an optional question. Experience sampling allowed the team to get to very recent needs & the student’s behaviour.

To collect the data, George used PACO, a free app that builds experiments quickly. It’s great for experience sampling and since it’s an app on participants’ phones they can take photos to include with their answers.

Tips for success

  • Get maximum value for the method – be clear about the research goal
  • Don’t rush, plan meticulously & plan to be flexible. Plan even when you need to go fast (it actually helps you move quickly!)
  • It’s a complex set up – test it; test your questions and mechanics
  • Get the most from people – recruit and onboard carefully. Establish how much data points you need to help determine how many participants you should have. When you screen them, ask questions along the lines of what you’ll be asking during the research. If they can’t answer in the screener, they probably won’t provide good data during the research. Your onboarding needs to have very clear instructions. George made a video to help explain the app and expectations of the participant (including what they needed to do /when they’d get paid).
  • Monitor it! Experience sampling is not a ‘set it & forget it’ method. You can be encouraging to the participants or ask them to tell you more about a specific thing. It’s awesome if you can instill a shared purpose of what’s going to happen with the data they provide.
  • Use the data to help refine the problem. Start finding themes, create categories, map answers to categories to find patterns, map data to graphs and examine categories to fine tune them. Look for trends. With participants using their phones, images will pick up detail the users might not think to say like how they solve their problems, their hacks, etc. You can combine the data with other research (both qual & quant). For this project, George combined experience sampling, resonance testing, journey maps from user interviews and ‘day in life’ models.

Currently the student smart assistant is in a pilot with a set of students. We’re looking forward to hearing how it goes!

George Cockerill on experience sampling #prodanon

A post shared by Product Anonymous (@product_anon) on

George recommended two excellent references that he found helpful in planning and running the research:

Why is marathon running important when introducing user research to an organisation?

Electronic Arts operates 8 research labs across 4 countries but it’s still early days for the games industry to embrace user research. In the APAC region, Kostas Kazakosis the 1st UX researcher at EA and thus needed to help communicate the value & importance of UX research.

Using ‘The Reflective Practioner‘ by Donald A Schon, Kostas reflected on his journey as a marathon runner and introducing UX research to a company – both ongoing!

Kostas finds there’s 8 stages to long distance running

  • Excitement where anything is possible! The organisation has no prior exposure to formalised UX research.
  • Denial when doubt starts to creep in. Here Kostas realised he didn’t know much about the FireMonkeys’ development process.
  • Shock where everything seemed to be really difficult. Kostas had to show the value of UX research, create a research space and creating research protocols to suit the games industry. Kostas’s plan was relying on the importance of dialogue: talking to people, understand what they do, and showing UX research helps them. This is where empathy is important but how do you do this? You empathise with the data and people and match it to research question.

  • Isolation or the fear you’re not going to make it. Having talked to as many people as possible, you need to accept the feedback and adjust your approach
  • Despair usually happens about mile 19 in a marathon. When you start to question if you really can do this, if you’re ready to do this and will it be ok?
  • The wall at mile 22 is when your brain doesn’t talk to your body anymore. You need to take one step at a time to keep going & identify mistakes and address them quickly. At EA, this meant all that earlier work to establish relationships with the team enabled collaboration. He had helped educate them & gave them ownership. The teams had begun the process of seeing the importance of data & value of user research.
  • Affirmation at mile 23 is feeling like you have a break thru. This is the stage Kostas is currently at work. He’s seeing people want to get involved in the UX research and wants to be able to sustain that team participation.
  • Elation at the finish line of mile 26 is when you’ve achieved the goal and need to shift your mindset towards the future. At work, this is what Kostas is working towards.

In summary, the DECEMA frame of reference that Kostas described – Dialogue, Empathy, Collaboration, Empowerment, Mutual respect and Advocacy – can take you a long way when introducing user research to your organization!

Thanks to both George & Kostas for a great evening and to Seek for hosting us!!!

seek

April wrap-up: The Making of Milanote

Posted on by
Reply

In April, one of the founders – Michael Trounce – of Melbourne startup Milanote, the notes app for creative work, let us in on a few secrets of their success.

Time

First of all, it’s been 3 years in the making. The 4 founders already have their own UX consulting business, Navy Design, and always had the ambition to start their own product business so back in 2014 they dedicated a week to working through potential product ideas. Ideas like a weather app and a hydration coaster were investigated then ditched (the coaster was referred to as a gimmicky Xmas present…).

They started working on a product which would solve a need their team had. Previously they had used post-its, a wiki, and other note keeping software but they all lacked a way to make connections and share.

During 2015, they began doing research with designers & other digital creatives and found there was a gap in the market for the product they had in mind. They build a (crappy) prototype & started using it in-house. They knew they were onto something when they found it worked better than any of their previous tools – whiteboards, Evernote, Trello, etc.

It later clicked that what they’d built wasn’t just a tool that could be applied to the UX design process, it was a tool that could be applied to any creative process. This insight broadened their market significantly and gave them the confidence to then break out the product from an internal project within the consultancy, to a product business in its own right.

It wasn’t until 2016 the focus changed to execution and as a result the hours of effort went up! They hired a small full-time team and ran a closed beta program for 6 months. Until then they were seeing where it would take them but those days were over.

They began granting early access when you referred friends and adding people to the waitlist by writing articles on Medium like ‘Why Using Evernote is Making You Less Creative‘ to get the word out (that article drove a lot of signups!)

When they did launch in Feb (2017), there was a flurry of press including reaching #1 on Product Hunt, the front page of Hacker News and #1 for the week on Designer News. It’s also been written up on Lifehacker and The Next Web covered it while it was in beta.

Challenges

Milanote can’t see your content due to privacy reasons. They have no idea what you are doing with their product or how you are using it which makes deciding on what features to build and understanding customers somewhat difficult.

To overcome this challenge, the Milanote team are using a mix of quantitative & qualitative methods to draw out data and feedback from their users along the different points in their product journey. The most obvious tactic is talking to its customers.

Michael from Milanote talking about the early days

A post shared by Product Anonymous (@product_anon) on

Pricing

They are continuing to evolve their thinking on pricing & looking at different models to help align the value of the product with the price.

Acquisition

The articles at launch including Product Hunt, #1 for the week on Designer News and word of mouth helped greatly with new customers. They need to experiment with other methods now to find scalable and repeatable ways of driving acquisition long-term.

Hiring

Milanote are currently looking for both developers & marketers. Check out their jobs.

AND the most shocking news of the evening!!! The Milanote team do NOT use post-its anymore! They have bare walls!

Thank you Michael for a great talk & elabor8 for hosting the evening!