
Sign up to save your podcasts
Or


Adam Creeger is the CTO of Slate and creator of iLoom (pronounced “il-LOOM”). His leadership experience at Meta, Greenhouse, and Frame.io not only informs Slate’s transformation into an AI-native organization, but also shapes the way AI influences product strategy, engineering workflows, and operational models.
Throughout his conversation with Sean and Dan, Adam argues that becoming AI native is not about layering AI features onto existing products. Instead, it requires companies to rethink how software is designed, built, and operated – from the ground up. His perspective offers a practical framework for product leaders navigating AI-driven transformation.
Here’s what else we learned:
‘AI Native’ Requires Organizational Reinvention
AI native organizations are willing to rethink every layer of their business, Adam says. Rather than adding AI features superficially, AI native organizations redesign workflows, team structures, and customer experiences around AI capabilities. He emphasized that AI transformation changes not only products, but also how people contribute inside organizations.
“To be AI native requires this deep exercise in re-imagination and not just imagination,” Adam continues. “In an AI native company – from the day-to-day operations to the ‘who does what’ – the roles and the owners of things are going to look very different.”
AI is expanding participation across teams, enabling designers, support teams, and non-engineers to contribute directly to product delivery. That shift signals a major change for modern software organizations.
AI and the Future of the Software Development Life Cycle (SDLC)
Our conversation then turned to an exploration of how AI is already changing the traditional software development lifecycle. Years ago, Agile development emerged because humans had historically struggled to fully reason through complex systems before implementation.
“I’ve realized that Agile was really a mitigation of a few things, mostly that we humans are limited in our abilities to reason through abstract concepts,” Adam says. “So when we thought about a software project, we didn’t have the ability to see around corners and understand the problems we’d face – until it was real, until you really started playing with it.
Turns out that many of those challenges are very solvable by AI, allowing us to go much deeper into the problem space without ever writing a line of code. In addition, AI-assisted planning allows teams to revisit some waterfall-style thinking, but with dramatically faster iteration and validation cycles.
Product Managers’ New Role: Communicate Context
Importantly, AI is actually elevating the role of product managers, Adam offers. Rather than acting primarily as tactical decision-makers, product leaders can (and should) focus on providing context that enables teams to make informed decisions independently.
“More than ever, the product manager has become a role about providing context,” he adds. “PMs should be elevated to a much more strategic role, understanding the long-term vision and helping to translate that to engineers.”
Adam also feels that PMs should be using AI to communicate ideas about the product vision much more effectively. That evolution creates a faster and more collaborative product environment. Teams can evaluate real implementations earlier, gather customer feedback sooner, and align around outcomes instead of specifications alone.
The post 187 / AI Native: Reimagining Product Roles and Development Cycles, with Adam Creeger appeared first on ITX Corp..
By ITX Corp.5
3131 ratings
Adam Creeger is the CTO of Slate and creator of iLoom (pronounced “il-LOOM”). His leadership experience at Meta, Greenhouse, and Frame.io not only informs Slate’s transformation into an AI-native organization, but also shapes the way AI influences product strategy, engineering workflows, and operational models.
Throughout his conversation with Sean and Dan, Adam argues that becoming AI native is not about layering AI features onto existing products. Instead, it requires companies to rethink how software is designed, built, and operated – from the ground up. His perspective offers a practical framework for product leaders navigating AI-driven transformation.
Here’s what else we learned:
‘AI Native’ Requires Organizational Reinvention
AI native organizations are willing to rethink every layer of their business, Adam says. Rather than adding AI features superficially, AI native organizations redesign workflows, team structures, and customer experiences around AI capabilities. He emphasized that AI transformation changes not only products, but also how people contribute inside organizations.
“To be AI native requires this deep exercise in re-imagination and not just imagination,” Adam continues. “In an AI native company – from the day-to-day operations to the ‘who does what’ – the roles and the owners of things are going to look very different.”
AI is expanding participation across teams, enabling designers, support teams, and non-engineers to contribute directly to product delivery. That shift signals a major change for modern software organizations.
AI and the Future of the Software Development Life Cycle (SDLC)
Our conversation then turned to an exploration of how AI is already changing the traditional software development lifecycle. Years ago, Agile development emerged because humans had historically struggled to fully reason through complex systems before implementation.
“I’ve realized that Agile was really a mitigation of a few things, mostly that we humans are limited in our abilities to reason through abstract concepts,” Adam says. “So when we thought about a software project, we didn’t have the ability to see around corners and understand the problems we’d face – until it was real, until you really started playing with it.
Turns out that many of those challenges are very solvable by AI, allowing us to go much deeper into the problem space without ever writing a line of code. In addition, AI-assisted planning allows teams to revisit some waterfall-style thinking, but with dramatically faster iteration and validation cycles.
Product Managers’ New Role: Communicate Context
Importantly, AI is actually elevating the role of product managers, Adam offers. Rather than acting primarily as tactical decision-makers, product leaders can (and should) focus on providing context that enables teams to make informed decisions independently.
“More than ever, the product manager has become a role about providing context,” he adds. “PMs should be elevated to a much more strategic role, understanding the long-term vision and helping to translate that to engineers.”
Adam also feels that PMs should be using AI to communicate ideas about the product vision much more effectively. That evolution creates a faster and more collaborative product environment. Teams can evaluate real implementations earlier, gather customer feedback sooner, and align around outcomes instead of specifications alone.
The post 187 / AI Native: Reimagining Product Roles and Development Cycles, with Adam Creeger appeared first on ITX Corp..

111,948 Listeners

9,113 Listeners

148 Listeners