Thoughts on Decision Making

Our 1st ever book club event is coming up this month & we’ve choosen Decisive: How to Make Better Choices in Life and Work by the Heath brothers.

This isn’t the first time we’ve covered decision making in our topics – last June, Steve Bauer did a prodanon session and then turned the session into a series of blog posts.  You can check them out here:

So come along, bring a friend and share a war story

January 23rd meet-up: Book club on Decisive by Chip and Dan Heath. Start time 6pm, for 6:30pm kick-off, at the Mail Exchange Hotel, back room behind the Restaurant area. Bourke and Spencer st.
RSVP below or click this button to go to Eventbrite for full details

Eventbrite - Product Anonymous - January 23 - Book club

 

 

The Art of Decision Making – Part 8: Learn and evaluate

This article continues the discussion from Product Anonymous back in June last year.  Full credit goes to the team and the attendees for providing key steps, insight and critical analysis.

In the last set of posts we defined the problem (topic and people), identified some alternatives, evaluated those alternatives, and even decided and implemented . The final step in the process is #6 – To learn and evaluate.

Now is the time to follow up on the decision; is the implementation going well, has the environment changed and what can you learn from it

Maintain your heading

Publicly stick with your decision.  If the team sees doubt then their commitment to the decision may drop, and it will be less effective.  Reiterating the decision outcome (or in PR terms being ‘on message’)  can seem like a waste of effort for you, but for everyone else who wasn’t part of the process it seems like new information.

Again, the plan is the plan until there is a new plan.

Monitor the outcomes

Follow up on how the decision is being implemented.  Are people working on it? Are the necessary steps being taken?  Are existing processes being modified?  If it is not being implemented then you have further influencing to do.

Follow up on the key metrics and points that were part of the decision analysis.  Are you getting the savings, revenue or traffic you predicted?  Are results shown in both quantitative and qualitative form?  Is everything else being held constant?

Adapt to changes by iterating

“Prediction is very difficult, especially if it’s about the future.”
Niels Bohr

It is a fact of life that every decision can have unintended consequences.  Or you may find that the decision-making assumptions were wrong.  Or you just aren’t getting the results you were expecting. Or you may just be plain wrong.

The important thing is that you stay on top of the outcomes of the decision, and get involved before they escalate out of hand.  The interesting project work always involves unknowns, and mistakes will be made.

Learn

The whole decision making cycle is a perfect opportunity to learn about the business, the process, and the people involved.

Step back and think about the bigger picture.  For example: What would you do differently next time?  How would you have achieved the same result in only 10% of the time?  How could you achieved the same outputs with only 10% of the budget?

Always ask yourself: What will you do better next time?

 

We are now done.  We have taken the full 6 part process and looked at some of the stickier issues within corporate decision making.

Have you got any other tools to help you make decisions? Please feel free to comment below to add to the discussion.

Go back & read part 7 on Implementation.

Steve is a Product Development Manager at Telstra Wholesale.  The views expressed in this post are his only and do not necessarily reflect the views of Telstra.

The Art of Decision Making – Part 7: Implement

This article continues the discussion from Product Anonymous back in June last year.  Full credit goes to the team and the attendees for providing key steps, insight and critical analysis.

In the last set of posts we defined the problem (topic and people), identified some alternatives, evaluated those alternatives, and then deciding.  Step #5 in the process is to implement that decision.

Ok.  We have made our decision.  Woohoo!

Now what?

Surely everyone will just crack on with it?

Communicate the decision so that it can be implemented.

And this might mean communicating well beyond the immediate team tasked with the implementation.  There are usually some impacted teams that you haven’t considered out there that need to be informed.  So back to the RACI model and consider the ‘Informed’ folk.

You may need to use your influence to get help from other people to implement it. There may be some resistance, but with a well reasoned decision process then you should have no trouble getting commitment and support from everyone.  You are going to need them to be ‘all in’ so they can run with the new decision.

Use the momentum

There will now be some momentum behind the decision as you have already involved a bunch of stakeholders.  Get the stakeholders to help implement and promote the decision.  Get them involved in the next decision that is the natural progression of the current.  Keep that momentum going.

Kill the alternatives

Depending on your culture, it may be necessary to kill the other alternatives. Because of the decision making process there may be doubt about whether the final solution is the best solution.

It is possible for a company to continue using resources on the unchosen option in the name of ‘risk mitigation’, ‘creating a plan B’, or ‘I disagree so I’ll do it my way’. It may be necessary to prevent each of the alternatives from being implemented just to prevent the waste of resources.

