Skip to main content
Transformidy

Article

The Decision With No Name on the Door

Decisions that span two or more functions, a safety concern, a vendor risk, a customer escalation, often default to whoever moves first, speaks loudest, or simply stays in the room longest, because no one has been formally named as the accountable owner of a decision that crosses functional lines. A

Published
July 28, 2026
Updated
August 19, 2026
Reading time
9 min
Paper-cut editorial illustration for The Decision With No Name on the Door

The Global Signal

General Motors became aware of a defective ignition switch, one that could unintentionally slip out of the "run" position and disable power steering, power brakes, and airbags, as early as 2004 and 2005, according to Anton Valukas's independent investigation, commissioned by GM's own board of directors and published in June 2014. GM did not issue a recall until February 2014, roughly a decade after the defect was first identified internally. The Valukas Report found that the defect moved between engineering, legal, and safety review committees for years without any single function or individual being clearly accountable for deciding whether to recall, describing a pattern the report itself characterized as a failure of individual accountability rather than a single deliberate decision to conceal the problem (Anton R. Valukas, "Report to Board of Directors of General Motors Company Regarding Ignition Switch Recalls," June 5, 2014). GM ultimately recalled approximately 2.6 million vehicles, the National Highway Traffic Safety Administration fined GM $35 million, and GM reached a $900 million deferred prosecution agreement with the US Department of Justice in September 2015. A compensation fund administered by Kenneth Feinberg on GM's behalf ultimately recognized 124 deaths linked to the defect.

No single person or committee ever formally owned the decision to recall. It sat, for roughly a decade, in the space between functions, each of which could reasonably point to another as the one that should have acted.

Visible cost
124

Deaths linked to the ignition switch defect, per GM's own compensation fund

A documented figure from the compensation fund GM itself established, administered by Kenneth Feinberg; specific to this case, not a general statistic.

Ambiguity about ownership is routinely mistaken for shared responsibility.

The Hidden Signal

A decision that requires input from multiple functions, engineering, legal, safety, finance, can move through every one of those functions repeatedly, generating meeting after meeting, without ever landing on a single named person whose job is to make the final call. Consider a hypothetical scenario, smaller than GM's case but illustrative of the same mechanism: a retailer discovers a supplier is shipping a product with a minor but real safety defect. The issue is raised in a supply chain meeting, then a legal review, then a customer experience discussion, over several months, with each group agreeing the issue is real and each assuming another group has been tasked with the final decision on whether to pull the product. No one is lying. No one has been named the owner, so the decision simply continues circulating.

What changes

What changes when one name is on the door

An issue discussed across multiple functions, however genuinely, is not the same as a decision anyone is accountable for making.

Naming a single accountable owner, with explicit authority and a deadline, for any cross-functional issue closes the gap that let GM's defect circulate for a decade.

Why the Visible Metric Misleads

A cross-functional issue being discussed repeatedly, in meeting after meeting, can look like the organization is actively working the problem, when in fact repeated discussion without a named decision owner is functionally indistinguishable from no decision process at all. The more revealing question is not how many meetings have addressed an issue, but whether a single named individual has the explicit authority and obligation to make the final call, with a deadline. The Valukas Report's core finding about GM was precisely this: the ignition switch issue was discussed across multiple committees for years, and that repeated discussion substituted for, rather than produced, an actual accountable decision.

The Leadership Move

The right move is not adding another cross-functional committee to review a hard issue. It is naming a single accountable decision owner, with explicit authority and a deadline, for any issue that spans more than one function, even when that owner must consult broadly before deciding.

Ownership

Engineering, legal, and safety functions at GM each held a piece of the ignition switch issue and, according to the Valukas Report, each could reasonably describe another function as responsible for escalating it to a final decision. A cross-functional issue needs exactly one named decision owner, chosen deliberately, not left to emerge informally from whichever function happens to raise it most persistently.

Tradeoff

Naming a single accountable owner for a genuinely cross-functional decision means giving that person authority that other functions may resist ceding, and it requires leadership to make an uncomfortable choice about which function's judgment takes precedence when views conflict. The alternative, GM's decade-long gap between defect discovery and recall, shows the cost of leaving that discomfort unresolved.

Human consequence

124 deaths were ultimately linked to the ignition switch defect, according to the compensation fund GM itself established. The people affected by those decisions had no visibility into the fact that the issue was being discussed, repeatedly and in good faith, by multiple functions, none of which had been named the owner of the decision to act.

Implication for Operators

Any organization with an issue that requires input from more than one function should assume that repeated cross-functional discussion, without a single named accountable owner and a deadline, is unlikely to produce a timely decision, regardless of how genuinely each function is engaging with the problem. The practical shift is naming an owner explicitly, before the discussion begins circulating, not after the gap has already persisted for years.

GM's ignition switch defect was known, discussed, and reviewed by multiple functions for roughly a decade before a recall was issued. The organization was not blind to the problem's existence. It was blind to the fact that discussing a problem across several committees is not the same as anyone being accountable for deciding what to do about it.

The decision blindness here is not a hidden defect. It is a real, known problem that circulated through every function with a stake in it and never landed on a single name accountable for acting.

Next Move

Reflection question

Name a cross-functional issue currently being discussed inside your organization. Is there a single, named person with explicit authority and a deadline to decide, or is the issue circulating among several groups, each assuming another owns it?

Practical step

For your highest-stakes unresolved cross-functional issue, name a single accountable decision owner today, with an explicit deadline, rather than scheduling another joint review meeting.

Soft invitation

Transformidy's decision-workflow review helps organizations name a real owner for decisions that would otherwise circulate indefinitely between functions.

Signal checkDecision BlindnessRegistry-backed

For decisions that cross functions, how clearly does your organization name one accountable owner with authority to make the call?

FAQ

Did GM deliberately choose not to recall the vehicles?

The Valukas Report specifically found the pattern was not a single deliberate decision to conceal the defect, but a structural failure of individual accountability, with the issue moving between committees for years without a named decision owner acting on it.

How is this different from a slow bureaucratic process?

A slow bureaucratic process still has a decision at the end of it, even if delayed. This pattern describes a decision that never definitively lands anywhere, because no single person or function was ever named as accountable for making the final call, so the process can continue indefinitely without producing an outcome.

How can an organization tell if a cross-functional issue has a real owner?

Ask whether one specific, named individual has explicit authority to make the final call and a deadline for doing so, regardless of how many other functions they must consult. If the honest answer is that the issue is being discussed across several groups with no single person accountable for the final decision, the ownership gap exists.

Does naming one owner risk that person making a bad call without enough input?

A named owner does not mean deciding without consultation; it means one person is accountable for weighing that consultation and producing a timely decision. The risk of a poorly consulted decision is smaller and more correctable than the risk of no decision being made at all, which is what GM's case shows over roughly a decade.

Who should decide who the named owner is for a given cross-functional issue?

A leadership function with the authority to assign accountability across functional lines, typically an executive sponsor or a governance body specifically empowered to name owners for issues that do not fit neatly inside one function's existing chain of command.