My contribution to a board
I would bring experience of technology decisions whose consequences continue beyond a launch date. Insurance platforms often serve several generations of products, and an apparently simple replacement can affect historical records, maintenance knowledge and the sequence of operating approvals. I can help a board ask whether management has identified those obligations and whether the investment case includes the work required to preserve them. My contribution would be to the quality of the enterprise decision, not an attempt to choose implementation details from the boardroom.
I also bring a habit of keeping unlike results separate. A document reference can match an approved map without establishing legal coverage. A faster processing run can improve a working interval without validating actuarial assumptions. A capability can be installed before its live use is approved. Those distinctions help directors understand what an engineering report supports and what still requires another owner's judgement. I would contribute alongside directors with deeper financial, legal, underwriting or sector experience, rather than present technology knowledge as a replacement for those perspectives.
Judgement in practice
01A bridge with a stated portfolio sacrifice
The eighteen-month JPY240 million bridge for an older product engine required us to defer two discretionary analytics features. I supported that choice because the existing service still had a responsibility and the successor had not completed acceptance. For a board, the useful question is whether the transition account makes that continuing obligation and opportunity cost visible. Approval of the bridge was not a completed retirement or evidence that the successor would meet a future date. The March 2026 review retained the open third acceptance stage in the account, allowing the next funding decision to be based on current evidence.
02A product decision retained outside the technical release
In the commercial-property programme, capability installation on 18 March 2026 was separated from product approval on 8 April and controlled activation on 13 April. I accepted the coordination cost because the owners of wording, pricing and operating arrangements still had decisions to complete. The prepared environment supported rehearsal, including correction of a referral instruction, without accepting live business through the new configuration. This illustrates the oversight question I would bring to another enterprise: does a programme's completion language preserve the authority needed for the next stage, or quietly imply that one successful workstream has approved the rest?
My first year on a board
I would use the first year to understand the business before concentrating on its technology agenda. That includes how it earns money, which customer commitments last beyond a transaction and where management sees the largest uncertainties. I would read its financial and strategic material, discuss the governance calendar with the chair and learn how the board receives evidence about investment and operating performance. An architecture diagram would be only one part of that preparation.
I would then follow a small number of consequential decisions from their proposed benefit to the responsibility left with the receiving team. The purpose would be to understand the organisation's reasoning and information, not to audit every project personally. I would ask how continuing obligations are funded during change and how the board learns when an assumption has ceased to hold. I would seek feedback on whether my questions help the full board and address gaps in my understanding through induction and further study. I would not seek to chair a committee before developing the relevant experience and confidence of the board.
Conflicts and their management
My Nerumori employment would be disclosed before any appointment discussion progressed. I would examine the proposed organisation's relationships with the insurer, its suppliers and other relevant commercial parties, as well as my own personal or financial connections. A shared software provider can create a relevant relationship even where two enterprises do not compete directly. I would therefore avoid treating the absence of a competitor label as sufficient evidence of suitability.
The receiving organisation's assessment would determine whether restrictions, recusals or other arrangements were appropriate. If a material conflict could not be managed responsibly, I would decline the appointment. I would not transfer confidential product information, pricing assumptions or internal engineering material from one enterprise into another board discussion. Public context and properly authorised evidence would be the basis for explaining my experience. The review would continue as circumstances changed; an acceptable position at appointment would not settle every future relationship.
My independence statement
I do not claim independence in advance. My employment, commercial connections and the proposed company's circumstances would need examination under its applicable framework before a role could be assessed.
Governance learning and readiness
IICA Independent Directors’ Databank: Not yet registered
I am not registered in India's Independent Directors' Databank and make no claim of an exemption or proficiency status. Any India appointment would require its own preparation and eligibility review.
- A structured induction covering the receiving company's business model, finances, duties and governance arrangements
- Further learning in enterprise financial analysis and insurance economics beyond the engineering budget
- Chair feedback on the distinction between useful oversight and executive intervention
Committee contribution
Chair and member readiness| Capacity | Committees |
|---|
| Ready to join | Technology committee · Risk committee with complementary financial and sector expertise |
|---|
Board and committee exposure
Presented to the Board or a committee
Nerumori Assurance
Board technology investment discussions
CTO appointment from April 2020
Presented engineering investment and continuing-service choices, including the older-engine bridge; executive presentation only, with no director appointment.
Capacity and preferences
- Time available
- 22 days per year
- Current directorships
- 0
- Sectors
- Insurance · Software-intensive services with long-lived customer obligations
- Company type
- A listed or privately held enterprise with a clear board mandate and accountable management
- Company stage
- A period of platform renewal in which continuing service and future investment must be examined together
The seat I am pursuing
I would consider one first external seat with a clear need for experience in software-intensive operations and a willingness to examine long-lived obligations. Twenty-two annual days is my proposed planning allowance, subject to employer approval and the actual meeting, preparation, induction and exceptional-work requirements. It is not a promise that any proposed schedule will fit. I would discuss capacity before agreeing to a role, especially where a major platform transition could create demands beyond the ordinary calendar.
A technology committee could be a suitable contribution, and a risk committee may also be relevant where other members provide complementary expertise. I claim no committee chair readiness or existing director status. I would prefer a board that expects questions about economics and customers as well as systems, and a chair who helps a first-time director contribute through collective oversight. My interest is in making the enterprise's technology choices more intelligible, while learning enough of the wider business to participate responsibly in the full agenda.