Alexander the Great may have burned his boats upon arrival on the shores of Persia as a sign of commitment.  While you may not have to be as extreme, you don’t want to waste resources on options that may never bear fruit.

The plan is the plan until there is a new plan.

We have now implemented our decision, but it is still not over.  Perhaps there is some iteration or learning ahead.  Next we’ll look at what we can learn.

Have you got any other tools to help you make decisions? Please feel free to comment below to add to the discussion.

Go back to Part 6: Decision time.

Steve is a Product Development Manager at Telstra Wholesale.  The views expressed in this post are his only and do not necessarily reflect the views of Telstra.

 

 

January 23rd meet-up: Book club

The first session for 2014, will be a book club session.  

The book we will be reviewing is Decisive by Chip and Dan Heath. Don’t worry, you don’t have to read it to enjoy/come to the session, but if you do wish to get a copy at Amazon (ebook is available) – here’s the link*: Decisive: How to Make Better Choices in Life and Work

This book and its content follows on from our session on Decision making in June last year, which Steve then put together a series of posts diving in deeper to the issues he raised during his session.  You can find the start of the series here and there are six articles in total.

The main treatise of the book is about the psychology behind the decision making process.  The great thing thing about the Heath brothers work, is they provide real insight into ways to actually start doing better at our own decision making and helping others to do so as well.  As product managers this type of influence is critical to what we do.

If you would prefer the cheat sheet reading approach, check out some of Teresa Torres‘ articles about this book and the elements that resonate for her and product management.  We will take a look at some of this work as well during the session.

January 23rd meet-up: Book club on Decisive by Chip and Dan Heath. Start time 6pm, for 6:30pm kick-off, at the Mail Exchange Hotel, back room behind the Restaurant area. Bourke and Spencer st.
RSVP below or click this button to go to Eventbrite for full details

Eventbrite - Product Anonymous - January 23 - Book club

 

*testing an affiliate link so if you buy via this link Product Anonymous will get something like 10c which will go towards hosting costs.

End of the year events

We have 2 more events before the end of the year so hope to see you – at least once!!

This month’s evening event is our annual social. There’s no speaker, no specific topic – it’s just all about chatting, catching up, talking product management (or not) and getting to know each other better. It’s also Product Anonymous’s 2nd birthday!!!!

This year our end of year social is Thursday Nov 21st at the Sahara bar on Swanston st. Sign up here: 
Eventbrite - Product Anonymous Coffee - October 31

And then we’ll finish off the year with an afternoon coffee on Thursday Nov 28th, 2-3pm, City Square by Brunetti’s. Drop in any time when you can, we will be there the whole hour. Sign up here: 
Eventbrite - Product Anonymous Coffee - October 31

Oct 24th write up – Digesting the IDEO +Acumen HCD course

The IDEO +Acumen+ HCD course is a do-it-yourself group course which in 6 weeks runs you through the entire IDEO design process for Human Centred Design. The course is sponsored in Australia by +Acumen, which is an organisation that helps people self-learn.

We had a big crowd for this session, and when circling the table to see what attracted people we had about a third who had done the course and were interested in unpacking it with others who had done the course and a third who had experience in human centred design and the last third interested in understanding the value of doing the course themselves.  It was a good mix of people to encourage good discussion throughout the presentation.

IDEO’s design process covers three areas: Discover, Ideate and Prototype.  Within each of these areas there are levels which are quite important breakdowns of the process.  By understanding these smaller elements, you begin to get an appreciation for a robust and repeatable process, which still has the flexibility and room for customisation to be applied to any project.

Includes the sub-steps in each of the stages of Discover, Ideate and Prototype

Includes the sub-steps in each of the stages of Discover, Ideate and Prototype

The Discover phase can iterate between research and context for a time until you are comfortable you know what you are pursuing before moving onto the Ideate stage.  Within Ideate, you can progress along – whilst repeatedly revising your direction – until the point where you consider heading towards Prototyping.  As we were on a course, we followed a VERY linear path, but those who had experience with this approach called out that you might stay in an area of focus for a long period until it was right or you might be very structured but repeat from start to finish each week.  It depends on the project, the team and the overall goals you may have when applying this approach.

It was a great part of the discovery to understand the more discreet steps within each area and learn ones strengths and weaknesses at each.  For example getting out there and just asking people questions was hard to get going, but once you started and found that people are amazingly open and willing to share their thoughts it got easier.

