Do Stakeholders and Customers EVER see eye to eye?

Join us on Thursday evening June 19th for ‘Do Stakeholders and Customers EVER see eye to eye?’

We’ll be discussing:

  • How do you balance customer need against business requirements
  • How do you connect the right customer need to the right business outcome
  • The importance of identifying drivers for each stakeholder group – and their value
  • What’s important? What can be compromised?
  • What has worked & not worked
  • What happens when things don’t go as planned

A product manager has a unique role in a business – one of the only roles in an organisation that is satisfying two masters – both the customer and the business. It needs to be in the DNA of the product manager to strike the balance between meeting the customer’s need and delivering on business outcomes.

Taking into consideration the various stakeholders (both inside & outside the business) plus the customer need may not lead to the best business outcome.  What steps can you take to make sure it does? How can you make sure you are satisfying both sides?  Is the need you are satisfying connected to the right business outcome?

Mat Vine, former Head of Product & Policy at Bupa Australia and current consultant for start-ups, not-for-profits and health projects will lead this discussion.  See his full bio below.

Product Anonymous is now on Meetup & we’ll be using it for event RSVPs.   Please join us there and RSVP now for this event.

6pm for a 6:30pm start at Royal Melbourne Hotel on Bourke St

Mat Vine is an experienced commercial executive with nearly 20 years experience in product and marketing and thrived in environments with P&L accountability.  He has worked with brands such as Sensis, NEC, London Electricity and Bupa. More recently at Bupa led the teams responsible for developing and delivering customer value propositions that resulted in significant uplifts in profit and revenues in B2C, B2B and international markets. Mat also spent some time in the UK headquarters where he led the customer value proposition agenda for Bupa businesses around the world – cross fertilising high value initiatives and building global CVP development capability. He is currently consulting on interesting projects in health, not-for-profits and start-ups.

May 14th event – Talking MVP – at 99designs

Our next event will be a session on Minimum Viable Product (MVP).

We’ll cover:

  • what is MVP – and what isn’t it
  • how do you ensure MVP is really testing your assumptions
  • what you can learn from MVP

Hear from other product manager folk and founders about their trials and tribulations with getting to an MVP and if it worked or not.  We will take questions from the audience for the panel and encourage discussion amongst our speakers and audience.

Our facilitator will be Jock Busuttil, Founder of Product People.

Jock is a product management consultant, author and startup mentor with over thirteen years’ experience working in technology. He is the founder of Product People Limited, author of imanageproducts and has a book coming out soon to be published by Hachette / Grand Central. Flick him any questions you would like to ask on MVP or of the panel @jockbu

We have a great panel of product managers and start-up founders joining us to share their experiences. Let us introduce them:

Susan Teschner, Super Product Manager at 99designs

Susan’s degree in Political Science qualified her for nothing, but her journey through the ranks of product management sure has. Having tried her hand at all angles of product, Susan’s found that straying too far from either the thinking or the doing makes her seriously cranky pants. She’s most happy building collaborative, creative and generally ass-kicking teams, learning daily, delivering on a shared vision and laughing hard along the way.

Currently looking after a few teams of engineers, UX and product managers, Susan’s work growing 99designs — the world’s largest marketplace for graphic design — keeps the cranky pants away.

Tom Howard, Co-founder Adioso

Adioso is a new kind of flight search engine, that supports unmatched flexibility on destinations, dates and other travel motivators.  Adioso was initially launched as an MVP in January 2008, and due to the complexities of the travel industry, has taken till 2014 to reach maturity.  Tom is now working on a mobile-focused flight search & booking application.  He will talk about the MVP that initially launched Adioso, contrasted with the one he is currently building for mobile”.

Emma Stabey, Senior Product Manager – Candidate Experience, SEEK Limited

Emma Stabey is a Senior Product Manager at Australia’s #1 online employment site, SEEK.com.au. In her time at SEEK she has managed the experience and vision for SEEK’s first foray into iOS apps, and evolved the candidate profile on the desktop channel with the aim of creating a more personalised experience, and is about to take on a new role to head up the Product team for SEEK Learning.

