tag:blogger.com,1999:blog-41532932356821111132024-02-20T14:47:34.065+05:30Operations everythingThe blog is about my views on the events in Operations and Supply Chain.Piyush Shahhttp://www.blogger.com/profile/00413083724751291686noreply@blogger.comBlogger73125tag:blogger.com,1999:blog-4153293235682111113.post-78074091257553092092017-06-20T01:43:00.000+05:302017-06-20T06:20:05.971+05:30Amazon's takeover of Whole Foods might not work<div dir="ltr" style="text-align: left;" trbidi="on">
I don't judge business events by stock market reactions, as stock markets can be absurd and have a logic that I can't fathom. That is why, I am questioning the logic of Amazon's buy-out of Whole Foods in spite of the seemingly massive stock market approval and also the jubilation among the proletariat. Stock markets have loved Enron till the day before the scam was disclosed and the general population beliefs have been massively wrong before. I don't claim that this marriage WILL fail, but I think there are many risk factors that are not being considered and because of them this COULD fail.<br />
<div>
<br /></div>
<div>
The Amazon and Whole Foods marriage, to be successful, would need to create synergies. Maybe if a few Amazon or Whole Foods warehouses can be closed without an impact on sales, the buyout would make sense. Or, if Amazon could push its products through Whole Foods (or vice versa) without an increase of cost, it would also make sense. In both these scenarios there has to be some level or merging of strategies or information between the two firms. Not withstanding the study from Harvard Business School that said that 70 - 90% of mergers and acquisitions do not achieve their goals, I raise some questions on the ability of Amazon to create synergies with Whole Foods. </div>
<div>
<br /></div>
<div>
Let us start from the general business strategy. One of the reasons Whole Foods works is that they are essentially 'local'. So, a store manager can make purchasing decisions without head office approval - like buying potatoes from a local farmer. Their distribution is very decentralized because of such local buying. There are large regional teams with significant autonomy. Of course such operations cost more and so Whole Foods ensures a 30%+ gross margins. Amazon by contrast is centralized, regimented and highly synchronized. The key skill of an Amazon manager is being able to follow the process and not independent thinking. So, the first set of questions - is there any possible synergy between Whole Foods and Amazon? Can the people of these two companies work together? Would a Whole Foods store manager be okay to give up his autonomy? Would an Amazon manager have the competency to be autonomous? </div>
<div>
<br /></div>
<div>
It is not just about the managers' autonomy. Whole Foods is known to have have 12 different inventory management systems - they also have autonomous inventory management systems. Whole Foods is trying to reign this in by creating a cloud based solution with Infor, but such attempts in previous firms have had limited success. Whichever ways, Amazon will either inherit a blind system or an Infor based system about which it has very little expertise. Will it be possible to seamlessly integrate Amazon and Whole Foods inventory systems? Will Amazon ever have the same granular level information about Whole Foods stores that it has about its own DCs?</div>
<div>
<br /></div>
<div>
Let us look at it from the customer front. Whole Foods is essentially a bit like a cult. Because of local buying, Whole Foods has fresher produce. Also, such local buying is good for the community. These two differentiators have created a following among a specific class of consumers who are ready to pay the high prices of Whole Foods. What happens to this 'cult' if Whole Foods centralizes the produce? Will consumers still be loyal to Whole Foods? </div>
<div>
<br /></div>
<div>
The list of questions can go on. Whole Foods has only around 400 stores in the USA. Walmart has more than ten times as many. Will it be possible for a small specialty store to compete with the might of Walmart? Let us say Whole Foods goes on a store opening spree - will it still be able to create the cult among customers with that high rate of expansion? </div>
<div>
<br /></div>
<div>
I don't have answers to my own questions. But, I do have these and a few more questions. In such times of a general jubilation I know there is a danger of me and my questions being labeled as cynical or old economy, and I am fine with that. I just hope to trigger a few thoughts among some people who can go beyond the general jubilation and think of an alternate - even if for only a few minutes. </div>
<div>
<br /></div>
<div>
</div>
</div>
Piyush Shahhttp://www.blogger.com/profile/00413083724751291686noreply@blogger.com3tag:blogger.com,1999:blog-4153293235682111113.post-68679867970079918992015-06-15T02:45:00.000+05:302015-06-15T03:12:37.924+05:30Flipkart eCommerce valuations<div dir="ltr" style="text-align: left;" trbidi="on">
I am not against eCommerce. Just that I am confused by the real business of Flipkart and its lot. I am writing this blog hoping that some intelligent reader will enlighten me. Okay, to start, the total investment in Flipkart has been around $2.3 billion dollars. And yet the value of the firm is supposed to be more than $15 billion. If we create a time value for the various investments the rate of return would be astronomical.<br />
<br />
Where has all the 2.3 billion gone? Assuming Flipkart has leased 3 million sq ft of warehouse space, and a lease rate of Rs. 20 per sq ft the costs come to around $12million per year. Assuming they employ 16000 people at an average of Rs.15000 per month the salary bill would come to be $48million per year. The company has been in existence for 8 years and it has grown rapidly only in last couple of years, so you can do the math of the total expenses. Ohh yes, this is expense as (to the best of my knowledge) Flipkart has leased all its its warehousing space and not invested in creating its own infrastructure. <br />
<br />
In May 2014, Flipkart bought Myntra reportedly at $320 million. Myntra had 2014 yearly revenue of around $160 million and probably no profits at all. Interestingly Tiger Global and Accel Partners are involved with both Flipkart and Myntra. So its like this, the two investors invest in Flipkart, who then buys Myntra, who then pays off its investors. Amazing circle of life. Note that the total investment into Myntra has been only around $100 million.<br />
<br />
(All my numbers are from internet based magazines and newpapers and could be completely wrong)<br />
<br />
Hmm.....my confusion. Whats happening here? <br />
<br />
Okay....let me predict the future. Flipkart will indulge into more acquisitions at astronomical rates. And by coincidence both Flipkart and the acquired company would have the same set of investors (directly and indirectly) . </div>
Piyush Shahhttp://www.blogger.com/profile/00413083724751291686noreply@blogger.com0tag:blogger.com,1999:blog-4153293235682111113.post-14132043896335790152015-02-13T08:54:00.001+05:302015-02-13T09:07:24.544+05:30Customer service through operational metrics<div dir="ltr" style="text-align: left;" trbidi="on">
<!--[if gte mso 9]><xml>
<w:WordDocument>
<w:View>Normal</w:View>
<w:Zoom>0</w:Zoom>
<w:TrackMoves/>
<w:TrackFormatting/>
<w:PunctuationKerning/>
<w:ValidateAgainstSchemas/>
<w:SaveIfXMLInvalid>false</w:SaveIfXMLInvalid>
<w:IgnoreMixedContent>false</w:IgnoreMixedContent>
<w:AlwaysShowPlaceholderText>false</w:AlwaysShowPlaceholderText>
<w:DoNotPromoteQF/>
<w:LidThemeOther>EN-IN</w:LidThemeOther>
<w:LidThemeAsian>X-NONE</w:LidThemeAsian>
<w:LidThemeComplexScript>X-NONE</w:LidThemeComplexScript>
<w:Compatibility>
<w:BreakWrappedTables/>
<w:SnapToGridInCell/>
<w:WrapTextWithPunct/>
<w:UseAsianBreakRules/>
<w:DontGrowAutofit/>
<w:SplitPgBreakAndParaMark/>
<w:DontVertAlignCellWithSp/>
<w:DontBreakConstrainedForcedTables/>
<w:DontVertAlignInTxbx/>
<w:Word11KerningPairs/>
<w:CachedColBalance/>
</w:Compatibility>
<m:mathPr>
<m:mathFont m:val="Cambria Math"/>
<m:brkBin m:val="before"/>
<m:brkBinSub m:val="--"/>
<m:smallFrac m:val="off"/>
<m:dispDef/>
<m:lMargin m:val="0"/>
<m:rMargin m:val="0"/>
<m:defJc m:val="centerGroup"/>
<m:wrapIndent m:val="1440"/>
<m:intLim m:val="subSup"/>
<m:naryLim m:val="undOvr"/>
</m:mathPr></w:WordDocument>
</xml><![endif]--><br />
<!--[if gte mso 9]><xml>
<w:LatentStyles DefLockedState="false" DefUnhideWhenUsed="true"
DefSemiHidden="true" DefQFormat="false" DefPriority="99"
LatentStyleCount="267">
<w:LsdException Locked="false" Priority="0" SemiHidden="false"
UnhideWhenUsed="false" QFormat="true" Name="Normal"/>
<w:LsdException Locked="false" Priority="9" SemiHidden="false"
UnhideWhenUsed="false" QFormat="true" Name="heading 1"/>
<w:LsdException Locked="false" Priority="9" QFormat="true" Name="heading 2"/>
<w:LsdException Locked="false" Priority="9" QFormat="true" Name="heading 3"/>
<w:LsdException Locked="false" Priority="9" QFormat="true" Name="heading 4"/>
<w:LsdException Locked="false" Priority="9" QFormat="true" Name="heading 5"/>
<w:LsdException Locked="false" Priority="9" QFormat="true" Name="heading 6"/>
<w:LsdException Locked="false" Priority="9" QFormat="true" Name="heading 7"/>
<w:LsdException Locked="false" Priority="9" QFormat="true" Name="heading 8"/>
<w:LsdException Locked="false" Priority="9" QFormat="true" Name="heading 9"/>
<w:LsdException Locked="false" Priority="39" Name="toc 1"/>
<w:LsdException Locked="false" Priority="39" Name="toc 2"/>
<w:LsdException Locked="false" Priority="39" Name="toc 3"/>
<w:LsdException Locked="false" Priority="39" Name="toc 4"/>
<w:LsdException Locked="false" Priority="39" Name="toc 5"/>
<w:LsdException Locked="false" Priority="39" Name="toc 6"/>
<w:LsdException Locked="false" Priority="39" Name="toc 7"/>
<w:LsdException Locked="false" Priority="39" Name="toc 8"/>
<w:LsdException Locked="false" Priority="39" Name="toc 9"/>
<w:LsdException Locked="false" Priority="35" QFormat="true" Name="caption"/>
<w:LsdException Locked="false" Priority="10" SemiHidden="false"
UnhideWhenUsed="false" QFormat="true" Name="Title"/>
<w:LsdException Locked="false" Priority="1" Name="Default Paragraph Font"/>
<w:LsdException Locked="false" Priority="11" SemiHidden="false"
UnhideWhenUsed="false" QFormat="true" Name="Subtitle"/>
<w:LsdException Locked="false" Priority="22" SemiHidden="false"
UnhideWhenUsed="false" QFormat="true" Name="Strong"/>
<w:LsdException Locked="false" Priority="20" SemiHidden="false"
UnhideWhenUsed="false" QFormat="true" Name="Emphasis"/>
<w:LsdException Locked="false" Priority="59" SemiHidden="false"
UnhideWhenUsed="false" Name="Table Grid"/>
<w:LsdException Locked="false" UnhideWhenUsed="false" Name="Placeholder Text"/>
<w:LsdException Locked="false" Priority="1" SemiHidden="false"
UnhideWhenUsed="false" QFormat="true" Name="No Spacing"/>
<w:LsdException Locked="false" Priority="60" SemiHidden="false"
UnhideWhenUsed="false" Name="Light Shading"/>
<w:LsdException Locked="false" Priority="61" SemiHidden="false"
UnhideWhenUsed="false" Name="Light List"/>
<w:LsdException Locked="false" Priority="62" SemiHidden="false"
UnhideWhenUsed="false" Name="Light Grid"/>
<w:LsdException Locked="false" Priority="63" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium Shading 1"/>
<w:LsdException Locked="false" Priority="64" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium Shading 2"/>
<w:LsdException Locked="false" Priority="65" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium List 1"/>
<w:LsdException Locked="false" Priority="66" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium List 2"/>
<w:LsdException Locked="false" Priority="67" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium Grid 1"/>
<w:LsdException Locked="false" Priority="68" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium Grid 2"/>
<w:LsdException Locked="false" Priority="69" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium Grid 3"/>
<w:LsdException Locked="false" Priority="70" SemiHidden="false"
UnhideWhenUsed="false" Name="Dark List"/>
<w:LsdException Locked="false" Priority="71" SemiHidden="false"
UnhideWhenUsed="false" Name="Colorful Shading"/>
<w:LsdException Locked="false" Priority="72" SemiHidden="false"
UnhideWhenUsed="false" Name="Colorful List"/>
<w:LsdException Locked="false" Priority="73" SemiHidden="false"
UnhideWhenUsed="false" Name="Colorful Grid"/>
<w:LsdException Locked="false" Priority="60" SemiHidden="false"
UnhideWhenUsed="false" Name="Light Shading Accent 1"/>
<w:LsdException Locked="false" Priority="61" SemiHidden="false"
UnhideWhenUsed="false" Name="Light List Accent 1"/>
<w:LsdException Locked="false" Priority="62" SemiHidden="false"
UnhideWhenUsed="false" Name="Light Grid Accent 1"/>
<w:LsdException Locked="false" Priority="63" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium Shading 1 Accent 1"/>
<w:LsdException Locked="false" Priority="64" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium Shading 2 Accent 1"/>
<w:LsdException Locked="false" Priority="65" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium List 1 Accent 1"/>
<w:LsdException Locked="false" UnhideWhenUsed="false" Name="Revision"/>
<w:LsdException Locked="false" Priority="34" SemiHidden="false"
UnhideWhenUsed="false" QFormat="true" Name="List Paragraph"/>
<w:LsdException Locked="false" Priority="29" SemiHidden="false"
UnhideWhenUsed="false" QFormat="true" Name="Quote"/>
<w:LsdException Locked="false" Priority="30" SemiHidden="false"
UnhideWhenUsed="false" QFormat="true" Name="Intense Quote"/>
<w:LsdException Locked="false" Priority="66" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium List 2 Accent 1"/>
<w:LsdException Locked="false" Priority="67" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium Grid 1 Accent 1"/>
<w:LsdException Locked="false" Priority="68" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium Grid 2 Accent 1"/>
<w:LsdException Locked="false" Priority="69" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium Grid 3 Accent 1"/>
<w:LsdException Locked="false" Priority="70" SemiHidden="false"
UnhideWhenUsed="false" Name="Dark List Accent 1"/>
<w:LsdException Locked="false" Priority="71" SemiHidden="false"
UnhideWhenUsed="false" Name="Colorful Shading Accent 1"/>
<w:LsdException Locked="false" Priority="72" SemiHidden="false"
UnhideWhenUsed="false" Name="Colorful List Accent 1"/>
<w:LsdException Locked="false" Priority="73" SemiHidden="false"
UnhideWhenUsed="false" Name="Colorful Grid Accent 1"/>
<w:LsdException Locked="false" Priority="60" SemiHidden="false"
UnhideWhenUsed="false" Name="Light Shading Accent 2"/>
<w:LsdException Locked="false" Priority="61" SemiHidden="false"
UnhideWhenUsed="false" Name="Light List Accent 2"/>
<w:LsdException Locked="false" Priority="62" SemiHidden="false"
UnhideWhenUsed="false" Name="Light Grid Accent 2"/>
<w:LsdException Locked="false" Priority="63" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium Shading 1 Accent 2"/>
<w:LsdException Locked="false" Priority="64" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium Shading 2 Accent 2"/>
<w:LsdException Locked="false" Priority="65" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium List 1 Accent 2"/>
<w:LsdException Locked="false" Priority="66" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium List 2 Accent 2"/>
<w:LsdException Locked="false" Priority="67" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium Grid 1 Accent 2"/>
<w:LsdException Locked="false" Priority="68" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium Grid 2 Accent 2"/>
<w:LsdException Locked="false" Priority="69" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium Grid 3 Accent 2"/>
<w:LsdException Locked="false" Priority="70" SemiHidden="false"
UnhideWhenUsed="false" Name="Dark List Accent 2"/>
<w:LsdException Locked="false" Priority="71" SemiHidden="false"
UnhideWhenUsed="false" Name="Colorful Shading Accent 2"/>
<w:LsdException Locked="false" Priority="72" SemiHidden="false"
UnhideWhenUsed="false" Name="Colorful List Accent 2"/>
<w:LsdException Locked="false" Priority="73" SemiHidden="false"
UnhideWhenUsed="false" Name="Colorful Grid Accent 2"/>
<w:LsdException Locked="false" Priority="60" SemiHidden="false"
UnhideWhenUsed="false" Name="Light Shading Accent 3"/>
<w:LsdException Locked="false" Priority="61" SemiHidden="false"
UnhideWhenUsed="false" Name="Light List Accent 3"/>
<w:LsdException Locked="false" Priority="62" SemiHidden="false"
UnhideWhenUsed="false" Name="Light Grid Accent 3"/>
<w:LsdException Locked="false" Priority="63" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium Shading 1 Accent 3"/>
<w:LsdException Locked="false" Priority="64" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium Shading 2 Accent 3"/>
<w:LsdException Locked="false" Priority="65" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium List 1 Accent 3"/>
<w:LsdException Locked="false" Priority="66" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium List 2 Accent 3"/>
<w:LsdException Locked="false" Priority="67" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium Grid 1 Accent 3"/>
<w:LsdException Locked="false" Priority="68" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium Grid 2 Accent 3"/>
<w:LsdException Locked="false" Priority="69" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium Grid 3 Accent 3"/>
<w:LsdException Locked="false" Priority="70" SemiHidden="false"
UnhideWhenUsed="false" Name="Dark List Accent 3"/>
<w:LsdException Locked="false" Priority="71" SemiHidden="false"
UnhideWhenUsed="false" Name="Colorful Shading Accent 3"/>
<w:LsdException Locked="false" Priority="72" SemiHidden="false"
UnhideWhenUsed="false" Name="Colorful List Accent 3"/>
<w:LsdException Locked="false" Priority="73" SemiHidden="false"
UnhideWhenUsed="false" Name="Colorful Grid Accent 3"/>
<w:LsdException Locked="false" Priority="60" SemiHidden="false"
UnhideWhenUsed="false" Name="Light Shading Accent 4"/>
<w:LsdException Locked="false" Priority="61" SemiHidden="false"
UnhideWhenUsed="false" Name="Light List Accent 4"/>
<w:LsdException Locked="false" Priority="62" SemiHidden="false"
UnhideWhenUsed="false" Name="Light Grid Accent 4"/>
<w:LsdException Locked="false" Priority="63" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium Shading 1 Accent 4"/>
<w:LsdException Locked="false" Priority="64" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium Shading 2 Accent 4"/>
<w:LsdException Locked="false" Priority="65" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium List 1 Accent 4"/>
<w:LsdException Locked="false" Priority="66" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium List 2 Accent 4"/>
<w:LsdException Locked="false" Priority="67" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium Grid 1 Accent 4"/>
<w:LsdException Locked="false" Priority="68" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium Grid 2 Accent 4"/>
<w:LsdException Locked="false" Priority="69" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium Grid 3 Accent 4"/>
<w:LsdException Locked="false" Priority="70" SemiHidden="false"
UnhideWhenUsed="false" Name="Dark List Accent 4"/>
<w:LsdException Locked="false" Priority="71" SemiHidden="false"
UnhideWhenUsed="false" Name="Colorful Shading Accent 4"/>
<w:LsdException Locked="false" Priority="72" SemiHidden="false"
UnhideWhenUsed="false" Name="Colorful List Accent 4"/>
<w:LsdException Locked="false" Priority="73" SemiHidden="false"
UnhideWhenUsed="false" Name="Colorful Grid Accent 4"/>
<w:LsdException Locked="false" Priority="60" SemiHidden="false"
UnhideWhenUsed="false" Name="Light Shading Accent 5"/>
<w:LsdException Locked="false" Priority="61" SemiHidden="false"
UnhideWhenUsed="false" Name="Light List Accent 5"/>
<w:LsdException Locked="false" Priority="62" SemiHidden="false"
UnhideWhenUsed="false" Name="Light Grid Accent 5"/>
<w:LsdException Locked="false" Priority="63" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium Shading 1 Accent 5"/>
<w:LsdException Locked="false" Priority="64" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium Shading 2 Accent 5"/>
<w:LsdException Locked="false" Priority="65" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium List 1 Accent 5"/>
<w:LsdException Locked="false" Priority="66" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium List 2 Accent 5"/>
<w:LsdException Locked="false" Priority="67" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium Grid 1 Accent 5"/>
<w:LsdException Locked="false" Priority="68" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium Grid 2 Accent 5"/>
<w:LsdException Locked="false" Priority="69" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium Grid 3 Accent 5"/>
<w:LsdException Locked="false" Priority="70" SemiHidden="false"
UnhideWhenUsed="false" Name="Dark List Accent 5"/>
<w:LsdException Locked="false" Priority="71" SemiHidden="false"
UnhideWhenUsed="false" Name="Colorful Shading Accent 5"/>
<w:LsdException Locked="false" Priority="72" SemiHidden="false"
UnhideWhenUsed="false" Name="Colorful List Accent 5"/>
<w:LsdException Locked="false" Priority="73" SemiHidden="false"
UnhideWhenUsed="false" Name="Colorful Grid Accent 5"/>
<w:LsdException Locked="false" Priority="60" SemiHidden="false"
UnhideWhenUsed="false" Name="Light Shading Accent 6"/>
<w:LsdException Locked="false" Priority="61" SemiHidden="false"
UnhideWhenUsed="false" Name="Light List Accent 6"/>
<w:LsdException Locked="false" Priority="62" SemiHidden="false"
UnhideWhenUsed="false" Name="Light Grid Accent 6"/>
<w:LsdException Locked="false" Priority="63" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium Shading 1 Accent 6"/>
<w:LsdException Locked="false" Priority="64" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium Shading 2 Accent 6"/>
<w:LsdException Locked="false" Priority="65" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium List 1 Accent 6"/>
<w:LsdException Locked="false" Priority="66" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium List 2 Accent 6"/>
<w:LsdException Locked="false" Priority="67" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium Grid 1 Accent 6"/>
<w:LsdException Locked="false" Priority="68" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium Grid 2 Accent 6"/>
<w:LsdException Locked="false" Priority="69" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium Grid 3 Accent 6"/>
<w:LsdException Locked="false" Priority="70" SemiHidden="false"
UnhideWhenUsed="false" Name="Dark List Accent 6"/>
<w:LsdException Locked="false" Priority="71" SemiHidden="false"
UnhideWhenUsed="false" Name="Colorful Shading Accent 6"/>
<w:LsdException Locked="false" Priority="72" SemiHidden="false"
UnhideWhenUsed="false" Name="Colorful List Accent 6"/>
<w:LsdException Locked="false" Priority="73" SemiHidden="false"
UnhideWhenUsed="false" Name="Colorful Grid Accent 6"/>
<w:LsdException Locked="false" Priority="19" SemiHidden="false"
UnhideWhenUsed="false" QFormat="true" Name="Subtle Emphasis"/>
<w:LsdException Locked="false" Priority="21" SemiHidden="false"
UnhideWhenUsed="false" QFormat="true" Name="Intense Emphasis"/>
<w:LsdException Locked="false" Priority="31" SemiHidden="false"
UnhideWhenUsed="false" QFormat="true" Name="Subtle Reference"/>
<w:LsdException Locked="false" Priority="32" SemiHidden="false"
UnhideWhenUsed="false" QFormat="true" Name="Intense Reference"/>
<w:LsdException Locked="false" Priority="33" SemiHidden="false"
UnhideWhenUsed="false" QFormat="true" Name="Book Title"/>
<w:LsdException Locked="false" Priority="37" Name="Bibliography"/>
<w:LsdException Locked="false" Priority="39" QFormat="true" Name="TOC Heading"/>
</w:LatentStyles>
</xml><![endif]--><!--[if gte mso 10]>
<style>
/* Style Definitions */
table.MsoNormalTable
{mso-style-name:"Table Normal";
mso-tstyle-rowband-size:0;
mso-tstyle-colband-size:0;
mso-style-noshow:yes;
mso-style-priority:99;
mso-style-qformat:yes;
mso-style-parent:"";
mso-padding-alt:0cm 5.4pt 0cm 5.4pt;
mso-para-margin-top:0cm;
mso-para-margin-right:0cm;
mso-para-margin-bottom:10.0pt;
mso-para-margin-left:0cm;
line-height:115%;
mso-pagination:widow-orphan;
font-size:11.0pt;
font-family:"Calibri","sans-serif";
mso-ascii-font-family:Calibri;
mso-ascii-theme-font:minor-latin;
mso-fareast-font-family:"Times New Roman";
mso-fareast-theme-font:minor-fareast;
mso-hansi-font-family:Calibri;
mso-hansi-theme-font:minor-latin;}
</style>
<![endif]-->
<br />
<div class="MsoNormal">
<span style="mso-ansi-language: EN-IN;">The first thing
business mantra that we are supposed to learn and believe is that “Customer is
the king”. Unfortunately in real life customers are those set of beleaguered individuals
who are forced to wait infinitely for their service and make do with inferior
products. In most cases there are no ways for customers to formally complain,
no individual manager would lose a KRA point because of customer mistreatment
or no CEO would ever have a customer service as a metric in business dashboard. </span></div>
<div class="MsoNormal">
<br /></div>
<div class="MsoNormal">
<span style="mso-ansi-language: EN-IN;">Take the case of HDFC
Home Loans. It is very easy to get a new loan as the sales personnel would
probably visit your office or residence at your convenience. For a query on an
existing loan you would have to wait for around an hour at the firm’s
office.<span style="mso-spacerun: yes;"> </span>The firm’s message seems to be
that new customers are important and existing customers are not. Same is the
case with all mobile service providers. Most of these places also do not have a
formal complain mechanism where a customer gets a tracking number and thus be
able to trace the resolution. </span></div>
<div class="MsoNormal">
<br /></div>
<div class="MsoNormal">
<span style="mso-ansi-language: EN-IN;">It is clearly the CEOs
who are to blame for this. So, Mr. Deepak Parekh is the culprit for the case of
HDFC bank. Sales is a metric that I am sure he would be measuring. Am assuming
that sitting in the head office Mr. Parekh would routinely examine the achievement
of weekly or monthly targets of disbursements. Thus it becomes imperative for
his managers to achieve the numbers. Like the entire household gets interested
in humouring the tantrums of an cranky child, the entire HDFC structure would
probably be fixated on achieving Mr. Parekh’s obsession with sales numbers.</span></div>
<div class="MsoNormal">
<br /></div>
<div class="MsoNormal">
<span style="mso-ansi-language: EN-IN;">Now think, the waiting
time for customers at the HDFC Home Loan branches is not at all measured. Nor
is the satisfaction of customers with the resolution process. Essentially these
are toys that Mr. Parekh would most probably not be interested in playing with.
Hence the entire rank and file of HDFC Home Loans deems it unnecessary to work
on and improve these parameters. Faster and better service at branches would definitely
be possible. But, no manager would ever get a carrot or a stick for performance
on service to existing customers. There is thus a completely lack of action and
existing customers are forced to meekly accept shoddy service. </span></div>
<div class="MsoNormal">
<br /></div>
<div class="MsoNormal">
<span style="mso-ansi-language: EN-IN;">Point one of the blog
is that customer centric behaviour is to a get extent dependent on the metrics
that the Chief Executive uses to control and manage the organisation. </span></div>
<div class="MsoNormal">
<br /></div>
<div class="MsoNormal">
<span style="mso-ansi-language: EN-IN;">Why should Mr. Parekh
even think of improving service to existing customers? For all my criticism,
HDFC is probably a lot better than its competitors and among the more humane
financial businesses. Every delay is a mark of inefficiency in the
organisation. Every customer who comes into the branch with a query is a
pointer to a flaw in the process. All these weakness create costs in terms of
excess manpower requirements, reprocessing, lost documents, etc. These
activities are shrouded within routine work and their horrendously damaging impact
is rarely uncovered. </span></div>
<div class="MsoNormal">
<br /></div>
<div class="MsoNormal">
<span style="mso-ansi-language: EN-IN;">Fast process dictate
that the firm be devoid of all wastes. They force efficient performance. A 20
year old wooden bodied truck can easily be driven on the highway where there
are no minimum speed parameters. That one truck can easily delay the movement
of many other vehicles. Now image that the highway has a minimum speed limit of
60 kmph. Suddenly all vehicles on the highway would be forced to be efficient.
The fuel efficiency would go up and all other operating costs reduce. For those
who feel that high speed could cause more accidents, well, India with among the
lowest average highway speeds has among the highest accident rates. </span></div>
<div class="MsoNormal">
<br /></div>
<div class="MsoNormal">
<span style="mso-ansi-language: EN-IN;">Point two, business
heads should invest him time in monitoring these operational metrics as it will
create an overall much leaner and better organisation. </span></div>
<div class="MsoNormal">
<br /></div>
<div class="MsoNormal">
<span style="mso-ansi-language: EN-IN;">A simple way to achieve
excellence on any parameter would be to continuously measure them. Branch level
operational metrics need to be given importance at the corporate level. HDFC
could start with measuring the average turnaround time for customers. They
could also have a simple metric of how satisfied the customers were with the
interaction. A best Branch Manager award could be instituted on the basis of
performance on these parameters. At a back end level a simple Pareto chart on
the nature of complaints and queries could generate a good understanding on
where the improvements are to be directed. </span></div>
<div class="MsoNormal">
<br /></div>
<div class="MsoNormal">
<span style="mso-ansi-language: EN-IN;">One of the easiest ways
to control crime rate is to not register complains or make the task of
registering complains difficult. Mr. Parekh needs to avoid such behaviour to
keep a tab on the operational issues before they blow out of control. (Even
now, I am pretty certain that HDFC Home Loan has high costs of managing Branches
and the firm is pretty unhappy with their ability to get data from Branches).
There has to be an easy way for customers to communicate with top management.
Not only must the complaining be easier, a better way would be to motivate
customers to give feedback. </span></div>
<div class="MsoNormal">
<br /></div>
<div class="MsoNormal">
<span style="mso-ansi-language: EN-IN;">The last point, CEOs
could well include the Branch level operational metrics in the corporate
dashboard and allow customers to reach out to them. </span></div>
<div class="MsoNormal">
<br /></div>
<div class="MsoNormal">
<span style="mso-ansi-language: EN-IN;"><b>A disclaimer here</b>: I
repeat that HDFC is probably among the better of all private financial
institutions in the country. I am using the name of HDFC and Mr. Parekh as this
idea of this blog came from a poor interaction with their branch. <span style="mso-spacerun: yes;"> </span><span style="mso-spacerun: yes;"> </span><span style="mso-spacerun: yes;"> </span><span style="mso-spacerun: yes;"> </span></span></div>
</div>
Piyush Shahhttp://www.blogger.com/profile/00413083724751291686noreply@blogger.com0tag:blogger.com,1999:blog-4153293235682111113.post-29785172417587166592014-12-06T09:40:00.000+05:302015-01-06T02:17:26.106+05:30Analytics - a tale of two movies<div dir="ltr" style="text-align: left;" trbidi="on">
The first movie is of course 'Moneyball' and the second is 'Trouble with the curve'. Both movies are about recruitment of players in baseball. But both movies take a completely different route for this. This article seeks to point out the extreme difference and I seek views of all of you readers.<br />
<br />
In Moneyball, Billy Beane (Brad Pitt) is a the General Manager of a poor Oakland Athletics team. He develops a statistical model for player selection with a Yale economics graduate. The focus of selection is numbers and not intuition and experience of the scounts. Gus (Clint Eastwood) is an aging scout for Atlanta Braves in Trouble with the Curve. He has a very weak eyesight. He rejects a star prospect based on the sound of the bat hitting the ball. This is in spite of his amazing statistics. In the end Gus is proved right.<br />
<br />
The debate is between using analytics and individual insights for decision making. In the movies both seem to work. In real life a lot of importance is given to the brilliance of an individual manager who seems to be able to make better decisions. Books by Kahneman and Taleb negate the role of intuition and seem to suggest a role for random luck. They support the decision making with numbers view.<br />
<br />
What would you do? How much importance would you give to decisions taken on the basis of analytics versus the gut based decisions of an experienced manager? </div>
Piyush Shahhttp://www.blogger.com/profile/00413083724751291686noreply@blogger.com0tag:blogger.com,1999:blog-4153293235682111113.post-24277835262286198192014-11-29T21:20:00.000+05:302015-01-06T02:15:39.950+05:30The Mumbai dabbawallah myth<div dir="ltr" style="text-align: left;" trbidi="on">
The Mumbai dabbawallahs seem to be a stuff of fantasy. Every supply chain conference and training seems to be incomplete without a mention of their supposedly fantastic performance. Their par six sigma performance is a dream achievement for every supply chain professional. They have seemed to have achieved an iconic level of excellence with 'uneducated' operators and no technology.<br />
<br />
Let me make my position clear. Yes, the dabbawallahs have surely achieved operations excellence. But, they have been able to do so because of some benign business conditions. Most other business are not blessed with the simple and stable pattern existing in the dabbawallahs business. Thus the dabbawallahs are able to excel in Operations without strategy, technology or any type of documented processes.<br />
<br />
The same dabbawallah visits the same houses every day at the same fixed time. He collects the lunch box (dabba) and relays it through the same train to the same office at the exact same address. The dimensions of the products are also more or less the same. This 'same' based operation continues every single day. The only variation is that a customer may not have a lunch to deliver on some days. No business enjoys such luxury of stability.<br />
<br />
The arrival of customers, the time taken to serve the customers and the type of service or products demanded by the customers all vary in 'normal' businesses. Without variation, or with low variation, business is easier to plan. With stable conditions a business can easily avoid all excess inventory, excess resources and product stock outs.<br />
<br />
Let us assume that a beauty salon has exactly one customer coming every ten minutes for exactly the same style of hair treatment and that the treatment takes exactly 30 minutes. In this case the salon can easily employ a staff of 3 people and deliver excellent customer service with very high level of resource utilisation - leading to six sigma operations with high profits. <br />
<br />
An average FMCG firm would have hundreds of SKUs for customers to randomly choose from. The distribution network with multiple independent profit making entities would also have their own buying pattern and behaviour. And, of course, the customers have no compulsion to order in a stable pattern. Thus these businesses are considerably more difficult. The dabbawallahs do the same thing every day. Thus they can easily work from memory. Since businesses have a high number of variables, they need the support of technology to make decisions. <br />
<br />
The dabbalwallahs would be very praiseworthy if they were picking up lunch from different houses every day as per some random pattern and also if the delivery addresses were different. To add to the fun it would be wonderful to have the trains running at varying time tables. What the dabbawallahs have achieved is good but nothing incredible. Their model of operation may be a benchmark for abnormal conditions of stability, but is absolutely useless in normal business conditions. </div>
Piyush Shahhttp://www.blogger.com/profile/00413083724751291686noreply@blogger.com5tag:blogger.com,1999:blog-4153293235682111113.post-74533416103921299332014-08-25T11:36:00.002+05:302015-01-06T02:16:42.176+05:30Stampede - an Operations failure<div dir="ltr" style="text-align: left;" trbidi="on">
Operations failures that cause a loss of lives and are avoidable without much difficulty are very painful. Here lives are at stake and not merely excess stocks or breakdowns or some other performance metrics. Take the lastest stampede in Madhya Pradesh: <a href="http://bit.ly/1p7f9yf">http://bit.ly/1p7f9yf. </a><br />
<br />
As of now 10 people have been reportedly dead.<br />
<br />
The number of temple stampede deaths in India are unprecedented. Take this data:<br />
October 2013: Madhya Pradesh, 115 dead<br />
February 2013: Allahabad, 36 dead<br />
November 2011: Haridwar, 16 dead<br />
January 2011: Sabrimala, 102 dead<br />
March 2010: Kunda, 71 dead<br />
August 2008: Himachal Pradesh, 162 dead <br />
<br />
The list can go on. These are all stampede events with relation to some religious activity. The data has been sourced from wikipedia.<br />
<br />
All places of religious importance have a significantly higher than average rate of human density. This makes the system highly susceptible to failures. An electric fire at home may at most cause a fire and in a worst case death of a few people. In a dense area, an exactly similar event can lead to very grave outcome. A small spark may ignite a chain of events leading to an enormous tragedy. The first point being made here is that tragedies of similar nature in domestic and public locations have a much greater impact in public places.<br />
<br />
At homes, or even in offices the people in the system are more or less constant. All those people generally have a long term stake in the well being of that place. Thus, in a majority of cases, minimum safety standards are ensured. In public places, in spite of the religious connection, the situation is very different. Pilgrims may not always be as careful in ensuring a risk minimizing behaviour. That there are so many other pilgrims may create a condition where no individual takes the onus. <br />
<br />
A third point is about the concept of risk probability. Say an office has 100 people and each of them is capable of causing a catastrophe with a probability of 0.01%. The chance the there will be a catastrophe in the office is still lower than 1%. In a gathering of 10,000 people the chance of a similar tragedy would be more than 60%. Simple statistical calculations point to the fact that the probabilities of tragedies caused by human failure are significantly higher in public places.<br />
<br />
Some religious places have a spurt of pilgrims on some specific days of a year only. This spurt can increase the number of pilgrims by more than a thousand times. With pilgrims the entourage also includes shopkeepers, beggars and similar people. Most places are not designed to handle this sudden increase in the number of people. Thus the system is in a shock and very susceptible to failures. <br />
<br />
There can be more reasons. But, the point remains, that in places with high human density, like the places of worship, the probability and the impact of a tragedy are both very high. It thus makes sense that temple management and the staff of such public places give more than average attention to safety issues. There has to be some sort of paranoia for tragedy prevention.<br />
<br />
One way to create such systems is of course by the rule of law. Temples and other religious places could be forced to have a set of safety based policies and the temple management could be made directly liable for any deviations or failures. The fear of punitive action might force attention on this ignored issue. However, it is common knowledge that forced compliance based system rarely result in intended outcomes. People would always find ways to subvert the rules and thus there would be no major improvement in the behavior. <br />
<br />
I am not clear to the exact nature of the solution. But, I am clear that every place of religious gathering would have to evolve their own ways of safety procedures. Temple management and staff must be educated and thus motivated to create safety policies. A temple would never have a deity that is unclean. Something should be done so that unsafe practices are a similar anathema. Every human is an incarnation of the divine. Thus, ensuring safety of humans is probably as big as any other offering made to the almighty. <br />
<br />
<br /></div>
Piyush Shahhttp://www.blogger.com/profile/00413083724751291686noreply@blogger.com0tag:blogger.com,1999:blog-4153293235682111113.post-24841994530117279062014-08-14T20:26:00.001+05:302014-08-14T20:26:55.943+05:30Imagining the future of Retailing<div dir="ltr" style="text-align: left;" trbidi="on">
Sunil Chopra and Aditya Jain had this article in the Economic times: <a href="http://articles.economictimes.indiatimes.com/2014-08-13/news/52768197_1_online-retailer-blue-nile-zales">http://articles.economictimes.indiatimes.com/2014-08-13/news/52768197_1_online-retailer-blue-nile-zales</a><br />
<br />
They talk about merging the concepts of online and offline retailing with overall benefits for everyone, the consumers, retailers and etailers. As a concept no one can doubt on such win win scenarios. But, as a matter of practice, the article says nothing, and uses completely wrong examples to prove their point.<br />
<br />
There is a comparisons of the costs of an online diamond firm <b>Blue Nile </b>with an offline firm <b>Zales. </b>Of course their cost structures are going to be different. For that matter the cost structures of Toyota and Mercedes Benz would be different, that of Walmart and Macy's would be different. To compare and then try and derive some relationships is perverse academics.<br />
<br />
Online and offline are very different businesses. So an online business is bound to have higher revenue per dollar invested in infrastructure. But, the aim of business is surely not to maximise the revenue per infrastructure dollar. For all our enthusiasm for etailing, Amazon is still losing money.<br />
<br />
In the <b>Costco</b> and <b>Amazon</b> example, Amazon's high transportation costs cannot be used to justify the better performance of Costco. The low variety model of Costco is great, but the profit margins of Wal-Mart are significantly higher than Costco. Here it seems that the authors have been selective in giving their pre-meditated examples so that they can prove a point.<br />
<br />
Online and offline are very different models. As of now, 'touch' is an important part of shopping for many items. Who knows, the evolved customer may not need need to feel. Also, this concept may vary with the category of material. Last mile is surely a major cost for online models, but collaboration with offline for this may not be the only way. Online businesses may create mini warehouses inside cities. Similarly, offline businesses may not be limited to being a demonstration center for products that are ultimately bough online. They will have their own needs and create their own purpose. There also might be some form of collaboration, but not necessarily in the model that Chopra has proposed. <br />
<br />
When I read an article by stalwarts like Chopra I expect articles with more imagination and not such mundane discussion that is part of every run of mill SCM seminar. But I guess the pressure to get something in print seems to be taking a toll of even the best among us. <br />
<br />
<br /></div>
Piyush Shahhttp://www.blogger.com/profile/00413083724751291686noreply@blogger.com0tag:blogger.com,1999:blog-4153293235682111113.post-47368268227777944672014-07-03T20:17:00.002+05:302015-01-06T02:18:30.262+05:30Using Operations to improve customer service<div dir="ltr" style="text-align: left;" trbidi="on">
Way back in 1969, Wickham Skinner had written an article in the Harvard Business Review saying that if designed, manufacturing can be a potent strategic weapon for firms. The key was in making manufacturing decisions, or in other words operations decisions, a part of corporate strategy making. Almost 45 years after the article was written, I was sad to see that a firm like Shoppers Stop had completely ignored basic operations principles in ground level operations. So, while operations parameters surely do not seem to be a part of strategy, they are not even a part of routine operations.<br />
<br />
July 2nd, 2014 was the first day of supposedly a special sale for their First Citizen members of Shoppers Stop. Obviously they must have expected a higher number of customers as the sale proposition mentioned in the advertising was fabulous. As expected, the customers were surely higher and the number increased towards the evening. There were no major problems in the store, the culprit were the checkout counters.<br />
<br />
When the number of customers are expected to be higher, the checkout, which would usually be the constraint, should have been designed to be as fast as possible. The number of customers would be more, and the number of SKUs per customer would also he higher. This one single factor could be a huge factor in realising the sale, as with larger queues, customers could just walk off.<br />
<br />
And this was precisely what was happening. It was not a hoard of customers walking off, but a few surely were. The checkout time at around 5:30 pm was more than 25 minutes and it was getting worse. There were loud, irritating discussions in the queue about this.<br />
<br />
The long checkout time had many reasons:<br />
<ol style="text-align: left;">
<li>The discounts were being manually entered. The problem was not just the entry, but since it was manual, the customers had lots of queries. Many were checking the calculations with the counter staff to confirm the discount amount. It is normal for customers to trust manual calculations lesser than automated ones. </li>
<li>There was a confusion with the fine print of discounts. There was a 5% additional discount for something and as per the new policy the discount would not be given as cash, but would be added as points. Customers were inquiring about the timing of this policy change, the reason and lots of other things that were in no way helping increase the speed of checkout. </li>
<li>Because the discounts were not cash (but points) a few customers were spending a lot of time at the counter debating if it was worth buying the material. Thus they were using up valuable time at the bottleneck process. </li>
<li>The concept of cash back on credit cards is clear. But, many customers did not know about this and again had loads of queries. </li>
<li>A few items had the bar codes missing. Though this was rare, even one item with a missing bar code could take up around 5 - 10 minutes to locate and clear. </li>
<li>The invoice was another classic document. Though it was correct, it was cryptic. You needed a good head in mathematics to match the discounts mentioned to the actual value. Customers would obviously ask questions on this.</li>
</ol>
There were many other minor reasons. Like one customer debated about the VAT. Another did not trust the manually written product code and insisted to see a similar product. One genius customer was calling someone from her mobile phone to decide on the purchase.<br />
<br />
My point is that none of these reasons are radically new. Shoppers Stop has been in this business for around 20 years now. They should have seen through this. Designing for quick check outs is no rocket science. For some reason however businesses routinely ignore the operational issues that arise out of some marketing actions and do not take adequate actions to manage performance. I could hear a lot of talk among sales people in the Shoppers Stop store about their huge targets during the sale period. There was no talk about the queue at the check out counters. Yes, the counter staff were very courteous and patient, almost all the counters were open, but the clear lack of attention to the customer flow through was clear. Come on Shoppers Stop, you can surely do better!!</div>
Piyush Shahhttp://www.blogger.com/profile/00413083724751291686noreply@blogger.com2tag:blogger.com,1999:blog-4153293235682111113.post-36970729336885510362014-01-17T09:37:00.001+05:302014-01-17T09:48:05.935+05:30The other side of large retail in India<div dir="ltr" style="text-align: left;" trbidi="on">
I am amazed by the vociferous opposition in the media to the AAP's proposal to ban FDI in multibrand retailing in Delhi (<a href="http://timesofindia.indiatimes.com/business/india-business/AAPs-decision-on-FDI-in-retail-irresponsible-Commerce-minister/articleshow/28785884.cms">http://timesofindia.indiatimes.com/business/india-business/AAPs-decision-on-FDI-in-retail-irresponsible-Commerce-minister/articleshow/28785884.cms</a>). Newspapers are full of articles of potential losses of billions and also of more than 10 million job loss (<a href="http://timesofindia.indiatimes.com/business/india-business/Blocking-retail-FDI-to-rob-India-of-1-crore-jobs/articleshow/28807283.cms?">http://timesofindia.indiatimes.com/business/india-business/Blocking-retail-FDI-to-rob-India-of-1-crore-jobs/articleshow/28807283.cms?</a>). There is also a lot of talk of how big box retail will improve everything wrong in our country. The opposition may not be completely valid. <br />
<br />
The reason that we have high wastage in agriculture is not the lack of systems. It is in fact the existing infrastructure bottlenecks. The cold chains can't operate profitably because of the lack of reliable electricity supply. The truck speeds are slow because of pathetic road conditions. There are high prices and variable quality in the produce because of the fragmented nature of the farm ownerships. All these are crucial issues which if solved would automatically impact the efficiencies of the retail business. The FDI is for direct retailing business. It will have no impact on the infrastructure. As it is the FDI route for cold chains has been open, without many takers, for quite some time now. <br />
<br />
There is a difference between the type of jobs created by large retail and the small mom and pop stores. With Mom and pop stores there are entrepreneurs who employ one to four low wage helpers. They are served by entrepreneur distributors and entrepreneur vehicle owners (sometimes with bicycles). Thus the job quality and the level of income is higher for a majority of people. In organised retail, the salary structures and job quality are highly skewed. The super rich but small number of top management would have an extremely high salary as compared to an army of shop floor drones who would barely be able to survive. The salaries of Target and Walmart CEOs are more than 500 times the average salary of their employees (<a href="http://money.cnn.com/magazines/fortune/fortune500/2012/ceo-pay-ratios/)">http://money.cnn.com/magazines/fortune/fortune500/2012/ceo-pay-ratios/)</a>. <br />
<br />
Such type of income distribution is never good for any economy. High growth and increase of consumption can only happen in markets where the income structures are relatively level. The type of jobs in multi brand retail are thus not likely to create a favourable impact on the economy. Plus of course there is a possibility that the large retail may cause a job loss in the existing set up.<br />
<br />
Proponents of large retail in India are demanding proof to show that if the existing large stores have caused any job loss as of now. However they avoid questions on the issue of the supposed benefits of large retail. Have large retail in India benefited farmers in any way? Have they led a significant price decrease for customers?<br />
<br />
Efficiency does not always mean low price. Low prices of cigarettes could possibly cause havoc in the economy. Efficiency calculations with a smaller set in considerations are usually wrong and cause something what is called as 'local optimum'. For an alcoholic (or a cigarette smoker) low prices of his vice would be a great proposition. So, if we limit are efficiency calculations to the immediate satisfaction of the person, the prices must be as low as possible. However, if we extend the calculation to his lifetime, higher prices that lead to lower consumption could be better. (Am assuming that consumption is related to price and in cases of alcohol and cigarettes this could be wrong, but the the point is the nature of example and not the exact relationship).<br />
<br />
Thus the low buying prices for the consumer could surely create a short term advantage for her. However in the long term, when the focus of efficiency is shifted from the buying transaction to the entire country, the effects of large retail could be very different. The documentary 'Wal-Mart: The high cost of low price' clearly shows that the public health care benefits that the Wal-Mart employees use are a huge drain on the tax revenue. Thus the low buying prices could be nullified by higher taxes.<br />
<br />
I am of course assuming here that the large retailers are honest citizens. There have been multiple cases of policy manipulation (though lobbying) and corruption against most large retailers. Being super large they have a clout to conduct such activities unscathed, but this could be the issue of another article. <br />
<br />
It is disturbing that the media savy and educated section of the Indian population are not even willing to consider the other side of the debate. News papers and TV media cannot be relied on so much to frame and base our opinions on such important issues. They have their own agendas. My appeal is for people to think on their own, to read alternate views, to go beyond 'popular' opinion and then decide. A society that is led by opinions manufactured by mainstream media can be a very dangerous place to live in. </div>
Piyush Shahhttp://www.blogger.com/profile/00413083724751291686noreply@blogger.com0tag:blogger.com,1999:blog-4153293235682111113.post-45685262609872233332013-06-28T18:34:00.001+05:302013-06-29T13:17:01.830+05:30Nano savings and other such dumb fables<div dir="ltr" style="text-align: left;" trbidi="on">
I am never able to understand some acts of the corporate world and from my limited means of understanding find them to be absolutely stupid. One such news is the grand announcement by Go Air in today's Times of India - <span id="advenueINTEXT" name="advenueINTEXT"><span class="arttle"></span></span><br />
<h1>
GoAir opts for female crew to save fuel</h1>
<a href="http://timesofindia.indiatimes.com/business/india-business/GoAir-opts-for-female-crew-to-save-fuel/articleshow/20805888.cms">http://timesofindia.indiatimes.com/business/india-business/GoAir-opts-for-female-crew-to-save-fuel/articleshow/20805888.cms</a><br />
<br />
Let us look into this issue. They say that every additional kilo costs the Rs. 3 per flight hour. So, for a Mumbai Delhi flight (accounting for the congestion) the cost would be Rs. 6 per trip. A male purser according to the article weights around 20 kg more than a female purser. Assuming a flight has 4 male pursers and replaces them all, the benefit would be Rs. 480 per flight. Assuming a cost of Rs. 4000 per ticket and 180 passengers per flight, the saving would be 0.07% of the revenue. The fuel savings from reducing magazine pages would be even lesser. <br />
<br />
The airline hopes to save Rs. 2.5 crores - 3 crores using this. Assuming the Rs. 480 savings per flight and 360 days in a year, the savings would require Go air to have around `175 flights of 2 hours each everyday. This is almost double their existing flight plan.<br />
<br />
My first objection is that these supposed inefficiencies have been brought into focus because of the rupee depreciation. A Non Value Adding activity is a Non Value Adding activity irrespective of the rupee price. Even if this fairy tale of savings was true, that it was not done earlier is a mark of inefficient management team at Go Air. Why wait for the dollar to be worth Rs. 60 to reduce the potable water tanks or install sharklets? These items would have served the firm in reducing costs irrespective of the rupee dollar exchange rate.<br />
<br />
In terms of cost reduction by reducing assets, it is important to understand the behaviour of costs. For the fight pursers, there is of course the cost of their salary and benefits. But, there is sometimes a much higher cost for their control and management. There are a set of people who create the schedules for these pursers, people who monitor them, people who train and recruit them, etc. In a hypothetical situation that a flight can be managed without the pursers, the cost benefit would be significantly higher than the Rs. 3 per kg per flight hour or the direct salaries of the pursers. This is because the entire set of activities related to the flight pursers could be junked. <br />
<br />
All other cost reduction would be very minor and have a very limited impact on the cost performance of the firm. Given that the complete elimination of the activities would not be possible, the focus must then shift to maximising the impact of the activity. The airlines would save a lot of money from eliminating the inflight magazine. But, if that cannot be done, it might be prudent to increase the pages of the magazines, increase customer satisfaction, and thus increase the load factor.<br />
<br />
All the savings being talked here are what i call nano savings. To expect these nano savings to save the firm would be very amateur. However the business world has always been fond of such hypothetical fables. Even if one customer chooses not to use the service because of such measures the benefit from days of such nano savings would be lost. One social media savy customer who does not get water to drink may cause a huge PR mess for the firm. The point - especially in times of recession, such nano savings are not at all worth the risks they create. Creating higher customer satisfaction and retention should be given much higher importance than such nano savings. </div>
Piyush Shahhttp://www.blogger.com/profile/00413083724751291686noreply@blogger.com1tag:blogger.com,1999:blog-4153293235682111113.post-21153183169592406532013-04-30T03:42:00.000+05:302013-04-30T10:27:13.131+05:30Extraordinary Maruti results? Where art thou common sense?<div dir="ltr" style="text-align: left;" trbidi="on">
Going by the mainstream media reports, Maruti Suzuki seems to have achieved an extraordinary increase of profits in a subdued market. This is as per the quarterly results of March 2013. In spite of a reduction in sales Maruti Suzuki has been reported to have an 80% increase in net profits over the previous year. Business journalists have been going head over heels on this announcement. The success is attributed to better product mix, lower discounts, price hikes, localisation and favourable price of yen. Truly amazing indeed.<br />
<br />
The major and only contributor to the high profits is the reduction in cost of materials. There is a direct 7% reduction in cost of material consumer. The cost of material consumed has fallen from being 21.4% of sales to 18.3% of sales. In the quarter ended March 2012, an average car would have Rs. 2.46 lakh worth of materials. In 2013, in spite of inflation and in spite of a higher proportion of larger cars being sold this cost has come down to Rs 2.39 lakhs per car. Larger vehicles would clearly demand more material and thus this cost should have increased. Surprisingly, the cost choose to come down.<br />
<br />
<br />
Let us first try to understand the imported materials. An average of weekly prices from April 2012 to March 2013 is Rs. 1.52 for one yen. For the previous year in the same period this was Rs. 1.64. This is around a 7% depreciation of the Yen versus the Rupee. Maruti Suzuki imports around 25% of its raw material and of this around 80% is from Japan. Applying this formula to the cost of material consumed, the imports from Japan for quarter of March 2012 would be Rs. 177,482 lakhs. A 7% reduction to this, because of currency depreciation by 7% would create an import bill of Rs. 165,058 lakhs. If we apply the formula (80% of 25% of the total cost of material consumed) to the quarter of March 2013 we get a remarkably similar actual value of Rs. 164,514 lakh. This is less than half a percent off the predicted value. We can safely assume that the yen depreciation has caused a 7% reduction in the import bill. Also, we must note that as the Yen rises this saving is bound to vanish. (In fact the Yen has already appreciated by around 5% in April 2013)<br />
<br />
Since the total material cost reduction was 7% over the two quarter, it means that there has been an equal 7% reduction in the domestic procurement of the year. When prices of metals (steel and aluminium) have remained more or less steady, this 7% reduction seems hard to believe. There is no definite word on how this 7% cost reduction has been achieved without a corresponding reduction in the prices of basic inputs. Maruti Suzuki attributes this to reduction of suppliers and other
techniques which have been standard industry practices for decades. To
attribute the dramatic reduction to such standard techniques seems
highly improbable. And if it was actually due to these techniques, that
Maruti Suzuki avoided doing this for so many years also points a finger
at the ability of the management. <br />
<br />
Obviously the financial reporters have not cared to question the company and have not done their homework. They merely choose to report directly from the company data and for reasons best known to them, create a feeling of exuberance, when no reason exists for the same. The future for Maruti Suzuki seems quite bad to me. The appreciating Yen would hit the imports hard. It would also not be possible to keep the local procurement costs low when the input costs are rising or at best steady. <br />
<br />
The quarter ending June 2012 was a very poor one for Maruti Suzuki. Any decent performance for the quarter ending June 2013 would thus again show a significant increase in profits. However, given the skills of financial engineers within firms, it would not be correct to base company analysis on the data and information supplied by the company itself. Analysts must dig deep, get a thorough understanding of the firm's business, ask relevant questions. Only after this, should any kind of analysis be submitted. My prediction for Maruti Suzuki is that I do not see a significant change in the profits over a year. What do you feel? <br />
<br />
<br /></div>
Piyush Shahhttp://www.blogger.com/profile/00413083724751291686noreply@blogger.com0tag:blogger.com,1999:blog-4153293235682111113.post-40910687932559506642013-04-28T04:24:00.001+05:302013-04-30T04:00:30.651+05:30The issue of low truck speeds in India<div dir="ltr" style="text-align: left;" trbidi="on">
It is very well known that the average speed of trucks in India is only around 20 kmph. There are estimates of a loss of Rs. 60,000 crores because of this. The Global average speed is said to be 60 - 80 kmph. These numbers point to a significant cost reduction opportunity in logistics.<br />
<br />
The toll plazas, checking points and the poor road conditions are the familiar culprits for this ailment of low speed. Firms have been pointing fingers at the government and are painting a picture of them being in a helpless position. However the frequent truck breakdowns, vehicle overloading and poor driving discipline are also major causes of this low speed. These factors can easily be regulated and are in complete control of the firms. <br />
<br />
A two lane road (with one lane for each side) with all vehicles moving in an exact straight line can easily have vehicles travel at a very high inform speed. There are many assumptions in this statement however. The first assumption is that all vehicles are moving at a uniform speed. Because of over loading and also poorly maintained vehicles the speed of a very few vehicles is at around 20 kmph. Especially in cases of two lane highways such vehicles can easily slow down all the other vehicles. Given that only about 14% of the national highways have 4 or more than 4 lanes, this problem affects more than 85% of the Indian National highways. <br />
<br />
In most cases the truck drivers are also least likely to follow the discipline of lanes. For four lane roads (with two lanes for each side), if all the slow vehicles could drive in one lane, the other lane could accommodate fast moving vehicles. Because the truck drivers choose to use the lanes that they deem fit at the spur of the moment, the entire highway network is slowed down.<br />
<br />
Frequent breakdowns are also a major cause in slowing down the vehicle movements. For various reasons we have had poor maintenance management in professional as well as the owner driven vehicles. The high average age of vehicles (debated to be around 12 - 15 years) is also partly to be blamed for the high rate of break downs. Like the issue of a slow moving vehicle mentioned above, a vehicle breakdown would also cause a reduction in speed for all traffic on that route.<br />
<br />
The altruistic answer to this problem would be for all firms to pay attention to vehicle maintenance and driver training and also ensure that all instances of overloading are avoided. Easier said than done. Low margins in business are forcing logistics firms to minimise the immediate expenses on maintenance also to resort to over loading and such tactics. It would seem that any firm that stays 'honest' would obviously not be able to survive. The honesty and survival issue are topics for another blog.<br />
<br />
The main point here is to get the industry to work on the same set of rules that minimise road disruptions and thus lead to high overall speeds. Such industry wide change can only come by forcing the application of the relevant laws in earnest. Instead of lobbying for easier rules, Organised firms should in fact push for strong rules and strict application. Given their expenses, it would be close to impossible for single truck owners to survive without overloading. Such changes would easily throw the unorganised players out of business and allow the organised players to expand their business footprint. That such strict rule implementation could also improve vehicle speed and thus profits would of course be an extra added advantage <br />
<br />
<br />
<br /></div>
Piyush Shahhttp://www.blogger.com/profile/00413083724751291686noreply@blogger.com2tag:blogger.com,1999:blog-4153293235682111113.post-69413049651289242182013-03-23T18:28:00.001+05:302013-06-27T15:33:52.061+05:30Accidents are cheap and safety expensive<div dir="ltr" style="text-align: left;" trbidi="on">
There was a blast in the Tarapur unit of Aarti Drugs Limited at the Tarapur MIDC yesterday. Five young people lost their lives. It seems these young people were screaming with pain for 2 - 3 hours before giving up the struggle. <br />
<br />
<a href="http://timesofindia.indiatimes.com/city/mumbai/5-dead-as-reactor-blast-brings-building-down/articleshow/19137728.cms">http://timesofindia.indiatimes.com/city/mumbai/5-dead-as-reactor-blast-brings-building-down/articleshow/19137728.cms</a><br />
<br />
This is not the first incident of an accident at Aarti Drugs Limited. As recent as October 2012 a major boiler blast in the Dombivali unit of Aarti Industries had led to three people being hospitalised and more than 125 others treated for vomiting, burning eyes and breathing problems. Coming back to Tarapur, this is just one of the many incidents which have been reported from Tarapur MIDC. In December 2012 a reactor blast in Sunrise Process Equipment had led to injury of four people. In September 2011 a hydrogen sulphide gas leakage at the Sequent Scientific plant at Tarapur had caused death of 4 employees.<br />
<br />
Tarapur is not a town secluded from the mainstream. It is less than
100 kms away from Mumbai and has the Atomic Power station. The
industrial town also boasts of organisations like Tarapur Management
Association (TMA) and Tarapur Industries Manufacturers' Association
(TIMA). Such frequent accidents do not show these organisations, factory owners and professionals working in Tarapur in a positive light. <br />
<br />
<br />
Why is it that the accident rate is so high in the Tarapur MIDC and also a few select companies like Aarti Industries? The only possible reason is that it is cheaper to manage accidents and more expensive to prevent them.<br />
<br />
<b>The low probability factor</b> <br />
<br />
Human minds are known to ignore all risks that have a very low probability of occurrence. That is why people avoid wearing helmets and seat belts. Even though the impact of a traffic accident is high, possibly death, the extremely low probability makes the human mind think - it can't happen to me. This is precisely why these firms, their owners and the senior professionals have a lax attitude towards accidents. <br />
<br />
What they fail to understand is that a series of low risk situations would lead to a high risk probability. For example, assume that one process has a probability of failure as 1%. If five such processes are kept in a series, the cumulative probability of failure would be higher than 60%. This is a very simple probability calculation and I do not think that the firm owners are oblivious of this fact. <br />
<br />
Accident prevention is a mindset. It starts with not tolerating even the slightest deviation from the operating norms. Equipments have to be maintained as per some fixed processes. Piping and valves have to be changed routinely. People working in the plants have to be trained continuously for safety procedures. But, all these activities are very expensive. It is probably easier to 'manage' a boiler inspector rather than shut the firm and have a honest boiler inspection. Same could be the case with pollution inspectors who are generally 'considerate'. As it is, it very rare for a business owner to get jailed for such acts of wilful murder. <br />
<br />
<b>Is it Tarapur and Aarti alone?</b><br />
Of course not. The lax attitude towards industrial safety seems universal in India. A major automobile OEM has different safety standards for its own and contract employees. It is rare to see a worker on scaffolding in industries and around new constructions wearing safety belts. There are many offices in Mumbai where adequate fire protection measures are avoided and extinguishers even when present are past the due date.<br />
<br />
May be, the government authorities who are responsible to monitor and the business owners who are responsible to provide have both enough incentives to not do their jobs. At such times it is the professionals and professional organisations (like TMA and TIMA) who are responsible towards highlighting lax procedures and forcing firms to implement safety procedures. Businesses surely have to run to create profits and every action of businesses would be directed towards creating higher returns. However, human life should be above all such calculations. It might be okay to work around excise, transport and all such officials. But, anything that could even have the smallest probability of impact on human life must be non negotiable. <br />
<br />
<b>Disclaimer</b><br />
There of course will be some exceptions. I am sure that some plants in Tarapur and such industrial clusters have a very elaborate safety mechanism. But at the same time, there would possibly be a large number who would consider safety as an unnecessary burden. The article is directed towards these firms. <br />
<br />
I do not have data of accident rates at other locations and I consider even a single occurance of such accidents as an untoleratable act. </div>
Piyush Shahhttp://www.blogger.com/profile/00413083724751291686noreply@blogger.com0tag:blogger.com,1999:blog-4153293235682111113.post-76062539034784405242013-03-20T11:09:00.004+05:302013-03-20T13:16:27.960+05:30Question of Scale in Indian retail<div dir="ltr" style="text-align: left;" trbidi="on">
An issue very close to my heart has brought me back to blogging. It also gives me an opportunity to say - "I had told you this". It was the news in the Economic Times dated 19th March, regarding Office Depot and Staples putting a halt to their India plans.<br />
<br />
<a href="http://economictimes.indiatimes.com/news/news-by-industry/services/retail/office-depot-staples-concede-fight-to-kiranas-pack-up-retail-plans/articleshow/19055125.cms">http://economictimes.indiatimes.com/news/news-by-industry/services/retail/office-depot-staples-concede-fight-to-kiranas-pack-up-retail-plans/articleshow/19055125.cms</a><br />
<br />
It is very clear that the large format retailers have a significant overhead and would need a huge scale to be able to sustain their business model. The MD's salary for Shoppers Stop is around 0.15% of the total revenue. For Walmart, this percent is 0.000045%. Well there are lots of difference between WalMart and Shoppers Stop, but the differences in the proportion mentioned above are too large to be ignored. (WalMart does not reveal the salary expenses and based on newspaper reports the remuneration for Mike Duke has been assumed to be 20 million USD). To put this into perspective roughly one third the gross margins (not profits) of one Shoppers Stop store are expnesed in paying the MD's remuneration. With only 53 stores this is way too much money spent on one person. (The expenses of Shoppers Stop considered for Gross Margin inclde the COGS and the employee costs)<br />
<br />
<br />
According to a report, 90% of Americans have a WalMart within 15 minutes of their house. It is only with this huge scale and the superlative use of technology that WalMart makes the money that it does. For a population around 2 million, Dubai has six super stores of Carrefour. Thus there is one Carrefour for every three hundred thirty three thousand (333,000) people. Mumbai metropolitan area which is about the same size as Dubai and a population of around 20 million has six Big Bazaar stores. This makes it around one Big Bazaar store for 3.3million people.<br />
<br />
Again, it is debatable if Mumbai and Dubai can be compared. The idea here is to indicate the stark difference and the lack of scale among Indian retailers. Overheads like salaries, IT expenses, etc are not very linear to the scale of Operations. Shoppers Stop is not even 0.1% of the size of Walmart in terms of revenue, but the compensation to the Shoppers Stop MD is around 3% of the WalMart CEO compensation.<br />
<br />
Unless these large retailers in India plan for scale, it will be impossible for them to sustain. They have to have planned growth that has a significant multiplier effect to the number of stores. Shoppers Stop has managed 53 stores in 20 years, and in ten years Big Bazaar has managed 214 stores. That they still have such a small footprint does not seem right. Walmart has 3000 stores in the US. Even Toys "R" Us has around 875 stores in the US. Tesco has 471 super stores in UK which is 80% of the size of Maharashtra. In all formats combined Tesco has almost 3000 stores in the UK. France, which is just around twice the size of Maharashtra has 1200 super and hyper markets of Carrefour. Across formats the number of stores is more than 5500. An Asian country like Taiwan, which is around 12% of the size of Maharashtra has 70 Carrefour stores.<br />
<br />
It is clear here that scale is an essential component for survival in organised retail. And, this scale is more about the stores in the same retail format than across formats Given this common knowledge the behaviour of Indian retailers is surprising. McDonald's India has managed to create around 250 restaurants in 15 years and now they plan to double the number in West and South India in the next two years.The message here is that it is okay to have a lower number of outlets now, but without a significant increase in capacity the survival of the organised retail market in India is questionable. <br />
<br />
<br />
<br /></div>
Piyush Shahhttp://www.blogger.com/profile/00413083724751291686noreply@blogger.com1tag:blogger.com,1999:blog-4153293235682111113.post-22641560675062796622011-04-23T10:17:00.000+05:302011-04-23T10:53:26.091+05:30Is it really the Kirana?<!--[if gte mso 9]><xml> <w:worddocument> <w:view>Normal</w:View> <w:zoom>0</w:Zoom> <w:trackmoves/> <w:trackformatting/> <w:punctuationkerning/> <w:validateagainstschemas/> <w:saveifxmlinvalid>false</w:SaveIfXMLInvalid> <w:ignoremixedcontent>false</w:IgnoreMixedContent> <w:alwaysshowplaceholdertext>false</w:AlwaysShowPlaceholderText> <w:donotpromoteqf/> <w:lidthemeother>EN-IN</w:LidThemeOther> <w:lidthemeasian>X-NONE</w:LidThemeAsian> <w:lidthemecomplexscript>X-NONE</w:LidThemeComplexScript> <w:compatibility> <w:breakwrappedtables/> <w:snaptogridincell/> <w:wraptextwithpunct/> <w:useasianbreakrules/> <w:dontgrowautofit/> <w:splitpgbreakandparamark/> <w:dontvertaligncellwithsp/> <w:dontbreakconstrainedforcedtables/> <w:dontvertalignintxbx/> <w:word11kerningpairs/> <w:cachedcolbalance/> </w:Compatibility> <w:browserlevel>MicrosoftInternetExplorer4</w:BrowserLevel> <m:mathpr> <m:mathfont val="Cambria Math"> <m:brkbin val="before"> <m:brkbinsub val="--"> <m:smallfrac val="off"> <m:dispdef/> <m:lmargin val="0"> <m:rmargin val="0"> <m:defjc val="centerGroup"> <m:wrapindent val="1440"> <m:intlim val="subSup"> <m:narylim val="undOvr"> </m:mathPr></w:WordDocument> </xml><![endif]--><!--[if gte mso 9]><xml> <w:latentstyles deflockedstate="false" defunhidewhenused="true" defsemihidden="true" defqformat="false" defpriority="99" latentstylecount="267"> <w:lsdexception locked="false" priority="0" semihidden="false" unhidewhenused="false" qformat="true" name="Normal"> <w:lsdexception locked="false" priority="9" semihidden="false" unhidewhenused="false" qformat="true" name="heading 1"> <w:lsdexception locked="false" priority="9" qformat="true" name="heading 2"> <w:lsdexception locked="false" priority="9" qformat="true" name="heading 3"> <w:lsdexception locked="false" priority="9" qformat="true" name="heading 4"> <w:lsdexception locked="false" priority="9" qformat="true" name="heading 5"> <w:lsdexception locked="false" priority="9" qformat="true" name="heading 6"> <w:lsdexception locked="false" priority="9" qformat="true" name="heading 7"> <w:lsdexception locked="false" priority="9" qformat="true" name="heading 8"> <w:lsdexception locked="false" priority="9" qformat="true" name="heading 9"> <w:lsdexception locked="false" priority="39" name="toc 1"> <w:lsdexception locked="false" priority="39" name="toc 2"> <w:lsdexception locked="false" priority="39" name="toc 3"> <w:lsdexception locked="false" priority="39" name="toc 4"> <w:lsdexception locked="false" priority="39" name="toc 5"> <w:lsdexception locked="false" priority="39" name="toc 6"> <w:lsdexception locked="false" priority="39" name="toc 7"> <w:lsdexception locked="false" priority="39" name="toc 8"> <w:lsdexception locked="false" priority="39" name="toc 9"> <w:lsdexception locked="false" priority="35" qformat="true" name="caption"> <w:lsdexception locked="false" priority="10" semihidden="false" unhidewhenused="false" qformat="true" name="Title"> <w:lsdexception locked="false" priority="1" name="Default Paragraph Font"> <w:lsdexception locked="false" priority="11" semihidden="false" unhidewhenused="false" qformat="true" name="Subtitle"> <w:lsdexception locked="false" priority="22" semihidden="false" unhidewhenused="false" qformat="true" name="Strong"> <w:lsdexception locked="false" priority="20" semihidden="false" unhidewhenused="false" qformat="true" name="Emphasis"> <w:lsdexception locked="false" priority="59" semihidden="false" unhidewhenused="false" name="Table Grid"> <w:lsdexception locked="false" unhidewhenused="false" name="Placeholder Text"> <w:lsdexception locked="false" priority="1" semihidden="false" unhidewhenused="false" qformat="true" name="No Spacing"> <w:lsdexception locked="false" priority="60" semihidden="false" unhidewhenused="false" name="Light Shading"> <w:lsdexception locked="false" priority="61" semihidden="false" unhidewhenused="false" name="Light List"> <w:lsdexception locked="false" priority="62" semihidden="false" unhidewhenused="false" name="Light Grid"> <w:lsdexception locked="false" priority="63" semihidden="false" unhidewhenused="false" name="Medium Shading 1"> <w:lsdexception locked="false" priority="64" semihidden="false" unhidewhenused="false" name="Medium Shading 2"> <w:lsdexception locked="false" priority="65" semihidden="false" unhidewhenused="false" name="Medium List 1"> <w:lsdexception locked="false" priority="66" semihidden="false" unhidewhenused="false" name="Medium List 2"> <w:lsdexception locked="false" priority="67" semihidden="false" unhidewhenused="false" name="Medium Grid 1"> <w:lsdexception locked="false" priority="68" semihidden="false" unhidewhenused="false" name="Medium Grid 2"> <w:lsdexception locked="false" priority="69" semihidden="false" unhidewhenused="false" name="Medium Grid 3"> <w:lsdexception locked="false" priority="70" semihidden="false" unhidewhenused="false" name="Dark List"> <w:lsdexception locked="false" priority="71" semihidden="false" unhidewhenused="false" name="Colorful Shading"> <w:lsdexception locked="false" priority="72" semihidden="false" unhidewhenused="false" name="Colorful List"> <w:lsdexception locked="false" priority="73" semihidden="false" unhidewhenused="false" name="Colorful Grid"> <w:lsdexception locked="false" priority="60" semihidden="false" unhidewhenused="false" name="Light Shading Accent 1"> <w:lsdexception locked="false" priority="61" semihidden="false" unhidewhenused="false" name="Light List Accent 1"> <w:lsdexception locked="false" priority="62" semihidden="false" unhidewhenused="false" name="Light Grid Accent 1"> <w:lsdexception locked="false" priority="63" semihidden="false" unhidewhenused="false" name="Medium Shading 1 Accent 1"> <w:lsdexception locked="false" priority="64" semihidden="false" unhidewhenused="false" name="Medium Shading 2 Accent 1"> <w:lsdexception locked="false" priority="65" semihidden="false" unhidewhenused="false" name="Medium List 1 Accent 1"> <w:lsdexception locked="false" unhidewhenused="false" name="Revision"> <w:lsdexception locked="false" priority="34" semihidden="false" unhidewhenused="false" qformat="true" name="List Paragraph"> <w:lsdexception locked="false" priority="29" semihidden="false" unhidewhenused="false" qformat="true" name="Quote"> <w:lsdexception locked="false" priority="30" semihidden="false" unhidewhenused="false" qformat="true" name="Intense Quote"> <w:lsdexception locked="false" priority="66" semihidden="false" unhidewhenused="false" name="Medium List 2 Accent 1"> <w:lsdexception locked="false" priority="67" semihidden="false" unhidewhenused="false" name="Medium Grid 1 Accent 1"> <w:lsdexception locked="false" priority="68" semihidden="false" unhidewhenused="false" name="Medium Grid 2 Accent 1"> <w:lsdexception locked="false" priority="69" semihidden="false" unhidewhenused="false" name="Medium Grid 3 Accent 1"> <w:lsdexception locked="false" priority="70" semihidden="false" unhidewhenused="false" name="Dark List Accent 1"> <w:lsdexception locked="false" priority="71" semihidden="false" unhidewhenused="false" name="Colorful Shading Accent 1"> <w:lsdexception locked="false" priority="72" semihidden="false" unhidewhenused="false" name="Colorful List Accent 1"> <w:lsdexception locked="false" priority="73" semihidden="false" unhidewhenused="false" name="Colorful Grid Accent 1"> <w:lsdexception locked="false" priority="60" semihidden="false" unhidewhenused="false" name="Light Shading Accent 2"> <w:lsdexception locked="false" priority="61" semihidden="false" unhidewhenused="false" name="Light List Accent 2"> <w:lsdexception locked="false" priority="62" semihidden="false" unhidewhenused="false" name="Light Grid Accent 2"> <w:lsdexception locked="false" priority="63" semihidden="false" unhidewhenused="false" name="Medium Shading 1 Accent 2"> <w:lsdexception locked="false" priority="64" semihidden="false" unhidewhenused="false" name="Medium Shading 2 Accent 2"> <w:lsdexception locked="false" priority="65" semihidden="false" unhidewhenused="false" name="Medium List 1 Accent 2"> <w:lsdexception locked="false" priority="66" semihidden="false" unhidewhenused="false" name="Medium List 2 Accent 2"> <w:lsdexception locked="false" priority="67" semihidden="false" unhidewhenused="false" name="Medium Grid 1 Accent 2"> <w:lsdexception locked="false" priority="68" semihidden="false" unhidewhenused="false" name="Medium Grid 2 Accent 2"> <w:lsdexception locked="false" priority="69" semihidden="false" unhidewhenused="false" name="Medium Grid 3 Accent 2"> <w:lsdexception locked="false" priority="70" semihidden="false" unhidewhenused="false" name="Dark List Accent 2"> <w:lsdexception locked="false" priority="71" semihidden="false" unhidewhenused="false" name="Colorful Shading Accent 2"> <w:lsdexception locked="false" priority="72" semihidden="false" unhidewhenused="false" name="Colorful List Accent 2"> <w:lsdexception locked="false" priority="73" semihidden="false" unhidewhenused="false" name="Colorful Grid Accent 2"> <w:lsdexception locked="false" priority="60" semihidden="false" unhidewhenused="false" name="Light Shading Accent 3"> <w:lsdexception locked="false" priority="61" semihidden="false" unhidewhenused="false" name="Light List Accent 3"> <w:lsdexception locked="false" priority="62" semihidden="false" unhidewhenused="false" name="Light Grid Accent 3"> <w:lsdexception locked="false" priority="63" semihidden="false" unhidewhenused="false" name="Medium Shading 1 Accent 3"> <w:lsdexception locked="false" priority="64" semihidden="false" unhidewhenused="false" name="Medium Shading 2 Accent 3"> <w:lsdexception locked="false" priority="65" semihidden="false" unhidewhenused="false" name="Medium List 1 Accent 3"> <w:lsdexception locked="false" priority="66" semihidden="false" unhidewhenused="false" name="Medium List 2 Accent 3"> <w:lsdexception locked="false" priority="67" semihidden="false" unhidewhenused="false" name="Medium Grid 1 Accent 3"> <w:lsdexception locked="false" priority="68" semihidden="false" unhidewhenused="false" name="Medium Grid 2 Accent 3"> <w:lsdexception locked="false" priority="69" semihidden="false" unhidewhenused="false" name="Medium Grid 3 Accent 3"> <w:lsdexception locked="false" priority="70" semihidden="false" unhidewhenused="false" name="Dark List Accent 3"> <w:lsdexception locked="false" priority="71" semihidden="false" unhidewhenused="false" name="Colorful Shading Accent 3"> <w:lsdexception locked="false" priority="72" semihidden="false" unhidewhenused="false" name="Colorful List Accent 3"> <w:lsdexception locked="false" priority="73" semihidden="false" unhidewhenused="false" name="Colorful Grid Accent 3"> <w:lsdexception locked="false" priority="60" semihidden="false" unhidewhenused="false" name="Light Shading Accent 4"> <w:lsdexception locked="false" priority="61" semihidden="false" unhidewhenused="false" name="Light List Accent 4"> <w:lsdexception locked="false" priority="62" semihidden="false" unhidewhenused="false" name="Light Grid Accent 4"> <w:lsdexception locked="false" priority="63" semihidden="false" unhidewhenused="false" name="Medium Shading 1 Accent 4"> <w:lsdexception locked="false" priority="64" semihidden="false" unhidewhenused="false" name="Medium Shading 2 Accent 4"> <w:lsdexception locked="false" priority="65" semihidden="false" unhidewhenused="false" name="Medium List 1 Accent 4"> <w:lsdexception locked="false" priority="66" semihidden="false" unhidewhenused="false" name="Medium List 2 Accent 4"> <w:lsdexception locked="false" priority="67" semihidden="false" unhidewhenused="false" name="Medium Grid 1 Accent 4"> <w:lsdexception locked="false" priority="68" semihidden="false" unhidewhenused="false" name="Medium Grid 2 Accent 4"> <w:lsdexception locked="false" priority="69" semihidden="false" unhidewhenused="false" name="Medium Grid 3 Accent 4"> <w:lsdexception locked="false" priority="70" semihidden="false" unhidewhenused="false" name="Dark List Accent 4"> <w:lsdexception locked="false" priority="71" semihidden="false" unhidewhenused="false" name="Colorful Shading Accent 4"> <w:lsdexception locked="false" priority="72" semihidden="false" unhidewhenused="false" name="Colorful List Accent 4"> <w:lsdexception locked="false" priority="73" semihidden="false" unhidewhenused="false" name="Colorful Grid Accent 4"> <w:lsdexception locked="false" priority="60" semihidden="false" unhidewhenused="false" name="Light Shading Accent 5"> <w:lsdexception locked="false" priority="61" semihidden="false" unhidewhenused="false" name="Light List Accent 5"> <w:lsdexception locked="false" priority="62" semihidden="false" unhidewhenused="false" name="Light Grid Accent 5"> <w:lsdexception locked="false" priority="63" semihidden="false" unhidewhenused="false" name="Medium Shading 1 Accent 5"> <w:lsdexception locked="false" priority="64" semihidden="false" unhidewhenused="false" name="Medium Shading 2 Accent 5"> <w:lsdexception locked="false" priority="65" semihidden="false" unhidewhenused="false" name="Medium List 1 Accent 5"> <w:lsdexception locked="false" priority="66" semihidden="false" unhidewhenused="false" name="Medium List 2 Accent 5"> <w:lsdexception locked="false" priority="67" semihidden="false" unhidewhenused="false" name="Medium Grid 1 Accent 5"> <w:lsdexception locked="false" priority="68" semihidden="false" unhidewhenused="false" name="Medium Grid 2 Accent 5"> <w:lsdexception locked="false" priority="69" semihidden="false" unhidewhenused="false" name="Medium Grid 3 Accent 5"> <w:lsdexception locked="false" priority="70" semihidden="false" unhidewhenused="false" name="Dark List Accent 5"> <w:lsdexception locked="false" priority="71" semihidden="false" unhidewhenused="false" name="Colorful Shading Accent 5"> <w:lsdexception locked="false" priority="72" semihidden="false" unhidewhenused="false" name="Colorful List Accent 5"> <w:lsdexception locked="false" priority="73" semihidden="false" unhidewhenused="false" name="Colorful Grid Accent 5"> <w:lsdexception locked="false" priority="60" semihidden="false" unhidewhenused="false" name="Light Shading Accent 6"> <w:lsdexception locked="false" priority="61" semihidden="false" unhidewhenused="false" name="Light List Accent 6"> <w:lsdexception locked="false" priority="62" semihidden="false" unhidewhenused="false" name="Light Grid Accent 6"> <w:lsdexception locked="false" priority="63" semihidden="false" unhidewhenused="false" name="Medium Shading 1 Accent 6"> <w:lsdexception locked="false" priority="64" semihidden="false" unhidewhenused="false" name="Medium Shading 2 Accent 6"> <w:lsdexception locked="false" priority="65" semihidden="false" unhidewhenused="false" name="Medium List 1 Accent 6"> <w:lsdexception locked="false" priority="66" semihidden="false" unhidewhenused="false" name="Medium List 2 Accent 6"> <w:lsdexception locked="false" priority="67" semihidden="false" unhidewhenused="false" name="Medium Grid 1 Accent 6"> <w:lsdexception locked="false" priority="68" semihidden="false" unhidewhenused="false" name="Medium Grid 2 Accent 6"> <w:lsdexception locked="false" priority="69" semihidden="false" unhidewhenused="false" name="Medium Grid 3 Accent 6"> <w:lsdexception locked="false" priority="70" semihidden="false" unhidewhenused="false" name="Dark List Accent 6"> <w:lsdexception locked="false" priority="71" semihidden="false" unhidewhenused="false" name="Colorful Shading Accent 6"> <w:lsdexception locked="false" priority="72" semihidden="false" unhidewhenused="false" name="Colorful List Accent 6"> <w:lsdexception locked="false" priority="73" semihidden="false" unhidewhenused="false" name="Colorful Grid Accent 6"> <w:lsdexception locked="false" priority="19" semihidden="false" unhidewhenused="false" qformat="true" name="Subtle Emphasis"> <w:lsdexception locked="false" priority="21" semihidden="false" unhidewhenused="false" qformat="true" name="Intense Emphasis"> <w:lsdexception locked="false" priority="31" semihidden="false" unhidewhenused="false" qformat="true" name="Subtle Reference"> <w:lsdexception locked="false" priority="32" semihidden="false" unhidewhenused="false" qformat="true" name="Intense Reference"> <w:lsdexception locked="false" priority="33" semihidden="false" unhidewhenused="false" qformat="true" name="Book Title"> <w:lsdexception locked="false" priority="37" name="Bibliography"> <w:lsdexception locked="false" priority="39" qformat="true" name="TOC Heading"> </w:LatentStyles> </xml><![endif]--><!--[if gte mso 10]> <style> /* Style Definitions */ table.MsoNormalTable {mso-style-name:"Table Normal"; mso-tstyle-rowband-size:0; mso-tstyle-colband-size:0; mso-style-noshow:yes; mso-style-priority:99; mso-style-qformat:yes; mso-style-parent:""; mso-padding-alt:0cm 5.4pt 0cm 5.4pt; mso-para-margin:0cm; mso-para-margin-bottom:.0001pt; line-height:115%; mso-pagination:widow-orphan; font-size:11.0pt; font-family:"Calibri","sans-serif"; mso-ascii-font-family:Calibri; mso-ascii-theme-font:minor-latin; mso-fareast-font-family:"Times New Roman"; mso-fareast-theme-font:minor-fareast; mso-hansi-font-family:Calibri; mso-hansi-theme-font:minor-latin;} </style> <![endif]--> <p class="MsoNormal">Foreign FDI has been blocked in multi brand retail on the pretext of protecting the small kirana (mom and pop) stores. Sometimes I wonder if this is the real reason. I strongly believe that the restriction is actually to help the large Indian organised retailers. They are the ones to be first affected by the direct entry of Wal-Marts and Tescos of the world in retailing. <span style=""> </span><span style=""> </span></p> <p class="MsoNormal"> </p> <p class="MsoNormal">The typical design of the large foreign retailers is that they have a very strong but investment intensive back end. <span style=""> </span>In order to get good returns from their investments, the stores have to be necessarily large formats. In addition, in one given market there have to be a high number of stores.</p> <p class="MsoNormal"> </p> <p class="MsoNormal">The high lease rates in urban areas of India make it impossible for retailers to have many large stores inside the city. The Wal-Mart model of having the store outside the city would be difficult given the traffic and road infrastructure bottlenecks. In rural areas the scale of operations is generally very low. Indians typically do not have a spend oriented culture like the Americans. So, it would be difficult for a retailer to set up and sustain a large store in a Tier 3 city. <span style=""> </span></p> <p class="MsoNormal"> </p> <p class="MsoNormal">The kirana stores in India have created a very low cost selling model. A pan shop could sustain itself at a monthly profit of around Rs. 5000 only. This number could be much lower in rural areas. This was not the case in the USA. These players can never be threatened by the foreign retailers. The existing so called organised retailers in India would probably have the most to lose. </p> <p class="MsoNormal"> </p> <p class="MsoNormal">Indian organised retailers are still in an experimentation mode. They hastily set up the front end and are now trying to make the back end work. Most have poor systems. Some companies have closed down and most of the rest are not making money. They have tried to copy the IT systems in foreign retail as this can be easily bought. But, the human systems and discipline needed are sadly missing. </p> <p class="MsoNormal"> </p> <p class="MsoNormal">By getting the government of India to form rules banning the foreign retailers, the organised players seem to be creating space for themselves. Foreign companies wanting to enter India would be forced to tie with the existing Indian players.<span style=""> </span>It clearly seems that the rule has been created in the first place to benefit these large Indian retail players. </p> <p class="MsoNormal"> </p> <p class="MsoNormal">Now suddenly there is a talk about relaxing the rule. Nothing has changed for the small kirana owner. But all the large format foreign retailers have already been subdued to partnerships with large Indian firms – this includes Wal-Mart, Tesco, Woolworths, etc. Having done this, and needing more investments, it seems that the large Indian players are now getting the government to allow more direct investment in multi brand retail. </p>Piyush Shahhttp://www.blogger.com/profile/00413083724751291686noreply@blogger.com4tag:blogger.com,1999:blog-4153293235682111113.post-16154829728975221962011-03-12T00:44:00.000+05:302011-03-12T02:10:44.679+05:30of Margins, Profits and CollaborationA manufacturer needs a retail store to sell its products. And, a retail store needs a good agile manufacturer. While this is common knowledge, supply chain practice tends to suggest otherwise. Look at this article in Economic Times:<br /><a href="http://lite.epaper.timesofindia.com/mobile.aspx?article=yes&pageid=1&sectid=edid=&edlabel=ETD&mydateHid=11-03-2011&pubname=Economic+Times+-+Delhi&edname=&articleid=Ar00100&publabel=ET"><br />http://lite.epaper.timesofindia.com/mobile.aspx?article=yes&pageid=1&sectid=edid=&edlabel=ETD&mydateHid=11-03-2011&pubname=Economic+Times+-+Delhi&edname=&articleid=Ar00100&publabel=ET</a><br /><br />The Electronic retailers want the manufacturers to raise the margins by 4% from the current 8 -10%. The manufacturers say that the organised retailers give them a lower throughput than the smaller mom and pop stores and hence they can't increase the margins for modern trade.<br /><br />Gross margin is defined as the buying cost subtracted from the selling price. For all practical purpose, this number is very different from profits. A high margin product can be a net loss product and a super low margin product can be a profitable item.<br /><br />There is the issue of overheads here. Traders who work on volume products on low margins strive to keep overheads low. This way they can ensure good profits even with gross margins of around 2 - 5% only. For some MNCs on the other hand, profits are not even 10% of the gross margins. MNCs have an expensive bureaucracy to support and pay salaries to. Point that I am trying to make is that increasing margins is not the only way to make more profits.<br /><br />A vendor who is unreliable would need lot of followups. This follow up is done by a buyer, and this buyer gets her salary from the buying organisation. So, a low cost vendor might actually be a loss making proposition. A bad quality product or a wrong shipment can surely be returned to a vendor. The vendor may also give a 100% credit note against the returns. But, the time lost in creating this return journey is a cost to the buyer. Similarly, a customer who demands frequent deliveries or who keeps changing order commitments is surely more expensive than a customer who lifts material in higher quantity, has lesser frequency of replenishment and also who give stable orders.<br /><br />Instead of haggling on margins, the electronic manufacturers and the retailers could sit together and analyse these very cost drivers. In a truly modern sense, the modern trade must give up the aggressive postures and come to the negotiating table. Together with the manufacturers, maybe they could work out arrangements of last mile delivery to the consumers homes or offer special after sales service deals.<br /><br />Same for manufacturing companies. An electronics company has significantly greater efforts in selling to smaller stores than large format chain retailers. Pan country buying decisions are probably made from one office for large format retailers. For smaller mom and pop stores, every small store would need a sales executive from the manufacturing firm visiting every week. The savings in sales effort costs would easily more than make up for the lower throughout in the organised retail.<br /><br />The key would be for one party to demonstrate maturity and initiate the process. This is not a zero sum game where one firm has to lose for the other to win. There are numerous cost drivers besides the basic price. There can be a truly win win solution here. It is not a fight of the retailer versus the manufacturer. It is actually a relay race where both players have to work together to capture and satisfy the end customer.Piyush Shahhttp://www.blogger.com/profile/00413083724751291686noreply@blogger.com1tag:blogger.com,1999:blog-4153293235682111113.post-67664568839456896272011-02-03T20:19:00.000+05:302011-02-03T21:40:18.553+05:30Not all customers are equal. Some customers are <span class="blsp-spelling-corrected" id="SPELLING_ERROR_0">extremely</span> expensive to serve. Profit for a company is not the direct price of the product minus the cost. There are many overhead expenses. And these overhead expenses are not shared uniformly over every customer.<br /><br />For a trucking firm, a customer with uniform orders is less expensive to serve than one with sporadic requirements. Few large orders are easier to pick and <span class="blsp-spelling-corrected" id="SPELLING_ERROR_1">dispatch</span> rather than many small orders. For an automobile dealership, a flexible customer who buys the vehicle available in the showroom is more profitable than a customer who takes a long time to decide or one who needs a specific configuration.<br /><br /><span class="blsp-spelling-corrected" id="SPELLING_ERROR_2">In spite</span> of this knowledge in most cases we generally charge the same price to all customers. The differential supply chain cost is rarely considered. While in cases there may be some differential in the price, it is rarely calculated from the cost of actually serving a customer. Marketing segments customers according to channels, need of service, etc. Costing segregates costs of every resource and every product. No function looks at cost of serving customers and then creating differential pricing.<br /><br /><span class="blsp-spelling-error" id="SPELLING_ERROR_3">Meru</span> cabs is a provider for taxi services in <span class="blsp-spelling-error" id="SPELLING_ERROR_4">Mumbai</span>, Delhi and a few other Indian cities. Customers who book cabs by using a call centre are billed a convenience charge of Rs. 50 extra. Customers who book online are spared of this cost. The Rs. 50 is clearly an approximate cost for the additional services the customer uses.<br /><br />Every business needs to think about this idea. By creating differential pricing, businesses can actually direct customers towards specific services. If a customer knows that by placing orders in a certain manner he may get a better rate, the customer might change her behaviour.<br /><br />With a uniform pricing policy, good customers may feel cheated. In spite of being low cost customers they pay as much as other customers. There is a definite danger of such customers changing vendors. In the end, the business will be saddled with high proportion of high cost customers.<br /><br />Differential pricing can be created on the basis of various basis. It can be the number of orders, quantity per order, consistency of business, number of delivery locations, number of product variants asked for, etc. Every business will have its own dynamics and the pricing has to be configured accordingly. The aim is to reward good customers and also to motivate other customers to migrate to better relationship pattern. Of course, the ultimate aim is to make doing business easier and <span class="blsp-spelling-corrected" id="SPELLING_ERROR_5">more</span> profitable.Piyush Shahhttp://www.blogger.com/profile/00413083724751291686noreply@blogger.com6tag:blogger.com,1999:blog-4153293235682111113.post-72393687771044152812010-10-07T12:49:00.000+05:302010-10-07T13:25:10.201+05:30measure outcomes or the means?Reading an article on the HBR site triggered many nascent thoughts. The article argues that some CEO decisions are based on the fact that their compensation is solely linked to the share price of the firm. You can view the article here- <a href="http://hbr.org/2010/06/column-you-are-what-you-measure/ar/1">http://hbr.org/2010/06/column-you-are-what-you-measure/ar/1</a><br /><br />Share price is the outcome of the current and the expected future performance of a firm. This, also only in an ideal situation where there is no price manipulation. The current and the future expected performance comes from a series of decisions. The decisions could be about sources of funds, types of markets, manufacturing facilities, etc. So, the share price is essentially an outcome of a series of decisions.<br /><br />About 50 years back process control ideas rocked the manufacturing industry. Instead of accepting or rejecting a product at the end of manufacturing cycle, effort was focused on ensuring the right set up, right tools, right trained operators, etc. to ensure a correct product. Process control advocated strengthening the process to ensure good products. The focus of measurements were process parameters and not end product features.<br /><br />Till the product reaches the end of the line, it is subjected to significant additional work. In this sense, the finished product is more expensive than the raw material. When significant amount of finished products are found to be defective it causes high rework cost. In some cases managers dilute the quality guidelines to ensure the product is accepted. In still some other cases, sometimes, managers cheat to show that the products are as per norm. This is because with the end of pipe measurement, the cost and stake of having a rejected product is just too high.<br /><br />This is what precisely happens in one number outcome based measurements. CEOs would do almost anything to ensure that this number stays up. Such measurements are the root of many corporate scams. The process shifts from ensuring good processes to ensuring good results. Just like in a shop floor, good results can rarely come from weak processes.<br /><br />The people to blame in most such cases are those who set and reward on the basis of such measures. It is definitely easy to use the stock price for CEO incentive, but it is definitely not a good measure. For one, it is merely a measure of outcome and not about the method or process strength in the organisation. Two, the stock price is a lagging indicator. The price goes down after the performance is reported as poor. In some cases it could be too late to affect an improvement. Three, it is not very difficult to manipulate stock price movement over a short term without a change or performance. This incentives short term behaviour among executives who might want to cash in and move out.<br /><br />This idea is not limited to CEO measurement alone. It can easily be expanded to measure every professional in every area. The key is to measure the means of doing work. Good outcome is a function of good means and vice versa is not necessarily true.Piyush Shahhttp://www.blogger.com/profile/00413083724751291686noreply@blogger.com1tag:blogger.com,1999:blog-4153293235682111113.post-53940390838364048202010-09-05T10:50:00.000+05:302010-09-05T11:10:33.496+05:30Is being Green a luxury?The CEO of a logistics group related to a major retailing company thundered that "green" was not something they could afford. Right now they want to set the supply chain right and think of being green at a later stage. He further added that being green was a branding exercise which his company did not need at this stage.<br /><br />The young CEO created two divisions - right supply chain and green supply chain and his speech clearly indicated that these were different. I guess the CEO is not alone in having these views. To a good extent we academicians and a few consultants are responsible for propagating green as a mechanism of adding an extra cost to be more environment friendly.<br /><br /><a href="http://www.sustainable-supplychain.com/Sustainability_is_Free___The_Case_for_Sustaina.pdf">http://www.sustainable-supplychain.com/Sustainability_is_Free___The_Case_for_Sustaina.pdf</a><br /><br />The article above cites the example of quality movement. Earlier, the basic idea of 'cost' of quality was prevalent. Quality was something that would be checked for after the product was made. It was about inspection and segregating good and bad products. Today, the term is 'cost of poor quality'. Quality is built in at every stage and includes product design, maintenance, and every function in the organisation. The major change was to have quality in every process to have a good quality product.<br /><br />Has this increased the 'cost' for firms? In certain areas, may be yes. But overall, the yields have gone up, the rejections reduced and the customers more satisfied. This shift was not overnight and it happened over a long span of time. Some companies are in fact discovering this fact in the last few years only.<br /><br />It is same with green and sustainability issues. Today, being green means installing a good effluent treatment plant or using expensive technology to emit less carbon. This is very similar to the end of the pipe quality concept followed earlier. With time, I am sure the young CEO and his brethren will realise the difference. Every individual has to work in a way to avoid wastage and every process has to be green. Its just a matter of time for sustainability to be a compulsion to do business.Piyush Shahhttp://www.blogger.com/profile/00413083724751291686noreply@blogger.com1tag:blogger.com,1999:blog-4153293235682111113.post-69636749465790855802010-08-06T09:38:00.001+05:302010-08-06T09:59:10.198+05:30Fun theoryControlling human behaviour is a major task in business. For businesses with presence in multiple countries this is number one priority. There are standard carrot and stick approaches that organisations follow to control behaviour and limit deviation. So, if a person comes late for three days in a month, she loses half a day's salary. A vendor who faults on quality pays a steep fine. Bonuses are awarded to employees who achieve a certain target.<br /><br />Nothing wrong with this approach. I personally have been a big proponent of a structured measurement system for employees. I have advocated that the financial incentives must be structured to incentivise the required behaviour. Reverse is also true. So, if a boss promotes a subordinate who does not question him at all and has a subservient and obedient behaviour, chances are that majority of his subordinates will behave like that. Some companies have incentives for sales professionals not just according to value and volume, but also according to the mix of the products sold. So, at least 20% (or some 'x' %) of the products sold must be those from a certain basket.<br /><br />There is another way. Have a look at this site: <a href="http://www.thefuntheory.com/virals">http://www.thefuntheory.com/virals</a><br /><br />Do have a look especially at the third video, the staircase one.<br /><br />It is a new perspective on controlling behaviour. It s about making it 'fun' to act in a particular manner. Staircases that make a piano sound, a dustbin with sound affects or a bottle recycling machine that doubles as a game are all simple examples. In all cases they managed to achieve the desired affect. People did start using the stairs more. The dustbin did gather more garbage.<br /><br />As business leaders we need to put our thinking caps. Yes, deviant thinking is difficult. But it is necessary. We need to insert some 'fun' into our businesses. Employees should enjoy coming to work. Their should be some pleasure in following the processes. This is a surely a very sound recipe to create path breaking innovations and high performance organisations.<br /><br />Yes, business is serious business. There are billions of Rupees (or Euros) at stake. Does this mean that we need to not smile while working? Maybe people who understand the hows and whys of human behaviour would add more value to this topic. This is precisely the Virgin (Branson) way of doing work and I am sure many of our businesses would do better that way.Piyush Shahhttp://www.blogger.com/profile/00413083724751291686noreply@blogger.com2tag:blogger.com,1999:blog-4153293235682111113.post-58009102956157733042010-07-24T11:11:00.000+05:302010-07-24T12:48:24.833+05:30Bottom of the pyramid employeesIn businesses that are bottom heavy (ignore the pun) like retail, transportation and warehousing, there is usually a significant difference of salary between the top and the bottom. The CEO of a retailing firm could have a salary package that is 200 to 400 times more than the package of a worker who manages the cash register. Such businesses are also characterised by high attrition of low salary scale employees and also have lower training expenses.<br /><br />That lower rung employees will have an attrition of around 15% per month is assumed to be a unchangeable fact. Firms design all their processes around this fact. These businesses try to "<span class="blsp-spelling-error" id="SPELLING_ERROR_0">McDonaldise</span>" their shop floor processes and reduce the dependence of employee knowledge on business. Employees are specialised in a particular task and department. So, a cash counter person will do just that. A person in the toys section will do just that. They set up a tall hierarchy based structure to ensure process compliance. They have a strong recruitment division and also they foster partnerships with recruitment consultants. The salary of the lower rung workers is kept at a minimum and they are trained only if they stay with the company for more than a year. It seems logical. If they are going to leave, it does not seem sensible to waste resources on these employees.<br /><br />A retail firm in Spain has turned this logic on its head. They pay their shop floor level employees higher, and invest significantly more in their training. <span class="blsp-spelling-error" id="SPELLING_ERROR_1">Mercadona</span>, a Spanish retailer, has sales per employee that is 18 times the average for Spain and 50 times higher than the USA. They have an attrition rate of only 3.5% per year. Look at the article here - <a href="http://bit.ly/mercadona">http://bit.ly/mercadona</a><br /><br />Its the vexing issue of questioning the assumptions. Bottom of the pyramid employees are directly in contact with the customers. Customers need intelligent employees. A McDonald's with 15 items only on the menu can standardise every little thing. A super market with 1500 items cannot do this. Many times sale happens because of good selling by the employees. And employees become good at selling only if they are on the job for some time and they feel good about the job that they are doing.<br /><br />Another way to look at it is the cost issue. A store clerk would have a salary or around Rs. 45,000 per year only. A retail CEO can have a salary of around Rs. 20 million. Assuming a store has 400 ground level staff, their total package would still less the package of the single CEO. A 20 % increment amounts to Rs. 750 per employee per month. In an apparels store if one employee sells one extra shirt, this cost is easily recovered. It may not be as simple as this. A salary hike for the shop floor workers would have a domino affect increase for the supervisors and above also. Yet, the impact would not be a difference of life and death for the organisation.<br /><br />If it has been done in Spain, I am sure it can be done in India also. But, someone needs to challenge the basic assumption. Some firm needs to start at recognising that the bottom of the pyramid employees are important. They need to move from lip service to actually facilitating these employees. Sam Walton had said, "I take care of my employees, they in turn take care of my customers". Someone needs to actually put this into practice.Piyush Shahhttp://www.blogger.com/profile/00413083724751291686noreply@blogger.com5tag:blogger.com,1999:blog-4153293235682111113.post-722137949892963032010-07-13T14:37:00.000+05:302010-07-13T16:12:41.497+05:30Growth through capacityA decade back idle capacity was abhorred. It was the duty of the plant manager to ensure that everyone was kept busy and the machines kept churning out material. High utilisation was a rule to balance the high costs of capacity. This also led to large batch sizes and long product runs. This was the time when demand was relatively stable, competition was manageable, retailers had low bargaining power and organisations were sure that sooner or later they would sell everything that they produce.<br /><br />The ripples caused by the recession and the subsequent recovery have ensured a high variance in demand. There is a steady increase in the product variety being offered. Competing players are also coming out with new products and innovative promotions. Retailers are also more adamant on the exact type of products they need. Organised retailers can in fact bully manufacturers and brand owners in product assortment and dispatch frequency. Given this scenario, now the companies are laden with many products that they are not able to sell.<br /><br />In the first scenario, the only cost of inventory was the cost of interest for the amount carried. This was a minor cost. If the cost of working capital was 12% (assumed for simplicity sake) and a product stayed in the factory warehouse for a month, the carrying cost would be only 1%. The product margin more than made up for this cost. Now, with the risk of the product not getting sold at all this inventory holding cost has shot up.<br /><br />Directly reducing inventory would reduce customer service. Especially with a higher variety and fluctuating demand, low inventory would lead to low fill rates. This would lead to high costs of not lost customers. Factories operating at high utilisation would have inflexible and rigid production schedules. A change of customer requirement is usually met through inventory. With low inventories, a change would have to be met with a change of production schedules. Again, with low inventories, A change of production schedule will invariably cause a stock out of some other product B.<br /><br />Demand variability is very difficult to control. So, it seems inevitable that companies learn to live with high inventories and high wastage. They can of course try to squeeze costs from vendors and other service providers. This is precisely what companies are indulging in now. What the companies need to do at this stage is to re look at the way they 'cost' capacity.<br /><br />Look at this article here:<br /><a href="http://www.livemint.com/2010/07/12233422/HUL-aims-to-react-faster-to-ma.html">http://www.livemint.com/2010/07/12233422/HUL-aims-to-react-faster-to-ma.html</a><br />The largest consumer goods company in India, HUL is planning to combat the volatility with capacity expansion. They are planning an increase in the capacity levels and a few places like the Selvas plant has doubled their existing assembly lines.<br /><br />Excess capacity is definitely cost. But here again, like the inventory of the earlier era, machines are sooner or later likely to be used. Having spare capacity means that the manufacturer is more flexible. They can be more responsive to the existing market demand and give the customers exactly what they want. Making consumer goods is not like making rockets. The lead time to make a product is a few hours provided the capacity exists. Thus firms can drastically cut inventories if they have spare capacity.<br /><br />Yes, the machines would be idle and the operators would also not have anything to do once in a while. But, overall the total costs would reduce and the fill rates would go up. Cheers to HUL for this change. Now with the leader showing the way, may be the others will follow.Piyush Shahhttp://www.blogger.com/profile/00413083724751291686noreply@blogger.com2tag:blogger.com,1999:blog-4153293235682111113.post-13294360276254966342010-07-05T01:10:00.000+05:302010-07-05T02:44:46.474+05:30Profits from expansionThe hypermarket chain <span class="blsp-spelling-error" id="SPELLING_ERROR_0">Hypercity</span> has 7 stores in India currently - three in and around <span class="blsp-spelling-error" id="SPELLING_ERROR_1">Mumbai</span> and 4 in other cities. Shoppers Stop had a 19% equity in the store which they have increased to 51%. Now they want to open eight new stores by next year and expect to triple their revenues to 1000 <span class="blsp-spelling-error" id="SPELLING_ERROR_2">crores</span> (from current 330 <span class="blsp-spelling-error" id="SPELLING_ERROR_3">crores</span>) by FY2012. The statement from the group says that this will lead the groups to break even in the FY2012. The detailed article is here:<br /><a href="http://retail-guru.com/shoppers-stop-eyes-around-rs-1000-crore-revenues-from-hypercity/">http://retail-guru.com/shoppers-stop-eyes-around-rs-1000-crore-revenues-from-hypercity/</a><br /><br />Let me bet....I do not see <span class="blsp-spelling-error" id="SPELLING_ERROR_4">Hypercity</span> breaking even in FY2012. Hypercity will of course have new and creative reasons in 2012. Unless something radical happens, I am sure that I will win my bet. Let me explain.<br /><br />Expansion helps improve the profits if it leads to better utilisation of existing resources. If a retailer has 5 stores in a city, starting say 3 more could help. The supply chain infrastructure would be more or less the same. The same overheads (city office infrastructure and professionals, buying team, etc) that earlier took care of 5 shops would now take care of 8 shops. The only new cost in opening the 3 stores would be the cost of employees in the store. So, there is a good chance of increasing the net profit for the retailer.<br /><br />For <span class="blsp-spelling-error" id="SPELLING_ERROR_5">Hypercity</span>, each location is a large store and has a baggage of huge overhead attached to it. Every individual <span class="blsp-spelling-error" id="SPELLING_ERROR_6">Hypercity</span> store would have to replicate all these expenses. There would be very little central overhead that would be shared. As mentioned in the article, 60% of the store's sales are foods. Since the food preference is regional in nature the merchandising and the buying team would have to be different for every region, or for that matter every store. Since every store would be in a different city, new supply chain infrastructure would have to be set up.<br />So, assuming that they follow the same policy, it is difficult to imagine <span class="blsp-spelling-error" id="SPELLING_ERROR_7">Hypercity</span> making profits with expansion.<br /><br />McDonald's in India had a model where they limited themselves to around 30 stores in a few pockets for 4 years. They made all the stores profitable, mapped the necessary processes, created the support infrastructure and then had a full blast expansion. McDonald's was a proven global brand. They had most of the processes available and could have implemented the same in India. Their India people were smart and they instead expanded slowly.<br /><br />At Rs. 330 <span class="blsp-spelling-error" id="SPELLING_ERROR_8">crores</span> from 7 stores, the current revenue comes to an average of Rs. 45 <span class="blsp-spelling-error" id="SPELLING_ERROR_9">crores</span> per store. In 2012, when the news release expects <span class="blsp-spelling-error" id="SPELLING_ERROR_10">Hypercity</span> to break even, the 8 new stores would only be one year old. It would be reasonable (or optimistic) to assume that each of these 7 new stores would also have a revenue of around Rs. 45 <span class="blsp-spelling-error" id="SPELLING_ERROR_11">crores</span> in 2012. This totals up to Rs. 360 <span class="blsp-spelling-error" id="SPELLING_ERROR_12">crores</span>. The existing 7 stores would have to get Rs. 640 <span class="blsp-spelling-error" id="SPELLING_ERROR_13">crores</span> and this comes to more than Rs. 90 <span class="blsp-spelling-error" id="SPELLING_ERROR_14">crores</span> per store. What we are talking of here is a 100% jump in revenue in just two years. Surprisingly the news release mentions that the strategy would be the same. I am not sure if it is wise to expect the same strategy to yield such amazing hyper growth for <span class="blsp-spelling-error" id="SPELLING_ERROR_15">Hypercity</span>.<br /><br />Expansions help improve profits if the basic model is correct. Else the expansion could merely be postponement of the inevitable failure. To use expansion as a way out of losses is a tried and tested methodology and it has almost always led to failure. Somehow business professionals have a scant respect for history and they forget that history repeats itself.Piyush Shahhttp://www.blogger.com/profile/00413083724751291686noreply@blogger.com3tag:blogger.com,1999:blog-4153293235682111113.post-18409179842167408102010-06-17T09:09:00.000+05:302010-06-17T09:50:50.349+05:30Vendor Capacity PlanningBoeing has decided to its capacity to produce the super successful Boeing 737 from the current 34 planes a month to 35 planes a month in early 2012. Read the article here:<br /><a href="http://www.dailymarkets.com/stocks/2010/06/16/boeing-boosts-737-production/">http://www.dailymarkets.com/stocks/2010/06/16/boeing-boosts-737-production/</a><br /><br />It may seem surprising that a 3% hike in capacity (from 34 to 35 planes per month) should take more and 18 months. Unfortunately this scenario exists in many industries. Even though significant opportunities exist, firms are unable to ramp up capacity fast enough to take advantage. In some cases, the demand piles on in the form of backlog. However, in many cases customers gravitate towards less deserving competitors and the demand is lost. <br /><br />The issue in most cases is that firms ignore to plan the capacities of their vendors. Making a product will need all the items as per the Bill of Materials (BOM). A constraint in even one single BOM component will limit the expansions. The problem here could be as small as water availability at a key vendor or in some cases the disposition of the vendor to expand the business. <br /><br />A key component in supply chain planning would be to monitor and keep track of the capacity on the supply side. It is necessary for firms to ensure that all the necessary vendors build enough capacity and are able to ensure the necessary supply. The OEM needs to take the lead time to build capacity at its vendors in consideration. Only then can the real increase in output happen.Piyush Shahhttp://www.blogger.com/profile/00413083724751291686noreply@blogger.com0tag:blogger.com,1999:blog-4153293235682111113.post-69970934828106185082010-05-15T19:56:00.000+05:302010-05-17T21:28:24.404+05:30Maintenance budgetingI am a frequent traveler in the new AC buses started by BEST (Mumbai public transportation). They are very comfortable buses and they run more or less on time. Generally there is a place to sit and it goes significantly faster than the other buses. Lastly given the record breaking heat and the pollution around, the bus presents a great option.<br /><br />Early last month I saw that the digital watch in one bus was not working. Next, in a few buses I saw the radio/ speaker system not functioning. Yesterday I saw a bus with the LED display that shows the destination in a faulty state. All this is really surprising since the buses are less than 6 months old.<br /><br />Somewhere 'maintenance planning' is not a part of the budget and operations in many organisations. Assets wear out. In any business that is dominated by such assets, it is imperative that some resources are committed to ensure a certain minimum level of performance. Maintenance is a big expense these days and companies have to ensure that this is budgeted in the capital budgeting plans and the reasonable costs taken care of. Besides the cost, there has to be a seperate process to ensure that defective and worn out parts are replaced regularly.<br /><br />Maintenance is not rocket science. Most equipment have a specific life cycle and need replacement in a specific time period. Organisations have to factor this and create individual or group replacement policies for components. The overall aim would be to ensure that the asset gives the desired performance for the longest possible time period.Piyush Shahhttp://www.blogger.com/profile/00413083724751291686noreply@blogger.com3