Dr. Darren Pulsipher
45 episodes listed below
Architecture before transformation theater.
Digital Transformation Architect treats transformation as architecture work, not tool selection. Through ODXA domains and the FORGE mapping method, Dr. Darren connects strategy, organizational behavior, digital platforms, data, and physical realities into decisions that can survive execution.
PRESS PLAY
Digital Transformation Architect takes digital change out of the buzzword layer and treats it as an architecture problem. It is methodical. Dr. Darren works through ODXA as a way to connect strategy, organization, process, digital systems, and physical reality without letting any one layer pretend it is the whole picture. The series repeatedly returns to FORGE: find, observe, reconcile, ground, and enhance. That sequence gives the show its shape. First, identify what exists. Then map relationships. Then resolve conflicts, define what matters, and improve from there. The episodes are technical, but they are not abstract for abstraction's sake. SaaS platforms raise questions about backups, data location, service layers, and infrastructure that a buyer may not directly control. Edge systems behave differently from cloud systems because physical context changes what digital logic can actually support. Data centers in different regions carry different operational, compliance, and uptime implications. Organizational design gets the same treatment. Personas, roles, responsibilities, skills, feedback loops, and communication channels become architecture concerns because they determine how strategy moves through the company. Silos are framed as structural symptoms, not just cultural annoyances. Roadmaps, value streams, capabilities, and architectural intent are presented as the connective tissue between aspiration and execution. The show is strongest when it slows down over a distinction that many transformation programs blur: a tool is not a platform strategy, a platform is not automatically resilient, and a strategy is not executable until constraints and priorities are mapped. It has a lecture-like rhythm. Points are repeated, corrected, and restated until the framework becomes usable. That makes the listening experience dense but grounded. The best fit is a listener who wants transformation decisions to be traceable, defensible, and easier to debug in the real world. Digital Transformation Architect is not selling novelty. It is building a disciplined vocabulary for change that has to last.
Made for: Built for transformation leaders, enterprise architects, technology executives, and operators responsible for connecting strategy to execution. It especially suits listeners who need structured language for dependencies, governance, platforms, data, organizational alignment, and physical constraints.
What sets it apart: The show stands apart by treating digital transformation as a mapped system of domains and layers rather than a parade of tools or trends. Its repeated use of ODXA and FORGE gives listeners a practical architecture grammar for spotting gaps before they become execution failures.
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 align…
Architecture diagrams become guardrails here, so your transformation plan has fewer places to hide.
Press play if you want
Short reviews from the PlayNext desk, based on the episodes we processed.
A clear people-first guide to organizational layers, communication flows, and the structure needed to support change.
Organizational design is framed here as the people-centered architecture of digital transformation. Dr. Darren lays out ODXA's organizational domain through its working layers: stakeholders, personas, communication channels, roles and responsibilities, skills and competencies,…
Public-sector tech, told from the workplace.
Measured conversations on technology-led business change.
Workplace change, after the buzzwords fade.
Digital tools for real energy operations.
Cloud bills, outages and IoT, straight from Vervint's consultants.
Dr.
Digital Transformation Architect defines the physical domain as infrastructure, devices, locations, communication channels, and environmental conditions.
Digital Transformation Architect argues that digital transformation cannot stop at software because physical locations, devices, infrastructure, and environmental conditions affect outcomes.
Dr. Darren explains why the “one platform to rule them all” creates cascading failures and rigid application coupling.
Dr.
Dr.
Dr.
Dr.
Dr.
Digital Transformation Architect introduces ODXA's strategy domain as "mission control" for change across organizational, process, digital, and physical domains.
Dr.
Dr.