Leading the Product Pitchfest – July wrap-up

We hope you’ve heard about Leading the Product – the fantastic product management conference Down Under.

We teamed up with the LTP folks to hold a pitchfest for lightning talk spots and we’re thrilled to announce Daniel Kinal & Shiyu Zhu will take the stage in October!!

Thanks to everyone for supporting the folks who pitched their talks, to Seek for hosting, for Leading the Product for the great idea and to our judging panel – Adrienne Tan of Brainmates/Leading the Product, Mark O’Shea of Seek and Dan Johnston of CultureAmp.

Before kicking off the pitches, we had a few of last year’s lightning talk folks – Liz Blink, Katherine Barrett & Zac Andrew – to tell us what it was like and give us a few tips!

  • Know your beginning and end! Give yourself some time to ad-lib in the middle
  • Good memes at the beginning & end help
  • Practice, practice, practice, practice!
  • Know how fast or slow you speak when you’re in front of people.
  • Focus on the content of the talk first and the slides second.
  • Props are your friend
  • Bring a story to life
  • Have 3 things the audience can walk away with
  • That sick feeling you have before getting up on stage is a good thing – it’s excitement!

We had 10 pitches on the evening – including a last minute submission! They were all fantastic!! Leading the Product only had 2 spots available so we hope to hear these other talks at Product Camp Melbourne in August!

Get your tickets to Leading the Product before they sell out (which they do every year!)!

Thank you Seek for hosting!

Our next event is Product Camp – register now and submit a pitch!

Every Product is a Service – June wrap-up

We gathered a couple people who work in product and a couple people who work in design to discuss if every product is a service and how we can work together well.

This would not have been possible without Service Design Melbourne & NEXT, a division of the Reece Group, who kindly sponsored the evening.

To introduce our panel, we quizzed them on their qualifications…
Dave Calleja – Associate Design Director at Isobar. Has a degree in design.
Kate Edwards-Davis – Product Manager at Karista. Studied classical music performance & philosophy.
Dr Stefanie Di Russo – Principal Designer at NAB. Holds design degrees including a PhD in design thinking.
Daniel Kinal – Product Manager at MYOB. His degrees go across economics, accounting, marketing and a some information systems stuff.

And our moderator – Liz Blink – Digital Customer Experience Manager at Department of Environment, Land, Water & Planning VIC Government. Holds a PhD in immunology.

Which goes to show we work with people from very diverse backgrounds & there’s different avenues to getting into the work we do.

First we surveyed the audience to see which camp they belonged to… service design, product, something else or multiple areas. 57% of our audience said they were something else! From the shouts from the audience, it seemed a lot of folks identified with ‘UX’.

kicking off our session with service design melbourne #prodanon

A post shared by Product Anonymous (@product_anon) on

Dave raised the definition of ‘product’ and how you can’t really divide up things like Netflix into those definitions of ‘product’ or ‘service’. Do you think Netflix is a product or a service? He feels to discuss the two, there needs to be some semantic mud hurdling.

Steph pointed out that service design has a time element with artifacts and actors while product is the artifact itself at a certain point of time.

While Daniel thinks it’s all ‘product’ going across goods & services lines. If we are talking about eating a mandarin for breakfast or getting a scalp massage there’s a clear ‘product’ or ‘service’ in those definitions but we probably all work on complex products which have both tangible & intangible elements. There is a basket of benefits you’re offering the end customer.

Kate asked ‘who cares?’. The outcome is the important thing! We’re trying to package something together to help meet a customer’s need. ‘Products’ co-exist with ‘services’ and we even buy some ‘products’ despite the ‘service’ we receive with them.

Kate brought a prop along to prove the point that a ‘product’ or good can always be improved when you think about the ‘service’! Who Gives a Crap is toilet paper that’s been wrapped in a ‘service’. They offer a subscription service so you never run out and they are focused on social good by being environmentally sound and donating profits. They are disrupting with their ‘service’.

There was lots of talk of physical products – mandarins, toilet paper and then coke! Steph discussed the difference between a ‘service’ and an ‘experience’. The taste of the coke is part of the ‘experience’ while there’s actors & elements that enable the ‘service’ to exist.

But Dave brought it back into the realm of the digital (which most folks in the room work in…). When you are using a digital ‘service’ like Netflix, there’s definitely a physical attribute which might be sitting on the couch, having a tablet or remote in your hand. It’s how the end user experiences this, how the end user views that as the product. What words we in the industry use to discuss it isn’t as important as the outcome.