Janet Horwell, Product engineer at Geoplex 

Janet Horwell is a Product Engineer at Geoplex, a GIS mapping services company. She’s been working in a team on a dashboard MVP and will be running through her experience in measuring risk and validating a concept to the point of MVP.

We look forward to you joining us!

Eventbrite - Product Anonymous - May 14 - MVP

Note the new day of the week and location: Wednesday night at 99designs, level 2, 41 Stewart St, RIchmond, which is just behind Richmond station.

Time: 6-6:30pm arrival & drinks. Talk starts at 6:30pm. We wrap up about 8pm.

March wrap-up – The 5 Skills for UX Mastery Workshop

We product focused people are concerned with the customer experience and of course that includes the usability of the product. For our March session, we asked two UX pros, Fox Woods & Matthew Magain, to help increase our skills & knowledge of UX. – Liz & Jen

A Bit of Back Story 

For the most recent Product Anonymous meetup on the 20th March, Liz Blink and Jen Leibhart invited us to come and talk to product managers about UX.

We are:
– Fox Woods, a UX and web consultant who works with startups and agencies on various types of projects – from analysing product ideas before they’ve even become a MVP, to crafting the information architecture and user experience for iconic Australian websites.
– Matthew Magain, the co-founder of UX Mastery, a website chock-full of resources for UXers and people interested in learning more about UX, including the UX Mastery community forums and a range of ebooks. Matthew also creates whiteboard animations and illustrated videos for companies that have complicated ideas that they need to communicate in a simple (and interesting!) way.

We both attended a Product Anon session before we finalised our plan, so that we could suss out what to talk about. It seemed like many product managers are already heavily involved in User Experience (UX) areas of work – whether from working with their UX teams or UX experts, or because that work sometimes defaults to them, or because they choose to champion good user experience in their teams, as no one else is looking after it.

The 5 Skills for UX Mastery Workshop

We decided to do a workshop (activities are much more interesting than passive listening!) rather than a talk, and we based the workshop on Jared Spool’s theory of The Five Indispensable Skills for UX Mastery.

We handed out a one-pager to everyone, and began by going through some descriptions and examples of the 5 skills.

Download “The 5 Skills for UX Mastery” sheet

1. Sketching

Sketching is a fantastic way to facilitate idea generation and communication. Having a whiteboard nearby – at all times! – for sketching out thoughts, sketching ideas with others, brainstorming… can be invaluable. The brain is able to loosen up and think in different ways when you’re playing with something that’s just “rough work,” unlike when you’re dealing with rigid letters, numbers, diagrams, boxes, lines. We don’t mind making mistakes when we’re in sketch mode, and sometimes great ideas can come from strange mistakes!

From talking with the product managers at Product Anon, it seemed like this is a skill that could be nurtured more in product teams.

2. Critiquing

We all have to critique ideas, designs, products and much more in our work, but we do want to remember that critiquing is a skill that can be improved. Skilled critiquing often goes hand-in-hand with skilled communicating: sandwich a criticism in between two positive comments; always use constructive criticism; be objective in your critiquing; always note down assumptions that people are making, so that you can test them later; and tie reasons for your criticisms back to your UX research: your users, their needs, and their empathy map.

3. Storytelling

We had made a guess that storytelling didn’t play a large part in the product manager’s role, but we were wrong! From listening to our attendees, we learned that most product managers find that they’re often using storytelling techniques – especially to communicate stories about their users to their development teams.

There are many different ways to tell stories to aid communication and understanding, and we had an example activity at the workshop: Communication Comic (details below).

4. Presenting

Like critiquing, we all need to do a lot of presenting in our roles. This is a skill we can always work on – and some of these other skills (like storytelling, and sketching) can lift our game enormously.

Like many of these soft skills, learning how to deliver a killer presentation is a lifelong skill that is useful in all aspects of business, beyond the worlds of Product Management and User Experience.

