1362696955
You've Been Heard

Advertise on podcast: You've Been Heard

Rating
★★★★★
4.9
from
51 reviews
This podcast has
478 episodes
Language
English
Explicit
No
Date created
2018/03/22
Latest episode
2026/11/17
Average duration
62 min.
Release period
4 days

Description

Having a seat at the table. Nice. Being heard? Nicer. For decades, IT leaders have been the backbone of defensible business growth, solving problems that could cripple a business often before anyone noticed. We know this world. The late nights. The firefights. The impossible deadlines that somehow got met. IT Professionals don’t just fix. They fortify. They’re the frontline heroes fighting an improbable battle thriving where others break, armed with a resilience the strongest military leaders consider simply another day safeguarding the world. When things get rough, you’re indispensable. When everything’s humming like a well-oiled Tesla, you’re the hidden engine of progress, often asked to do the extraordinary. And one of the toughest parts? Being hunted by short-term sales reps chasing quotas, pushing shiny solutions they “know” you need… but you know you don’t. What if you could work with those who have sat in your seat, been precisely where you are? You can. That’s right: We’ve been there. Negotiating partnerships, being pitched by vendors across the table, and standing on the frontlines of IT. That’s why we built a platform where IT leaders are amplified, not sidelined. Not just “another platform.” In fact, three in one. A triple-threat to the industry norm. Doing to IT what the iPhone did to the Blackberry redefining the game (and expectations) forever. And to be clear, we refuse to be part of the “Hype Cycle” and inflated expectations. Which is why we’ve perfected a proven model that elevates you, the IT leader. Just ask our clients. The first piece? A podcast, not just a show. A platform where IT pros share hard-earned truths, not corporate scripts. The second piece? A community where peers (real ones) have sophisticated conversations—without vendors lurking in the corner. The final component? An advisory with only one agenda: your performance and sanity, so you make smarter vetted choices without the sales circus. Think of us as your backstage pass to whoever you need to meet to eliminate headaches and accelerate resolutions. The kind of exclusive pass that gains you access to our ecosystem with $1.2 billion in buying power. When we knock, the door’s already unlocked. And here’s the kicker: We make vendors fund your success. What about vendor-neutrality? If we were any more neutral, we’d be beige. Our triple-threat model doesn’t just transform how we do business. It transforms the impact you have on a day-to-day basis and on a year-over-year basis. It’s how you balance innovation with stability. Where you not only have a seat at the table, but get invited to speak. And be listened to. And there’s one final point that makes everything work: We don’t disappear when you need us. Ever. We stay. We escalate. We stand with you. We are anti-spin. Anti-transactional. Pro-IT leader. Your resilience is our resilience. Because when IT leaders rise… so does everything else. Welcome to the platform. Welcome to the movement. Join the next wave of IT leadership. Welcome to You’ve Been Heard. *****DISCLAIMER***** All views, opinions, and statements made by guests on this show do not represent the beliefs of the host Phil Howard, or any entity whatsoever with which the show has been, is now, or will be affiliated. Any statements, views, random thoughts, or opinions expressed by the hosts and guests do not necessarily reflect the personal beliefs (could easily be misconstrued) and are not the official policy/position of our company, agency, podcast, and affiliated partners. Finally, because human beings are characteristically prone to flaws and mistakes, we warn all listeners to think critically for yourself and seek true knowledge before taking action upon anything.

Unlock You've Been Heard podcast Email contact info,
Listeners & Audience details

Email contact information

Direct podcast contact details

Listeners

Audience numbers & engagement insights

Audience details

Podcast Insights

Podcast episodes

Check latest episodes from You've Been Heard podcast


