The board should be able to see what the revision changed.

A delivery plan reaches the board as a set of commitments that may appear more compatible than they are in practice. Account forecasts, project schedules and support obligations often arrive through different reporting channels. Each can be reasonable within its own boundary. The operating question is whether their conditions can coexist. I want the board to receive an intelligible account of that relationship, especially when growth depends on several teams drawing on the same specialist attention or production-support capacity.

My responsibility as COO is to explain the operating choices management has made and the evidence supporting them. It is not to ask directors to schedule the work. A useful paper should identify a material constraint, the alternatives considered, the commercial and delivery consequences, and the decision or oversight question that belongs with the board. Raw activity counts can help describe scale, but they do not establish that the commitments have a credible route to completion. The paper needs to connect the count with the work and its dependencies.

The review of forty-one active packages in 2013 remains a useful example. We paused eleven and continued thirty after examining the combined workload. The paused packages retained their owners and client obligations, while JPY 63 million was spent on transition and resequencing. A board-facing account should preserve all of those facts. A lower active count alone could create the impression that the problem had disappeared. The more important question is what changed in the operating conditions, what remained owed and what evidence management expected to bring back about the revised sequence.

I also want the cost of preparation distinguished from an imagined outcome. In the 2024 calendar review, nine of twenty-seven proposed production windows had unresolved conflicts. Moving them cost JPY 42 million in additional scheduling and support. That decision can be examined on the basis of the known conditions and available alternatives. It does not need a speculative figure for incidents supposedly prevented. A board should be able to ask why the conflict was discovered when it was and whether the revised arrangements were supported, without receiving a hypothetical saving that cannot be verified.

The history of the plan matters as much as the latest version. Our review of twenty-six weekly reports found nine in which a revised baseline had displaced the original commitment. Fourteen client milestones had changed; nine new dates were accepted and five remained under discussion. Showing only the current version would have hidden the decisions management needed to understand. Preserving the earlier account does not mean every interruption is a failure. It makes it possible to distinguish a necessary response to changed circumstances from an assumption that should have been challenged before the plan was made.

Governance should also examine the burden of coordination itself. I once required too many routine sequence decisions to pass through central meetings. Returning bounded decisions to four account teams reduced twelve recurring meetings to two focused forums, with JPY 9 million spent on the transition. The lesson was not that fewer meetings are always better. It was that an added management process needs a clear purpose and a proportionate boundary. Directors can ask whether a proposed control addresses the problem identified, while leaving the executive team responsible for designing and operating it.

My own experience remains executive rather than non-executive. I have presented to Seikoma’s board as COO. My earlier title of Executive Director, Delivery Operations described an internal function and did not make me a statutory director. A future board role would require a different use of the same operating knowledge. I would contribute through collective discussion, agreed requests to management and the chair’s direction. I would not create informal instructions to account teams or use familiarity with delivery work as a reason to step around the institution’s governance arrangements.

The contribution I would aim to make is a clearer account of commitments and consequences. A services company can choose to grow, pause, resequence or accept an urgent interruption, but those choices should remain visible in the record. The board should understand which assumptions support them, which responsibilities remain distinct and what would prompt management to reconsider. That clarity allows challenge without turning oversight into another scheduling meeting. It also makes it easier to recognise when the operating model itself needs to change, rather than repeatedly asking colleagues to compensate for incompatible promises through additional effort.