February 2010

Archive for February, 2010

8 ideas for understanding product / market fit using the web

Tuesday, February 9th, 2010

Here are 8 ideas for understanding product / market fit using the web. Please add thoughts and other ideas as comments.

1. Run a news aggregator

Run a site which aggregates interesting news and articles related to your product area, presenting a headline / brief summary and then linking out to the original content. Categorise the articles and tag them. Keep a tally of which tags are used most often and observe clickthroughs, keeping a tally of clicks by tag.

A good source of content is twitter and it is relatively easy to do. Create a twitter list of people that post news and articles relevant to your area. Bingo!

This is more likely a qualitative aid than a hard quantitive technique, it would take quite some time and effort to make such analysis statistically significant and it is important to understand how the content you are posting may bias clickthroughs. However, if you do succeed in building an audience or community, that in itself is valuable.

2. Run a forum or question/answer site

An interesting example of this is Oracle Overflow. Whilst the aim may be to attract and help a community of Oracle users, this is potentially a gold mine of information on problems Oracle users encounter which in turn could spawn many ideas for products and tools. 

3. Survey, send out short questionnaires – perhaps with a prize draw

Ask customers or potential customers to fill out a questionnaire asking about their requirements and/or experiences. My advice would be to use a mixture of multiple choice and free text questions. Multiple choice questions have the advantage of being relatively quick to answer – many people don’t like writing. As multiple choice questions have a closed set of answers they are easier to process and analyse. However, sometimes you want to get a feel for problems people are having or their feelings towards your product so it can be useful to mix in some free text questions.

Achieving a good level of participation in your survey is very important. To encourage participation, keep your questionnaire relatively short and tell the user upfront how many questions and/or how much time it will likely take to complete. Consider giving them an incentive to complete your questionnaire. This doesn’t necessarily have to be something very big and expensive. I’ve successfully run a questionnaire offering a £50 SatNav as a prize and got over 500 replies. Obviously, the size of your response will be affected by the size of your audience.

Here’s an excellent post on “What my Survey Taught Me” .

4. Encourage questions and enquiries – make sure you follow up though

If you have the resources to answer questions then why not encourage visitors to your website to ask questions about your product / service? Along with their question make sure you automatically capture what product/content they are looking at and any options they may have already selected i.e. a hotel room in Amsterdam, April 25th. The product data and options are important because it may help you to categorize your data when you analyze it.

When reading through peoples’ questions, make sure you tag them into categories for later analysis – for example, if you sell radios you may find 30% of questions are asking whether the radio has a USB port for MP3 upload, if you’ve tagged these questions with for example ‘usb’ and ‘mp3′ this should be easier to identify and quantify.

Once you’ve collected a large set of questions you may be able to improve the product. If you can’t improve the product, perhaps you can improve sales by changing your sales pitch, or including an FAQ.

5. Gather reviews, use post purchase or enquiry questionnaires

Gather data and content about people’s satisfaction and experiences with you product and purchasing / enquiry processes. As before, make the questionnaires relatively short, use multiple-choice questions possibly with a few free text questions mixed in.

Design your questionnaire so you can categorize replies and if necessary take further action, for example: happy, unhappy, needs follow up. One way of doing this is to explicitly ask them if they are (a) very happy, (b) happy, or (c) unhappy.

If would like to use content from these questionnaires on your website, encourage advocacy by asking a question such as, “What would you say to a friend to encourage them to buy?”. You probably want to avoid using their answer to this question if they have earlier selected option (c) unhappy!

6. Design your site to self segment

Enable the user to self-segment by providing section or filter links.

For example, if you are selling televisions, you probably already provide filters to limit the list of available products by type, size and other features. Capture this information and use it to inform the selection of products you offer such that it better matches the demand your marketing is creating.

If your site is about operating an email server, you no doubt have sections about different aspects of operating the service, for example: backup, setup, spam, performance etc.. By getting people to self segment you can get a idea for where the biggest problems and pain points lie.

The following may be  a little controversial. If you use it, I’d recommend you use it with care. Consider providing links to products or content you don’t currently have but are considering. Don’t over do this though, people hate following links then being disappointed. Don’t do this is you cannot or do not intend to fulfill the need very soon. As a consolation, offer similar alternative products or related articles.

7. Look at funnel drop outs

Using Google Analytics or a similar tool, set up goal tracking e.g. product purchase, sign up for newsletter, post question, make enquiry. How to setup goals and funnels in Google Analytics.

Once you have goals and funnels set up and have a few weeks of data (depending upon how much traffic your site gets). Take a look at Google Analytics’ Goals > Funnel Visualisation. You’ll see a vertical list of funnels showing progress through each step. Take a good look at the right hand column, it shows where people who abandon the funnel go to. Any patterns in funnel abandonment will likely be useful for web design and conversion optimisation activities but they may also point to product opportunities to or problems.

