An incident can create a damaging argument before the technical investigation has established what happened. Several teams are involved, each can see part of the problem, and nobody wants to accept a role that might be interpreted as admitting fault. The operating response waits while the participants debate ownership. I have seen how an ambiguous coordination assignment can produce that result. My position is that somebody should be able to organise the response without first confessing to causing the incident.
The distinction is easy to state and harder to maintain. Organisations often use the same word, owner, for the person arranging a response, the team responsible for a service and the party later found to have caused a fault. Those meanings can overlap, but they need not. If the language is unclear, accepting a practical coordination task can feel like accepting a much broader judgement. People may then spend valuable time protecting their team’s position rather than helping the response become coherent.
Give coordination a remit people can recognise
The coordinator needs enough authority to assemble the right participants, maintain an account of decisions and escalate matters that cannot be settled within the response. That is a real operating role. It does not require the person to have every technical answer or to overrule the specialists responsible for a particular decision. The remit should make those limits explicit, because otherwise resistance to the role may reflect a valid concern about authority rather than a reluctance to help.
When we reviewed twenty-two service incidents in 2018, eight included a delay in assigning coordination because teams disputed the origin of the problem. Our first attempt to clarify the role was not sufficiently precise. Some technical leaders read it as giving the coordinator authority to direct actions outside that person’s expertise. They were right to challenge the wording. I revised the proposal so that coordination concerned the operating sequence and escalation, while diagnosis and specialist approvals remained with the relevant authorised people.
A useful remit also explains how the assignment can change. The initial understanding of an incident may be incomplete, and the response may need different coordination as the scope develops. A transfer should preserve the decision history and identify the point at which responsibility moves. Otherwise a change of coordinator can create another gap in the very account the role is intended to maintain. The process needs to be workable under pressure, rather than an ideal sequence that assumes every participant is already available and fully informed.
Rehearsal helps reveal ambiguity before a live event. We allocated JPY 24 million to operating guidance and exercises following our review. Participants practised assigning a coordinator without a prior causal finding, obtaining specialist decisions and escalating unresolved questions. The rehearsal did not make the role universally effective or remove the need for judgement. It gave us evidence about whether people understood the assignment and where its boundaries still needed explanation. That is a more useful result than a document whose readers attach incompatible meanings to the same title.
Preserve investigation without delaying organisation
Separating coordination from blame does not mean suspending accountability. The institution still needs to establish what happened, which decisions contributed and what should change. That work should follow the appropriate evidence and responsibilities. The problem is timing: requiring a causal conclusion before organising the response asks the investigation to finish before the conditions for a useful investigation may even exist. Meanwhile, important decisions and observations can be lost because nobody is maintaining a coherent operating account.
The coordinator can help preserve that account without deciding the conclusion. Who was asked to examine a condition? What decision was made, by whom and on what basis? What remained uncertain at the time? These questions matter later because hindsight can make a decision look more obvious than it was. The record should distinguish knowledge available during the response from knowledge established afterwards. It should also respect confidentiality and the relevant handling requirements, rather than collect or circulate sensitive material merely because an incident is urgent.
One concern is that a neutral coordination role could allow the responsible team to avoid taking charge. That risk deserves attention. The response should still require the relevant service and technical owners to participate and make decisions within their authority. Coordination is not a shelter from those obligations. It is the means of connecting them. If a participant is unavailable or a decision is not forthcoming, the role needs a clear escalation route. The organisation should not solve ambiguity by making the coordinator nominally responsible for work they cannot authorise or perform.
Client communication may add another boundary. The person maintaining the internal operating sequence may not be the person authorised to make external commitments or describe the technical findings. Those responsibilities need to be connected deliberately. A client should not receive a speculative explanation because the response team feels pressure to provide certainty before it has evidence. Equally, the absence of a final cause does not necessarily prevent an appropriate update about what is known and what is being done. The authorised communication owner must make that judgement within the institution’s arrangements.
Review the operating response as well as the technical cause
After an incident, the technical explanation often receives most of the attention. It is concrete and may suggest a corrective change. The operating response also deserves examination. Was coordination assigned promptly? Could the right people be reached? Were decision boundaries understood? Did a transfer lose context? These questions can identify weaknesses that would recur even if the next incident had an entirely different technical cause. Improving only the specific failed component may leave the organisation’s response difficulties untouched.
The review should avoid turning the coordinator into a convenient subject for every criticism. A person may have performed the assigned role reasonably within an inadequate structure. Conversely, a good structure does not mean every individual action was appropriate. The evidence should support the distinction. I want the organisation to examine the remit, the circumstances and the actions together, because an overly personal account can prevent learning about the operating conditions that management itself created.
Our eight delayed assignments gave us a reason to change the process. They did not prove that the revised approach would shorten every future incident. I report the change as clarified boundaries and rehearsed coordination, with its expenditure stated. Subsequent incidents would need their own examination. This restraint matters because an exaggerated improvement claim can conceal the same uncertainty that the original review was meant to expose. A more credible account leaves room for further correction when the operating evidence warrants it.
The question I now ask is whether a responsible colleague can accept the coordination role knowing what it requires and what it does not decide. If the answer is clear, the response can become organised while the technical investigation proceeds. If accepting the role remains indistinguishable from admitting fault, the organisation has built hesitation into its own process. I would rather resolve that ambiguity in preparation than ask people to overcome it through personal courage during an incident. The role should make cooperation easier to exercise, with accountability strengthened by a better record rather than presumed from who agreed to coordinate first.