5. Facilitating

Lastly, facilitating. As we mentioned above, having a whiteboard culture (whiteboard nearby, at all times!) can really help with the facilitation of meetings – to get people on the same page, to increase understanding, to capture different thoughts and perspectives, and to plan quickly. There are many other functions where we perform a facilitating role – workshops, brainstorms, gathering stakeholder or user feedback and surveys, etc. Facilitating is a skill we can always improve, and as with presenting, storytelling and sketching are two skills that can help with this one.

Workshop Activities

Next, we asked for four volunteers to share their experience as a product manager, the type of product they’re working on, and the role that UX plays within the project. (Aside: We specifically asked for two men and two women to volunteer, so that women would be more encouraged to participate – in retrospect, we should have had some affirmative action for introverts to be encouraged more to participate, as well!) Four people kindly shared their experiences, and we then broke off into groups of four for the first activity.

Activity 1: Empathy Map

Taking the real-world scenarios that had been described by our volunteers, our groups-of-four put themselves in the user’s shoes, and on a large sheet of paper, drew the user and  six empathy areas:

  • Thinking
  • Seeing
  • Saying
  • Doing
  • Feeling
  • Hearing

We then encouraged everyone in each group to take a marker and some Post-It notes, and to add notes on behalf of the user. We suggested a minimum of 5 notes per empathy area.

For example, if the product was an app that helps a person find a nearby venue with micro-brewed beer, then a note for “Feeling” might be “Thirsty!”, and a note for “Thinking” might be “I’m not familiar with this area…”

Empathy map workshop

Activity 2: Communication Comic

For the Communication Comic, we gave everyone pens and A4 paper, and asked them to draw three boxes. Then, using the tips from the one-pager – creating box-figures instead of stick figures, and changing the shape of the box to indicate movement and perspective; looking at ways of doing simple facial expressions simply by adjusting the eyebrow and mouth shapes – we asked everyone to pretend that they were communicating the need for a new product feature to their development team, and needed to draw the user’s story in a 3-panel comic.

We weren’t sure how people would take to this activity – so many people are told (or think) that they “can’t draw” and it inhibits them from trying visual communication – but it was fantastic! Everyone had a go, and the comics each told a user story about the product.

comic-strip

To Conclude

The night was a massive success, and we would like to thank Liz and Jen for inviting us to speak, and to everyone attending for being such good sports about sharing their rough work – we had a really good time and hope we can do another workshop one day!

If you’re interested in learning more about these UX topics, you might like:

Cheers!

Fox & Matthew

An evening with Steve Blank

On Tuesday March 11th, I attended a talk by Steve Blank at the Melbourne Accelerator Program at Melbourne University. One of our Product Anonymous community mentioned Steve was talking so I signed up due to this recommendation. But I didn’t do my homework and I didn’t know what I was getting into.

I was nicely surprised as I walked in – due to the beautiful location that is the Melbourne University Law building, the free book (The Startup Owner’s Manual: The Step-By-Step Guide for Building a Great Company) I was given for the attendance and signs that suggested drinks and food to follow – but I digress…

Steve Blank’s book – The Four Steps to the Epiphany – and his customer development methodology for entrepreneurs launched the lean start-up movement. He was/is a mentor to Eric Ries. Steve teaches customer development and entrepreneurship at Stanford. He is a very intelligent, experienced individual across start-up land and he is also very funny so the hour flew by.

While I didn’t do my research prior to the talk, I quickly realised I needed to sit-up and listen. What pearls of wisdom did I learn? Many! AND I also heard so much that resonated for the product manager.

The session was for founders who presumably are part of the Melbourne Accelerator Program and are getting insight and guidance from that program. Steve took the time to outline what a start up is and isn’t and what makes them different to an existing business.

“Start-ups search for business models. Large corporates already have them and execute on them.”

