Are we asking ourselves an honest question about who really owns automation inside a business anymore?
In my conversation with Darin Patterson, Vice President of Market Strategy at Make, we explore what happens when speed becomes the default requirement, but visibility and structure fail to keep up.
Make has become a breakout platform for teams that want to build automated workflows without writing code, and now, with AI agents joining the mix, the stakes feel even higher. Darin talks candidly about the tension between empowerment and chaos, especially in organizations that embraced no-code tools fast and early, only to discover that automation can quietly turn into sprawl if left unchecked.
What struck me most is how strongly Darin challenges the idea that documentation alone can save modern IT teams. He argues that traditional monitoring tools and workflow documentation are breaking down under the weight of constant iteration.
That’s where Make Grid comes in. Make Grid creates an auto-generated, real-time visual map of a company’s automation ecosystem, something Darin describes as a turning point for governance.
He explains why this matters now, not later. As companies deploy AI into processes that were once the province of specialists, Grid provides a shared lens for understanding what is running, who built it, and where dependencies exist. It’s an answer to a problem many IT leaders are reluctant to admit publicly, that automation systems often grow faster than oversight systems ever could.
Darin also offers a refreshingly grounded take on the psychology of ambitious teams. He talks about the need to prevent “no-code anarchy,” a phrase I’ve heard whispered at conferences, but rarely unpacked with clarity.
His view is simple: trust teams to build, but give them shared maps, guardrails, and governance that don’t slow them down. That balance between autonomy and oversight becomes even more meaningful when AI is introduced into workflows that touch security, IT performance, and cross-team accountability.
Make Grid attempts to address that balance by visually showing the automation architecture, even when internal documentation has gone stale.
So here’s the question I want to leave you with: if AI agents can now design, connect, and deploy workflows across an organization, what role will visual governance play in keeping businesses both fast and accountable? And what does good oversight look like when humans are no longer the only builders in the system?
Useful Links
Subscribe to the Tech Talks Daily Podcast