Service design is a design methodology & an approach to tackle problems. There are lots of frameworks & ways to understand problems and each discipline (product, design, marketing, etc) will have preferred ways. You can have customer experience people who do not use design methodologies and may rely more on marketing.

Daniel sees the rise of design thinking as a level of maturity in seeing the value of not going right to a solution and looking for ways to truly articulate the problem.

There was some discussion on how good ‘service’ can recover people when they have a bad ‘product’ experience. The ‘service’ element is what helps to get the good online reviews.

Steph asked Daniel if a good product person should have a design background which lead to a discussion about working together.

Everyone agreed a team needs to exist which brings different perspectives and skill sets. Kate brought up the skill set of being able to deliver a product at a price point that will sell & the act of using the organisation’s capabilities. Daniel discussed one of the responsibilities for a product manager is to be the advocate for the stakeholder who is not in the room (including the customer). Dave said if the team isn’t considering viability, feasibility & desirablity together, you’re unbalanced. Steph focuses more on the desirability while working with product people but is also thinking about the other two.

Healthy debates where you’re not so dogmatic about your position are best said Steph. Daniel wants designers to have a different perspective and be even more customer driven than he is so they can have creative (good) conflict about the different ways to reach a specific goal. He’s found that the more experience a person has, typically they have a level of maturity that allows them to leave their ego at the door about whose idea it was but at the end of the meeting, you are all focused in 1 direction.

Kate recommends spending time together to understand the customer & strategy. What a person’s title is doesn’t matter as long as you are there to learn & understand from each other. Dave also mentioned psychological safety of having those conversations & suggested leaving the drama to Love Island, not the office.

Thank you to NEXT, a division of the Reece Group and Service Design Melbourne for a wonderful evening!

 

Check your bias at the door – May wrap-up

A cognitive bias is a shortcut your brain takes to make decisions. Cognitive biases can impact our decision making, our memory, the way we interpret research and more.

As product managers need to understand our customers & their needs, motivations, problems (etc), it is a ‘mistake’ to let your lazy brain fall prey to the cognitive biases that make you hold onto your own preferences or beliefs, no matter what evidence is presented!

Our speaker was David Di Sipio, a registered Psychologist and currently working at Squiz as a UX Consultant. David creates great experiences by focusing on what makes people tick. His approach is grounded in academic research, big-data and best-practice.

David ran us through some great examples & how to manage the 6 most common biases:

  1. Selection Bias – who are you talking to?
  2. Framing Effect – the words you use & way you present your questions
  3. Confirmation Bias – focusing on the information that reinforces your ideas & ignoring the ones that disprove your idea
  4. Observer Effect – subconsciously influencing someone with your body language
  5. Anchoring Bias – putting too much emphasis on the 1st bit of info we receive
  6. Clustering Illusion – seeing patterns when none exist

After walking thru these biases, David gave us time to talk thru some of the biases we’ve fallen for & there was a bit of conversation regarding which is our favourite bias!

Want more info? You can view David’s slides or read his article on Medium which also contains the links to all the great videos he showed.

Thanks again to Origin for hosting us.

Origin Energy

We’ve announced our June session – RSVP now for a collaboration between Product Anonymous and Service Design Melbourne discussing ‘every product is a service’.

Does data or design win with product folks? March wrap-up

Does data or design rule supreme for us product folk? When we’re deciding what to work on or how to create whatever we’re creating… which do we lean towards?

To debate data vs design, we gathered a fabulous panel: 

Firmly on the data side was Marty Kemka from Northraine. Marty is a data scientist and entrepreneur. He’s worked on projects where something needed to shift and he says as long as you know the metric & design the experiment properly, the data should be able to show you the way.

On the design side, from Cogent, Amelia Crook is very interested in what human need is being solved and thinks people leave a trail of data but that data can’t give you the insight as to why the person has done something. The why is what gets you to the need.

Also, Steve Bauer was sitting on the design side. Steve also wants to understand the human element, is appreciative of qualitative research & yet knows his way around the numbers.

And finally Jane Register who has a design background and said she was also representing design. She’s previously worked with qualitative research but currently works on a product with lots of data. She has more data available now than ever before and finds that exciting.

FYI Jane & Steve work together at Aconex and prior to the event, Steve thought Jane would absolutely be on the data side. Jane later talked about how as a UX designer, she can’t have data without design nor design without data. For her you need to data to tell you some things but you also need the ‘why’.

