Capacity is a consequence of industrial strategy, not the reason for it.

In 2023 we compared a JPY 7.4 billion dedicated-volume proposal with JPY 4.6 billion for flexible assembly. The first emphasised output in a narrower product range; the second supported a different mix of industrial assemblies. A comparison based primarily on total units would have made the dedicated line look more ambitious. I wanted the institution to decide which customer work it intended to pursue before treating either capacity description as the measure of strategic success.

Takuma Nagisawa, our fictional industrial investment director, supported the dedicated proposal. He argued that a clear volume commitment could focus the business and make better use of its manufacturing experience. That case deserved attention. My preference for flexible assembly was not an assumption that flexibility always creates more value. It reflected the direction we were choosing towards more varied assembly work, with the applications and customer requirements that direction would bring. The alternative's scale was attractive, but it represented a different emphasis.

I recommended the JPY 4.6 billion option. The capital decision remained with the authorised body, while engineering and operating leaders assessed the capability, quality, safety and practical requirements. I did not select equipment or certify output. My contribution was to connect the investment choice with the business the company wanted to develop and to keep the narrower volume opportunity we were giving up inside the discussion. The approved direction required a different commercial effort as well as physical investment.

The JPY 2.8 billion difference between the proposals was not a realised saving. The scopes, product mixes and intended outputs were different, so subtracting their budgets did not establish that we had bought the same undertaking more cheaply. Nor did the selected option prove that the dedicated proposal would have failed. We chose a capability and accepted the opportunities it would leave outside our immediate direction. That is the trade-off I would want a reader to understand before quoting either amount.

The case made my view of industrial strategy more concrete. Capacity should follow the work the business intends to become good at, with the responsible specialists explaining what the proposed assets can support. A large output number can be useful evidence, but it cannot choose the company's future on its own.

The assembly-engineering business acquired in 2016 had JPY 18.5 billion annual revenue, 70% from customer-specific projects. The initial integration discussion focused heavily on its factories and their apparent overlap with our footprint. That was relevant, but it risked making the acquisition look like an opportunity to move work between similar buildings. Much of its value to our industrial direction lay in application-engineering knowledge developed around particular customer requirements. I wanted the integration account to preserve that reason for acquiring it.

Colleagues responsible for consolidation argued that keeping separate capabilities would delay the benefits expected from bringing the businesses together. They wanted an earlier, simpler account of shared resources. I agreed that integration needed a clear purpose and could not become an excuse to leave everything unchanged. My disagreement concerned the assumption that the most visible physical overlap identified the best place to start. Customer-specific work could rely on knowledge and relationships that a factory comparison did not describe.

I supported retaining the application-engineering capability and JPY 420 million in integration preparation. Engineering, operating, employment and customer-contract owners assessed the actual arrangements. The strategic recommendation did not prescribe staffing outcomes or promise that every existing process would remain. It required the integration proposal to explain how the acquired capability would contribute to the assembly direction before claiming that physical consolidation had already delivered the acquisition's value. The transaction price and any return calculation are outside this fictional case.

We accepted a less immediate consolidation story and continued effort to understand the different work. That could disappoint colleagues looking for a single early efficiency figure. I did not replace it with an invented estimate of capability value. The outcome was a more qualified integration plan that retained the customer-specific character of the acquired business and the expense of preparing it properly. Subsequent operational results would need their own evidence rather than be assumed from the strategic decision.

I use the case to explain why an industrial acquisition needs a reason that survives integration. If the business was acquired partly for what its people know how to solve, the plan should identify how that contribution will continue. Factory count can describe the footprint while still missing the capability that made the transaction worth considering.

In 2021 we decided to stop pursuing new bids in three commodity-component families. They had contributed JPY 9.8 billion revenue in 2020, so the choice removed a substantial source of potential future volume from the commercial plan. The direction was towards precision motion and industrial assemblies, where we intended to concentrate development and application effort. I wanted that choice expressed through work we would decline, rather than present a new strategic emphasis while leaving every previous pursuit equally active.

Commercial colleagues argued that the existing families maintained customer contact and helped fill the industrial footprint. They were concerned that declining new opportunities would create a visible gap before the assembly direction produced comparable business. Their objection was central to the decision. A strategy that gives up volume cannot assume the replacement appears immediately. I supported the change because continuing to pursue the same range would preserve demands on attention and resources that the new direction was meant to alter.

