The trouble with good ideas

Lightbulbs

One of the great things about the internet is the amount of opportunity there is to build new products, to create new websites for practically anything, whether it is a site for you to trip out on running dogs or a forum to debate political issues, and of course then we have millions of Apps for entertainment, productivity or all sorts of other random things.

So we are not short of ideas. The problem from a Product Management perspective is ensuring a “good idea” isn’t a silly idea. People tend to be able to come up with plenty of ideas they think are good, but when the idea is scrutinised, or released upon the world, it can often crumble.

This is due to one or more of the following reasons:

  • The person is unable to put themselves in the customer’s shoes
  • Assumptions are made about user behaviour
  • There has been no problem identified that the idea is trying to solve
  • The idea is driven by office politics or personal gain
  • The idea is focussed on money or organisational gain, and not for customer benefit
  • It requires time and effort to validate an idea

The Product Manager’s job is to filter ideas by seeking evidence, and challenging assumptions.

That’s assuming you have:

A Product Manager or Product Owner in place who gets this.

Unfortunately many organisations don’t and as a result, the “good ideas” go straight to the Chief Execs, presented as a thing that will solve all their problems with very little evidence, if any to back it up. The Chief Execs trust that the person with the idea must know what they are talking about and the green light is given. Time and money are then wasted building something “shiny” usually at great expense, only to find that the customer has no interest in using it.

I’ve seen this present itself with software companies trying to flog “Apps” citing that other competitors are seeing great successes, but seem to be unable to provide any meaningful data when pushed.

Someone convinced the board “We need an App!” which sounded great in theory until it was built and then the sudden realisation hits that people are just searching on Google to find what they want, with no interest in clogging up their phone with more Apps they might use once and then never again.

So what do you do?

  • Seek data
  • Understand what customer pain point or problem you are trying to solve
  • If you have no data (as it’s completely new territory), get some – pretotype or prototype – I highly recommend trying a design sprint used by GV (was Google Ventures)
  • Focus on what failure will look like – how could it go wrong, why would it go wrong (the design sprint approach above will help you with this)
  • Don’t believe what your customers tell you – asking customers what they would do can often be very different to what they actually do – so test any assumptions
  • Hire good Product Owners and Managers
  • Finally, seek data (yes I know I’ve said that already)

 

Leave a Reply

Your email address will not be published. Required fields are marked *

Scroll to top