This video is featured in the AI and UX playlist and 1 more.
Summary
NASA faced increasing complexity in managing data, meeting customer needs, and streamlining processes across its diverse missions and operations. With fragmented data sources, manual workflows, and a lack of integrated AI tools, teams struggled to maintain efficiency, consistency, and innovation. Through a cross-organizational AI-readiness initiative led by the OCIO, NASA engaged stakeholders across Service Lines, Centers, and Mission Support Offices to identify challenges, articulate use cases, and prioritize AI opportunities. Workshops, assessments, and stakeholder collaboration provided a roadmap for integrating AI solutions, enabling secure data usage, and automating repetitive tasks. Focused efforts on training, governance, and iterative implementation ensured alignment with organizational goals.
Key Insights
-
•
Organizational culture is more critical than technology in successful AI adoption.
-
•
AI readiness requires understanding people’s workflows, hopes, fears, and data landscapes first.
-
•
Incremental, low-stakes experimentation builds organizational comfort with AI over time.
-
•
Today’s AI tools are rapidly changing, so organizations should focus on stable strategic destinations rather than specific tools.
-
•
Cross-departmental communication is vital to bridge siloed data and enable AI use across teams.
-
•
Many AI implementations fail when tools are adopted prematurely without aligned strategy or culture.
-
•
Human-centered design applied to AI integration helps align AI capabilities with actual user needs.
-
•
Safe, sandboxed environments encourage employees to explore AI without risking sensitive data.
-
•
Bring Your Own AI (BYO AI) is the emerging model, letting organizations control their AI core rather than vendor lock-in.
-
•
The people who build and support AI systems within an organization are like the unseen heroes, akin to mission control supporting astronauts.
Notable Quotes
"Culture over technology is all that matters. Technology can’t help you out of cultural problems."
"Focus on the destination, not the vehicle, because AI tools will change every single day."
"Hope is the only thing that lets the conversation continue and reach forward."
"You have to hold people’s hands through your organization—not just hype about AI."
"If you don’t know the type of trip, how do you choose your vehicle?"
"Most of us are not Neil Armstrong; we’re the ground control building the scaffolding."
"Bring your own AI and keep control over the process rather than being locked into vendor solutions."
"Start small and learn in low-stakes ways so you can train the organization to think, act, and react to AI."
"Cross-silo communication is huge because AI is only as good as the permeable membrane between data."
"This is a paradigm, a civilization-altering step change in human capability on the scope of Prometheus bringing fire from the gods."
Or choose a question:
More Videos
"If you launch in the US and politeness is an issue, first try to fix it with prompts; only if that fails should you build an eval."
Peter Van DijckBuilding impactful AI products for design and product leaders, Part 2: Evals are your moat
July 23, 2025
"If you don’t measure if research is successful, what do we ultimately have to show for it?"
Chris Geison Cristen Torrey Eric MahlstedtWhat is Research Strategy?: A Panel of Research Leaders Discuss this Emergent Question
March 4, 2021
"We help teams onboard their coded components onto the UXPin platform so they can be enabled with component-driven prototyping."
Jack BeharHow to Build Prototypes that Behave like an End-Product
December 6, 2022
"Not growing the team was disheartening but led me to create training for partners to start taking a user-centered approach themselves."
Abbey Smalley Sylas SouzaScaling UX Past the Size of Your Team
January 8, 2024
"We're hearing do more with less, cut down or cut out the research, build features that we tell you to, not the ones users ask for."
Jon FukudaTheme One Intro
October 2, 2023
"Decades worth of agricultural experimental data was garbage because of poor experimental design."
Erin WeigelGet Your Whole Team Testing to Design for Impact
July 24, 2024
"We choose to measure design ops value not because it is easy, but because it is hard."
John Calhoun Rachel PosmanMeters, Miles, and Madness: New Frameworks to Measure the (Elusive) Value of DesignOps
September 24, 2024
"Scaling is not for the sake of scaling, but scaling over time."
Jacqui Frey Dan WillisPanel Discussion: Integrating DesignOps
November 7, 2018
"Controls like insurance qualifiers and legal agreements were necessary guardrails for this new way of working."
Amy EvansHow to Create Change
September 25, 2024
