Digital Transformation Architect

Digital Transformation Architect is the canonical architecture podcast for leaders who need transformation decisions to last. Hosted by Dr. Darren Pulsipher, the show applies the Open Digital Transformation Architecture (ODXA) to help organizations navigate digital change across people, process, and technology. Each episode focuses on architectural thinking—examining tradeoffs, dependencies, governance, and long-term impacts—so listeners can move beyond trends and tools toward durable outcomes. Whether you’re a CIO, enterprise architect, policymaker, or transformation leader, Digital Transformation Architect provides a structured, domain-driven approach to designing transformation that aligns strategy, operations, and technology at scale.

Digital Transformation Architect is a business podcast hosted by Unknown Host, with 29 episodes on record and a Required Pod Score of 80. PitchCentric scores this show on Booking Probability, Listen Score, and live audience signals refreshed every 24 hours.

Unknown Host hosts Digital Transformation Architect, a business show with 29 episodes published.

Our AI reads these to draft pitches. Use them as grounding for a pitch that cites a real guest and a specific topic.

• 

  Episode #377

  #377 Cloud War Games for Executive Readiness

  Aug 17, 202627 min

  Cloud outages, cybersecurity incidents, and high-pressure decision-making can make even experienced teams freeze. Dr. Darren welcomes Matt Lea, AWS consultant and creator of Cloud War Games, to explore how simulated outages, gamified cloud training, and scenario-based exercises help leaders build resilience, improve collaboration, and reduce risk before a real crisis hits. Tailoring these simulations to different organizational sizes and cloud setups ensures relevance and effectiveness for diverse teams. ## Key Takeaways - Passive training often fails to prepare teams for real-world outages; simulated pressure reveals how people actually respond, helping them feel more confident and supported in their readiness. - Cloud war games can help teams practice misconfigurations, ransomware attacks, and other outage scenarios in a controlled environment. - These exercises are useful not only for training, but also for hiring and assessing soft skills like communication, collaboration, and calm under pressure. - Cross-training is critical: if only one person knows how a system works, that creates a dangerous single point of failure. - Gamifying cloud and cybersecurity concepts can make learning more engaging, especially for non-technical audiences and future builders, encouraging enthusiasm and active participation. - Technical resilience is a leadership issue, not just an engineering one—teams should rehearse failure before it happens so that leaders can inspire confidence and preparedness. ## Chapters - 00:00 Opening story: outages and pressure - 01:10 Meet Matt and his AWS background - 03:00 From boring training to cloud war games - 05:10 Simulated outages and ransomware scenarios - 07:20 Team collaboration under stress - 09:10 Why interviewing through gameplay works - 10:40 Building the Tech Debt game on Steam - 13:10 Teaching cloud and security basics through play - 15:00 FinOps, leadership, and technical resilience - 16:40 The trucking factor and cross-training - 18:20 Final thoughts and where to find Matt

  ListenShow Notes
• 

  Episode #376

  #376 Vibe Coding Still Needs Architects

  Aug 12, 202631 min

  AI can turn a rough idea into a working prototype fast—but can it make that prototype production-ready? Host Dr. Darren speaks with Konstantin Klyagin about why **vibe coding** is powerful for innovation, yet still needs **software architects, security, testing, and business logic** to become real-world software that enterprise teams can trust. ## Key Takeaways - **Vibe coding is great for prototypes**, especially when nontechnical teams want to validate an idea quickly. - **Production software still needs architecture**: security, maintainability, reliability, and clear system design can’t be skipped. - **AI-generated code often misses edge cases**, error handling, permissions, and dependency management unless you guide it carefully. - **Subject matter expertise matters more than ever**—AI can generate syntax, but humans must define requirements, tradeoffs, and release criteria. - **The role of developers is shifting** from writing every line of code to reviewing, governing, and productizing AI-assisted software. - **Testing and QA remain essential** before anything goes live, especially for customer-facing or business-critical systems. ## Chapters - **00:00** Vibe coding, prototypes, and production risk - **02:14** Konstantin's early programming background - **05:36** From self-taught coder to software agency founder - **08:10** Why vibe coding is a tool, not a replacement - **10:18** Bridging business teams and engineering with AI - **12:22** Turning customer prototypes into production software - **15:08** Why architects still matter in an AI-driven workflow - **18:03** Common vibe coding mistakes: security, edge cases, and tests - **21:14** How AI models inherit code quality from training data - **23:40** The future of software engineering and talent strategy - **26:10** QA, testing, and release readiness in the AI era - **28:05** Where to find Konstantin and learn more

  ListenShow Notes
• 

  Episode #26

  Physical Constraints and Failure Modes

  Aug 12, 202613 min

  Summary

  ListenShow Notes
• 

  Episode #23

  Platforms and Data as Strategic Assets

  Jun 23, 202618 min

  In this episode, we explore why platforms and data must be treated as strategic enterprise assets, not just technical infrastructure. The discussion highlights how strong governance, clear architectural boundaries, and shared capabilities create reuse, consistency, scale, and resilience across the organization. We also examine why fragmented platform sprawl creates duplication and complexity, why governed data is essential for trusted decision-making, and how AI depends on these foundations to deliver real value. Security is part of the architecture from the start, making this a practical conversation about building digital transformation on durable, enterprise-ready foundations.

  ListenShow Notes
• 

  Episode #22

  Why Application-Centric Thinking Fails

  Jun 18, 202617 min

  Summary

  ListenShow Notes

Recent guests on Digital Transformation Architect. Study who booked and why before you pitch.

Based on semantic analysis of episode topics and host coverage, this show is a strong guest fit for executives in:

Industry fit is computed by PitchCentric using vector embeddings of the show's episode catalog.