Artemis II is the first crewed lunar mission of the twenty-first century, but its significance lies not only in its destination. It represents a deliberate re-examination of what human spaceflight should be in an era defined by new technologies, new risks and new ambitions. NASA did not begin by designing a spacecraft. It began by interrogating the problem. What does sustainable lunar exploration require? How should human and automated systems interact? What lessons from Apollo, Shuttle, ISS and Orion must be carried forward, and which must be re-evaluated? How should risk be understood in a world where the technological landscape has changed dramatically?

These questions shaped the earliest phases of the Artemis programme. NASA's Pre-Phase A work involved extensive concept studies, trade analyses and risk assessments. The agency examined multiple mission architectures, evaluated the interplay between spacecraft, crew, ground systems and deep-space communication networks, and considered the organisational and operational lessons learned from decades of human spaceflight. This was not a procedural formality. It was a systems-level effort to identify the right problem before committing to a solution.

NASA's culture reinforces this approach. The agency's lessons-learned processes, particularly those shaped by the Columbia Accident Investigation Board, emphasise the importance of organisational behaviour, communication and emergent interactions. These are not technical issues in the narrow sense; they are systemic issues that only become visible when one looks at the organisation as a whole. Human-in-the-loop design, central to Artemis II, reflects the same understanding. Humans are not external to the system but integral to its operation, and their interactions with technology must be considered from the outset. Although NASA does not routinely label these practices as "systems thinking," they embody precisely the behaviours that the term describes.