He talked about why he launched his own start-ups – due to his own frustrations with such questions as what is the “5 year business plan” and the apparent plethora of ideas he had in his head that would mean he always has a something next to try. Steve hates it when companies or people ask for that long term 5-year view, because who has that good of an insight into so many unknowns? He sees that as one of the futile corporate organisational questions which give them a bad name and which start-ups don’t waste time on.

Steve talked about founders being artists. An idea which resonated for me as I had seen this idea previously in some of Seth Godin’s works, Linchpin and the Icarus Deception. He then told everyone in the room:

“if you don’t believe in what you are doing, get out now. Don’t do it. You need to think about this (your idea) when you wake up, when you are in the shower, in other words ALL THE TIME”

Steve believes founders are the type of people who can see a work of art when others see only a blank canvas. They are a set of people who haven’t even been given paintbrushes yet – but they know they need to paint. He talked about incubators and accelerator programs as ways in which you give your artists/founders an art school. In other words, they give you room to learn to wield the paintbrush, room to fail on that first canvas when you use too much red and room to work on your masterpiece. To follow on with this analogy – one cannot learn to paint from books, one must paint.

He went on to say the lean start-up movement writings are not scriptures that one must follow religiously but they are a way in which to encourage and nurture the artist to reach their full potential. The same way an art school may help you understand whether you need acrylics over water based paints, the customer development model and lean start up methodology are there to help you understand whether your art (ie your idea/product/concept) is worthy. It’s a way to find out if you are the only one who loves what you do or whether there is an audience willing to pay for your idea. An concept that is so important for founders, but also for product managers.

How are you going to test these hypotheses (as he would ask his students at Stanford) or guesses (as he would ask those outside Stanford)?

“Get out of the office and test them”.

This statement immediately jumped out as we in the product management and user design communities know it well. It does seem to be a principle that shouldn’t have to be discussed anymore, right? No! Apparently even the guru – Steve – had to be reminded it can be applied everywhere.

Steve had sworn black and blue that the customer development methodology wouldn’t work in life sciences. After quite a bit of chasing, he was finally convinced to step in and work with a group of scientists on bringing a more customer oriented thinking to their work. He set the group a challenge to talk with x patients in 10 weeks. And he found himself proven wrong! Scientists also need to get out of the lab!

One of the audience asked, why would you need to do that if you are curing cancer? Isn’t your need fairly obvious? The answer provided was that you still have to work with many bodies to get your cure to the patient. Any insight, better knowledge and validated assumptions will make that path more likely to succeed if you have tested and validated along the way.

A member of the audience asked about the difference between talking lean rather than doing lean. Steve laughed at this point and said the word pivot has become an excuse for ADHD. In other words, a poor excuse to change direction suddenly off a single data point. Steve’s advice was to apply a 72 hour rule before being allowed to mention any new insight – let alone tie it to a pivot. He suggested having a board or a group of people keeping an eye on the founder to prevent this. I think this also makes sense for a product manager. A lot of the constructs around the discipline of the development cycle are there to help make sure no one is running off a single data point.

Steve had another way of seeing this – a founder cannot be smarter then the collective intelligence of your customers. This is so true for everyone’s product. Anyone can be guilty of continuing to tinker with the product without seeking further input but it’s so much easier for a founder to tell people what to do rather than to get out of the building and hear your baby is ugly! This is a great reminder for product managers working with founders who may be not be used to hearing alternative viewpoints and it also serves as another reminder to get out of the office!

Humility is very important to remember. You or your team or your company may think something is fabulous but you need to test it to know for sure. To that end, the artists metaphor is receiving a standing ovation from the audience as a clear sign of success. Silence in the auditorium might be the moment you know you need to pivot.

Did you attend the talk or have you read Steve’s work?  What are the product management bits that spoke to you?

Feb session wrap up – Your APIs are so product ready, it hurts

Our February session focused on product-tising APIs and our speaker, Jason Cormier from Mashery, has put together the following post in case you missed anything.

You can also check out Chris Chinchilla’s summary of the night.

Take it away Jason…