We also had a great facilitator for the evening, Jane Scowcroft from Data61.

#prodanon

A post shared by Product Anonymous (@product_anon) on

Everyone had a card to vote if they were ‘data’ or ‘design’ and the initial check suggested most were leaning towards the data side. Our unscientific count was data in the lead at maybe 60% of the audience. The subsequent discussion may have gotten us to a different outcome!?!

Delving into the data isn’t easy according to our design folks. You need to know the context of the questions asked, if the data is spread across different tables or db & there will be back & forth between you & the data analyst in order to even craft the right questions. You can get lost down data rabbit holes. Marty agreed that it needs to be a collaboration with the data analyst because you need to realise there will be database changes to work with, you need to know the context of when an event happened, you have to really understand what you’re measuring and what confidence level you have in all this.

We also touched on using the data to tell the right story of your product. How are you measuring success, what are you optimising for and is that in the context of your product, your department or the entire (especially when large) organisation?

About half way thru the evening, another audience check had us about 50/50 split across data v design.

We see the value of bringing data scientists & analysts into the design fold to help them do their jobs better. Marty recounted a project he worked on where he went out to the field to see how things where done which then greatly helped when he was back at his computer. Over the years it’s been about getting developers to understand the customers more… now we need to bring along the data folks.

Amelia mentioned that looking at an excel sheet doesn’t help you connect with your users. You don’t gain a lot of empathy amongst the cells and rows! Taking folks out in the field so they can meet users is great motivation for wanting to solve that problem for the user.

At the end, the panel couldn’t help itself and admitted needing both data and design to get a great outcome in your product world. I think maybe even Marty started coming around 🙂 And our audience was pretty even 50/50.

Thank you to Jane! Thank you Amelia, Jane, Marty & Steve! Thank you Data61 and Intrepid Group for sponsoring the evening!!

February Summary: Building & Scaling Product Teams with Rich Mironov

We kicked off the year with ‘Building & Scaling Product Management Teams’ because it was one of the most requested topics in our year end survey and it’s something Rich Mironov knows a bit about as he often comes into a company to help them sort out their team (and of course product).

After a quick review of what a product manager’s role is, Rich got right into the team aspect. Both problem finding AND problem solving are team sports, not only for you THE product manager. When there isn’t someone within the business who is knowledgeable about product management, you will find someone is ‘playing’ product manager.

At a startup, the founder who has the passion for the problem & users will often be working on the product. A startup founder has a lot of other responsibilities so need to think about hiring a PM when the sales pressure is increasing, they need someone to help them FOCUS & scalability is needed – often this is somewhere between hitting 12-25 employees. Rich STRONGLY believes you need to bring in someone who with experience at this point – not someone with deep domain knowledge, not someone at the company in another role, not someone with a ‘scrum’ or ‘project’ word in their title but someone who’s been here & done that & has the scars.

At any company, when it comes to building the product team. Rich believes it’s better to reduce the distance between the customer/user, the product person & the development team. His favourite structure for a team is a product person & the dev/ux/design/etc team to be close (physically & collaboratively) with the users via frequent learning conversations. He is not a fan of the customer feedback/problems/conversation filtered via sales or a single product person or marketing, etc.

Which is when we hit the controversial part of the evening – Rich believes the ‘product owner’ job is setup for failure for several reasons including they don’t have time with customers to understand the problems before writing stories & they’re not focused on the end value but productivity focused. Instead of having the owner & manager roles as separate people, it should be the same person doing both roles.

Multiple screens #prodanon

A post shared by Product Anonymous (@product_anon) on

Lastly, we talked a bit more about the different roles in a product team. The product manager should be shipping great individual products, thinking 2-4 quarters ahead & is a relentless communicator of truth. The Director of PM should be focusing on processes, resources & the team. Budget & Strategy, planning for the next 6 quarters & ‘keeping the trains running’ are the focus. A Head of Product/VP is part of the executive team, focusing on aligning strategy, products & the organisation.

Rich’s 4 takeaways for the evening were:

  1. The need for product management is not obvious to a lot of people including founders/CXOs
  2. Hire for product experience
  3. Product Managers own real market value and direct customer learning
  4. The head of product manages the PMs AND the executive team

Rich has posted the slides for your reference and perusal. And for those who couldn’t be there in person check out the full recording of the session.

