Tag: predictive analytics
Connect With Us
Value of SKU Intelligence (What Are Customers Buying?)
One of the most frequent questions we are asked about Emcien’s methodology is “why hasn’t anyone done this before?” The answer seems obvious to us, but we should probably write it down once and for all so we can just point people to a definitive document.
Exploding SKU’s to attributes generates a LOT of data. It is only useful if this translates to actionable intelligence. As we all know, we don’t need more data. We need actionable items and recommendations to improve business. The simplest answer is that collecting all the attribute data for SKUs has not been done before, because the algorithms have not existed to farm intelligence from them. In this blog I am going to address –
- Why having the data with the SKU attributes is invaluable!
- What analytics capabilities are needed, if you have that data
- Value of having SKU Intelligence (To drive SKU velocity)
Consider a product that has attributes, and offers lots of variety, also called configurations. Almost all products come under that class today! Think car, computer, or cell phone. The product has features, and each feature has alternative options. For example, a car has an engine (V-6 or V-8), a body type (sedan or convertible), and a color (red, green, blue, black, or white). Any specific car has many choices for each of the features. Customers make choices on the features. Do you want the cloth seats or the leather seats? Do you want the DVD player? How about the iPod connector? Make a choice for about 30 features and you are done. This applies for shampoo, toothpaste, computers, light fixtures, consumer electronics, … all products that have attributes choices.
We consider a configurable product that has a large number of features, each of which many alternative choices/options. Notice that we have finessed the hierarchy problem by allowing only two levels: feature and option. A customer will typically call out only a few attributes during a purchase. They expect you to know how you can complete that spec to fill the order. That is the single biggest opportunity at every point of sale!
If we have data with attributes for every SKU, we can begin to talk about buying patterns! A buying pattern is groups of options that are bought together, like the red color with the convertible body style. Or the DVD player with the leather seats. Or the pattern might involve 3 options, 4 options, 5 options…. many options.
Auto detect most popular attributes in fastest sellers
This brings me to a very important point. If you have sales data with attributes, you need an analytics engine that will automatically detect and tell you what attributes are bought together and are highly popular. A reporting tool that makes you query every choice combination will NOT work! You will be very old by the time you get an answer to most popular choices, as there are millions of attribute combinations. Emcien offers an analytics engine with cluster analysis that will tell you what attribute groups are popular. This answers the questions – what are customers buying and what attributes are popular. This knowledge can also be used for planning the SKU definition and knowing what products need to be on the top landing pages of your web site/ store aisles. (SKU Definition is the list of attributes in the SKU.)
Once the SKU definition is in place, 75% of the cost structure and efficiency of your supply chain has been fixed ! Your supply chain operates under the assumption that the SKU definition is correct. What does this mean? This means that if you offer 2 SKUs with slightly different attributes, that could have been consolidated into one, the supply chain will suffer that cost and inefficiency. The SKU definition has to be optimized before you send it into the supply chain. This is a key driver to SKU inventory.
Customers buy products based on choices at the attribute level. If you cannot gather demand intelligence at the attribute level, you are out of touch with your customer. Customers DO NOT buy SKUs. They do not know the SKU numbers, and they do not care.
SKU Challenges Based on Supply Model
Your business falls into one of these categories based on your supply model (see table). Knowing what attributes customers are buying can dramatically improve your demand response. You will be able to improve -
- SKU definition -This means knowing how many SKUs you need and what needs to be in the SKU
- Demand Forecasting – You will be able to forecast demand at the attribute level, which is the level that customers are buying
- SKU Inventory - plan what to stock to have highest turns.
- Sales Productivity and Efficiency – If you know what attributes are selling together, you can implement an automated recommendation engine (EmcienMatch) and your sales rep can recommend a good choice to the customer during the ordering process. This is probably the single biggest value of knowing what attributes customers are buying. Your sales reps are a trusted advisor to your customers. If the sales person know that all customers of a certain type bough a particular configuration, he could recommend that choice to the customer. Win! Customer is happy because he done! Sales person is happy because he looks smart! You are happy because you increased your sales repeatability!
For our Nerdy Math readers, here is technical nugget that you will love:
SO – here is another reason why what Emcien does has not been done before. Statistics deals with numerically valued variables. A numerically valued random variable X has a domain that can be classified as a ratio scale, an interval scale, an ordinal scale, or a nominal scale. In a nominal scale, the numbers {0,1,2,3,…} are just labels and have no numerical significance. In an ordinal scale the numbers provide an ordering, so that 2>1 in some appropriate sense. An interval scale allows real numbers (like 3.27) and differences are significant, but ratios are not. The classic example is temperature. A difference of 10 degrees is bigger than a difference of 5 degrees, but 100 degrees is not twice as hot as 50 degrees. Finally, a ratio scale allows all of the usual numerical operations on real numbers. Most of statistics assumes a ratio scale, and almost all of it assumes at least an ordinal scale. This leads directly to the mean, variance, covariance, and correlation. It also leads to metric spaces with distance functions.
But we want to consider a random variable X that represents a choice between cloth seats and leather seats. You might argue that leather > cloth, because leather is more expensive. But what about color? Is there any sense in which green > red? We are really interested in nominal scales. We may assign 0, 1, and 2 to “none”, V-6, and V-8 respectively, but these are just labels. That has a profound effect on the statistics we can use. And beyond statistics, we will have to develop notions of proximity or closeness that do not depend on distance functions. So it hasn’t been done before because the mathematics you need is not the popular stuff that’s in the textbooks.
Comments Off
True Demand Intelligence – Knowing who is buying what, where and why
Demand Intelligence – Knowing Who is Buying What, Where and Why
SKU numbers are an easy way to keep track of items that are built, stocked and sold. The SKU number itself is arbitrary and contains no ‘intelligence’.
The SKU number was invented for a very good reason. When this practice started, the number of SKU’s was small, and people and systems needed a simple way to track what they had. So ASP-678 may be the SKU number for a toothpaste tube with spearmint flavor, whitening, and tartar control. However, customers do not look for SKUs. They look for toothpaste with whitening, tartar control, flavors, sizes, etc. Customers buy attributes, and combinations of attributes. Some companies code the attributes into the SKUs, by concatenating two or three character codes (like SPWHTC). But this is at best a clumsy way of handling a few attributes. Companies want to know what attributes customers are looking for, and SKU numbers hide the attributes.
As the number of attributes starts to grow, whether you have them coded into the SKU number or not, the problems start to mount! The most important one is that companies do not know what customers are buying, or trying to buy. As the number of choices grows, the number of combinations grows much faster and companies drown in their own SKUs.
SKU intelligence is going behind the SKU numbers and ‘detecting what attributes customers are buying’. Knowing who is buying what, where and why is “True Demand Intelligence”.
Products have attributes. For example, a computer has a processor, a memory, and a hard drive. For each attribute there may be several alternative choices. This means that there are many different product configurations. Some companies make only a fixed subset of all the possible configurations and give each one a SKU number. Other companies allow customers to order exactly what they want, and if this is something new, then they create a new SKU number for it. In either case, a SKU number is supposed to represent a unique product configuration.
If you are trying to figure out what your customers want, then SKU numbers are a form of encryption. You have to look at your sales history in terms of the underlying attributes, and the choices for those attributes. Instead of looking at one SKU number you need to look at perhaps 20 separate attributes. The SKU number is a way of collapsing those 20 dimensions into a single dimension, with tremendous information loss. One of the things that is lost is proximity to other SKU’s, based on attribution. A customer who bought SKU A-1234 might have been satisfied with (or really looking for) SKU B-3728. These two SKUs have the same choices for 18 of the 20 attributes, and differ on only two. This is obvious when the unique configurations are represented as a set of attribute choices, but hidden when they are represented as SKU numbers. The first step in analyzing a sales history has to be expressing it in terms of the underlying attributes. Each SKU number has to be expanded into a list of choices. Then we can begin to find patterns in how the choices are made. The leather seats and the DVD player are usually bought together. Engine block heaters are not ordered on convertibles. Buying patterns exist at the attribute level, not at the SKU level.
“Buying patterns” are popular combinations of attribute choices. These can be pairs of attributes, triples of attributes, or even more. Popularity is measured by the share of sales that have that combination. Buying patterns are helpful in selling, because they reveal how customers can be moved to configurations (SKUs) that we have in stock, or that we would prefer to build. Experienced sales people are skilled at moving customers, but If these patterns are represented in some kind of knowledge base, then a computer can make the recommendations.
Customers also have attributes. The simplest is perhaps geographical location. There are patterns that involve both product attributes and customer attributes. Customers in Florida are more likely to buy convertibles; customers in North Dakota are more likely to buy engine block heaters. Customers may have several attributes, for example demographic attributes for individuals or industry attributes for companies. (We don’t assign SKU numbers to customers!) If your sales history contains information about the customer as well as information about the product, then we can look for buying patterns that are associated with certain kinds of customers.
As an example, for a desktop computer the list of attributes might be: Processor, Memory, Hard Drive, Keyboard, Monitor, Mouse, CD/DVD, Application. A specific SKU number like A-1234 is a code for a specific configuration, say (2GHz, 2GB, 120GB, Ergonomic, 22” flat panel, Wireless, R/W Combo, Gaming). The Application attribute is really a customer attribute, with values like Home, Small Business, or Entertainment, as well as Gaming. This would make it possible to look for typical Gaming configurations and typical Entertainment configurations.
SKU numbers are a useful shorthand for record keeping. Each SKU number represents a unique product configuration. But analyzing SKU numbers is like analyzing telephone numbers. To see the buying patterns, you have to go to the attribute level. The patterns exist among the attributes, so you have to decode the SKU numbers to see them.
Recommendation engine for configurable products
The Amazon recommendation engine has received a lot of attention and imitation. It has been successful at increasing sales by pointing out that people who bought book x also bought book y. This simulates a helpful book store employee who has an extensive mental map of how books relate to each other. Recommendations have been most successful for books, movies, and music. Companies that sell complex configurable products could also benefit from a system of automated recommendations. Products like trucks, tractors, computers, lighting fixtures, valves, and industrial fans. These are products that the buyer can customize to his own preferences or needs. The buying process is complex, and sales agents make recommendations, just like the book store expert. But many of these products are far more complex than books.
How is a book different from a truck? Could a recommendation engine for books be used to recommend trucks? The purpose of this note is to consider the ways in which the two cases are similar and different, and to explore what a recommendation engine for configurable products might look like.
Books and trucks can both be described in terms of attributes (also called features or characteristics). Books can be described by their genre, author, language, and publication date for instance. Trucks can be described by their engine, transmission, wheelbase, gross vehicle weight, and many other attributes. Books, movies, and music can be classified in sufficient detail with ten or fewer attributes, while configurable products usually have a lot more. Heavy-duty trucks can have anywhere from 30 to 300 attributes. For books, the attributes are used to classify existing books. For configurable products, each attribute represents a choice for a customer who is ordering the product. Each attribute has several alternative options, so an order is really a list of option choices.
Amazon uses attributes to let customers search for a book, but the recommendation engine does not use them. The recommendation engine remembers each customer’s purchase history. For example, Joe has already bought “War and Peace” and “Crime and Punishment”. When he buys “The Sound and the Fury”, a connection is made between “The Sound and the Fury” and “War and Peace”, and another connection is made between “The Sound and the Fury” and “Crime and Punishment”. More accurately, the weights of these connections are increased. The connection between “The Sound and the Fury” and “War and Peace” depends on the number of customers that have bought both books. Commonality depends on common purchase by individual customers.
One big difference between books and trucks is that an individual will buy many books, but is unlikely to buy many trucks. So the basis for the connections between trucks can’t be the common purchases of individual buyers.
Another difference is that only books that have already been written are of interest. No customer is looking for a book that hasn’t been written yet, and you certainly can’t recommend one. But because of the very large number of choices, a buyer who is customizing a truck may arrive at a configuration that has never been built before. So our recommendation system must be able to accommodate trucks that don’t exist yet.
The helpful book store employee will jump from one book to another book that his customer might like. When we look at the helpful sales agent, he is doing something quite different. Based on the first, and usually most important, choices that the buyer makes, he will suggest ways of completing the order. The buyer may really only care about 10 of the 30 choices, and want guidance on what else to choose. The book store employee jumps from one complete item to another complete item. The sales agent is finding a path from a partial order to a complete order.
So we have an initial set of requirements for a recommendation engine for configurable products. It must help a buyer who has made some choices to make additional choices, so as to arrive at a complete order. From the seller’s point of view, we would want these recommendations to guide the buyer toward items that are advantageous. This might mean popular, in stock, and/or profitable. Its concept of the product (e.g. truck) must be broad enough to encompass configurations that have never been built before, and its concept of commonality must be based on something other than common purchases.
To show one way this might be done, consider a different way of making connections. When a customer buys a red truck with a V-8 engine, he is making a connection between red, a value of the Color attribute, and V-8, a value of the Engine attribute. So the customer’s vote is not recorded as a connection between two complete trucks, but as a connection between two attributes. More precisely, it is recorded as a connection between two values, or options, of the two attributes.
When a customer buys a truck with n attributes, we will record his “vote” n times, once for each of the options he has chosen. Then we will also record it nC2 more times for each pair of options. The symbol nC2 stands for the number of different pairs of attributes there are, and can be computed as n*(n-1)/2. For example 10C2=45. The relative popularity of the different pairs of options (like red and V-8) tells us something about how customers are buying the product, and gives us a different basis for making recommendations. (If you want pineapple on your pizza, you probably want Canadian bacon.)
If pairs of options are interesting, then so are triples of options. The same customer vote can be recorded for nC3 different sets of three options (10C3=120). Every option of every attribute has its own popularity (i.e. number of votes). Expressed as a fraction of total units sold it is known as a first-order take rate. Every pair of options also has a popularity, and as a fraction is defined as a second-order take rate. Similarly, each triple has a third-order take rate. Of course we can also define fourth, fifth, and higher-order take rates.
If customer purchases (votes) are recorded in this way, then we will have captured the buying patterns in the form of first, second, third, and higher-order take rates. A new customer who begins to select the options that are important to him will trigger these patterns, which will then serve as the basis for recommending a complete truck. So we see that two complete trucks may be related because they both contain instances of the same fifth-order take rate. This can be true even if neither truck has ever been built before.
We conclude that a recommendation engine for configurable products could be built by mapping customer purchases into a structure of take rates that record the relative popularity of options, pairs of options, triples of options, and so forth.
Comments Off
What does the stairway to complexity tell us?
If a product is too complex, where is the complexity coming from? Which features are causing the explosion in the number of build combinations? The stairway to complexity tells us where to look.
The stairway to complexity shows how the number of unique configurations drops as features are removed. Here is another stairway for a backhoe with 30 features.
The number of build combinations drops from 934 down to 1 as we remove the features. Behind the graph is the actual list of features in the order they were removed. In the table below, the features are ranked from 1 to 30, corresponding to the steps in the graph.
If we want to simplify our product, this ranking of the features tells us where to start. The greatest contributor to complexity is the Buckets, of which there are 34 different kinds. The number of build combinations would drop from 934 to 838 if we didn’t have to worry about Buckets.
Is the ordering of the features in the stairway the same as the ordering by number of options? The first feature in the stairway is certainly the one with the most options (34). But Tran_Control has the second largest number of options (9), and doesn’t appear in the stairway until step 15. So there is more going on than just the number of options.
The amount of complexity introduced by a feature depends not just on the number of options, but on the relative popularity of the different options. Having two options that are split 50% to 50% is much worse than if they are split 90% to 10%. (See earlier post: Entropy of a coin toss.)
Introducing a new feature only increases product complexity if it splits existing configurations that would otherwise be the same. One manufacturer insisted that his product was so complex because it was produced for many different countries. But the number of unique build combinations was exactly the same whether the Country feature was included or not.
Comments Off
The Number of Choice Combinations Depend…
The number of choice combinations depend on which product features are included. The build combinations is the product mix or the marketing mix.
Let’s consider the sales history of our product. There are two very important numbers: the number of units sold and the number of unique configurations. The number of units is well defined, but the number of unique configurations is ambiguous. The ambiguity comes from the fact that there will be more unique configurations if we use more features, especially soft features, to describe our product.
One very special soft feature is a Serial Number, or VIN (Vehicle Identification Number). The whole purpose of the Serial Number is to make each instance of the product unique. So if we look at our sales history and include Serial Number, we will see that the number of unique configurations is exactly the same as the number of units of the product (instances).
If we want to begin to understand the demand for our product we have to see which instances are actually the same. That means we have to get rid of the Serial Numbers. When we do, the instances collapse into groups of now unique configurations; that is, unique without Serial Number.
If we are interested in the tangible features of the product, then we may want to take out other soft features as well. Geographic region is important for some purposes, but may be a distraction when we are interested in the physical product. Taking out the geographic region feature will cause another reduction in the number of unique configurations. The red, V8, convertible in Florida will get combined with the red, V8, convertible in New York.
Sometimes we are interested in the variants of our product ignoring color. We know that every real variant is going to come in several colors, but we want to look at the product without the distraction of color. This is sometimes called the “body in white”. So the red, V8, convertible and the green, V8, convertible collapse into the V8, convertible.
The point I am making is that the number of unique configurations depends on which features are included, and this number drops whenever a feature is taken away. Mathematically, this is called “projecting out the feature”.
The number of unique configurations is at most the number of units sold, and at a minimum it is just one. If we take away all of the features, then every unit looks the same, which means just one configuration. There is a path from one extreme to the other that we will introduce next time.
By the way – understanding this is important as product complexity is a key driver of process complexity.
Comments Off
Take Rates – What are the most popular product choices?
I want to apply the discussion of entropy to the features of a configurable product. But first we have to introduce the important concept of a “take rate”. In different industries this is called an “attach rate”, or a “penetration rate”. The idea is very simple: the take rate of an option is the fraction of units sold that include that option.
The take rate of option x is the number of units sold with option x, divided by the total number of units sold. So if 70% of our cars are sold with cloth seats and 30% with leather seats, then cloth has a take rate of 0.7 and leather has a take rate of 0.3.
In the case of a feature with two options, like cloth and leather, this looks just like a coin toss with two options, tails and heads. Recall that coins may not be fair. If I send you a message about a customer’s choice of seat, the entropy of that message is the same as for the outcome of one toss of a suitably biased (.3 to .7) coin. So take rates can be interpreted as probabilities.
Some features have more than two options. For example a backhoe feature called Feet has four different options: none, Flip, Flip Guard, and Street Guard. Each of these options has a take rate, and as long as we include the “none” option, these take rates have to add up to 1.0. So perhaps 30% of customers do not order Feet, 40% order Flip, 20% order Flip Guard, and 10% order Street Guard. The take rates are 0.4, 0.3, 0.2, and 0.1, respectively, which add up to 1.0.
With four options we lose the connection to coin tosses. We could use a loaded die to talk about features with six options, but an all purpose metaphor is the roulette wheel. Think of a spinning roulette wheel, or a stationary wheel with a spinning arrow as in many children’s games.
The wheel represents a feature, and there is a pie-slice for each option. The size of the pie-slice is proportional to the take rate. An example is shown above for the Feet feature of our backhoe. We can simulate a customer’s choice by spinning this wheel (or spinning an arrow). With this metaphor we can have any number of options, with any take rates. The “none” choice must be included to get a full pie (or there may not be a “none” choice).
To summarize, a product is a collection of features. Each feature has some mutually exclusive options, each of which has a take rate. These take rates add to one.
The Entropy of a Coin Toss.
A product is a collection of features, and each feature has mutually exclusive options. If a feature has only two options, then the choice is like a coin toss. The information contained in that choice is measured by entropy.
Entropy is a concept from classical thermodynamics that deals with the amount of disorder in a physical system (see http://en.wikipedia.org/wiki/Entropy). It was extended to information theory by Claude Shannon (see http://en.wikipedia.org/wiki/Entropy_(information_theory)). Shannon used entropy as a measure of the amount of information in a message. The simplest example is a coin toss. If we toss a fair coin, there is a 50% chance of getting tails, and a 50% chance of getting heads. Shannon defined the outcome of this experiment as having an entropy, or information content, of one bit. If I send a message (say 0 or 1) to tell you the result (tail or head), that message contains one bit of information.
Things start to get interesting when the coin is not fair. Consider a two-headed coin. The tossing experiment always results in heads, and the message will always be 1. According to Shannon, the information content of this message is zero.
If the coin is weighted so that the probability of tails is 25% and the probability of heads is 75%, then Shannon assigns an entropy of 0.811278. There is some information in knowing the outcome of the coin toss, but not as much as for a fair coin, because we already know that it will probably be heads. The graph below shows the entropy as a function of the probability of getting heads. When this probability is zero or one, the entropy is zero. The entropy reaches its maximum of one when the coin is fair (50%).
Where did the 0.811278 come from? How is the entropy actually computed?
We can’t answer this without introducing logarithms to the base two. In English, two to the third power is eight, so three is the logarithm of eight to the base two. We can write “blog” to mean log to the base 2, or binary log. If p denotes the probability of heads, then entropy is computed by the formula:
Entropy = -p*blog(p) – (1-p)*blog(1-p).
Logarithms to the base 2 arise naturally because one coin toss (2 outcomes) has entropy one, two coin tosses (4 outcomes) has entropy two, three coin tosses (8 outcomes) has entropy three, and so forth.
Comments Off
Self-Service simplifies Product Offerings and increases Margins
Self service is a term we all know, such as pay-at-the-pump gas and self-checkout stations at some grocery stores, and now more obscure things like video game kiosks by GameFly, but the true tidal wave of self-service hasn’t even started, and it’s going to be good for both the consumer and the manufacturer, if done right.
Self Service Grocery Scanner
When you checkout your soda and cereal by swiping products across a scanner at the auto-checkout stations, there isn’t much complexity other than when you get a problem with the scanner reading a smudged bar code or trying to locate the button for ‘snap beans’ when you put those on the scale. The transaction is smooth, quick and you are in control, which is a good feeling as a buyer, you are not being sold, you are buying just what you want, quickly and easily.
But what happens if you try to buy a “configurable product“? In the grocery store, the only thing configurable is the weight of produce, but other than that, the costs and configurations are set in stone and are detected by reading the bar codes. Easy to understand as the buyer and relatively easy to deal with as the seller. Configurable products are those where you have to make many choices before you can order the one product. Products like computers, cars and thousands of others where the buyer has to describe their preferences or choices so the product can be created and delivered. It’s even more complex in a B2B environment than it is in B2C, where the products available and choices are astronomical. Products like Lighting, Valves, Agriculture and Construction Equipment, Lifts, Electrical equipment, cooking equipment and conveyors have more choices and variants than you can imagine and that variety makes it hard to order, build and deliver efficiently.
Usually a large direct sales force is sent out with complex price books (sometimes online in PDF form) to sit with customers and prospects and help them combine choices in hopefully valid ways. The choices a customer have to make are quite extensive, ranging from tens to hundreds of choices. Most of these choices the customer doesn’t care about, but they are required by the manufacturer just so they can build a valid product. Customers care about the few things that matter to them but after that, they will just choose things that “seem to make sense” just to complete the order. Sometimes they don’t even do that, they get so frustrated with 60 more questions about features and options on the product (many of which they don’t understand) that they walk away.
In some cases companies believe that putting in a configurator is the solution to their problem. Configurator’s automate the order process by ensuring that the order is VALID. The engineering and marketing rules that drive what can be built and offered are setup in a configurator such that the user ordering the product is led through valid questions and end up with a build-able product. Now this product may be build-able but it also may be a one-off low-margin brand new SKU that manufacturing hasn’t built before and requires some parts they aren’t carrying at this time. All this for something that was only 2 choices from a very popular configuration. And those 2 differences only happened because the customer was asked 20 more questions after they entered the 5 things they cared about. They chose as best they could, but without any guidance or suggestions, ended up on a new SKU which will ultimately explode into huge numbers of parts and processes to support the new SKU.
Now if the customer only had to enter the 5 things they cared about and the system recommended the combination of other choices such that the customer’s price limit was met and the configuration wasn’t a new SKU and the SKU had a good margin, then it would have been a win-win for everyone. And the whole process could be complete quickly and easily. The customer wouldn’t have to answer any other questions and would feel that same feeling that you do when you swipe your can of soup across the scanner at the market. The manufacturer wins as well because the customer was guided toward an existing configuration so the cost of creating and supporting a new SKU was avoided. It’s happening now with recommendation engines that leverage buying patterns to suggest full configurations based on the few attributes a customer gives it. Just like Amazon can recommend other books you might want to read based on the current “fly fishing” book you are looking at now, suggestion engines can be utilized to provide this convenience for much more complex products.
That’s the self-service tidal wave that’s coming, when all products, not matter how complicated can be ordered by simply asking for the attributes that YOU care about, what your price limit is and then Voila! it’s done. Customers will order more from companies that offer this convenience. Just think about how often you walk into the gas station to pay as opposed to pay at the pump. And if you had two stations to fill up at, one was pay at the pump and the other required you stand in line after pumping the gas, which do you think you would most often go to? Simplification is good for everyone, and profitable too.
Comments Off
Q&A with John Sloan, former director, Jeep Brand Global Product Marketing
In today’s post, John Sloan talks about challenges dealers face in ordering inventory that best matches customer demand.
Emcien: Describe the Chrysler-Emcien initiative that examined dealers’ struggles with complexity in the ordering process.
JS: In a soft “push” market where volume is driven by heavy incentives versus the merits of the brand / model, managing cost is paramount. A key piece to focus on is product inventory. Dealers get roughly 60 days of no-interest floor plan. In a soft market, vehicles can easily sit for longer than two months before being sold, so it’s critical that vehicles be easy to order, stock and sell. Simple is better.
Emcien worked on a model to simplify the Chrysler PT Cruiser product mix. There were thousands of possible build configurations for the PT Cruiser, creating significant complexity for engineering and the assembly plant, as well as the supplier extended enterprise. Emcien’s ability to accurately forecast demand is invaluable for a complicated product line because it can assist with reducing the build configurations to those that best match demand. The PT Cruiser initiative validated the power of the Emcien inventory model.
Variation is valuable
Advances in interconnection technologies are driving an increasingly demand-driven market. Customers are learning to expect to get what they want, when they want it, how they want it. And they tell you in each and every interaction they have with your company, or not. In a demand-driven world, increasing product variation and complexity in your business model is inevitable. Left untended, your business can become a tangled web of counterproductive business strategies with a dense portfolio of product families comprising thousands, even millions, of variants.
However, make no mistake, variation is valuable. To deny complexity or view the long tail of product variation as a management failure is to deny diversity of the world in which we make our living. Eliminate complexity in your product offer and you will find yourself competing with boatloads of product from China, India or any of a number of low-wage production markets.
The “keep it simple” principle is the root of good management. However, as Oliver Wendell Holmes, Jr. has observed, “I would not give a fig for the simplicity this side of complexity, but I would give my life for the simplicity on the other side of complexity,” it matters which form of simplicity you choose. The wrong simple answer is to try to focus on the 20% of product variants that make up 80% of your revenue, the head of the ubiquitous Pareto distribution, and find ways to minimize or eliminate the so-called unprofitable remaining 80% of product variants that lurk in the tail. Hello commodity, goodbye margins. The right simple answer is to deliver Intelligent Variation based on the voice of the customer shouting through the many interactions they have with you each and every day.
Comments Off