Product Managers: Start Taking Control of Your API Strategy

Let me take you back some 15 or so years ago. The Internet was in its infancy, and the World Wide Web was something mysterious and scary for most people, let alone businesses to think about. Getting yourself online required getting off your land line telephone first.

There were trailblazers of course, those who saw the potential of a new emerging technology and put the first commercial websites online. It was a technical challenge, but they succeeded. They invented the blink tag, the splash page, the shopping cart. E-commerce was born.

During these early years, almost all websites were built and managed by people who worked in IT departments who answered to the strange and slightly kinky sounding title of Webmaster. Eventually however, the power and influence of the technology was recognized as being too valuable and important to the business. Marketing and Product Managers took control and we haven’t looked back since.

You wouldn’t let your IT department plan and run your website strategy today. Yet in most companies, history seems to be repeating itself when it comes to their APIs.

It’s understandable of course, since you may not even know what an API is, let alone why as a Product Manager you MUST own the strategy for APIs within your business. But rest assured, much like the World Wide Web 15 years ago, APIs today present a wide open playing field for businesses to embrace a new emerging technology trend. Whether you act or not there are already trailblazers leading the way, some of whom are likely to become your future competitors.

First, the basics: What is an API?

API stands for Application Programming Interface. It’s a technology protocol that enables disparate systems talk to each other, and share information. Think of it like a system of security doors you put in front of your most valuable data, making it accessible only to those who have been given a key.

For example, imagine your business has a proprietary digital storage service that you use to archive important documents. Perhaps you decide to develop a mobile app that requires access to those documents. If your storage service has an API, it makes it easy for the app to access your data. The app is given a unique key, which it uses to request access to documents whenever needed. The API recognizes the key and gives the app access to the documents. Pretty simple, right?

Well, to be fair this analogy is pretty basic. There is a LOT more to APIs of course, it’s a complex piece of technology. And at some point before any API roll out someone has to make decisions about things like data structures, object classes, protocols, authorization tokens, proxies, caching, and more. Given this, you can see why most APIs are currently managed by IT departments. However if you take a step back, if you think like a Product Manager and consider the potential of this technology and what it can do for your business, how it can power your products, how you can better enable external partnerships… you’ll forget about the specs and start to focus on why APIs have the potential to be one of your most valuable commercial drivers.

Value of APIs as a Product

No matter who you work for today your business has digital assets of some kind, from which you are already extracting value. There are 3 main types of assets that are suitable for sharing:

  1. Content: Consumable information, ex. FoxSports live stats feed, Lonely Planet city overviews, etc.
  2. Services: Functionality, ex. Telstra SMS services, Dimmi restaurant booking engine, etc.
  3. Data: Your internal business metrics, ex. units sold over time by location to whom, customer profiles, etc.

I can guarantee you that no matter what you are currently doing with these assets in your business, there are ways to extract even more value from them. And the key to optimizing the value of your assets is to make them easier to access, via APIs.

What kind of value?

When you have easy, fast access to your assets you can do things like:

Build and iterate your own products much faster.  Has your website team built a new search feature? Your mobile apps team can get access to it immediately via the API.   For example, Comcast now roll out new features across their products in just 30 minutes when it used to take months. Check out the Comcast success story & webinar where the Senior Director of Product Development & Technology and a Senior Engineer talk about the change and benefits.

Better business intelligence.  Want to know which products on which platforms are drawing on your assets most frequently? When everything goes through a single API it’s easier to track.  Sensis track all the advertiser impressions generated on their own products AND a range of 3rd party products via their APIs. More on how Mashery helped Sensis.

Facilitate strategic partnerships.  Want to see your brand integrated into 3rd party products?  It’s as easy as giving them their own API key. Fantasy sports platform, SportData was able to syndicate out to channel partners like Google and Facebook quickly and easily by providing access to their APIs. See how it drives results and ROI.