A big thank you to Rich & Zendesk for a wonderful evening!!!

Zendeskmironov.com

November Summary: Product Manager v Product Owner!

How many times can the product community talk about the differences between product managers & product owners? Apparently we’re not at max conversation yet!

This was one of the topics suggested during Product Camp and while it didn’t have enough votes on the day, we had several people ask us to run it as a session.

Steve Bauer, a product manager at Telstra Wholesale assembled 3 folks with different backgrounds who have been across the 2 roles to hash out the differences & how they can work together.

Our panelists included Michael Sloan who has recently changed roles from product manager to product owner at NAB. Nadia Gishen who’s currently a product owner at Aconex but has been a product manager before. Manoel Pimentel is an agile coach at elabor8.

One man who feels strongly about this debate is Nick Coster from Brainmates. Unfortunately Nick couldn’t attend as he was overseas but he made a guest appearance. 😉 You can read his thoughts about the Dynamic Duo on the Brainmates blog or watch the talk he gave at the 2015 Product Camp Melbourne

@nick.coster makes a guest appearance #prodanon

A post shared by Product Anonymous (@product_anon) on

Before kicking off the discussion, we wanted to know what roles the audience had – were they more owner or manager? Much to our surprise, they were neither! In the audience, 40% were not product owners OR managers (!!!!), 25% were product managers, 20% were doing both roles, 15% were product owners.

If you work in product, you already know companies define the role in a variety of ways. If you are a product manager and work with a product owner (or vice versa), how do both of you set yourself up for success? Our panel agreed that talking with each other to clearly understand what you feel responsible for and what the company thinks you’re responsible for is required. This should be a conversation you have – not a job description.

Some other random tidbits from the evening…

The business analyst (BA) role typically sits between product & development to write very detailed requirements but with the rise of the product owner role, BA roles are disappearing.

A danger of being a product owner is being an order taker in terms of what is built, how & when. Product owners need to think & talk about how they can support both the product manager and the team. They can add value in many ways so determine what works best for your current situation.

No matter which role it is, our panel recommends looking for a few things when hiring someone – problem solving ability, communication, resiliance and someone who doesn’t tire easily 🙂

#prodanon

A post shared by Product Anonymous (@product_anon) on

There was some conversation regarding ‘product manager’ being a cooler title than ‘product owner’ – until Manoel suggested the future title will be ‘problem owner’.

The slides for those who want the references and the jokes 🙂

Thank you to inspire9 for hosting!!!

inspire9 logo

This was our last event for 2017. Product Anonymous will kick off in February 2018 so sign up to our newsletter, add yourself to meetup, follow us on twitter, join the slack group, follow in instagram… all that good stuff! See all the links.

September Summary: Chatbots & Voice

At our September evening, we had 5(!) folks talk about using chatbots and voice activated products within your product.

Keith Swann began the evening with a bit of background on chatbots. Keith is a Lead Consultant at Elabor8 and while he was at Sensis / Yellow Pages he was able to work on bots. Daniel Galindo, the lead ontologist at Sensis, joined him in the presentation to share with us some of the experiments they had tried with working with natural language requests.

Did you know the 1st chatbot was ‘born’ at MIT in 1966? Eliza was a psychologist you could chat with.

In 2005, IKEA introduced Anna which was another big leap for the use of chatbots.

Keith giving us some robot history #prodanon

A post shared by Product Anonymous (@product_anon) on

Chatbots come in handy for sharing information with people. A good example is to collect information via chatbot while the customer human is awaiting the customer service human. This can decrease the amount of human time involved in the call. Sensis used API.AI and Python.AI for their business search in this manner.

Keith also talked about how chatbots can be easy to create – but it’s not easy to make it work correctly. It’s also not a set & forget product as you need to continue to manage user expectations. One of those expectations that’s the hardest to get right is the natural language of the chatbot. Getting this right is important as it impacts on people’s engagement with the service.

Jen Leibhart & Stuart Hill from Australia Post talked about developing a chatbot as an experiment & how to approach giving your chatbot a personality.

The team used an internal hackathon as the opportunity to experiment. They wanted to drive awareness and traffic to a MVP product they were working on and the primary audience for the MVP were digital folks who used Slack on a regular basis so a Slackbot was a given.

At the beginning of the hackathon they had grand ideas of having both a Slackbot and a bot in Facebook Messenger. They wanted their bots to have great personality and do x,y AND z. That’s a lot of work for a 1.5 days so they kept functionality x and dropped y & z. 🙂

