We at TRC conduct a lot of marketing research projects using Conjoint Analysis. Conjoint is a very powerful tool for determining preferences for the various components that make up a product or service. The power of Conjoint comes from having consumers make mental trade-offs in evaluating products against each other. Do they prefer a lower cost product that contains few features, or a higher priced product that provides many benefits? How willing are they to choose a product that meets 2 or 3 of their criteria, but not all? Conjoint forces consumers to make these decisions, and the results can then be simulated to determine purchase preferences in a variety of scenarios.
But not all product development problems can be solved with Conjoint. Conjoint requires certain steps in the development cycle to have already been taken (defined features, some idea of pricing – see my previous blog on the topic.) In some cases, though, you may be at a stage in which Conjoint is feasible, but a different approach may be more appropriate, such as a Configurator. In a Configurator, otherwise known as a "Build-Your-Own" approach, you would use the same product features as in a Conjoint, but instead of pitting potential products against one another, the consumer "builds their own" ideal product.
So why choose one technique over the other? There are many reasons, but here are a few:
1. If determining overall product price sensitivity is the goal – Choose Conjoint. Conjoint will produce scores that assess both the importance of price overall as well as price tolerance for the product as features are included or excluded.
2. If you just want to know which features are the most popular, or which ones are selected when choosing or not choosing other features – Choose Configurator. In an a la carte scenario, respondents can choose which items to throw in their shopping cart and which ones to leave on the shelf. Getting simple counts on which features are popular and which ones are not – and in what combinations – can be very useful information, and it's an easier task for respondents. Keep in mind though that the Configurator works best if each feature is pre-assigned a price (to keep respondents from piling on).
3. If understanding competitive advantage/disadvantage is paramount – Choose Conjoint. Conjoint allows you to include "Brand" as a feature, and the results will link brand to the product price to see if respondents are willing to pay more (or less) for your product vs. that of a key competitor. You can also simulate competitive market scenarios. While you can include Brand in a Configurator, modeling the trade-off between brand and product price is far less robust.
4. If you have a lot of features, or complex relationships between the features - Choose Configurator. It's much easier for a respondent to sift through a long list of features and build their ideal product just once than to choose between products with a gigantic feature list multiple times. Conjoint works best when the features are not dependent on one another; a long list of restrictions on the features can disqualify Conjoint as a viable solution from a design perspective.
There are plenty of times when a technique may present itself as an obvious choice, and other times when the choice may be more subtle. And in those cases, we turn to our senior analysts who use their expertise and understanding of the research objectives to make sound recommendations.
When working with clients on parameters for a conjoint design, there is often an assumption that the design includes a current product configuration, or base case. This base case provides a benchmark against which new configurations can be compared.
Having a benchmark can be both useful and comforting when analyzing the conjoint results. Replicating a base case allows us to reference important metrics that are known for that product (for example, market share, CPU, revenue, etc.). As we configure new products and compare their appeal to our base case, we can gain insight into how these key metrics might be impacted.
Aside from establishing a benchmark, having a base case is also critical if there is concern about cannibalization. If the expectation for the new product is that it will compete in the market with a current configuration it is critical to understand what impact the new product will have on the current landscape.
However, allowing for a base case in the conjoint design is not always warranted. As products become more dissimilar from current offerings it can become difficult to include a base case. Trying to integrate the components of a current and new product that don’t share many characteristics can lead to conjoint parameters that are too complex to administer, or create apples to oranges comparisons. It is not wrong to leave out a base case as long as it is understood there will be no benchmark comparison.
One hybrid solution to consider is to allow for a set choice that reads something like “None of these, prefer the PRODUCTS currently available”. This is similar to a typical “none” option in the conjoint but provides a bit more information; specifically, that they would not leave the category but are not interested in the new, very different product configuration. Of course this solution would not be appropriate in all instances but does provide a good compromise.
Ultimately, the extent to which “real products” are modeled with a conjoint study’s parameters is a function of the specific information needs and the complexity of the design. Most of the time we want to include that dose of “reality” in our design but don’t be afraid to leave it behind if warranted.
During my recent first time home buying experience I learned there are many, often competing, factors to consider. My last blog discussed how I used Bracket™, a tournament-based analytic approach, to determine what homebuyers find most important when considering a home. My list of 13 items did not include standard house stats like # of bedrooms, # of baths, etc. To measure preference for those items I used a conjoint design.
I framed up the conjoint exercise by asking homebuyers to imagine they were shopping for a home and to assume it is located in their ideal location. Using our online panel of consumers, we showed recent or soon-to-be homebuyers 2 house listings side by side, plus an “I wouldn’t choose either of these” option. Each listing included the following:
I felt a conjoint was best suited here, because in addition to importance, I wanted to see what trade-offs homebuyers were willing to make between these 5 items that are highly important in home buying. Are homebuyers willing to give up a bedroom to get the right price? Are they willing to do some sweat equity to get the number of bedrooms and/or bathrooms they want?
We found the top three most important factors are # of bedrooms, price and house condition. This made perfect sense to me as I would not consider any house with less than 3 bedrooms. Price and house condition were the next two key pieces. Was the house in my price range? How much work was needed? Did the price give me enough wiggle room for repairs? I was curious to see the play between price and house condition among the recent and soon-to-be homebuyers we interviewed.
Using the simulator I selected a 3 bedroom , 2 full baths, Single Family home. I picked 3 price points ($150,000, $300,000, $450,000) and then varied the house condition. Overall, homebuyers are less interested in a "gut job" compared to "move-in-ready". However, at the $150,000 price point, share of preference drops more drastically going from "move-in-ready/some work required" to "gut job" compared to higher price points....
Here in Philly we are recovering from the blizzard that wasn’t. For days we’d been warned of snow falling multiple inches per hour, winds causing massive drifts and the likelihood of it taking days to clear out. The warnings continued right up until we were just hours away from this weather Armageddon. In the end, only New England really got the brunt of the storm. We ended up with a few inches. So how could the weather forecasters have been this wrong?
The simple answer is of course that weather forecasting is complicated. There are so many factors that impact the weather…in this case an “inverted trough” caused the storm to develop differently than expected. So even with the massive historical data available and the variety of data points at their disposal the weather forecasters can be surprised.
At TRC we do an awful lot of conjoint research…a sort of product forecast if you will. It got me thinking about some keys to avoiding making the same kinds of mistakes as the weather forecasters made on this storm:
So, with all these limitations is conjoint worth it? Well, I would suggest that even though the weather forecasters can be spectacularly wrong, I doubt many of us ignore them. Who sets out for work when snow is falling without checking to see if things will improve? Who heads off on a winter business trip without checking to see what clothes to pack? The same is true for conjoint. With all the limitations it has, a well executed model (and executing well takes knowledge, experience and skill) will provide clear guidance on marketing decisions.