Section · The boardroom
Examine the continuing commitment behind the proposed change
I have presented technology investment choices in Nerumori's board discussions as an executive. I have not served as a director, and I do not treat those presentations as an equivalent appointment. They have taught me to explain engineering choices in terms of the responsibilities they create for the enterprise. A board needs to understand why a decision matters, what alternatives management considered and what evidence supports the proposed course. It does not need a CTO to replace that account with a catalogue of technical components.
The continuing life of insurance products makes this especially important. A platform may need to preserve a relationship with an earlier product edition after the current offering has changed. The engineering team can demonstrate that a reference matches an approved map, but the responsible product and legal owners determine the meaning that map is intended to preserve. In a board discussion I would make that division clear. Directors should be able to see whose judgement supports the result and which further conclusion the technical test does not establish.
Investment timing is another useful subject for oversight. The eighteen-month JPY240 million bridge for an older engine did not make the replacement less desirable. It made the interval between the existing obligation and the accepted successor visible. Deferring two analytics features showed the capacity trade-off. At the March 2026 review, two of three successor acceptance stages were complete and one remained open. A responsible account retained that unfinished work, rather than claim a retirement benefit merely because funding for the transition had been approved.
I would want a board to ask how management handles the next decision if a transition assumption changes. Who owns the continuing service? Which specialists are needed by both the old and new arrangements? What evidence would justify extending the bridge or transferring responsibility? Those questions connect the programme to resource allocation and customer obligations. They do not require directors to select an implementation method, and they should not become an invitation for a technically experienced director to direct the project team outside the agreed governance relationship.
I also distinguish the sequence of approval in product programmes. Installation of a capability can be a useful milestone while wording, pricing and operating arrangements still await their owners' decisions. The March and April 2026 commercial-property sequence preserved those stages. A board could examine whether the programme's status language reflected that authority. It should not assume that a technical release grants permission to offer a product, or that a prepared environment establishes every condition for live use.
My first external appointment would require preparation beyond these engineering questions. I would need to learn the company's economics, financial position, customers and governance arrangements. Twenty-two annual days is a proposed allowance for consideration, not an assurance that every board schedule fits. Employer agreement and a review of commercial and personal relationships would be necessary. I would disclose relevant connections and follow the receiving organisation's assessment, including declining the role if a material conflict could not be managed responsibly.
I could contribute to a technology committee and potentially to a risk committee with complementary financial and sector expertise. I do not claim readiness to chair either. The distinction between executive action and director oversight would be part of my induction and an ongoing discussion with the chair. My experience can help examine the evidence behind a technology investment, but it should also make me more careful about the limits of my own authority.
The contribution I seek is a clearer account of how the enterprise will honour its existing commitments while preparing new capability. That includes the cost of history, the cost of transition and the decisions that remain outside engineering. I would bring those questions to collective board work, alongside a willingness to learn where another director or management colleague understands the matter better than I do.
On governance
I want a platform to preserve the context of a contract without turning yesterday's technical choices into permanent constraints on tomorrow's work.
Formation
Education & credentials
- Degree in information engineeringTakemori Institute1994
An invitation
Contact
I would consider a selective governance conversation about software-intensive services with long-lived obligations. I hold no director seat and would discuss twenty-two annual days for a first appointment, subject to employer agreement, relationship checks and a realistic induction plan.
- Board appointments
- Speaking invitations
- Executive opportunities
office@norikomizuhane.example