A few weeks after the hackathon they focused on the Slackbot, put in a little more effort and launched the bot across multiple slack workspaces. Six months after that hackathon, the Slackbot still has limited functionality but does indeed drive traffic.

The next experiment is to see how conversation increases that engagement. Stu was looking at how to build conversation with the bot. This includes thinking about both tone of voice and attitude. Just as you’d think about voice when building a brand or website, you need to translate that to the bot.

Stu thinks of it like one of those ‘choose your own adventure’ games. You need to think through the conversation a human will be having with a bot. To help give a bot more personality and be useful, Stu has been creating conversation maps to think thru the variety of answers the bot needs to provide. While it’s great fun to teach the bot to tell jokes, you need to make sure it always leads back to delivering value.

Advice from Jen & Stu if you’re creating a bot:

  • As with any channel, will it reach your target market? Is your audience using FB or Slack or something else?
  • Focus on 1 task that can be done well. You can expand beyond 1 after that’s working well.
  • Use conversation maps to ensure the bot delivers the information required.
  • Give it a go, learn & experiment!!!

How to build your Chatbots personality #prodanon

A post shared by Product Anonymous (@product_anon) on

Srinjoy De works at RACV in their New Products team. The team are currently working to bring intelligent tech solutions for the home. Previously he was at Catapult Sports, a leader in wearable athlete analytics for elite athletes.

Srinjoy talked about the possibilities of using voice technology to improve customer experience. Washing machines, fridges, cars and other machines are now loaded with Amazon’s Alexa. With Google Home recently launching in Australia, we’ll start seeing more and more voice products.

At RACV, they are running a trial using Google Home in some resorts. When you enter your room, there’s a Google Home which you can ask about the local weather or traffic or other holiday related queries. Using the device to play music is popular though in the future it could become a personal concierge (by controlling the lights or more). Since the device is so new to the market, we wondered what the adoption & onboarding was like during the pilot – Srinjoy said people adopt the technology quickly.

Srinjoy on a Google home experiment #prodanon

A post shared by Product Anonymous (@product_anon) on

Thanks to everyone for coming along last night! Fantastic eve of new tech learnings. Summary will be on blog soon #prodanon

A post shared by Product Anonymous (@product_anon) on

Thank you to Fiona Knight for volunteering on the night & helping to pull this blog post together!

Big thanks to MelbourneIT for hosting us!

July wrap-up: You can prototype ANYTHING!

Prototyping – typically we digital folk think of going from some sketches to maybe a clickable prototype then to a fleshed out, semi-built format which we can test on.

But what if your product wasn’t digital? And even with digital, can you do something different?

Jes Simson is a product manager of greeting cards. Not digital but paper. And she loves to prototype. Having a physical product reminds us of the importance of risk. When you’re producing 1,000 products a year with an expensive production cycle, you want to test & validate along the development cycle.

In the grand scheme of things, there’s a lot of similarities between digital and physical. Start by looking at your insights & research. Prototype and soft launch with 1 item until you’re ready to go bigger and branch out.

Jes says a prototype is just a question embodied – and first you need to decide what will kill it?

Brainstorm your assumptions in each category (desirability, feasibility, viability). Try to surface every assumption you have & use tools like a risk template in order to get as many as possible.

After you’ve discovered your assumptions – rank them! Take the riskiest assumption & decide what your questions are. Find the cheapest way to test this. ‘Cheap’ could be money, time or the people involved.

Some of the ways Simson tests assumptions are taking a short period of time to create a mood board and see if it resonates with card buyers. This is quick to produce & quick to get feedback.

One ‘fabulous’ example of a prototype Jes shared was using a post-it note to illustrate you could fit the word ‘fabulous’ on a card – that it wasn’t too many characters and you could stylize it in such a small space. Point made & progress continued.

Ask yourself who’s in the best position to answer these questions? You might not be able to access them depending on budget or time so … who’s available?

Be willing to throw things away, to iterate quickly and focus on the getting to no.

Jes also thinks of a prototype as a communication tool. A tool which needs to change based on who your audience is. Your design team may need 1 type of prototype while sales or finance will probably need another. Keep those team specific prototypes with the team… don’t show your CEO the grey lead sketch 😉

To help us understand you can prototype ANYTHING, Jes gave us aluminum foil and a challenge. This then became the most photogenic Product Anonymous session EVER.

