Section · Speaking & conversations

Give every owner a clear part in the technology conversation

Which edition did the platform actually retrieve?

Thirty-minute presentation with a worked discussion · Insurance technology, product and legal leaders

I examine the difference between a service that returns a document and one that returns the document associated with the record under review. The session uses the fictional 6,400-reference rehearsal in which 184 links initially pointed to the newest wording. It shows how a technically successful response can conceal a historical correspondence problem, and why the responsible product owner must determine the intended mapping. Participants consider the cost of preserving editions, the maintenance decisions that can later erase their meaning and the evidence a receiving team needs. I keep engineering validation separate from a legal conclusion about coverage. The discussion is suitable for leaders who need a shared language across product and technology responsibilities, without turning either group into the other's decision maker. Attendees leave with questions to apply to their own historical records; the session does not prescribe a universal retention rule or claim that one storage design is appropriate for every insurer.

The price of the transition between two insurance engines

Forty-minute executive briefing and questions · CFOs, CTOs, portfolio sponsors and directors

I explore a replacement decision in which the existing engine still has work to do and its successor is not yet accepted. The fictional eighteen-month JPY240 million bridge provides a concrete discussion of funding, specialist capacity and the two analytics features deferred to make the transition supportable. The session examines why a roadmap is different from an available service and why maintenance cannot be removed merely to make an investment account look cleaner. It also considers the opposite risk: a temporary bridge becoming an unexamined permanent arrangement. Participants discuss remit, review points and the evidence needed for a further funding or retirement decision. I distinguish approved expenditure from money already spent and a completed acceptance stage from a realised retirement benefit. The purpose is to improve the portfolio conversation, helping financial and engineering leaders examine the years between the current service and the intended destination without making a promise about any particular programme's outcome.

When faster processing costs more and may still be worthwhile

Thirty-five-minute case discussion · Actuarial, engineering and finance teams

I use a fictional actuarial replay to examine a decision that combines shorter waiting with higher recurring expenditure. The same agreed 1.2 million-record snapshot and assumptions ran in 4.1 hours under a revised arrangement, compared with 9.6 hours in the baseline conditions, while compute cost increased by JPY3.2 million a month. The session asks what must remain comparable, who accepts the output comparison and how the receiving team's decision calendar affects the value of different completion windows. It avoids treating a speed ratio as proof of better estimates or lower staffing needs. Participants consider the difference between a technical processing measure and the professional judgement applied to its outputs. I also discuss why selecting the shortest achievable run may be less useful than selecting a service that fits the work at an understood cost. The conversation is intended to connect technical evidence and financial choice without substituting engineering authority for actuarial responsibility.

Installed, approved, activated: three different events

Forty-five-minute leadership workshop · Product sponsors, operating leaders and technology executives

I examine how a single launch milestone can conceal several decisions with different owners. A fictional commercial-property programme installed capability on 18 March 2026, received product approval on 8 April and activated live use on 13 April. Participants work through why those stages were separated, what additional coordination they required and how rehearsal exposed a referral instruction before introduction. The workshop does not imply that separate activation is always the correct technical design. It asks whether the chosen sequence reflects the approvals and operating conditions actually outstanding. Teams compare short status statements that preserve the distinction with broad completion labels that erase it. I include a separate intake-capacity example to show why acknowledgement speed cannot stand for claims settlement. The intended result is a clearer discussion of responsibility and evidence at each stage, with no promise that a workshop alone establishes launch readiness or satisfies an insurer's own governance process.

Short speaker biography

I am Noriko Mizuhane, CTO of the fictional Nerumori Assurance in Japan. My work connects product history, platform investment and operating authority. I lead 155 employees and discuss how insurance engineering can preserve long-lived obligations while making room for change, without confusing technical evidence with a wider business approval.

Standard speaker biography

I am Noriko Mizuhane, chief technology officer of the fictional Nerumori Assurance, a Tokyo-headquartered non-life insurer. I began as a developer in 1994 and joined insurance systems management in 2001. Today I lead 155 employees through five direct reports, with thirty-eight contractors separately, and have JPY7.8 billion FY2026–27 engineering and maintenance authority. My speaking subjects include historical product definitions, the funded interval between old and new platforms, and the difference between installed capability and approved live use. I hold no director seat. My examples make the receiving owner's decision visible and retain the limits of the technical evidence, rather than turn a useful rehearsal into a claim about every operating outcome.

Extended speaker biography

I am Noriko Mizuhane, CTO of the fictional Nerumori Assurance, a listed Japanese non-life insurer headquartered in Tokyo. I lead 155 employees through five direct reports, with thirty-eight contractors separately, and report to the CIO. My FY2026–27 authority is JPY7.8 billion, comprising JPY4.9 billion engineering platforms and JPY2.9 billion maintenance. The insurer's JPY184 billion gross written premium for the year ended March 2026 is employer context, not a technology revenue account.

I began in software development in April 1994 and joined Nerumori in April 2001. Systems management, product-platform leadership and engineering direction preceded my CTO appointment in April 2020. That progression shaped my interest in the technical history an organisation must preserve while its products and systems change.

I speak about edition-aware records, actuarial processing comparisons, transition funding and the sequence from capability installation to live activation. The examples distinguish a demonstrated technical result from a legal, actuarial or operating conclusion that belongs to another owner. I have no director appointment and would consider a first external role only after employer agreement, relationship review and a realistic time assessment. My aim in a discussion is to make the enterprise choice clearer, including the work and uncertainty that a simplified completion label can leave out.

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.

Open to

Board appointments
Speaking invitations
Executive opportunities

Write to Noriko

office@norikomizuhane.example