Is your IT operation ready for AI agents? Not chatbots. Not automation
rules. Actual agents that observe, plan, and act on their own.

In this episode of The Wired Garage with Pops, Steele and Pops go
under the hood of Agentic AI in ITSM — breaking down how AI agents
are changing incident triage, change management, and CMDB health in
real IT environments.

🔧 What we cover:
- Why traditional ITSM automation is getting brittle
- How agentic AI thinks vs. how old automation rules work
- LIVE demo inside ServiceNow AI Agent Studio
- 3 real use cases: Incident Triage, Change Co-Pilot & CMDB Health
- Guardrails, blast radius, and why autonomy has to be earned
- The metrics that actually tell you if agents are working
- What executives are asking — and what IT leaders need to answer

💬 The quote that says it all:
"If you thought a bad process could run fast when automated...
wait until you add AI on top of that."

Whether you're in IT ops, running ServiceNow, leading a team, or just
trying to understand where AI is actually landing in the real world —
this one's for you.

🔔 Subscribe for more no-hype tech talk from the garage.

📩 Got a story or question? Send it our way.

⏱️ Chapters:
- Welcome to The Wired Garage
- What Is ITSM Really?
- Why ITSM Still Struggles
- Why Old Automation Gets Brittle
- Agentic AI: Observe, Plan, Act
- Guardrails: Data, Scope & Autonomy
- Recommendation → Supervised → Autonomous
- Controlling the Blast Radius
- Specialized Agents vs. One Superstar
- Use Case #1: Agentic Incident Triage
- LIVE DEMO: AI Agent Studio in ServiceNow
- Use Case #2: Change Management Co-Pilot
- Use Case #3: Agentic CMDB Health
- Measuring CMDB Health Before & After
- How Executives Are Responding
- Metrics That Actually Matter
- Pitfalls & Guardrail Failures
- How to Prepare Your Team
- Rapid Fire Takeaways

#AgenticAI #ITSM #ServiceNow #ITAutomation #AIAgents #CMDB
#ChangeManagement #ITLeadership #WiredGarageWithPops #ArtificialIntelligence

Support the show

This episode of The Wired Garage with Pops is a roundtable with three “recovering” enterprise architects discussing what enterprise architecture really looks like in practice over a career. They frame EA less as a job title and more as a mindset that bridges business strategy with the messy reality of technology, legacy systems, and organizational behavior. The conversation covers recognizing “messy” enterprises, saying no (or “not yet”) to cool tech like AI and new platforms, governance and decision frameworks, empathy and frontline experience, and how their beliefs and communication styles have evolved.

• EA is a mindset, not a title. You don’t stop being an architect when the job title changes; it’s a way of thinking that follows you into leadership, platform ownership, and solution delivery. Architecture is as much about people, context, timing, and decisions as it is about diagrams and standards.
• What makes an enterprise “messy”? “Messy” isn’t just lots of tech; it’s unclear decision-making, weak governance, overlapping tools, and skills spread too thin across too many platforms. Mergers, half-in/half-out cloud moves, redundant monitoring tools, and fragmented information repositories all contribute to mess over time, often from good intentions. A clean decision structure and a clear plan can coexist with temporary mess; the real danger is unmanaged complexity and poor visibility, especially for security.
• Role of the architect: giraffe, not wizard. A good architect is like a giraffe on safari: they see farther, spot danger early, and buy the organization time to choose options instead of reacting in panic. The value is in anticipating issues, proposing options (hybrid models, phased approaches), and structuring decisions so mess is prevented or at least contained.
• Saying “no” (or “how”) to cool tech. Often the right call is to say “not yet” to AI, new SaaS, or hot platforms when knowledge management, data quality, or operating models aren’t ready. The architect’s job isn’t simply “no”; it’s reframing the conversation to “how do we get there?” with a realistic path, timeline, and alignment to business priorities. Start with business outcomes and capabilities, then choose solutions and platforms last; starting from tools locks you in and reduces long-term flexibility.
• Governance, frameworks, and alignment. Using themes, epics, and idea portals helps ensure every piece of work ties back to business strategy and prevents scattered, one-off projects. Any governance framework can work, but the critical part is using it consistently so decisions are traceable and you can understand and revisit past choices. Feedback loops and organizational change management are needed early and often, so you can see how decisions play out (e.g., a 3‑day install becoming 14).
• Empathy, communication, and frontline experience. They stress empathy: everything in IT is in service to someone, and it’s easy to forget that if you never see real users. Frontline roles (help desk, service desk, customer success) are invaluable; going back periodically keeps you grounded in how people actually experience your systems. One example: a CMDB/CSDM explanation was reframed as a ballet analogy tailored to an executive’s interests, which made the concept finally stick. Great architects practice empathetic storytelling—knowing the audience, choosing the right narrative, and over-communicating during change.
• Avoiding “villain” status between business and IT. Architects often sit between business leaders demanding outcomes and IT teams building and running systems, which can make them the perceived “villain.” Transparency in how decisions are made, involving engineers early, and allowing people to see and participate in the conversation builds trust even when the ans

Support the show

S1E29 A Candid Conversation on Life, Leadership, and the Stories Behind a Global CEO with Chad Mattix
This episode of The Wired Garage with Pops features Chad Mattix, founder and CEO of Kinnetix, an IT field services company supporting customers around the world. Chad shares how an entrepreneurial childhood, a paper route, and early exposure to ham radio and custom PC building with his father set the foundation for his career in technology and business. He walks through, starting his first company as a Miami University junior, scaling through law firms and regional clients, navigating tough economic cycles, and learning to balance risk, integrity, and perseverance as a leader. The conversation also explores the human side of entrepreneurship—marriage, family, grief, faith, friendship, travel, cigars, bourbon, and shared rituals that keep him grounded while leading teams across multiple cultures and countries.

Keywords: leadership, entrepreneurship, personal growth, mentorship, family, technology, business challenges, networking, resilience, life lessons
​
SEO-friendly keywords: The Wired Garage with Pops podcast, ​Chad Mattix interview, Kinnetix IT field services, Entrepreneurial leadership story, Building a values-driven company, Leading teams across cultures, Handling failure as a founder, Perseverance and resilience in business, Work–life balance for entrepreneurs, Mentors and role models in tech, Miami University entrepreneurship story, Law firm technology and WordPerfect history, Family fatherhood and legacy, Faith and returning to church, Cigars and bourbon conversations, Travel, F1, and bucket-list experiences
​
Key Takeaways

• Failure as an efficient teacher
• Chad reframes failure as an “efficient” way to learn, especially when you strip out emotion, ask whether the idea was structured wrong, and iterate quickly instead of getting stuck.
• Many people let one big failure become their permanent stopping point; disrupting that narrative is essential to keep growing.

Support the show