Introduce new revenue streams.  If your assets are valuable to you, maybe they’re valuable to others as well? With APIs you can commercialize your assets by selling access. Choice Hotels are using Mashery technology to assist in generating additional booking revenue via the 6000+ partners they service via their APIs.

There are a myriad of ways you can create and manage your APIs, and that’s definitely something you will need to work with your IT teams to define eventually. But don’t let yourself get lost in those details too early, as can sometimes happen. Focus first on what business goals you as a Product Manager seek to deliver. Hopefully you’re starting to see now, that by treating your API services like a product, you are effectively creating a service platform. A platform that empowers you to make business decisions and take action, without having to engage your IT team to build you something new every single time.

What does a successful API platform look like?

A successful API platform will look like rapid prototyping and faster innovation on the product ideas you have now, preparation and readiness for unknown future opportunities, and a willingness to open yourself up and let others carry some of the burden and risk. It’s not something all companies are necessarily comfortable with –  not even Google.

I’ll leave you with a link to the infamous leaked memo issued by Google employee Steve Yegge, who roundly criticized Google for failing to recognize the importance of APIs as a platform back in 2011:

 “Google+ is a knee-jerk reaction, a study in short-term thinking, predicated on the incorrect notion that Facebook is successful because they built a great product. But that’s not why they are successful. Facebook is successful because they built an entire constellation of products by allowing other people to do the work. So Facebook is different for everyone. Some people spend all their time on Mafia Wars. Some spend all their time on Farmville. There are hundreds or maybe thousands of different high-quality time sinks available, so there’s something there for everyone.”

—–

Jason Cormier is the Director of Strategy and Business Development for Mashery in Australia. Mashery works with over 200 brands worldwide to help them manage their APIs in order to build new revenue channels, speed time-to-market, and spur innovation. Find out more at www.mashery.com

March 20th event: 5 skills for UX Mastery

Our next event on the 20th of March is all about the skills needed to master UX!  Really, you ask?  Yes really!

The fabulous Matt Magain, co-founder of UX Mastery and the fabulous Fox Woods, freelance user experience architect and co-founder of Girls Club Melbourne, will look at the 5 skills required for UX mastery and how to incorporate them whether you have a UX team to work with or if you’re the sole UX representative.

They will talk about what skills UX experts specifically bring to your team and which skills product managers may already have and can hone further.  They will share practical exercises for improving these skills.

Eventbrite - Product Anonymous - March 20 - The 5 skills for mastering UX

Note the new location:  The Governor’s Lounge, Royal Melbourne Hotel is just off the corner of Bourke & Spencer (almost directly across from previous location of the Mail Exchange Hotel).

Time: 6-6:30pm arrival & drinks. Talk starts at 6:30pm. We wrap up about 8pm.

Decisive book club – part 5 of 5

We have covered all the villains and their counter actions and all that is left to do, is to work on keeping these villains out of our decision making efforts.  To get more anecdotes and tips that will resonate for you pick up the book by Chip and Dan Heath yourself: Decisive: How to Make Better Choices in Life and Work.  They also have a great set of tools to support the reading at their website.

I needed one last post to pull all lessons of this great book together.  Each piece of advice will improve your decision making, but if you do not include people in what you are doing the tools will only help you with personal decision making.  As product managers, it is how we help others that will really make a difference at what we do each day.  So please resist the trap of thinking you don’t have time to add these steps into your product management process. Because there never is enough time in the day, a product should have shipped yesterday, the development team is screaming for more stories, and there is always someone calling for decisions to be made faster.  Resist the temptation to make a snap decision. Teresa Torres also draws attention to this area from her review of Decisive and argues it is an area product managers need to be mindful of.  Taking time to consult with people on the decision(s) to be made creates buy in.  Buy in helps with execution and will save you time in the long run.