The transition carried a JPY 680 million commercial planning budget. Responsible operating, contractual and professional owners assessed existing orders and support, which were not erased by the decision about future bidding. Employment matters likewise retained their own process and authority. I did not present the change as an immediate withdrawal from current commitments or promise a particular staffing outcome. The strategic account needed to distinguish the work no longer pursued from work the institution still had to address.

We accepted the loss of potential volume and the possibility that the industrial footprint would look less fully occupied while the mix changed. The JPY 9.8 billion figure described the previous year's revenue, not a predicted amount of sales lost or an immediate cost reduction. The transition budget was an expense of changing commercial direction, not a saving. Those distinctions prevented a difficult choice from being converted into a simple before-and-after performance claim.

For me, the case shows how a direction becomes real. It needs a boundary around what the company will continue to pursue and an account of the consequences of that boundary. The decision was not that commodity components are inherently unattractive. It was that this company could not give every possible industrial undertaking the same place in the future it was choosing.

In 2009 I supported an integration plan that combined two eighteen-person engineering-team lists into a thirty-six-person resource account. Twelve colleagues appeared in both teams because they supported work across the divisions. There were twenty-four distinct people, not thirty-six. I had accepted the organisational labels as if they described separate capacity and had not reconciled the individuals behind them. The error mattered because the plan implied more independent engineering attention than the company could actually assign.

Sae Kuzuhara, our fictional engineering resource-planning lead, challenged the count. Some colleagues wanted to retain the two-team presentation because it reflected the way the divisions organised their work. That description could remain useful, but it could not support an additive resource claim. I needed to distinguish two organisational responsibilities from two independent groups of people. The revised account preserved the cross-divisional work while making clear that the same colleague could not be treated as a full additional resource simply by appearing on another list.

We incurred JPY 85 million in replanning. Engineering and employment owners retained the decisions about responsibilities, capability and workload. The correction was not a redundancy exercise, nor evidence that twelve people were unnecessary. It showed that the original plan had overstated the distinct resource available. I accepted responsibility for supporting that plan before the reconciliation and for explaining the change to colleagues who had begun to use it in their own assumptions.

The consequence was a less ambitious immediate integration schedule and more work to understand competing demands on the shared colleagues. We gave up the apparent simplicity of adding the team totals. It would be misleading to claim that the corrected count itself improved engineering productivity or produced a financial saving. The first outcome was a resource account that no longer depended on the same people being counted twice. Any later improvement would require a separate measure and evidence.

That mistake still shapes how I read industrial strategy proposals. A label can organise work without establishing additional capability. Before using a number to support a commitment, I want to know what has been counted, where the overlap sits and who is qualified to judge what those people can realistically undertake.

A 2025 joint-venture proposal described an equal 50:50 equity arrangement. The strategic presentation used that symmetry to suggest balanced influence over the future product roadmap. A review of the proposed decision schedule told a different story: of nine identified roadmap decisions, seven would sit with one partner and two would be joint. I wanted the institution to examine that proposed authority before allowing the ownership headline to carry an implication it did not establish.

The partnership sponsors argued that the specialist partner needed greater control over areas close to its capability. That could be a valid reason for asymmetry. I was not seeking equal control over every decision merely because the equity was equal. The question was whether the proposed arrangement supported the industrial contribution we expected to make and whether our account described that position honestly. A partnership could be worthwhile with unequal decision responsibilities, provided the company chose them with a clear understanding of their consequences.

We supported JPY 190 million in commercial and legal assessment and revised the governance proposal before an investment decision. Qualified legal advisers interpreted the proposed arrangements; technical and commercial owners assessed their practical significance. I did not derive statutory rights from the ownership percentage or offer a general model for joint-venture governance. The nine-decision schedule was specific to this invented proposal, and the case does not claim that a joint venture was completed.

The revision delayed a simpler announcement narrative and required the sponsors to explain what each party would actually be able to decide. It also left open whether the eventual arrangement would remain attractive. That uncertainty was preferable to treating equal equity as a complete account of influence. We gave up the ease of a symmetrical headline, not necessarily the partnership itself. The assessment expense remained part of the work required to reach a responsible investment discussion.

I connect this case to industrial capability because a partnership's contribution depends partly on who can direct its future work. Ownership is one part of the relationship. The decisions through which the product direction changes need their own account before the company can say what kind of capability it is helping to build.