Summary: Weak components determine the lifecycle of a product. Similarly, in the business, weak points within the IT systems and processes determine failure. In addition 'inbuilt obsolescence' reduces shelf-life. This article looks into the design decisions for identifying those points and options to manage them.
PART 1 - This is part 1 of the 2 part series on this topicTwo months ago, my Surface Pro's charger stopped working. upon closer inspection, it is broken at the point the thin wire connects to the main processing adapter unit.
Here is the photo.
The problem is at a juncture where the soft wire meets a hard component. The solution is to include a sleeve which gradually transitions from the soft component to the hard component. This provides a gradual shift and protects the wire. However, in this case, the key design principles were not followed. In this case, the sleeve is made up of hard material which does not provide the required protection.
Here is a charger from another manufacturer of using a sleeve to provide a gradual transition from hard to the soft surface.
BTW - Apple's original adapters and cables for iPad also broken at the same place in the past due to a similar design flaw.
Whilst the entire adapter could be used for a couple of years more, it needs replacement due to one small breakdown.
How many times you felt that you could use the smartphone longer if its battery lasted through the day? Even if everything else in the smartphone is perfectly alright, you have to replace it with the new due to its battery.
How many times have you used products which are rendered useless due to one small component breakdown?
In product management, this is called - Weakest link. The strength of a chain is equivalent to the strength of the weakest link. It doesn't matter how many strong links are in your chain, the strength is always determined by the weakest link.
The weakest link may not be apparent until the product is used by customers, or it may be identified early on, however, due to various reasons it is left in.
A product manager usually has three options:
1) Maintain the products as is: This is done when customers do not have a very good alternative and the replacement of the product provides better revenue. This applies to the Adapters, accessories and smartphone batteries.
2) Fix the weakest link: This might improve the life of a product. However, this might not be favoured for two reasons: a) cost of improving the strength of the weakest link (or multiple links). b) Fixing the weakest link might expose the next weakest link and that link might provide undesirable negative PR.
3) Smooth out the curve: If the weakest link determines the strength of a chain then it might be prudent to align all links to a particular strength profile. While redesigning the next version of a product, gradually bring all links of a chain to the same quality/longevity but reduce the strength of all links to a degree where they become affordable. This strategy has been used in Cars and Consumer white goods in recent years. These products work perfectly through their warranty period, but multiple components start failing subsequently.
The image above shows the weakest link having the strength of 30 whereas other links are at 100. As the weakest link determines the overall strength of the chain, the strength of the entire chain is 30.
During subsequent iterations, the strength has been dropped to 60 whilst improving the strength of the weakest link to 60. This has improved the strength of the overall chain to 60 (double than previous) while saving 30%.
You can see why Product Managers like this approach due to commercial reasons. However, from the consumer point of view, the overall product's quality has reduced from 100 to 60 (a net reduction of 40%). I will go through the advantages and disadvantages of this strategy in a separate blog.
Now, when we apply this wisdom to the IT systems, we can see how this pans out. Every IT service is a combination of several IT systems, their interfaces and components. These links together form a chain (operation) which underpins the day to day business operation. Going with the key principle above, the strength of the business operation will be determined by the weakest link.
Here are some examples of weakest links:
- An interface between the E-commerce system and delivery management system may be weak and prone to breakdown.
- The 3D secure (verified by Visa) link breakdown may be resulting in several abandoned shopping carts by customers.
- One attribute missing from the product information may deter customers not buying that product.
- Internal IT helpdesk's wrong processes may result in dissatisfaction of internal users.
Wherever I worked, I found hundreds of such weak links. So the question is - why no one takes initiative to fix them.
The product-focused technology companies such as Microsoft, Facebook, Google have product managers, however, in non-technology companies, IT Product management is in a nascent stage.
The IT product management responsibility is shared between Business Product Owners, Business Analysts, Engineering team and Architects. It is not even recognised as a role or considered as a skillset within the IT department in traditional businesses. As a result, no one is accountable for the longevity of IT Products. Most leaders do not realise that the lack of Product Management results in significant deterioration of IT products within a short period of time.
Most teams are aware of the weak links, but they are not empowered nor given the resources to fix them.
The holistic understanding of the business and IT aspects of IT products is missing. In addition, fixing the weakest links is considered a less exciting task than creating a new strong link within the chain. It is exciting to replace a system or transform a set of systems than fixing the legacy systems.
However, I have seen products becoming bloated and weak links manifesting pretty soon after the large transformation programme because the Product Management skillset is missing.
There is no coherent strategy for ongoing management of the products and maintaining their integrity in the long term. In-fact in most organisations, there is little or no control or reporting on the integrity of their products. Once in a while, IT teams will initiate bugathon (to clear out defects from the product) or spare some time to repay the technical debt (the problems left in the product during development to address later).
So how this should be addressed?
to be continued in part 2...Summary of part 1,
The strength of a chain is measured based on the weakest link, hence when working on an interconnected set of processes or systems, it is important to look into improving the strength of the weakest link.
A holistic approach while executing any change can go a long way to maintain the integrity of the product.
As always, any comments/feedback appreciated