475- Lights Out IT w/Peter Hogan
2026/11/17
Peter Hogan, the 2024 St. Louis ORBIE Enterprise CIO of the Year, calls his approach lights out IT: automate as much as humanly possible and get rid of the tech debt, so your IT people can spend their time on business value. He walks through the three steps he uses to pair IT people with the business problems that move the needle, and the mobile site that taught him to get out in front of the business. Peter Hogan won the 2024 ORBIE for Enterprise CIO of the Year, and he gives the credit to his team at Compana: "My team. It had nothing to do with me." The story they told was IT unification. The company had acquired 13 or 14 brands or divisions and ran three or four IT departments, and Peter later took its six ERPs down to three, with two as the goal: "a big brother little brother model." Before that he was CTO at Post Holdings, where a decision science team and then a data science team saved "$188 million" in hard numbers between about 2015 and 2020, each one a project a business owner signed up for. His name for where IT should go is lights out IT. "Shift the focus away from support, operations, maintenance, automate as much as humanly possible. Reduce the complexity by getting rid of the tech debt." Then the people move into the business, and the test of a great business technologist is whether they can help write the business requirements document. He explains tech debt in money terms, down to the licenses on virtual machines nobody needs anymore, why he is an opex guy, and tells the story from Brown Shoe, now Caleres, around 2009: a vendor showed a three-page mobile site, the room stood up in applause, and two of his developers came back the next Monday with prototypes that went all the way through checkout. Then the framework. Peter gets to know every person on his team, asks business leaders for their toughest problems that aren't being worked, finds the person in each function who could partner with IT, and plays matchmaker, starting with quick wins because "it builds street cred." He also covers saying "not now" instead of no, the contract skills he learned at Mastercard, why he integrates the data first in M&A, and the company-wide AI training he ran after five months in a new job. His advice to his younger self: listen more. "Some of the best concepts I come up with, I don't really come up with. I'm connecting dots from what I'm hearing." Key takeaways: Put a number on your tech debt: every virtual machine you don't need still costs licenses and the IT time to support and patch it. Clean it up before the renewal, so the CFO sees the saving; Send your IT people to work one on one with their business partners, and pick a partner who will set them up to succeed, especially when they are introverts; Ask each business function leader for the problems that aren't being worked and would move the needle the most, then ask who on their team could partner with IT, and match the two; Start with the quick wins. They build the trust you need when you ask for the bigger investments; Show a working prototype instead of a slide. Business leaders often can't articulate a technology until someone puts it in front of them; Say "not now" before you say no, and put the idea back on the list in six months. Chapters: 00:00 Cold open, and the team that won the ORBIE 04:38 Tech debt nobody sees, in business terms 08:49 Opex, capex and the cloud 12:23 Business technologists and storytelling 17:34 The mobile site the room applauded 22:04 Two hats, and lights out IT 27:20 $188 million from decision science at Post 30:11 Three steps to pair IT with the business 42:13 Saying "not now," battle scars and contracts 48:47 Adaptability, and integrating the data first 56:15 Marketing your team's wins, and the company's AI story 68:26 Listen more, and the next IT leader
473- Go Live Is Just a Milestone w/Mahesh Adnani
2026/11/16
Mahesh Adnani, IT Director, Manufacturing Technology at Daltile, thought he was hired to build an MES and found a label printing system the tile lines could not run without, so he stabilized and documented it before changing anything. He and Phil Howard get into M&A day one, the MES he built at Coherent, the CFO game, and the IT leadership habit of measuring what happens after Go Live, because "Go Live is just a milestone." Mahesh Adnani joined Daltile expecting to build an MES system. What his team was running turned out to be "truly just a label printing solution," looked after by a team that attrition had taken from three people to one, with very little documentation left and business folks who told him "if this system stops working, we can't produce tiles." So he stabilized it first. A contractor documented the system end to end, the team reverse engineered the code in three months and took it back to the business, and a second developer brought the breakdown tickets down. Only then did he propose a simpler design, starting with a POC in the lab and one site before going big. He and Phil Howard start with M&A, where he has been on both sides. Day one "has nothing to do with technology": it is how executives connect to the network, and how one company's financials will map to the other's before the quarter closes. At Coherent, after acquiring Rofin, he saw that forcing every corporate rule on a lean site "might have killed those sites." He also walks through the MES he built there, "a global system used by 5,000 users every single day," which saved more than $2 million in IT cost and let process engineers run their own lean programs. In Phil's CFO game he translates multi-factor authentication, a Teams launch in the first weeks of COVID that also moved desk phone numbers onto salespeople's PCs, and invoice automation, where he leaves the headcount decision to the department owner. His playbook for real business outcomes: define the outcome in business terms, understand the actual work "without choosing a technology," deliver in increments, and measure the result, because "Go Live is just a milestone." On an ERP move he wants shipments back at their old levels 15 days after go-live, and if they sit at 60% or 70% he asks the project team what went wrong. He closes on transparency ("you will make long term friends if you are completely honest with them"), being on the floor when you go live, and the advice he'd give his younger self: "it's always better to give up what you know so that you can learn new things." Key takeaways: Before you change an inherited system, stabilize it: document what it does end to end, then take that back to the business and ask what you missed; Prove a new design with a POC in the lab and one site before you go big; Write each project's outcome in business terms, such as yield or risk, before anyone picks a technology; Set a number for after go-live, like shipments back to their old level 15 days later, and ask the project team what went wrong when it stalls; Tell the business up front what will get harder, and be on the floor with the users when you go live; Move people into business-facing IT jobs only when they can speak the business language and know the function they serve. Chapters: 00:00 Cold open: two types of developers 00:49 A resume on steroids, and tiles made in the US 02:18 M&A: what happens on day one 05:28 Two CIOs, and how hard to push an acquired site 10:54 The translator between executives and the site 12:25 Stabilize first: the label printing system 18:49 Machine data, and the MES that saved $2 million 24:14 IT leaders who speak the business language 29:57 The CFO game: MFA, Teams and invoice automation 39:11 The cost of not innovating, and ChatGPT 45:27 Go Live is just a milestone 49:52 Be transparent, be on the floor, give up what you know
472- You Don't Want to Automate Chaos w/Chris Stierle
2026/11/12
Chris Stierle, Chief Information Officer at TemperPack, has not found a viable use case for agentic AI in business process automation, and he explains why repeatable work and predictive models do not fit. He also gives CEOs the four things to understand before they hire an IT leader. Chris Stierle holds a four-digit CCIE, and he says the lab humbled him. What stayed with him is systems thinking: the value of any system is in the interconnects, not the entities. Phil puts it to the test with a game, asking him to explain a late collision to a CEO, then a network upgrade, then multi-factor authentication. Then AI. Chris treats it as the top abstraction layer on everything built over the last two to three decades, and says it will not scale without structured data. He has not found a viable use case for agentic AI in business process automation: agents are predictive, the work is repeatable, and the loops cost a lot of money. He is clear that this is about agentic AI for BPA, and that AI in manufacturing is a huge space. For the CEO hiring an IT leader, he names four pillars that connect: data architecture, cybersecurity, agile delivery and platform engineering. He uses agile data as a shield, not a sword, backs diversity of thought because he likes to win, and argues that the next move is to wrap bits around atoms. Key takeaways: Before you build an agent for a back-office process, check whether technology that has been around for five years already does it for less; Get your business processes in order first: you don't want to automate chaos; Build the structured data before you try to scale AI; agents without an enterprise data warehouse stay proofs of concept; When you interview an IT leader, ask about the things that are standard, and ask them to describe an ETL pipeline end to end; Consider a fractional executive when you need a new leader and want to see them in the role first; Use agile data to protect an overworked team and prioritize its backlog, not to go after people. Chapters: 00:00 Cold open 00:34 Meet Chris Stierle: the CCIE lab and big egos 04:04 The game: explain a late collision to a CEO 09:29 Systems thinking and why networks are the backbone 15:49 Not sold on agentic AI for BPA 23:43 The game reversed: network upgrade, integration, MFA 28:01 How a CEO knows they hired the right IT leader 31:29 The four pillars: data architecture and cybersecurity 36:21 Agile delivery: a shield, not a sword 44:48 Diversity of thought, because he likes to win 50:01 CapEx, OpEx and depreciation 54:38 Bits around atoms, and patience
471- From Code Black to No Outages w/Shane Froebel
2026/11/10
Shane Froebel, Chief Information Officer, joined a hospital as VP while it was losing its computer systems for four to six hours every week, and decided on his first day that fixing it was squarely on him. He explains the memo that stopped unreviewed production changes, the meetings that got a 50-person infrastructure team talking, and why he offers to be the reference for anyone on his team who wants to leave. Shane Froebel is a Chief Information Officer with more than 15 years of IT leadership. On his first day as VP at a hospital, sitting in orientation as the only VP in the room, he heard that the hospital had a code black every week: the computer systems went down for four to six hours, and staff were told it was nothing to be afraid of. His reaction: "That's going to be squarely on me and that's something I have to fix." He walks through the fix. He met with every one of the 50 people on his infrastructure team, rebuilt rapport with the doctors and nurses, and asked what the hospital was trying to do. Then he sent a memo: "Dear staff, as of today, you're not to make any more production changes without my express consent." It slowed the team down for a while, and he was fine with that: "I'd rather have no outages than outages." He explains the standing meetings that got the network, server, project management and service desk teams talking in a set order, because "the network builds on everything else." He also tells the story from his first hospital of equipment that was signed off as implemented and turned up in the storeroom, in boxes, still not even opened. The last part is about people. Shane translates cloud and scalability into business terms, using COVID as the example: when the hospital needed staff working from home, the software was already in place. He says IT leadership doesn't have to be the most technical person in the room, and he tells his team that if they want to leave, he'll be their reference and help them build the skills for the job they want. "The benefit of that, by the way, is not for people to leave, it's for people to stay." Key takeaways: Put every production change through one review until the outages stop, and tell the team up front it won't be forever; In your first weeks, meet everyone on your team one on one and ask what they think the problem is and where it could improve; Before you buy anything, walk the inventory: list what was bought, then go find it and check it was really implemented; Run your team meetings in a set order, starting with the teams everyone else depends on, so each team hears what's coming before its turn; Give people a direct line to you when there's a problem, and treat the quiet as the goal: "If I don't hear from you, that means everything is going good."; When someone wants to leave, offer to be their reference and help them build the skills for the role they're after. Chapters: 00:00 Cold open 00:46 From a Tandy 1000 at age 2 to IT leadership 05:08 Code black every week, and his first three moves 12:51 Resiliency, survivability, scalability, and keeping it simple 20:23 "Dear staff": no production changes without his consent 23:45 Signed off as implemented, still in the boxes 27:32 Winning respect one win at a time 35:49 Four teams and three standing meetings 48:34 No judgment: why every leader needs a safe person 56:17 What CIOs get wrong, and why infrastructure comes first 1:09:58 Translating cloud and scalability for the business 1:14:50 The one promise: I'll be your reference
470- Being 100% Correct Isn't Enough w/Devon Simmons
2026/11/09
Devon Simmons, an IT manager, learned that a solution can be technically correct in every aspect and still stall without a business case the C-suite can get behind. He thinks back to a four-site move from MPLS to SD-WAN on Cisco Meraki that got approved once he came back with the outages and the ROI, and explains why he asks where the data is going before anyone picks the next AI tool. Devon Simmons once brought the C-suite a network overhaul that was "technically correct in every aspect." Four sites were moving off MPLS to SD-WAN, on Cisco Meraki, with the option of two ISPs at the cost of one and the redundancy the sites badly needed. The room understood it to a degree, but they were looking at the pricing on the paper. So he went back to the drawing board, put the ROI next to the upfront costs, and brought the outages: multiple a week, while the company spent thousands and thousands of dollars a month on MPLS. The project went ahead in phases, firewalls and switches first, once the business case was right. "That being 100% correct definitely isn't enough." He opens on AI and data. The first question he hears is which AI tool to use, and nobody asks where the data is going. With a standard ChatGPT Pro subscription, he points out, you have to go into the settings and tell it not to train on your data. He wants AI subscriptions run through IT and the identity provider, without restricting anyone from the tools. He also shares how he connected Claude to their NetSuite ERP over MCP, and how it found a bug across several script deployments in an afternoon instead of a few days. Then the path that got him here: shutting down every display computer at Cons Electronics as a kid, applying to Geek Squad from 16 in a button-down shirt and tie, and getting in at about 19 or 20 with half an A+ from trade school. He tells his own kids A+ first, "without a shadow of a doubt." He tells the story of an ERP module he had to abandon and why he's never a fan of buying on the promise of updates later, why he asks vendors for customer references, why security should be more than a line item, and his advice to his younger self: keep your ear to the ground and never stop learning. Key takeaways: Before the first meeting, put the upfront cost next to the ROI. A solution the C-suite can't digest won't get approved, however correct it is; Bring the outage numbers and what the old circuits cost every month. For Devon, multiple outages a week against thousands a month on MPLS was the argument nobody could fight; If the whole ask is too big, phase it. He started with firewalls and switches, and the project was approved once the business case was presented properly; Don't buy a product on the promise of updates later. Ask the vendor to send the hardware so you can test it, and ask for a customer who uses the tool the way you would; Before you pick an AI tool, find out where your data goes. Check settings like ChatGPT's training option, and run subscriptions through IT and your identity provider instead of blocking people. Chapters: 00:00 Cold open 00:52 Where is our data going? 05:24 Claude, NetSuite and MCP 13:27 Being 100% correct isn't enough 14:41 Four sites, from MPLS to SD-WAN 21:14 Back to the drawing board: outages and ROI 27:29 From Compaq Presarios to Geek Squad 32:25 A+ first, then pick a path 39:24 Pulling the plug on an ERP module 46:19 Security is more than a line item 54:16 Keep your ear to the ground 1:02:38 Proper planning, and learning to communicate
469- Not Just the Break-Fix Guy w/Desi Rodriguez
2026/11/05
Desi Rodriguez, Director of Information Technology at Tilson Homes, says the IT leaders who get ahead learn how every other department works, so they don't come in like a wrecking ball. He explains how he answers vague AI requests with the question he once asked about SharePoint, and how he puts tech debt into hours of downtime for a CFO. Desi Rodriguez was eight years old, on a field trip to a sewage plant, when he got fixated on the bank of monitors in its NOC. From there he went through a Cisco Systems Network Academy pilot program in high school, an internship at AMD, a two-year degree from ITT Tech, State of Texas agencies and IBM, where he became a Citrix SME and spent six months in Bangalore training Citrix technicians. Then he answered a post for a systems administrator at Tilson Homes, a custom home builder in Texas, where he is now Director of Information Technology. It'll be 15 years in December. He has advised the company to hold its breath on AI until there are business justifications, from the executive committee or department by department. The requests he hears are very vague, and they take him back to SharePoint at the state: his bosses asked what it does, he asked what they wanted it to do, and nobody had a clear answer. On spend, he works from a daily dollar figure the accounting team and the C-suite worked out, what the company loses when it isn't running, and he puts tech debt into hours of downtime for the CFO. Respect is one of his top relational needs, and for him it means nobody keeps IT from knowing about an initiative and then expects his team to fix it when it doesn't work. His one lesson for other IT leaders is to learn how the other departments work and build relationships before you need them, down to talking trucks with a drafter at Home Depot. He closes with what he'd tell his younger self: be humble, and learn to say no respectfully and to the right people. Key takeaways: Learn how the other departments work before you change anything in them. You'll make smarter decisions about IT spend and direction, and ruffle fewer feathers; Build relationships before you need them, then ask the decision makers to help you pilot what's coming. You get more buy-in that way; When an AI request is vague, ask what they want it to do, and ask for business justifications before anyone buys licenses; Put tech debt into hours of downtime, so the business can turn it into money with its own daily figure; Tell other leaders, respectfully, that IT needs to know about an initiative before it's pushed through; Assume people may just not know. Give your team the reasons behind the rules, so they can say no with a clean, concise answer. Chapters: 00:00 Cold open 00:37 Meet Desi Rodriguez: from a NOC on a field trip to Tilson Homes 06:57 A resilient network for a seven-day-a-week shop 16:38 AI requests and the SharePoint loop 19:20 Cash flow, job costs and a first AI use case 27:51 Growing into new markets with a homegrown CRM 31:50 Relational values and "That's disrespectful" 40:17 Hiring for a passion for the industry 44:42 One talk for IT: learn how the business works 48:14 Getting past the fear: grace and a pink keyboard 51:14 Tech debt for a CFO: hours of downtime 54:33 Advice to his younger self: be humble, learn to say no
468- It's Usually Our Fault w/Alexandre Quinze
2026/11/03
Alexandre Quinze, former CIO for Latin America at Philips, says that when IT isn't heard, it's usually IT's own doing, and the way back starts with understanding the CFO's pains. He explains how he picked just enough technology for a startup heading to Series C, how he turns cyber risk into dollars with FAIR, and why an unlimited budget would go to changing people's behavior. Alexandre Quinze studied engineering with a sandwich degree at Seattle U, lived through Y2K and the dot-com bubble in Silicon Valley, and went on to work in Brazil, Germany and Mexico, at Flex, and at Philips as CIO for Latin America, based in Panama. His starting point is blunt: "it's usually our fault." Walk into a room of C-levels and talk bits and bytes, and nobody follows. A professor taught him early that you only have to understand the CFO well enough to understand the CFO's pains, so as an IT executive he did internships in every area, FP&A included. He never discusses ERP versions with stakeholders: "They don't care about that." He brings the examples. A startup getting ready for Series C ran on a simple version of QuickBooks while investors asked for a consolidated balance sheet; he proposed a month-end close and an FP&A tool first, then a middle-ground ERP instead of an SAP project that would cost millions. At a waterproofing company in Brazil that served 800,000 small shops, he asked how rain affected sales and which shelves were empty, then started with simple inventory capture so salespeople could go where there was no stock. His question for his teams: "do you want to be a donut shop or are you going to be a trusted advisor?" On security, he uses FAIR (factor analysis of information risk) to put a dollar amount on risk, like a SCADA network at a mining company, and he classifies the crown jewels and tags the data so AI can be used without the sensitive data leaving. He says 75% of incidents come from humans, and one phishing campaign he ran had a click-through rate close to 90%, so with an unlimited budget he would invest in behavior change. He closes with the doctors who held back from new technology, the Viking boat, and the advice he would give his younger self: study psychology. His bicycle model: the rear wheel is people's needs, the front wheel is their desires. Key takeaways: Learn enough of the CFO's world to understand the CFO's pains, like a negative cash flow or no visibility into the cash flow projection, and start the conversation there; Spend time inside other functions. Ask the CFO if you can sit close to FP&A and learn how it works; Keep ERP versions and application comparisons out of stakeholder conversations, and size the technology to the company now and three to five years out: just enough; Put cyber risk in dollars: lost hours, lost revenue, the cost of the fix, set against the investment that avoids them; Classify your crown jewels and tag the data, so people can use AI with the data you can afford to share and nothing else; Budget for behavior change, beyond the training: find the belief behind the resistance and give people a reason the change works for them Chapters: 00:00 Cold open 00:42 Meet Alexandre Quinze: Seattle U, Silicon Valley and Philips Latin America 02:59 When IT isn't heard, it's usually our fault 05:37 Learn enough to understand the CFO's pains 08:03 Just enough technology: an ERP for a startup heading to Series C 14:09 Rain, stock-outs and 800,000 small shops 20:21 Donut shop or trusted advisor 22:18 Cyber risk in dollars with FAIR, and the crown jewels 29:29 What are you doing with your humans? 31:25 Unlimited budget: change the behavior 35:25 Doctors, Viking boats and changing minds 41:33 Psychology, the bicycle model and goodbye
467- Show Me the Riser Room w/Zack Miller
2026/10/29
Zack Miller, Director, Global Infrastructure at Catalent, walks into every new network with one request: show me the riser room. He explains tech debt as a town full of potholes, shows how he asks the business for its cost per hour so he can price the risk, and why his first question for a CFO is how much they want to spend on IT over the next three years. Zack Miller started at 13, watching his dad tinker with computers at the kitchen table, then fixing the neighbors' things. After high school he got a smart-hands job at Cisco, earned his CCNA, worked through a couple of MSPs and settled in biotech and life sciences, where a client hired him away. Consulting showed him the patient impact of the work: sitting with a client about a new biologic for cancer patients, he thought, "my keyboard strokes can help them." He built his career on VMware and Azure engineering and has done 11 data centers, "from literally nothing but dirt in the ground to fully functional GMP data center." Today he runs global infrastructure at Catalent, across four regions and over 60 sites. His framework starts at the door: "Go into a new environment. Show me the riser room. Where does it come in?" In shared buildings the handoff is often a 15-year-old Cisco WAN aggregation switch that serves every tenant, and the first problems are no UPS and a single WAN aggregate. From there the conversation repeats: what do you want to pay for, what level of redundancy, what capacity at the edge, whose firewall. "The technology is easy," he says. The hard part is getting people to believe you and give you their money. So he turns the network into a town, with neighborhood roads, stoplights, a fiber highway and an airport at the edge, then adds 15 years and 2,000 new residents until "that is tech debt." And he asks the business for the cost per hour and the EBITDA per day, so he can name the cost of the risk. In life sciences the rules come from the FDA and the DEA, with 21 CFR 210 and 211 as the main compliance set, and his advice is to involve IT before you source lab systems. With CFOs at early and growth-stage biotechs, he starts with one question, how much do you want to spend on IT in the next three years, then backs into what you can afford, including whether you can afford to exit it: "You don't have to start with the Ferrari." He also shares what he'd do differently with his own consulting firm (find a sales leader), why context switching is a skill to build, and the advice he'd give his younger self: anger is a six-second chemical reaction. Key takeaways: Start every new site at the riser room. Find out where the service actually comes in and whether the handoff is a shared WAN aggregation switch you don't control; Check the basics first: UPS, a single WAN aggregate, the physical security and the environmentals of the riser room and the data center; Ask the business what it wants to pay for before you design: redundancy, capacity at the edge and whose firewall all follow from that answer; Pull finance into your world. Ask for the cost per hour and the EBITDA per hour and per day, then state the cost of the risk; Ask your CFO how much the company wants to spend on IT over three years, then back into what you can afford, including the cost to exit; Involve IT before lab systems are sourced, so the next FDA audit doesn't find a computer system validation problem built in Chapters: 00:00 Cold open 00:47 Meet Zack Miller: from the kitchen table to Cisco smart hands 05:31 The network needs focus, across four regions and 60 sites 13:34 The plumbing, and who answers the door when the FDA shows up 17:01 Show me the riser room 23:48 The technology is easy, getting the money is hard 27:22 Tech debt as a town, and the cost of an outage 32:54 What AI is doing to the network 39:11 FDA, DEA and GMP: involve IT before you source 43:11 Running his own firm: find a sales leader 49:12 Align with the CFO: the Ferrari or the Corolla 54:26 Context switching, and advice to hi...
466- Talk Business First, Then Tech w/Fletus Poston III
2026/10/27
Fletus Poston III, Director of IT and Cybersecurity at 3D Systems, says IT and security leaders now have to be bilingual: talk business first, then introduce the tech. He shares the elevator test he gives the people he mentors, then translates a network upgrade, tech debt, automation and a scattered data platform into language a board can act on. Fletus Poston III has worked in IT officially since 2006. He was an IT auditor at Wachovia before 13 years at Duke Energy, where he helped grow the security engineering team from 5 to 15. At his next company he built out the security program and left as acting deputy CISO. Today he is Director of IT and Cybersecurity at 3D Systems, with a team of 30, and he teaches an AI business cybersecurity class at Appalachian State. His rule for the C-suite: "I talk business first and then I introduce tech." Executives want the return on their investment and the effect on EBITDA, and they don't need to know you're blocking and tackling with firewall rules. He gives the people he mentors an elevator test. A C-level turns to you in the elevator and asks what you do for the company, and you have 10 to 15 seconds to answer in terms of business value and business change. He also explains why board members and senior leaders have told him some deputy CISOs will never be CISO: they see them as operational leaders who can't yet walk into a room and just talk finance. And he shows how attackers come in through your providers, from the caterer to the HVAC company. Then comes a game: hear the tech speak, translate it for the board. Fletus turns "we need to upgrade the network" into a business impact and a request to start at the small sites, and compares tech debt to the monthly subscriptions and gym memberships nobody looks at. He closes with the habits he relies on: come in with a problem and a solution, never go to the board asking for money, make friends with whoever has the checkbook, and don't make up an answer when you don't know. His last word: "Be a mentor, find a mentor, be a mentee." Key takeaways: Lead with return on investment and the effect on EBITDA, then the tech. Bring three to five slides and expect to cover one or two; Have a 10-to-15-second answer to "What do you do for my company?" built on the business value and business change you drive. If they want more, they'll ask; Meet your CFO between board meetings and hand over an appendix and quick notes, so the CFO can answer the board's questions; Keep a risk register of the five things that should keep the company up at night, and let some of them sit outside cyber, like a natural disaster where your suppliers are, or losing people you need to keep; Come in with a problem and a solution, and lay out options A, B and C with the one you want them to choose; When the board asks something you can't answer, don't make it up. Say you'll get back to them, and name when. Chapters: 00:00 Cold open 00:47 Meet Fletus Poston III: from a Commodore 64 to 3D Systems 03:20 Teaching AI to business students, and securing what citizen developers build 15:06 Be bilingual: talk business first, then tech 17:57 Keeping the CFO ready, and attacks through your providers 20:06 Risk registers and what keeps the company up at night 23:39 Co-owning projects, triage and healthcare 29:36 When a C-level loses their voice, and human-centric security 38:31 The elevator test 41:39 Why some deputy CISOs plateau 46:03 Translate it for the board 50:06 Habits that land, and be a mentor
465- From Department of No to Department of Risk w/Jeff Posluns
2026/10/22
Jeff Posluns, CIO of Traffic Tech, a logistics company with about 40 offices around the world, wants to be the Department of Risk: an unreasonable request goes to a risk assessment, and the business decides which consequences it will accept. He explains why a project without a business owner should not start, and why anything that pulls a person off a high-priority project gets logged and decided by the business. Jeff Posluns runs the tech part of Traffic Tech, a third- and fourth-party logistics company with about 40 offices around the world and about 1,200 people. In his view, a project without a business owner should not start, because the business owner defines the outcomes. He applies the same thinking to funding: most organizations fund projects, the team disbands after go-live, and technical debt stays invisible until something fails, so he advises persistent funding of business capabilities, with lifecycle and run costs approved at the same time as the build. Technology risk is business risk, and the business should own it. When ownership is unclear, risks get accepted by default because nobody made a decision, so he puts technology risk on the enterprise risk register with named business owners. A new initiative starts with the named business executive, the number and the date, and he decides up front how progress will be measured and at what point in the spending to ask whether the project should be stopped and shelved. He also argues that a CIO still needs real technical depth, or ends up approving decisions they can't evaluate. When a request is unreasonable, he answers as the Department of Risk: a risk assessment from the GRC team, and the list of what the business has to accept. Spend a day changing the color of a baby puke green button, and you might lose two loads of melted Hershey Kisses and have to make an insurance claim. His priorities come from a meeting every two weeks, with five high-priority projects that have delivery dates and five medium ones with target dates, and his one-line advice for technologists is to learn to hate the right things. Key takeaways: Don't start a project until a business owner has defined the outcomes they're looking for; Approve lifecycle and run costs at the same time as the build, so technical debt is visible and the total cost of ownership gets discussed before anyone signs off; Put technology risk on the enterprise risk register with named business owners, so every deferred decision becomes an explicit risk acceptance; Start an initiative with the named business executive, the number and the date, and decide how you'll measure progress and at what point you'd stop and shelve it; Keep five high priorities with delivery dates and five medium ones with target dates; anything that pulls a person off a high priority goes through a formal change register and the prioritization committee; Answer an unreasonable request with a risk assessment and what the business will have to accept, and keep your technology team out of the meetings about button colors. Chapters: 00:00 Cold open, and the tech part of Traffic Tech 03:59 No business owner, no project 07:23 How technology gets funded, and technical debt 09:16 The three-month ERP, and technology as a business decision 14:29 Technology risk is business risk 20:20 The business as internal customer, and three SOCs 26:00 The named executive, the number and the date 32:04 Technical depth, and saying no with credibility 36:35 Five high priorities, five medium, everything else 40:59 The Department of Risk and the baby puke green button 47:44 Diagram fatigue and Clean Language 53:04 Learn to hate the right things
464- We Really Are Innovation Technology w/Jennifer Terrill
2026/10/20
Jennifer Terrill, CIO of Sperber Landscape Companies, says IT often gets labeled as Mr. No and calls that a big myth, because IT really is innovation technology. She explains why technology has to work the way people already work, and why she won't hand AI a blank check as costs shift from SaaS subscriptions to tokens. Jennifer Terrill started as a programmer with a computer science degree and calls her career a jungle gym: fintech, internet banking, retail, where she was CIO of True Religion Brand Jeans, payments, and a cemetery and mortuary company she took from paper to digital. For a little over a year she has been CIO of Sperber Landscape Companies, which has about 3,500 employees and branches from coast to coast, including Hawaii, and she reports directly to the CEO. Her superpower, she says, is solving problems, and it starts with embedding herself in the business. She explains why technology is secondary for crews out in the field, where a screen that takes 10 clicks is too much, and how IT gets into the conversations it's left out of: ask to sit in on the meeting. On AI, she describes an experimental phase built on a prompt library and brain files, and she explains why tokenomics needs watching as costs shift from SaaS subscriptions to tokens. She closes with her game plan for the first 90 days in a new organization, which starts with an assessment and a day in the life. Key takeaways: Ask to sit in on business meetings to learn how the business runs. If you're in that room, you can help solve the problem; Design for the way people already work. If a SaaS screen takes 10 clicks for a crew in the field, it's too much; Give the business options, from the cheap and cheerful solution to the Ferrari, and let them pick based on the impact and the money; When you consolidate tools, have the people who use them build the scorecard, then let them pick the winner; As costs shift from SaaS subscriptions to tokens, keep an eye on tokenomics, and put a semantic layer and permission layers in place before people start calling APIs; When you join a new organization, start with an assessment of applications, infrastructure, cybersecurity and vendor data privacy, do a day in the life, then present what needs fixing right away with its cost and three options Chapters: 00:00 A jungle-gym career from programmer to CIO 04:10 Her superpower, and don't make me think 07:31 Telling the story, and making it easy for them 12:49 Herding AI cats, and the Mr. No myth 15:04 Solving problems, and the conversations you're not in 21:16 A day in the life and the Innovation Council 24:19 AI in the experimental phase 27:38 From SaaS to tokens, and no blank checks 30:30 Hiring for curiosity, and a softer place to land 37:02 When the team makes the wrong call 39:19 The first 90 days 42:55 Be fearless, and the business acumen gap
463- AI Will Fill the Gap w/Erich Gazaui
2026/10/15
Erich Gazaui, Chief Information Officer at Papa, says AI makes it look as if typing and writing are the only skills you need, and when you leave a gap in a prompt or a design, AI is going to fill that gap very quickly. He explains the intent engine he wrote about, why systems do not automatically know the finish line, and how his team built AI-driven playbooks into almost every department. Erich Gazaui's first computer was an Apple II, and his mom put him in a computer class to learn BASIC. He was pre-med until organic chemistry, graduated in economics, and learned DOS batch scripts in the dorms so he could play Privateer. In college he and two friends started a company whose first customer was the university: a survey tool for a political science professor, then a computer lab to run it. That company later became a security firm he ran for 15 years. He went on to be a senior director at TrueCar with "a really big hand in the security side, the governance and compliance", was recruited to Beachbody by its CIO, and was head of IT at ZipRecruiter, where vetting job posters made marketplace safety a competitive advantage and procurement ran "janitorial all the way through AWS". Today security, IT compliance and enterprise apps sit under him at Papa. His warning about AI: "When you leave a gap in a prompt or in a design, AI is going to fill that gap very quickly." The output looks so professional that you won't know what was filled, and the miss may only show up when it is very expensive to change. He compares it to firing a laser pointer at the moon, where being off by a fraction of a millimeter means you miss it. His answer is what he calls an intent engine: a central source of truth for what the company believes. One request at ZipRecruiter to "make sure that marketing is included" in an event shows why: even the head of marketing came back with a question. Then the other end of the work: the success criteria, the definition of done. Using mean time to resolution as the example, he explains why "systems do not automatically know the finish line" and keep refining past the state you wanted. He talks about the political capital he spent with his CEO and president to build AI properly, how restrictive his team was about which AI features to enable while they built a central knowledge store, and the playbooks that now run in almost every department, including the day the CEO asked to take his old laptop for personal use and the system handled it with no human interaction. His rule for his own meetings: "Everybody has a voice and it's equal. You leave the title at the door." Key takeaways: Give every AI system and automated playbook its finish line: write the success criteria and the definition of done, or it will keep refining past the state you wanted; Instruct the models to identify gaps rather than fill them, and decide upfront which gaps are intentional; Before you switch AI features on, build one central knowledge store with the goals, processes, teams and names; disable or downgrade the tier on tools that can't point at it yet; Test your definitions on something small. "Make sure marketing is included" turns into who goes on the list, who maintains it and who writes the rules; Put a gate on every action an AI-driven playbook can take, and keep it supervisory until you trust it; Use the visibility IT has. Procurement and governance let you show the board and the audit committee where security and compliance drive revenue Chapters: 00:00 Cold open 00:42 Meet Erich Gazaui: an Apple II, a 286 and a computer camp 03:15 Pre-med, Privateer and a first company in college 07:21 TrueCar, Beachbody and a workout at orientation 09:52 Beyond the cost center: governance at Papa 14:28 ZipRecruiter: marketplace safety and company-wide procurement 21:22 The missing skills: AI will fill the gap 26:12 Make sure marketing is included: the intent engine 31:43 Start and finish: systems don't know the finish line 39:21 A beautifully wrong sys...
462- How Do We Get to Right? w/Christopher Childs
2026/10/13
Christopher Childs, CIO of Evans Army Community Hospital, on why IT has to be in the business of healthcare and not the healthcare business, and why he tells leaders who text him about a broken computer that he is not the help desk. He walks through his four pillars of leadership and the Innovation Board he pushed for, built around one question: how do we get to right? The skill Christopher Childs credits most for his success has nothing to do with technical ability: listening more than he speaks and meeting people where they are. The CIO of Evans Army Community Hospital, speaking for himself, explains how a master technician can also become a master isolationist, and why he tells his branch chiefs to use IT as a force multiplier and a healthcare enabler. He describes telling his own leadership that he is not the help desk, why he asks every department for downtime procedures so nobody uses IT as a crutch, and the two questions behind his decisions: does it help deliver safe, quality care, and does it make the patient experience better. Then come his four pillars of leadership, compassion, passion, standards and discipline, and the Frankenstein IT you get when nothing is standardized. Chris also pushed for the hospital's Innovation Board, a bimonthly meeting where anyone in the organization can bring an idea to the experts who would have to deliver it. It brought IT to the table before decisions get made, and it runs on one rule: how do we get to right? He closes with how he sells standardization when the payoff is slow, using Vocera badges that let the hospital drop five contracts, and with the legacy he wants to leave. Key takeaways: Listen more than you speak. When someone seems distracted, offer to have a different conversation than the one you're having; Pick the framework your organization delivers on and run every decision through it. His: safe, quality care and the patient experience; When leaders treat you as the help desk, say so plainly, and send the call to the person whose job it is; Make every department keep downtime procedures, so a planned maintenance window doesn't stop the work; Standardize before you scale. Patched-together good ideas turn into Frankenstein IT that nobody can fix when it breaks; Give people a standing room to bring ideas, and steer the talk toward how to get to right, so a no costs nothing. Chapters: 00:00 Introduction: from the MLB draft to the Army 06:59 Listen more than you speak 14:04 Master technician, master isolationist 16:25 In the business of healthcare, and downtime procedures 22:13 "I am not the help desk" 26:36 Why technicians rarely get to learn leadership 33:21 Safe, quality care and the patient experience 38:17 Four pillars: compassion, passion, standards, discipline 42:14 Showing passion, and the Innovation Board 48:35 A seat at the table: how do we get to right? 55:12 Selling standardization, from Batman to Vocera badges 68:33 Words of wisdom: the legacy you leave
461- Just Because It's Old Doesn't Make It Wrong w/Jeremy Mayfield
2026/10/08
Jeremy Mayfield, Director of IT at National Sugar Marketing Cooperative, took the company from a legacy on-premise ERP to a fully SaaS platform in under 12 months, against a 14-month board approval, after a year of defining requirements and a vendor hit list that ended with "now you have to show us." He explains why an organization that can't tell you its requirements isn't ready for change, and why he thinks that 18 months from now IT leaders will be talking about what he calls the death of the data center. Jeremy Mayfield came out of school as a fresh engineer and fell into IT back when it was called MIS. As the only IT person at his first company, he taught himself everything, from Cat5 cables and phone-system punch-down blocks to databases, and at one point he was a SQL expert. A leader tapped him early, and he has spent most of his 30 years in IT in leadership while staying hands-on. In 1997 he ran a 3 meg internet link over a 17-mile wireless hop and negotiated free internet by letting the provider use the company's silo as a hop. At a global company of more than 90,000 people, he was a program owner for voice over IP and landline optimization across 1,600 North American locations, work that saved about $11 million in copper. Today National Sugar, which distributes sugar to companies across the US, runs completely serverless and fully SaaS, with a zero trust framework in place of VPNs. Its new ERP went live on May 1 in under 12 months, against a 14-month board approval, and finished well under the approved budget. It started with a year of defining requirements, including visits to the co-op's members and to 3PLs. A roughly 90-page RFP went to about 10 vendors, Tier 1 and Tier 2, with a hit list every one of them had to answer: anyone who couldn't come back with "here's how we'll do it" was disqualified, and the finalists heard "now you have to show us." Jeremy wanted a vanilla, canned app, which he sums up as configuration over customization, and he phased the rollout to keep scope creep out. National Sugar was formed from one of the co-op's members about 15 or 16 years ago, and that member was still running all of its IT, ERP hosting included, when Jeremy was hired and told, "your task is to modernize us." His first day on the job was the cutover from the member's Microsoft 365 tenant to National Sugar's own. He took a cautious approach to AI through the ERP project and the stabilization after go-live. Now, with shadow AI already in use across the company, he puts security first and has asked the CFO to realign the budget for business licenses the company can administer and secure. Asked what IT leaders will be talking about in 18 months, he picks the death of the data center, with data spread out like an atom, "all over the place but no place at the same time." Key takeaways: Nail down your requirements before you shop. If the organization can't tell you what they are, it isn't ready for change; Build a hit list around what only your business needs, like FDA and USDA requirements and lot traceability for a food grade business, and disqualify any vendor that can't answer with "here's how we'll do it."; Make vendors show you before they get time with your leadership team; Choose configuration over customization: a vanilla app, with pre-built connectors for what sits around it; Phase the rollout, with the high-value, high-impact pieces first, and keep scope creep out; Budget a stabilization period after go-live. He planned about six months before turning to AI. Chapters: 00:00 Cold open: not ready for change 00:43 Meet Jeremy Mayfield: the only IT person, self-taught 03:17 Still hands-on: a 17-mile wireless hop and $11 million in copper 11:54 Completely serverless, with zero trust instead of VPNs 13:57 SOC 2 and configuration over customization 18:32 Pre-built connectors, and an ERP live in under 12 months 20:59 How the co-op works, and a year of requirements 27:06 The hit list and "now show us" 30:37 Five ERP chan...
460- Seat at the Table, Still the IT Guy w/Brian Ledbetter
2026/10/06
Veteran CIO and US Air Force veteran Brian Ledbetter on why IT leaders who earn a seat at the table can still be seen as the person who fixed the printer. He walks through the six pillars of his LEAD IT framework and explains why developers who hammered out code all day will end up managing AI agents. Earlier in his career, at a small company, one of its leaders called Brian Ledbetter his CIO. Another called him his IT director. A third called him his IT guy. Brian, a veteran CIO and US Air Force veteran, says the title matters far less than how the organization sees you, and that perception is hardest to shift when you came up through the help desk at the same company. He walks through LEAD IT, the framework he built from lessons he learned the hard way: Lead, Elevate, Align, Deliver, Innovate and Transform. Former guest Bruce Otte joins to press on delegation, which brings out Brian's three-foot hole story and his test for who is ready to own an outcome. Later, Brian argues that whoever makes a technology decision should share the accountability when it fails. He explains how to answer a technical question and turn it straight to business impact, and why every AI conversation should start with the outcome. Asked what IT leaders will be talking about in 18 months, he picks the guardrails needed to tame AI, and he says companies are already hiring agent managers. Key takeaways: Answer the technical question, then turn it to business impact before anyone else speaks; Before handing someone an outcome, check whether they see the work around the task; Once you delegate, stay close and available without hovering. Delegation is not abdication; Whoever makes a technology decision should share the accountability when it fails; Start every AI request with the outcome you want. Pick the tool after that. Chapters: 00:00 Cold open: CIO, IT director or IT guy 00:43 Meet Brian Ledbetter, from the Air Force to a wall of certifications 03:59 Three titles for one job, and the printer problem 08:08 Where LEAD IT came from, and why Lead comes first 14:57 Letting go of the work, and leaving the code behind 18:12 Bruce Otte's questions on delegation, and owning the outcome 21:50 The three-foot hole guy 25:15 Building confidence, and room to fail 33:27 Peer groups, and who owns the decision 39:52 Speak the business, step zero and shared accountability 44:58 Governance is rules, and AI starts at the end 50:30 The 18-month prediction: developers, AI and agent managers