For example, if you have a site which sells flights, you may have a banner or link to pre-book car parking at the airport. I wouldn’t advise adding such distractions to your checkout process, but if you already have them they may give clues as to related items your customers are looking for, or concerns they have with your product or process. In this example, perhaps flight and car parking could be offered as a single package/purchase.

8. AB test

This requires more expertise and effort but can be a very effective way of evolving a website to better suit customers needs. For those not familiar with AB tests the idea is that users are split into 2 groups, each group is shown different content, features or user interfaces. The test measures how likely each group is to complete a goal. If you are selling something the goal is usually a sale.

Do you have any techniques or tips for understanding how users use your sites or products? If so please share them in the comments.

Paul

Dumb-ass Features and Really Agile Management

Sunday, February 7th, 2010

If you have been a professional developer for a while, at some point you’ll probably have thought to yourself, “why are we going to so much effort for this dumb-ass feature!?”. If you work with developers, there’s a very good chance that at some point they’ve thought this about your project – honestly. Thinking through this question and its causes can give some insight into why software development customers should embrace agile approaches as part of their product marketing toolkit.

IMO there are 3 answers to this question (not mutually-exclusive):

  1. The customer doesn’t realise how “expensive” the feature is;
  2. The developer/s don’t know/understand how much of a benefit this feature will bring;
  3. Nobody knows how much of a benefit this feature will bring.

Answer 3 is where the real power of agile development lies – much more on that in a moment. First let’s briefly address answers 1 and 2.

Answer 1, “the customer doesn’t realise how expensive the feature is”, is bad because the business really ought to know what it is spending – how much a decision is going to cost before they commit to it. In the short term this is most likely an opportunity cost. However, if systematically repeated, this can have a huge impact on both effectiveness and efficiency. Both developers and customers have a duty to each other to expose likely costs of alternative solutions as early as possible. 

Answer 2, “The developer/s don’t know/understand how much of a benefit this feature will bring“, some people think this isn’t very important but personally I believe it is very important. From the developer’s perspective this is demotivating. If the developer isn’t demotivated by this sort of thing, do you really want to employee them?! It really isn’t a question of just an individuals’ motivation though. The business is missing an opportunity too. With a better understanding of how a feature benefits the business, the developer may also be able to point out low cost improvements or cheaper/better/faster alternatives.

Answer 3, “Nobody knows how much of a benefit this feature will bring.”. This is where the big money is made. The best managers and leaders will strive for ways to answer this question as quickly and as cost-effectively as possible. They’ll look to test their opinions and assumptions about the product/service and the end-customer as quickly as possible. This is where the real power of agile approaches to software lies.

Moving from a Waterfall approach to software development to a basic iteration based agile approach will likely result in fewer defects and a better product – at least in terms of meeting the internal customer requirements. It is also more likely to be released when it is expected. I won’t go into this in detail, but broadly speaking the iteration approach leads to these improvements due to: more and more frequent internal customer involvement; better understanding of what needs to be built; and more frequent integration and testing.

Broadly speaking (though there are many nuances in practice) these improvements can be achieved by taking, for example a 16 week development project and organising it into 8x 2 week iterations/sprints each followed by customer acceptance (iteration meetings / sprint reviews).

Unfortunately, none of this addresses answer 3, “Nobody knows how much of a benefit this feature will bring.” End-customers still haven’t used the new features, new product or service. Even if the customer is internal and is involved in the agile process they probably still haven’t used the new features in earnest or for real work.

To understand the customer better and what features or changes will benefit them and our company we need to break these projects up into much smaller feature increments and move towards an even more agile approach.

Many projects are conceived from a piece of data and/or an assumption about the end-customer. What if our first iteration of development work is the smallest thing we can do to try and move the data point, or test the assumption we’ve made about the end-customer? The development team work for an iteration then release. Now the end-customer can see and use the new feature and we can assess its benefit before deciding whether to take it further and making another smallest step.

Lots of small quick steps enable us to evolve our product based on end-customer data and feedback. That’s really agile development and evolutionary product marketing.

Thanks for reading.

Paul

Site Conversion and Lipstick on a Pig

Tuesday, February 2nd, 2010

“You put lipstick on a pig, it’s still a pig” – Barak Obama

If I’m looking for a 40 inch LCD HD TV and your site only sells 28 inch Plasma you’re not going to make a sale. If you’ve spent money advertising your “wide choice of LCD HD TVs” then too bad :-p

When it comes to ecommerce website conversion the strongest lever probably isn’t how the site looks. If you don’t have the product people are looking for at an acceptable price then endlessly tinkering with how the site looks won’t make a jot of difference to conversion.

If you’re an ecommerce site then spend some time and effort determining what visitors to your site are currently looking for. They’re probably giving signals left right and center. What do they search for? What filters do they apply? What product sections do they click through to?

Thanks for reading,

Paul

P.S. my earlier, longer and slightly more serious post about 3 ways to improve conversion