One of the complaints regarding the course was that it took far more time than indicated. One of the group at the session didn’t complete it as they struggled to keep momentum going after 6 or 7 weeks and not being in sight of finishing.  The group I was with came very close to giving up, but we managed to rally to get to the finish line.  We also made a conscious decision to skip some elements in order to see out the course to the end.

Once my group got to the brainstorming stage we as a group had one of our best grok moments of the course.  We found that it wasn’t so hard to generate ideas, by having everyone think out loud so we could build off each other – the faster we shared “conventional” ideas the quicker we got to better ideas.  Once we were done it was quite easy to spot the good stuff.  With only the option to score on achievable and innovative and one vote per person per criteria the “winners” bubbled up quickly.  This methodology for group focus on progressing ideas to prototyping was fabulous.

The last stage was Prototyping and I must admit I thought we would immediately start to build and kind of get creative right away.  I was impressed with this stage having a scientific approach that ensured you tested an idea rather than the whole product.  The user experience map was a great way to break it up into small achievable steps, whilst at the same time understanding your goals and vision for an end state product or service.

A photo of our experience map during our Prototyping workshop

A photo of our experience map done during our Prototyping workshop

This was the moment this course struck gold for me for as a product manager.  I think these elements are used commonly in product management (testing, revising, build at “story” level) but the insight here was that you need to test a step in the user experience before committing to the whole product.  The other insight was that prototyping does not need to be such an expensive fully designed product, but something light (easy to throw away!) such as a story, a diagram or an ad.  These options allow for prototyping without development and can be really useful at many stages of the product management lifecycle.

As Steve highlighted, even before you have a team, and before you have money, and when you need to make the case for the business case this no cost prototyping brings the validation to get your next idea across the line.

Some additional thoughts are called out in the deck below. Please feel free to add your comments or questions below if you have done the course or have your own experiences with this methodology.

 

Sept 26th write up – Wèishéme (Why)

For those who don’t know, I’ve been overseas the last few months – mostly in Shanghai. Being in a new city with such a different culture to my own (even my adopted cultures), I found I was constantly asking ‘why’ on a very regular basis.

I was taking mandarin classes learning how to ask ‘what’ and ‘where’ but what I really wanted was to ask ‘why’. I kept seeing all sorts of scenarios where I wanted to ask ‘why’! For example, why do some foods need to be wrapped in layer upon layer of plastic wrap when meat was available for sale unrefridgerated on a cardboard table?

Although even after I learned the word for ‘why’ – wèishéme – I knew I wouldn’t be able to understand the answers (my mandarin has improved but it’s very much a work in progress!). I became a little obsessed with wèishéme and it got me thinking about asking the question in product management.

Whether we’re talking with a customer or end user, determining which feature to build next or how to market our product, understanding the ‘why’ is needed to help us connect, make our products great and create success. Understanding ‘why’ uncovers the value and explains why we care, what the context is, influences us and focuses on the problem (not the solution).

We can integrate ‘why’ into our existing tools like positioning statements, interviews & research, and even agile stories.

Some of the references include:

Simon Sinek’s ‘Start with Why’ TED talk & the golden circle

Bill DeRouchey’s ‘Power of Why’ deck on slideshare

Steve Portigal’s Interviewing Users: How to Uncover Compelling Insights

I’d also recommend The Power of Habit: Why We Do What We Do in Life and Business. It didn’t make it into the deck but is an excellent read.

Product Anon Coffee – Oct 31st

At our last meeting, you told us you wanted #prodgmt than just once a month!!  Out of this conversation and other feedback we’ve had, we’re trialing a monthly coffee/lunch session.

We held our 1st coffee session on the afternoon of Oct 3rd.  It was good to see both new & familiar faces stop by (note to self: must remember to take photos!!).  The concept of being able to pop in for a few minutes or have a leisurely coffee seems to be a winner.

We’ll be mixing it up with different times (& maybe get crazy with a different day!) so keep that feedback coming!    On the 31st,  our coffee session will be more of a lunch time affair.    We’re hoping for some good weather so we can all meet in a park but let’s see closer to the date.   Venue suggestions are welcome!!

Our next Product Anon coffee will be Thursday Oct 31st, 12:30-1:30.   Subscribe to our google calendar / Twitter / Linkedin for updates.

Eventbrite - Product Anonymous Coffee - October 31

October 24th Meet up – Digesting the IDEO + Acumen HCD course

