What does the Many Hands Problem describe in the context of system design?

• A. Too many stakeholders always ensure accountability.
• B. A problem with too few participants in the design process.
• C. When so many hands are involved in the design, building, programming, and configuration of systems such as iCloud servers or Therac-25, it's difficult to determine accountability.
• D. A lack of system complexity leads to unclear responsibility.

Answer: (C)

The Many Hands problem is about accountability becoming hard to pin down when many people are involved in designing, building, programming, and configuring a system. When a large team contributes across different stages and components, responsibility for decisions and outcomes gets diffuse, making it tough to identify who is accountable for failures or mishaps. This diffusion of ownership can lead to gaps in governance, weak traceability, and challenges in safety reviews, as seen in complex systems where multiple teams touch the same infrastructure. It’s not about simply having more stakeholders guaranteeing accountability; it’s about ensuring clear ownership and decision-making boundaries so that when something goes wrong, someone can be held responsible.