We often find ourselves having to communicate decisions to those not necessarily involved directly in that moment.  Here the procedural justice approach can be really helpful in allowing people to understand the path that got you to that point.  They may not like the decision outcome itself, but if they understand what went into it, it will help with acceptance of the decision.  One tip that was called out here, was to not only highlight the good sides to the decision but also the downsides or weaknesses.  Again, this allows others not directly involved in the decision know what the triggers might be for changing the direction.  While we might fear this will lead to sabotage of the effort, it can lead to the opposite and helps with gaining support.  Because now, those impacted by the decision can help with preventing the negative outcomes.  And sharing the consideration that went into the thought process buy in is more likely. By having everyone on the team keeping an eye out for tripwires, you actually have empowered your entire team/organisation to ensure you keep doing the right things at the right time.

So the last pieces to remember to include people in the process are:

  • Bargaining yields buy-in (seems painful to the decision making timing, but helps with implementation/execution)
  • Procedural justice is another way to show that thought has been put into a decision (think of a judge system here, when the reasons are clear and considered, both sides of the case feel heard).
  • Highlighting some of the downsides of a decision can be another way to get buy-in by calling out areas that might be a trigger or tripwire for reconsidering in the future

“Decisive is a way of behaving.  Better to try and fail than to delay and regret.” 

In summary of the entire blog series we have covered the 4 villains and how we can counteract them:

Thanks for reading and please feel free to add comments on any of these areas below or let us know if there is anything else you would like to see us cover.

Decisive book club – part 4 of 5

So we have got to the last and final villain of decision making: Over confidence. This is the moment you need to prepare to be wrong!  But don’t worry – being wrong is not a bad thing – it is a time to learn and being prepared is part of your success strategy.  To review how we got this far check out the previous posts Part 1Part 2 and Part 3.

Preparing to keep your project or efforts on track are not signs of weakness but as I said ensure success.  The key insight from what the Heath brothers have researched is that if you follow some of these steps as a process you can really assist yourself in getting yourself out of some of the mind traps that we all fall into. For example one way to help get people thinking of things that could go wrong is to do a pre-mortem; i.e. do the post-implementation review or what could be done differently activity at the start of the project instead of at the end AFTER you have made the mistakes you are now discussing.

If you as a product manager guide this process by puling your team together who is executing on this decision and asking what could go wrong here, you can guide them into the mental shift to plan for the future.  Don’t forget to ask what could go wonderfully right.  A lot of projects I have worked on often worry about the worst case scenarios – I may have been surrounded by good decision makers already – but we often fail to plan for success and that can catch you out as well.  Using any tool to think ahead and prepare to be wrong does not mean you don’t go ahead with what you have decided, but it helps to know what you will do when those situations occur.

Some of these areas will make sense if you have followed a good project management approach, but you can kick off any of these techniques yourself.  My favourite out of all these tips was the tripwire.  The tripwire can be a great way to catch yourself at a certain point in the future and consider making a new decision, because you have new information at hand, or that flag that someone said “would never happen” has.  It can be a chance to go back to others who have made a decision and allow you to challenge it, because the factors that the original decision was based on have changed.

The great story that went with this tripwire in the book was about David Lee Roth and his bowl of M&M’s free of brown ones, which he insisted he have backstage at every performance.  The ultimate diva behaviour if this is the only part of the story you have heard.  The band’s production design was particularly complex, and while they had a road crew, much of the prep work had to be done in advance of the road crew arriving.  So they had a set-up contract that was pretty complex, and if any of it wasn’t followed correctly it could leave the band exposed to serious injury.  One of the clauses, deep into the contract and amongst all these technical specifications, was to have a bowl of M&M’s backstage that must be completely free of brown M&M’s.  If David Lee Roth walked back stage and saw even one brown M&M in the bowl, he would pull everyone up and insist on a check of the entire production set up.  His tripwire had gone off, and this was a great way to let him know the band was at risk because critical instructions had not been followed.

