Are you a technology exec? Join us for practical insights and wisdom from a 4x CTO in Private Equity, Enterprise and Startups. We have great guests that are absolutely crushing it and want to share their experiences, playbooks, best practices and key insights with other top leaders. <br/><br/><a href="https://newsletter.technocratic.io?utm_medium=podcast">newsletter.technocratic.io</a>
Technocratic Podcast
Claim This Podcastby For technology execs by technology execs.
42 episodes
Updated Daily
Accepts GuestsHas Sponsors
Podcast Overview
Are you a technology exec? Join us for practical insights and wisdom from a 4x CTO in Private Equity, Enterprise and Startups. We have great guests that are absolutely crushing it and want to share their experiences, playbooks, best practices and key insights with other top leaders. <br/><br/><a href="https://newsletter.technocratic.io?utm_medium=podcast">newsletter.technocratic.io</a>
Language
🇺🇲
Publishing Since
7/10/2024
1 verified contact email on file for Technocratic Podcast
Pitch yourself as a guest, propose sponsorships, or reach out directly to the host.
Recent Episodes
July 16, 2026
You 3x'd engineering...but how's your roadmap?
<p>Steve Taplin “sells” engineers for a living.But lately, he’s telling most of his clients the same thing…</p><p>“You don’t need more of them.”</p><p>Taplin runs a software engineering firm. His clients call him when something is broken — seven years into a roadmap, nothing shipping…</p><p>Much of the time, it’s a CEO who wants to know what’s wrong with the engineering team. In more and more cases, after spending a few days on site, he ends up giving them the same answer: engineering isn’t the problem.</p><p><strong>That is an unusual thing to say when you sell engineering capacity for a living.</strong></p><p>But that’s what makes Steve so trustworthy.</p><p>If engineering isn’t the problem — then what is?</p><p>Here’s how Steve puts it: Engineering is the only function that really adopted AI. The coding assistants work. Teams are faster. The gains are real.</p><p>But shipping software takes two things: deciding what to build, and building it. <strong>AI made the building fast. It did nothing for the deciding.</strong></p><p>The bottleneck didn’t go away. It just moved upstream, to product.</p><p>I’ve seen this in my own work: a CTO runs a genuinely good AI program. Then their engineers run out of things to do. Velocity gains only make a difference when there’s a next thing in the queue. </p><p>It’s easy to clock a review queue back up. But no one’s measuring when a product team fails to make a decision. </p><p>Product may need to catch up. But there’s still plenty of opportunity for Engineering to push forward.</p><p>We discuss what those opportunities are and how to execute on them — including these <strong>three items that are worth getting started on </strong><strong>this week: </strong></p><p>* <strong>Review your backlog.</strong> When Steve ran this exercise with a recent client, the measure that came back was 14 years<strong>.</strong> That number is not an engineering capacity problem…we discuss what it is and what comes next.</p><p>* <strong>Cap how much of your code AI writes.</strong> With insider access across dozens of organizations, Steve’s found there is something of a “magic number.”</p><p>* <strong>Flip how you train engineers on AI.</strong> For the vast majority of teams, AI writes code → Engineer tests it. Steve’s teams flip it. And get consistently better results.</p><p></p><p><strong>Also in the full episode:</strong></p><p>* <strong>Why I don’t believe AI costs are ever coming down.</strong> We were sold this exact promise fifteen years ago and it wasn’t true then either.</p><p>* <strong>The tech debt surprise:</strong> why some engineering leaders are suddenly less worried about their legacy code than they were a year ago.</p><p>And then there’s the central debate — and I want you guys to weigh in on it…</p><p>Steve says product is starved. It never got the tools engineering got. He wants the person closest to the customer writing the requirements.</p><p>I think the opposite. In a $100M company, most of product management is coordination. AI now writes the requirements and builds the prototypes. What’s left of the job is talking to customers and picking which problems to solve…let engineering absorb the rest.</p><p>Tell me what you guys think — settle it for us. </p><p><p>Steve and I have gotten into it before. Hear another heated conversation — this time about CTO Leadership - on the Software Leaders Uncensored Podcast.</p></p><p></p><p>Steve, thanks for joining me.</p><p>This was a particularly fun conversation — and I suspect we’ll be revisiting some of these core discussion points as things unfold.</p><p>About Steve</p><p>Steve Taplin is founder and CEO of <a target="_blank" href="https://sonatafy.com/"><strong>Sonatafy Technology</strong></a>, a software delivery firm with engineering teams across the US and Latin America, which means he spends most of his working life inside other companies’ delivery problems.</p><p>He is co-author of <a target="_blank" href="https://thebacklogillusion.com/">The Backlog Illusion</a>, written with Sonatafy CTO Chris Horvat, and author of <a target="_blank" href="https://www.amazon.com/Fail-Hard-Win-Big-Ventures/dp/B0FFWC64S3">Fail Hard, Win Big</a>.</p><p>Steve also hosts <a target="_blank" href="https://www.youtube.com/@SoftwareLeadersUncensored"><strong>Software Leaders Uncensored</strong></a> — a podcast that features close to 200 conversations with CIOs, CTOs and engineering leaders. </p><p><a target="_blank" href="https://www.linkedin.com/in/stevetaplin/">Connect with Steve on LinkedIn: linkedin.com/in/stevetaplin</a></p> <br/><br/>This is a public episode. If you'd like to discuss this with other subscribers or get access to bonus episodes, visit <a href="https://newsletter.technocratic.io/subscribe?utm_medium=podcast&utm_campaign=CTA_2">newsletter.technocratic.io/subscribe</a>
July 4, 2026
July 4th Listen: Escape the Chaos of Product, Engineering & AI
<p>In this episode of Technocratic, I speak with <a target="_blank" href="https://www.linkedin.com/in/edwardstracy/"><strong>Tracy Edwards</strong></a>, a highly experienced product and technology executive, about the messy reality of aligning product, engineering, and business outcomes in the AI era. </p><p>The conversation starts with a problem almost every technology organization knows too well: teams are busy, roadmaps are full, JIRA is active, velocity charts look impressive — but the business is still asking, “Why didn’t you move the needle?”</p><p>Tracy brings a practical operator’s view to the conversation, breaking down why engineering and product so often drift apart, why too many OKRs create noise instead of focus, and why roadmap capacity has to be treated like a strategic asset. </p><p>She also shares a simple but powerful way to think about engineering investment, greenfield innovation, optimization, and maintenance.</p><p>We also discuss AI’s impact on product & engineering, where Tracy cuts through the hype with a line every executive should hear: AI is not a strategy. It is a tool. </p><p>We explore why faster coding does not automatically mean better product output, why companies are struggling to measure AI productivity, and why the real breakthrough may not be “doing the same work faster,” but redesigning entire workflows. </p><p>We also get into <strong>taste, judgment, and why product leaders still need to know which problems are worth solving</strong> in the first place.</p><p>I REALLY liked this episode, Tracy was so on the money with everything, and I think you’ll enjoy it.</p><p>—Bobby 🇺🇸</p><p>Quick Links</p><p>You can find more on Tracy at LinkedIn:</p><p>* <a target="_blank" href="https://www.linkedin.com/in/edwardstracy/">https://www.linkedin.com/in/edwardstracy/</a></p><p>And more on Bobby here:</p><p>* <a target="_blank" href="https://www.linkedin.com/in/bobby-tahir/">https://www.linkedin.com/in/bobby-tahir/</a></p><p>If you want to be a guest on Technoratic or host Bobby on your podcast, please contact us at: bobby@technocratic.io</p> <br/><br/>This is a public episode. If you'd like to discuss this with other subscribers or get access to bonus episodes, visit <a href="https://newsletter.technocratic.io/subscribe?utm_medium=podcast&utm_campaign=CTA_2">newsletter.technocratic.io/subscribe</a>
June 8, 2026
Why Faster Engineering Hasn’t Touched Your Roadmap
<p>Chanille Juneau oversees product, engineering, security, DevOps, and QA for Accumulus, a platform that exchanges confidential data between the world’s largest drug makers and regulators in 75+ countries. She’s never written a line of code. It doesn’t matter.</p><p><strong>The CPTO Role and AI Reward the Same Thing: Systems-Level Thinking</strong></p><p>A great CPTO doesn’t need dev experience. Chanille Juneau proves that. </p><p>CPTO is a systems role. The value comes from connecting domains rather than mastering any one of them: seeing how a product bet hits infrastructure cost, how an architecture call lands on support, how a security rule reshapes the roadmap. The hard problems live in those seams, and only someone holding the whole picture catches them in time. </p><p>Chanille points out how AI works the same way. If you want it to do something really well, it needs all the context. Feed it a thin slice and it produces confident work that doesn’t fit the system around it. The role and the technology reward the same scarce thing: whole-system context.</p><p><strong>You Only Move as Fast as Your Slowest Stage</strong></p><p>Engineering velocity is up 30, 50, 80 percent, and the roadmap still hasn’t moved. I hear it from CTOs constantly. The ship rate’s the same, but the bill’s getting bigger. </p><p>Shipping is a chain: requirements, story, code, QA, deploy, security, prod. You move only as fast as the slowest stage. Speed engineering up 80 percent while security sits at 20 - the whole system gains 20. The bottleneck just moves downstream.</p><p>So the fix is rebalancing the chain: add QA and security capacity where the work piles up, even if that means fewer engineers. More engineering seats won’t move it; that stage was probably never your constraint. AI ROI is a throughput problem. </p><p><strong>Judgment Is the Job Now</strong></p><p>AI amplifies whatever direction you give it. Point it at a sharp problem with clear context and it gets you somewhere good - fast. Point it at a vague one and it gets you somewhere bad just as quickly. You can’t hand it your product strategy and walk away. When AI can produce any output, the scarce input is judgment: knowing which problem to point it at, and why.</p><p>AI does junior-level work well, which tempts leaders to keep only seniors. Push that across the industry and you starve the pipeline that grows seniors in the first place. Judgment is the one thing you can’t automate, and cutting the junior ranks is how you stop building it.</p><p><strong>In the episode:</strong></p><p>* <strong>How to put AI features in front of customers</strong> who legally can’t switch them on yet, <strong>without slowing the sale or the rollout.</strong></p><p>* <strong>Why running out of AI credits actually points to success right now</strong> - and whether that bill ever comes back down.</p><p>* <strong>Why I think AI is making the hardest job in tech harder</strong>, not easier: three mandates landing on one person.</p><p>I’ve done this job. It’s the hardest in tech short of the CISO’s, and AI is making it harder. Chanille makes it seem doable, nonetheless.</p><p>Listen to the full episode to find out how.</p><p><strong>About Chanille Juneau</strong></p><p>Chanille Juneau is Chief Product and Technology Officer at Accumulus Technologies, the company spun out in 2025 to commercialize a platform that lets life sciences companies exchange data and submissions with regulators across 75+ countries in real time. She was previously Chief Technology Officer at Berry Appleman & Leiden, where the software her team built helped land the firm on Fast Company’s 2023 World’s Most Innovative Companies list. She came up through product, not engineering, and holds a degree in biomedical science she now puts to work in the industry she helps run.</p><p>Connect with Chanille: linkedin.com/in/chanille</p> <br/><br/>This is a public episode. If you'd like to discuss this with other subscribers or get access to bonus episodes, visit <a href="https://newsletter.technocratic.io/subscribe?utm_medium=podcast&utm_campaign=CTA_2">newsletter.technocratic.io/subscribe</a>
42 total episodes available
Deep-dive analytics for Technocratic Podcast
Frequently asked questions
Have a different question and can't find the answer you're looking for? Reach out to our support team by sending us an email and we'll get back to you as soon as we can.
- What is Technocratic Podcast?
- How often does this podcast release new episodes?
This podcast updates daily.
- Where can I listen to this podcast?
This podcast is available on 4 platforms including Apple Podcasts, Spotify, and more. You can also use the RSS feed directly.
- Does this podcast accept guests?
Yes, this podcast regularly features guests.
Legal Disclaimer
Pod Engine is not affiliated with, endorsed by, or officially connected with any of the podcasts displayed on this platform. We operate independently as a podcast discovery and analytics service.
All podcast artwork, thumbnails, and content displayed on this page are the property of their respective owners and are protected by applicable copyright laws. This includes, but is not limited to, podcast cover art, episode artwork, show descriptions, episode titles, transcripts, audio snippets, and any other content originating from the podcast creators or their licensors.
We display this content under fair use principles and/or implied license for the purpose of podcast discovery, information, and commentary. We make no claim of ownership over any podcast content, artwork, or related materials shown on this platform. All trademarks, service marks, and trade names are the property of their respective owners.
While we strive to ensure all content usage is properly authorized, if you are a rights holder and believe your content is being used inappropriately or without proper authorization, please contact us immediately at hey@podengine.ai for prompt review and appropriate action, which may include content removal or proper attribution.
By accessing and using this platform, you acknowledge and agree to respect all applicable copyright laws and intellectual property rights of content owners. Any unauthorized reproduction, distribution, or commercial use of the content displayed on this platform is strictly prohibited.