It appears a bit extreme now – but it was very common at time when I was a navigating cadet.
As a 17 year old cadet learning to navigate a large 28,600 metric tonnes vessel, one of first things I was asked to do was to make sure that I learnt the entire ‘International Rules of Road’ by heart. Almost all the cadets had to do this. The intention seemed to be that you must have no doubt in times of panic. At a time of impending collision there would be no room to think or maneuver – and the reaction must be automatic.
The Chief Mate (mentor for the cadets) would ask us any rule at any time, and expect the cadets to be able to recite these line, chapter and verse.
Here is short video of the perils of sea – mainly to put thing in the right context.
Most good yachtsmen and navigators would have these rules stuck in their memories no matter how much time has passed since they did their MoT (navigators’ license).
For me, after more than 30 years they are still alive, and many of them serve as good guidelines for practical decision making in strategy.
Here is an example: RULE 7 (COLREGS 72)
|NAVIGATION RULE||STRATEGY GUIDANCE|
|(a) Every vessel shall use all available means appropriate to the prevailing circumstances and conditions to determine if risk of collision exists. If there is any doubt such risk shall be deemed to exist.||Every company should use all available means appropriate to the prevailing market conditions and competitive landscape to determine if significant risk to profitability exists. If there is any doubt such risk should be deemed to exist.|
|(b) Proper use shall be made of radar equipment if fitted and operational, including long-range scanning to obtain early warning of risk of collision and radar plotting or equivalent systematic observation of detected objects.||Judicious use should be made of diagnostic tools and methodologies that are available and appropriate, including long-range forecasting to obtain early warning of risks of significant profit drops, and benchmarking or equivalent systematic observation of risks identified.|
|(c) Assumptions shall not be made on the basis of scanty information, especially scanty radar information.||Assumptions shall not be made on the basis of scanty information, especially poor diagnostic information.|
|(d) In determining if risk of collision exists the following considerations shall be among those taken into account: (i) such risk shall be deemed to exist if the compass bearing of an approaching vessel does not appreciably change; (ii) such risk may sometimes exist even when an appreciable bearing change is evident, particularly when approaching a very large vessel or a tow or when approaching a vessel at close range||In determining if risk of significant profit drop exists the following considerations shall be among those taken into account: (i) such risk shall be deemed to exist if the performance of an appropriate benchmark does not appreciably change; (ii) such risk may sometimes exist even when an appreciable performance change is evident, particularly when approaching a turbulent market condition, or when benchmark itself has become irrelevant.|
In case you are wondering why I am focusing on the second biggest mistake rather than the biggest one – it is because I have already written a blog post on that topic last week. Here is the link to it.
But the second biggest mistake is even more common and well known.
Yet it is so common that it worth spending half an hour writing a blog post about it. Even if 10 business transformations are put back on track after reading this blogpost – it would have done its job. After all each derailed business transformation is a huge waste of human effort and ingenuity.
So, what are the cliches that are used to describe this second mistake. I am sure everyone is familiar with these:
Putting the Horse Before the Cart.
Confusing the Cause with Effect.
Post Hoc Fallacy
A theoretical discussion of human fallacies is out of scope of this blogpost. You can read more about these here.
In many cases these IT upgrades take a life of their own and business objectives of the transformation projects start taking a back seat to these technological considerations.
In my book UNCHAIN YOUR CORPORATIONS I have given more than 20 examples of this phenomenon, in various contexts. Below I quote from the book:
Modern supply chains collect information at each node of the network. This rich data is methodically analyzed to optimize demand, supply, inventory, costs and service levels to create the best profit results. Not many people know this art – while there might be many pretenders.
The next component in business transformations is the informational part of the business network, which is strongly bounded by its IT systems. A word of caution, though, IT should always be viewed as a means to an end rather than the end in itself. In other words, systems are implemented to facilitate information exchange that is conducive to business transformation.
In the project we were working on, the challenge was indeed, moving the system from the regional to the global structure. Apart from having islands of data to consolidate, the company also found themselves dissatisfied with a system that met only 70% of its needs.
Even though you may be tempted by flexibility as it offers more room for maneuver in the future, every additional bit of flexibility breeds corresponding complexity.
To get a more realistic picture of the complexity, type “supply chain software” into Google and you will get more than 75 million results. How do you know which one is the right one? Though many of them will pretend that they can, there is not a single piece of software that can do everything that you require from a supply chain software solution.
Plethora of tools are available – each with its own peculiarities and limitations. Old ERP type systems can lead your operations into a big hole from which it will take years to emerge. Furthermore, each tool is most suitable for certain situations, and unsuitable for other situations. You need the ability get the right tools – just the ones that suit your situation – and combine them well.
I have dedicated a whole chapter to IT systems in my book The 5-Star Business Network and here I would like to focus only on a few key things. To get this component right, you also need to see things through the eyes of the system provider. It is a delicate dance between rigid functionality and flexible business outcome.
How do you choose the right software for, say forecasting, from among more than 2,500 such systems? How do you link this system to the other systems it needs to work closely with – say inventory management software? How do you pick the right inventory management software from among more than 2,000 systems that claim to do more or less the same thing? Do you go for a single solution that is about 50%-60% right, at best – or do you go for a best-of-breed solution that can cover more than 85% of your need, if you do it properly? All these are very complex questions to answer.
Figure below, taken from my book The 5-Star Business Network, illustrates just some of the ways a business can falter along their road to using IT for business transformation.
FIGURE: PROBLEMS WITH USING INFORMATION TECHNOLOGY FOR BUSINESS TRANSFORMATIONS
Then you configure the pieces to form an integrated system, that meets your rapidly changing needs in a business transformation.
We need to revisit the strategic component, to examine the level of disconnect between the corporate strategy and the IT capabilities and carefully find tools that fill that gap.
In the past, it might have been the case that corporate strategies were made up in the air, then supply chain strategies were formed by people down in the warehouses based on their own assumptions about what the business wanted to achieve, and the IT staff work in their own cubicles to provide systems based on poorly articulated needs.
If the above example of three isolated types of strategies resonates with your personal experience, you would also concur that despite numerous vocal calls for enterprise-wide collaboration, people still continue to work in silos. This is equal to saying many companies are still staying at Supply Chain 0.0 while others are moving towards 1.0 or 2.0 or, even mastering Supply Chain 3.0.
Figure – The process and service component
As you can see from Figure above, which shows typical processes in a supply chain 1.0, there are four levels that need to be weaved into a cohesive whole. Typically, there can be missing links between processes – vertically, or even horizontally.
Even worse, for instance, a delivery scheduler may not know how his work output related to that of his next cubicle neighbor – the customer forecast expert.
During a transformation, processes and services may get streamlined, re-aligned or even created from scratch to accommodate change. That is why it is pivotal to keep in mind how they all fit together by devising a visual presentation such as the pyramid diagram above.
I was having a conversation with one of the senior executives responsible for business transformation in a large-sized industrial company with operations and plants across the developed world. This particular person had come from one of the top tier global consulting houses and obviously was very well versed in the hypothesis-driven problem-solving approach, which both he and I had learned in our formative years in top tier consulting houses. He was adamant that this approach would be enough to carry out a large-scale supply chain transformation in his business. Hence, he was very skeptical about the supply chain methodologies that we were espousing.
In his mind, he could derive the same results from the first principles using his hypothesis-driven approach. And I was patiently explaining to him the difference between going back to the first principles to create a new approach, and deploying a tried and tested approach for supply chain transformations which had the benefit of having adapted the same hypothesis-driven approach.
So I gave him an example of the early stage motorcars where people were still using solid rubber tires and a number of fittings which were a carry-over from the days of horse buggies. Of course, if he had the luxury of time and budget to make all the mistakes there were, he could probably recreate a modern-day motorcar, going through all the stages of evolution. He was smarter than most of the population, so he could perhaps complete the task in 20% of the time that it took for the actual evolution to take place and perhaps, at 20% of the budget. Yet, if a modern-day motorcar was already developed, wouldn’t he be better off testing if it suited his purpose and adapting it for his use?
Obviously, on one hand, you can become too rigid and attached to the process itself. On the other hand, robust processes, based on experience from a number of similar business transformations in the past, are far more useful than some skeptics envisage.
After all, who would you like to be your guide for a climb – a person who can theoretically show you a path through a map of a mountain, or a person who has actually traversed that particular journey several times before, and knows all the pitfalls along the road?
Now let us talk about the “service” bit in the process and service component.
One of the hangovers from the last century industrial organizations which never ceases to surprise me in a modern-day organization, is the importance attached to a product in comparison to the importance attached to service by the company.
What do I mean by that?
The service might be just fitting the product, or providing the right information about the product, or helping customers choose the right product for their needs.
To give you an example, if you are a customer of a motorcar company like Ford or General Motors and you are looking for a particular part, you will be amazed to know how many different possibilities there are of fitting the right part for the purpose. You will then need to discuss your particular needs with someone called a Parts Interpreter in order to pick a suitable part for your motorcar. It is a very specialized job and invaluable service provided by the car industry to its customers. It is the service that makes the cost of parts more expensive than the base cost of manufacturing and selling that part.
In almost every project we have done, when we calculated the overall cost-to-serve, it is very clear that the product component of the cost was supplemented by the service component of the cost, which was quite substantial to start with, and getting higher progressively.
In other words, the overall cost-to-serve is made up of cost of product plus cost of service, each a fairly significant component of the overall cost-to-serve. Then why do companies keep ignoring the cost of service or treat it as a minor hassle, rather than manage it as an overall part of the full cost equation?
Hence, service is merely an after-thought, even though the cost of service might, in many cases, be higher than the cost of product.
That is the reason why a cost-to-serve analysis is an eye-opener for senior management teams or for boards of directors, when an overall cost breakdown is laid out, clearly showing that cost of product is far less than the cost of service. Suddenly, the entire orientation of the management changes towards managing the service component much more efficiently and effectively than they have ever done in the past.
We have noticed that tendency in airlines, in the automotive industry, the mining industry and in many other industries.
Similar to the informational component, companies are increasingly discovering their ability to cherry-pick service providers that deal with different service modules. Before this can happen, service components must be broken up into geographical, asset based and activity based components to discover and engage best service provider for each module. This is known as modularization.
Then, service modules are homogenized in order to create and manage parallel interactions with several service providers at same time. The cherry-picking or commoditization of service modules enables you to configure a best-of-breed customized business-to-business network that would be impossible to emulate for your competitors, and provide flexibility, cost advantage and risk mitigation to your company.
Sure you will need the right tools, and deploy them rightly – that is important. But much more important is why you are deploying them, and are you getting the right results from them?
Nobody sets out thinking, I have no purpose for bringing this technology into our company, but I will do this anyway (well a few rare twisted souls might do it – totally driven by a side deal that meets their self-interest). Yet, post-hoc analysis reveals so many IT projects fail due to a variety a reason that one has to ask – what happened to the original purpose. Where did not lose track of that? I have written in detail earlier about why IT projects fail. For example in my book THE 5-STAR BUSINESS NETWORK, I wrote the following:
Many large scale information technology deployments derail!
Data, anecdotes and case histories abound on the misapplication of information technologies for supply networks. Not too many years ago, a very large corporation operating worldwide, made news with the downgrading of their earnings expectations due to supply chain system’s implementation setbacks. The expectation was that the new system would reduce the new production cycle from 1 month to 1 week. Furthermore, it would better match the demand and supply of its products to place the correct products in the right locations and quantities, all at the right time – a very lofty goal. The company spent an enormous amount of money, exceeding US $400 million in order to achieve its aim. However, the software system ‘never worked right’. It caused the factories to crack out too many unpopular products and not enough of the trendier ones in high demand. While making the earning downgrade, the CEO asked the rhetorical question, ‘is this what we get for $400 million?’
The market analysts were not surprised. One respected market analyst [AMR] commented, ‘ fiascos like this occur all the time but are usually kept quiet unless they seriously hurt the bottom line.’ Another respected market analyst commented that while the CEO made it sound like it was a surprise for him, if he did not have checkpoints for the projects, he does not have control over his company. A third analyst commented that companies are confused by escalating market hype and too often underestimate the complexity and risks. Another [Forrester Research] commented ‘when the software projects go bad companies are more likely going to scurry up and cover it up because they fear that they are the only ones having trouble. But far from it; our conversation and research reveals this company was not unique or the only one having this kind of trouble‘.
Despite their lofty goals, many of the large information technology deployment projects derail. It takes time for the word to filter out because, in most cases, the executives involved in the process are far too embarrassed to talk about what happened. They do mutter among themselves; after several similar instances the mutterings become more vocal and a trend emerges where a number of people start talking about the shortcomings of the system itself or the implementation process or of the time taken for implementation. Because the cost of this failure is so high – greater than $400 Million in the above case – it is instructive to understand the real root causes of this failure. I am not looking to apportion the fault or apportion the blame in this chapter.
30 years of accumulated wisdom is now available
However, it will be a fallacy not to learn from all the accumulated wisdom of the past. After all, those who do not learn from history are condemned to repeat the same mistakes again and again. This will enable us to understand the steps we can take from the very beginning to increase your probability of success. This will also allow you to confidently move forward with Business Network Information Technology system selection, integration and use in order to achieve the results that you set out to achieve.
The supply networks information technology projects have become bigger and bigger over the last 15 years. It is quite customary now to start with an expectation of spending around $ 50 million but end up spending in excess of $200 million on systems renewal projects.
Rough estimates indicate that, even today, about one third of these projects are cancelled without delivering any benefits, after spending more than $100 million. Another third of the projects are not cancelled, but fail to deliver significant parts of what they set out to achieve. Only one third of the projects achieve most of their strategic goals, but many still incur several budget upgrades and time overruns.
Why is this pattern of failure repeated over and over again?
In general, the original purpose is lost somewhere between the scope creep #2 and #3, and thereafter technology becomes an end in itself, and not a means to achieve a business outcome. There is an admirable drive to digitization underway – but does it suit the purpose of all businesses in all locations? You can find comments on Technology Without Purpose is Like a Missile Without a Guidance System on LinkedIn.
It’s no surprise that customers hate companies with too much internal focus. As organizations free up their inter-departmental planning from rigidities, the communications start to bloom. Efficiency improves considerable and everybody starts running together, faster. However, a higher set of problems emerge due to lack of external focus – on suppliers, customers, and end-consumers. Many times everybody inside the organization is running together, faster, but in the wrong direction.
New challenges need new responses. The common organizational model looks like the generic drainpipe structure, meeting the mammalian need for an ordered hierarchy and flow of power within a business. Most companies have evolved in the last 2 decades and their functioning has become almost entirely customer centric. Their customers’ priorities drive most of the business workings. The traditional drainpipe model frequently stifles customer responsiveness and innovation, therefore there is a clear need for a new standardized customer centric model of business. The new customer centric model starts with customers at the apex of the organization. It is the customers’ needs which the organization is trying to serve, so directly aligned with the customers is the sales team. The function of the sales team is to have an https://www.viagrapascherfr.com/le-viagra-vente-libre/ intimate understanding of the customers’ needs. Only then can an organization create successful products. An organization can outsource almost everything else it does, but it can never outsource its sales. Two other key functions which are equally important and support the sales team is marketing and research & development. Between these three we form the top tier of the modern organization’s structure.
There are a number of factors that have ensured that business have been struggling in the current economic environment. Technology has made many business models defunct, incomes and profits are falling due to cost cutting and price conscious consumers and off-shoring has hollowed out entire industries. Given this reality, business networks are essential to struggling companies to help turn their fortunes around. Here are five ways you can use your business network to turn your company around – the five cornerstones of a Five Star Business Network.
When I engaged Vivek’s services for supply chain transformation in one of the companies I was heading, we expected the careful and methodical approach that he was famous for. Outsourcing was only one of the components of our supply chain, and at the time we did not think it was even a particularly important one.
I was already convinced that critical business turnaround can only be achieved by taking an end-to-end supply chain approach to this transformation. I was pleased to note that the original target set for 3 years was surpassed by almost 70% in just 18 months – providing graphic evidence of the full power of these ideas in action.
On the information technology side, the supply chain requirements were never fully translated into a usable system resource base. I will not go into the reasons in this blog. SAP has since invested in Ariba – a procurement management software. unfortunately, the confusion between procurement and supply chain management continues to persist. A number of journalists, and even business professionals use the terms interchangeably. On the IT side the supply chain workflow still remains inadequately supported. A few newer companies are starting to crop up, yet a great majority of them (to some degree) seem to be falling into the same traps that their predecessors fell into above. In my next blog I will cover this in more detail. Meanwhile, share your experience with SAP, Ariba or other so called supply chain transaction processing software systems. Not only will you add to the accumulated IP on supply chain system, but also you may earn a copy of the book quoted above. You can find comments on My Experience With Freight Cost Reduction Using Supply Chain Software on LinkedIn.
The person who does less than s/he is paid for, will soon be paid less that s/he does.
So, what do you get paid for? And, are you getting paid for what you are worth? What skills do you bring to the job? What attitude to you bring? Are you being rewarded for the two? What can you do? Use the figure below as a guideline: You can find comments on LinkedIn.