A big thank you to Jes for a great talk and to Sportsbet for hosting us!
Once again, a huge thank you to Fiona Knight for taking these notes!

Directing the Product – June Wrap-up

Our June session brought together a panel who lead a team of product managers – as well as a product. It was a fantastic evening covering a wide range of topics, from cats and racehorses to ***holes.

We were joined by Susan Teschner from 99designs, Luke Bongiorno from Nintex and Rachel Morley from REA.

Once again, a huge thank you to Fiona Knight for taking these notes!

Product people always have diverse backgrounds – our panelists included. Susan has a political science degree and accidentally fell into tech via project management. Rachel was studying Law & Arts degrees before getting enticed into this new thing called an ‘intranet’. Luke started in tech but realised it wasn’t for him. Fortunately he was in a company with opportunities that lead to product management.

How do you nurture product management teams? What do they need?

Rachel, Susan & Luke all mentioned that managing product folks can be challenging since PM requires such a broad spectrum of skills & interests. Susan & Rachel talked about how a great product team is made of people from across that spectrum but that diversity is part of the challenge of managing them and helping each individual to grow in their career. Luke looks at how they can build their skills to be more holistic.

Ensuring the team of product folks are working consistently across the business was a theme both Luke & Rachel raised. That includes making sure they’re in sync with the company’s vision

What’s it really like managing product folk? Rachel finds it’s sometimes like looking after a bunch of cats that scatter when they see you. While Luke compared us to managing racehorses who are strong willed leaders with a range of skills and experience.

Tips? Show them respect. Nurture the diversity. Encouraging communication with their peers and other teams.

this evening hosted by Nintex

A post shared by Product Anonymous (@product_anon) on

What does the business expect of the product management team? What do you ask of your team?
As with much in product management… it depends!

REA is mature in understanding what it wants from a product management team but at previous roles Rachel needed to champion the value of a product management team. These days she focuses on creating the best opportunities for work relationships, establishing those relationships between people & creating harmony.

Luke is helping his team understand their boundaries & show them how to have space to do their job.

Susan asks for a focus on the goals. Doing the impossible by being down in the detail and up at 30,000 ft keeping an eye on the end game. We have to learn to live with some fires. The incredible attention to detail and passion for delivering great products is the very thing that can also distract us.

Cue the conversation about product people fighting fires versus keeping an eye on the long game.

Going from product manager to product director – what is it like? Are you still working on the product?

Luke is relatively new to the role and learning – while still influencing all of the products. Rachel added that doing actual work on the product depends on the size of the team. If you have more than 8 people, you’re in a true leadership role & need to love helping people rather than the products. Susan thinks it can differ depending on how you define success and what it means to you. Being successful doesn’t always have to mean managing people so you should decide what is meaningful to you. Liz brought up the difference between rock stars & superstars which come from the Radical Candor framework – TED talk or check out the book and site.

How do you keep the alignment with product managers and their development teams?

Lots of consensus on making sure there is a product vision across all teams, making sure there’s clear alignment on the objectives and measures on how they will achieve the objectives.
Rachel believes clear goals are the way for teams to be autonomous and self sufficient.

Product managers have broad & different skills sets. What are the detailed or deep skills product managers need?

Susan — There are lots of different kinds of products that need different kinds of product managers. We need the good old ’T’ person. Good coverage of the basics and deep knowledge of something — UX, data, growth, whatever they’re strong in and passionate about.

Rachel – Always talks about goals. Rachel gives them time to look at their goals & sends the prioritisation list to the executive team. Being able to focus on the goal and prioritize the things that will bring you closer to the goal is important. Being busy and getting lost in the detail can be a distraction.

Luke – Something to watch for is product managers who work on what they’re good at and avoiding goals that might not play to their strengths. Bring the product folk together to talk through this – make sure the team talks about strategy and doesn’t only talk about the tactical.

What are the top three things that makes a good product manager?
Rachel – Start at hiring and look for attitude, aptitude and empathy. If someone is committed and enthusiastic, that’s a great start!

Susan – Smarts/ intellectual horsepower, humility (realise there is the likelihood of working for no individual credit but all reflecting back on the team), judgement/decision making/ instinct

Luke – Switched on/ thinking ahead/ inquisitive, passionate/ excited about releasing products, emotional resilience

Thanks again to Nintex for hosting!

See you next month at Sportsbet where we will be talking Prototyping. RSVP now.

May wrap-up: Working with User Research

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