There are, of course, solutions to elude the seven pitfalls hindering improvements in effective ROIC management.
1. Between headquarters and business units:
In order to invigorate the discussion of selling or exiting a business, it is effective to manage business portfolios as a trinity together with technology (or organizational capabilities) and human resources portfolios. This encourages objective discussions by visualizing which businesses should focus on investment and, conversely, which businesses require bold structural reforms, and whether eliminating those businesses would result in an outflow of valuable technology and human resources.
In addition, before requesting business units to improve ROIC while leaving inefficiencies unaddressed, headquarters should start by cutting their own costs (HQ cost structure reform).
2. Between business units:
In order to extract the full potential of each business unit, KPIs should be constructed from the customer value point of view. It is necessary to make choices carefully based on the premise that "a wrong outcome indicator does not produce results, and may have the opposite effect." Thinking along the KBF (Key Buying Factor) and value chain axes, one must identify what factors are important to customers and whether those factors are stagnant, pinpoint what is causing the blockage (that is the “key”), and then set those identified factors as KPIs (i.e. "what" to aim for).
It is also important to specify "who" carries the weight of the identified KPIs. It is not easy to instill balance sheet thinking, particularly in employees who are steeped in profit-and-loss thinking, so consideration must be given to the “who.” For example, regarding the overhead cost allocation problem, which is common when calculating consolidated business ROIC:
- Allocate sales, general, and administrative expenses and fixed assets, which are often shared by multiple business units, to large business units (large segments) instead of unnecessarily allocating them to small business units (small segments) ("Balance sheet by business category" is broken down by large segment units with similar business models)
- Ensure, however, that small segment leaders are jointly responsible for the ROIC of the large segment
- Set ROIC targets in two tiers: a "hurdle rate," which is based on direct costs plus a margin that should be recovered, and an "expected value," which also requires the recovery of overhead costs
Hopefully, these approaches to expense items, hierarchies, and targets can offer some solutions.
Additionally, providing prospective leaders with tasks that include balance sheet responsibilities for projects and subsidiaries, much like with general trading companies, and letting them take ownership of the tasks, could prove effective when encouraging balance sheet thinking to take root.
3. Between management and infrastructure:
To change the rigid way data is held, the data infrastructure for consolidated business management needs to be restructured, with the key being how to integrate data that is scattered across the company and difficult to totally replace. An effective way to achieve this is to establish a data integration tier (second tier) that consolidates scattered data into a form that can be utilized across the board (third tier) on the premise that existing IT assets (first tier) can be utilized through a three-tier architecture.
With the seven pitfalls in ROIC management operations, there is a high risk of rework if large-scale ERP modifications are made suddenly, and therefore, the process should start with spreadsheet compilation, followed by RPA, followed by large-scale modifications in conjunction with periodic ERP updates, and so on, in a sequential manner.
4. Between business units and subsidiaries:
To prevent subsidiaries from favoring individual optimization, it is important to reallocate the original functions of the subsidiaries, and to revise group organization by, for example, organizing flow distribution. This has significant IR benefits in that it makes the structure of business consolidation easier to understand.
5. Between ESG and business units:
In order to gain approval from the business units regarding the ESG cost burden, it is effective to lower the hurdle rate in return for a reduction in the cost of capital. However, the trouble with this is that fairness among units cannot be maintained unless it can be rationally explained that contributions to units are equivalent to "the effect of capital cost reduction by unit." In this regard, it is good to promote the visualization of ESG value in a data-driven manner.
6. Between technical and administrative C-level executives:
To create a common language base among C-level executives regarding the technology agenda, a technology resource inventory (a strategic technology management approach) is effective. This allows the assessment of priorities and the necessary scale of technology investment from a customer value perspective.
Although some object to this by arguing that basic research or company-wide infrastructure have infinitely wide-ranging applications and cannot be linked to business contributions, every technology investment should have a main target (application) in mind, and it is quite possible to demonstrate this as a contribution to the business (customer value). This can be structured by drawing a technology tree from the customer value point of view.
7. Between investors and managers:
To clarify returns commensurate with the business risk from the investor's perspective, it is necessary to show what type and amount of investment is needed, why, when it is likely to be recovered, and the path to cash generation. Generally, we should factor into this explanation how different types of businesses in the same corporate group earn different amounts of money. For example, business types can be classified from a profit-and-loss perspective (advantage matrix: potential economies of scale and differentiating factors) and a balance sheet perspective (investment and returns cycle duration).
To avoid falling into the trap of partial optimization with KPIs, the prioritization of various measures should be determined by returning to the corporate philosophy (the company's raison d'etre and purpose).
These are some potential prescriptions to elude the pitfalls hindering improvements in effective ROIC management. It is worth noting that these are not simple solutions and the hurdles for implementation are not low. This emphasizes the importance of approaching it through an appropriate system.
While ROIC management is generally thought of as the CFO's agenda, it is also closely related to other C-level executives and evolves as a hub that connects the entire company, as shown in Figure 2. Perhaps this could be utilized as one of the guidelines to eliminate the silos of Japanese companies.