I learned to examine the conditions behind the date.

I began in service coordination, where the calendar often looked more orderly than the working day. A request had a date, a team and an expected next step. The difficulty appeared when several requests needed the same specialist at once, or when a routine change became urgent because an earlier decision had arrived late. I was not designing the client’s systems. I was trying to establish which commitment could reasonably be kept next and who had the authority to change the sequence. That experience made me interested in the operating choices hidden inside a busy schedule.

After completing a degree in information systems and management at the fictional Hoshivera Institute in March 1998, I joined Naremi Services in April. The company provided enterprise application support in Japan. My early work involved service records, change calendars and communication between support teams. I learned to ask whether a date described an agreed appointment or simply the date somebody hoped to obtain. The distinction could be easy to miss in a report and expensive to discover during a maintenance window. I also learned to preserve the reason when a commitment changed, so the next colleague did not have to reconstruct the discussion.

In July 2003 I became a service coordination manager. I led twenty-six colleagues across several support accounts and worked with technical leads on the sequence of planned changes. I made an early mistake by allowing each account to treat its own preferred date as the first claim on shared specialist time. A 2006 review of sixty-four planned changes found nineteen competing for the same constrained support windows. We resequenced those nineteen, with JPY 18 million in additional coordination and client-support expense. The work taught me that apparently reasonable local schedules can combine into an impossible operating plan.

I joined Seikoma Systems in January 2010 as an application services director. The larger remit made it necessary to choose which changes could begin, not merely to move dates after every team had already started. I worked with account and engineering colleagues to examine the work in progress, the conditions for finishing it and the interruptions being introduced. A 2013 review of forty-one active work packages led to eleven being paused with explicit client discussions. Thirty continued. The pause was not a claim that the eleven were unimportant; it was an acknowledgement that starting all of them had not created the capacity to finish them responsibly.

In October 2016 I became an executive director responsible for delivery operations. This appointment connected multiple accounts, service desks and implementation teams. I became more careful about the operating calendar as a shared decision instrument. A customer’s maintenance window, an internal release preference and an engineer’s available time were different facts that needed to be reconciled. We also examined incident coordination. The team responsible for arranging the response did not have to be the team whose change would eventually be found to have caused the problem. Waiting to settle blame before assigning coordination wasted time and made collaboration harder.

I was appointed COO in April 2021. The role now includes 1,480 delivery and service colleagues, six direct reports and JPY 12.8 billion delegated annual delivery expense for 2026–27. Seikoma’s JPY 46.2 billion revenue for the year ended March 2026 describes the company, not a personal profit-and-loss claim. I report to fictional CEO Haruka Naremori. Engineering architecture, information security, sales, people policy and financial reporting remain separate functions. My work connects their decisions through a delivery account that shows what can proceed together and where another choice is required.

One recent decision concerned a release calendar with twenty-seven proposed production windows. Nine had unresolved conflicts involving shared recovery support or client-side availability. We moved those nine and retained eighteen, recording JPY 42 million in additional scheduling and support expense. I did not describe the revised calendar as proof that incidents had been prevented. It was evidence that the known conflicts had been addressed before the changes occurred. That distinction matters because a sound preparation decision can be justified without inventing a counterfactual disaster that never happened.

Another question is how the organisation learns when urgent work interrupts the plan. I do not want a delivery report to make unplanned activity disappear by silently changing the baseline. Nor do I want every interruption treated as an individual failure to follow a schedule. The operating account should explain the decision, its consequence and whether the original plan was realistic. My public writing develops those questions through concurrent work, shared maintenance windows and incident coordination. I have executive presentation experience with Seikoma’s board, but no director appointments. A future board contribution would use this operating perspective to examine management choices, not reproduce my current line authority.