The CTO Podcast · Insights & Strategies for Chief Technology Officers Navigating the C-Suite while Balancing Technical Strategy, Team Management, & Innovation

From Pragmatism to Pivot Tables: Navigating Leadership, Philosophy, and Data Mastery with Matt Van Itallie

·47 min·3 clips

Matt says code without coders is like a half-written novel without the novelist.

1. The CTO Podcast episode centers on Matt Van Itallie, founder and CEO of SEMA, and his work helping engineering leaders explain codebases to non-technical executives. 2. Etienne de Bruin hosts the conversation and frames SEMA as software for managing Gen AI in the SDLC and translating code into business language. 3. The episode asks how pragmatism, logic models, and data discipline help CTOs make better leadership decisions. 4. Matt says graduate school pulled him into philosophy after law training, including the history of treating law as a science. 5. He cites the American pragmatist tradition from the late 1800s and says outcomes matter more than what simply "makes sense." 6. Matt uses "competing canons of construction" to show that opposite aphorisms can both sound right. 7. He gives a small-claims mediation example where A-B-B-A and A-B-A-B both feel fair, which shows how the brain can generate two contradictory but persuasive logics. 8. Matt says a logic model should separate resources, activities, outputs, and outcomes when teams argue about priorities. 9. He says code quality and non-functional requirements can be important outputs, but they are not outcomes. 10. He suggests that conflict can be useful when teams discover they are pursuing different outcomes or trust has broken down. 11. Matt recommends a judgment-free exercise where each side writes a logic model, then asks only clarifying questions before debating. 12. He says organizations should test reversible decisions and revisit likelihoods after two, four, or eight weeks. 13. He argues that every person on an org chart should be able to trace their work to an output that drives an outcome. 14. Matt says pragmatism means serving the organization’s goals rather than vanity metrics or actions that merely feel right. 15. He contrasts pragmatism with originalism in law and says, outside law, a values-based approach can sometimes play the opposite role. 16. He says SEMA sets five core principles early and believes a small company should not rely on a collaborative values exercise. 17. The tone stays analytical and conversational, with Etienne pressing for examples while Matt answers in long, structured explanations. 18. The episode also turns playful when Matt talks about pivot tables, hotel-room learning at age 22, and an open offer to run a BYOB virtual demo. 19. People who lead engineering teams, manage CTO conflict, or care about code metrics will get the most from this episode. 20. Listeners looking for a light, purely technical chat about software tooling may skip it.

Listen to the show on

Apple Podcasts Spotify

Play clips from this episode More from The CTO Podcast