There are so many ways to help overcome over-confidence and prepare to be wrong, that I felt this was one of the easiest villains to defeat.  (Hah, a bit of over-confidence slipping in there!). Often one is following through on someone else’s decisions and these tools can be really useful for feeding back to the decision-maker flags or tripwires for when a decision needs reconsidering:

  • do a pre-mortem.  Think what could go wrong and then plan in preventing that
  • bookend things – worst to best scenario and have a plan for either outcome
  • FMEA = failure mode + effect analysis.  How likely is it, and how severe the consequence if it were to occur (and how likely will we be able to detect it, if it were to occur)
  • pre-parade: prepare for success as well as failure!
  • correct for over-confidence by multiplying by a certain factor (i.e. dev estimates, predictive models etc.)
  • treat the future as a spectrum not a point in time
  • add in a tripwire!!  (David Lee Roth story, brown M&Ms)
  • Triggers are another way to recognise when a (new) decision making moment has come up
  • Partitions also an option to create conscious thought on following through/or not on a decision

The book by Chip and Dan Heath can be purchased here: Decisive: How to Make Better Choices in Life and Work.

The last blog post will wrap up with a couple of key take-outs from the book overall and summarise what we have covered so far.

February Events

This month we have Jason Cormier from Mashery talking about APIs.   His session is entitled ‘Your APIs are so product ready, it hurts’.   We’ll be at the Mail Exchange at 6p for a 630p start on Thursday Feb 20th.    RSVP now!

And our afternoon coffee will be the following Thursday, the 27th, at Brunetti’s at City Square (Swanston & Flinders Ln).   We’ll be there from 2-3pm.   RSVP now!

You can just turn up for any of our events but we appreciate it when you RSVP as it gives us an idea re: how big of a table to grab at coffee or organising space at Mail Exchange.

Decisive book club – part 3 of 5

We are middle of the way through reviewing Chip and Dan Heath’s excellent book Decisive. To review previous posts check out Part 1 and Part 2.  This section is about short-term emotions and how they can get very much in the way of making a good decision, which is especially perplexing when you have made significant effort to overcome self-confidence.

This next villain, short term emotion is an important one for product managers to think about as we are always introducing new things to an organisation. Short term emotion or loss aversion lead to strong bias against change. So even if you personally have managed to overcome your own bias against change, others are going to express their resistance strongly, and having some tips to work through it will help you be an effective leader of change.

One of the ideas the Heather brothers suggested here is to introduce familiarity, or as they more eloquently put it make use of the exposure principle. By introducing concepts gradually it can help overcome strong emotional responses. One of our group shared an experience, where they kept printed copies of all the pieces they were working on stuck up on their cubicle wall so that everyone could see what they were busy with at any time. This meant that by the time more formal presentations occurred, there were no surprises and thus less resistance to what was new.

The example in the book called out that the approach to breeding familiarity can take many different courses. In this case, new words were shared with students by chalking them up on the lecture board each day.  When the students were introduced to a new author to read, they felt they already knew who this person was, as the author’s name was one of the words that had been on the chalkboard each day (familiarisation done over a period of a few weeks). That might seem an odd approach but the key is that it doesn’t matter where the familiarity comes from, it helps with the acceptance of the book and author anyway. This particular tool resonated for many in the group, when we discussed it at our Product Anonymous session, and people could see some new possibilities for improving on their previous efforts at introducing the new.

So you have overcome confirmation bias thus far and those ugly Short-term emotions cloud your judgement, so some of the ways to help Attain distance before deciding (or as I like to call it “Phone-a-Friend”) are listed below:

  • sleep on it
  • what would you tell your best friend to do?
  • Exposure principle + loss aversion leads to a powerful bias against change
  • 10/10/10 rule: how would you feel about this decision in 10 minutes, 10 months or 10 years
  • short-term emotion may distract you from long term aspiration
  • core priorities (I hear vision in this tool, what is the product and its purpose)
  • the what will I stop doing in order to DO the things I said I will now do

Just in case you haven’t been convinced to own it for yourself because I cannot cover everything, the book can be purchased here: Decisive: How to Make Better Choices in Life and Work by the Heath brothers.

The next blog post will be about the last bias of them all Over confidence and how to Prepare to be Wrong.