Podcast reviews

Read You've Been Heard podcast reviews


4.9 out of 5
51 reviews
★★★★★
junegirl0929 2025/07/11
Informative, Relevant and Accessible!
I thoroughly enjoy this podcast and actually look forward to my 90+ minute commute on in-office days so I have uninterrupted time to listen. The conte...
★★★★★
ddskleod 2024/09/17
First class podcast production!
I met Doug Camin while speaking at the NYS Cybersecurity Conference in Albany. He introduced himself to me after the session and asked me to be a gues...
★★★★★
Macfrosty 2024/09/15
Great Perspectives
Great show, digging in past the surface of subjects in IT. Critical for navigating our digital landscape.
★★★★★
Abdul hafeeth 2024/06/01
Great Show
Awesome show! Real talk about real tech. Great learning experience.
★★★★★
Izodius 2024/05/31
Great IT Leadership Content
Lots of interesting guests and a myriad of topics. There’s something for every IT leader here from big industry to small shops.
★★★★★
JakeScsg 2023/12/22
IT Podcast
I really enjoy listening to this podcast. The conversations are great!!
★★★★★
Wills_Opinion 2023/12/14
Perfectly fills an important niche
I am a listener and I had the privilege of being a guest on the podcast. Dissecting Popular IT Nerds is such a great resource for IT leaders and other...
★★★★★
Different Kind of Athlete 2023/11/17
Most informative IT Podcast!
Well before interviewing with Phil Howard, I was an avid listener to the episodes already available on a wide variety of topics and industries. T...
★★★★★
Humble_Trailblazer 2023/11/15
Great Podcast
I would recommend any IT professional listen to this podcast. It’s great to hear from IT professionals that share their own real experiences and outlo...
★★★★★
IHATEROBINHOOD75927 2023/10/05
5 stars aren’t enough!
Best IT podcast on the planet!!
check all reviews on apple podcasts

Podcast sponsorship advertising

Start advertising on You've Been Heard relevant audience podcasts


What do you want to promote?