IDEO and Acumen offered the chanced to do an online course on IDEO’s human centred design process.  All you needed was a bit of time and at least one other person to sign-up with.  I gathered a group of fellow product managers and Product Anon attendees and we signed up to give it a go and learn more about this leading process for innovation.  They will join me for the session to share from their point of view as well.  

This month’s session will be on how we found the course, what we learnt, how we will try and fit it back into our Product management worlds, and how we will keep our minds open. If you took the IDEO/Acument course, please come along and share your experiences.

The usual location – Mail Exchange Hotel on the corner or Bourke St and Spencer st.  This is the last topic event before we have our end of year Product Bash. Sign up here.

Eventbrite - Product Anonymous - October 24 - Digesting the IDEO + Acumen HCD course

October is Bring a Buddy month!!! Do you have a friend, co-worker or colleague from a previous job who you think might be interested in Product Anonymous? Someone who has asked about the group but never comes along? We’ve heard from some people that they’d like to attend but don’t know anyone at Product Anonymous … so they don’t attend. This month, think about who you know would be interested in the group or topic and bring them along! Be a buddy!

The Art of Decision Making – Part 6: Decision time

This article continues the discussion from Product Anonymous back in June.  Full credit goes to the team and the attendees for providing key steps, insight and critical analysis.

In the last set of posts we defined the problem (topic and people), identified some alternatives, and evaluated those alternatives.  Step #4 in the process is to decide between those alternatives.

With all the evaluation you did in the last section, it should be pretty clear what the correct decision should be.

Some extra thoughts on the actual decision point.

Sometimes it is hard to make a decision.  You will need to balance the upside against the downside.  For quantitative information this may be a mathematical decision, but this is unlikely to be the only part.  Since there is always a human element there will be additional complications to resolve.

A good decision should not be a surprise to anyone. Certainly the easiest decisions are those that don’t seem like they were required.  If anyone is surprised then it is likely you haven’t done your homework in building engagement and consensus.  Everyone should understand that they had a part in the decision, that their opinions and ideas were listened to, and they all got the right background.  Everyone should see the decision as a natural evolution out of the options and the situation.

Sometimes it is easier if you decide on what you’re not doing.  Striking off alternatives that you aren’t going to do, and see what you are left with.

Will the decision stick?  The previous sections discussed the RACI analysis – if the decision is not being supported by the right person then it might not stick – and therefore it won’t be the decision that was needed.

Is the water clouded with too many issues?  Whenever there is “Fear, Uncertainty and Doubt” (FUD) then it will become hard to make the decision.  Clear up any misunderstandings by going back to first principles.

What would it take for me to believe in the decision?  Are you personally convinced this is the right way to go?  Or are you going by the numbers?

Are you looking for something that is the optimal decision or just good enough?  Some people (known as maximizers) will spend a lot of energy optimising a decision, while some people (satisficers) will simply try to get by with a possible solution.  Which one are you?

How will you feel about the decision in 10 minutes, 10 months and in 10 years?  Using this tool is a good way to separate yourself from the emotional here-and-now of the decision

Is there some form of personal fear in your decision?  We all experience fear of failure and fear of getting it wrong.  This is normal.  But if this is your product, you need to be proud of your decision, regardless of your fear.

Is it fear that this is a one-way decision?  Such decisions are rare, and many can be corrected.  And if other people are part of the decision process then they will help.  Especially if you have called out assumptions, then they can recognise that change will need to be made.

If you can’t decide then maybe it doesn’t matter.  Maybe everything has an upside and a downside that can’t be compared – so every option is good and bad. In which case the option chosen doesn’t matter.  But still make a decision because you need to set a direction.

If you can’t decide, then try the ‘slightly cranky’ method.  This is the time to channel your inner cranky product manager.  Pretend you have been at this all night and you have had enough?  Now what?  Evaluate and check that it makes sense at the end though. You are effectively trusting your gut now, so look inside and work out the things you decided were most important, and use these for your reasons.

Doing the exact opposite might still be valid.  Can you flip it on its head?  This can be such a big mental shift that you will probably need to explain the reasoning to everyone again.

So we now have some well evaluated alternatives, we have though about the implications and finally it is crunch time.

You have to make a decision.

Do it.

We have a decision, but it is not over yet.  You will need to implement it, and then learn from it.  Next we’ll look at the implementation.

Have you got any other tools to help you make decisions? Please feel free to comment below to add to the discussion.

Go back to Part 5: Evaluating Alternatives

Steve is a Product Development Manager at Telstra Wholesale.  The views expressed in this post are his only and do not necessarily reflect the views of Telstra.