You've Been Heard

You've Been Heard

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.

  1. 17h ago

    477- When Not to Implement Technology w/John Wurl

    John Wurl, Chief Technology & Transformation Executive at Lake County Health Department, has learned that sometimes the best technology solution is not to implement technology. He walks through the IT leadership habits behind that view: asking what a report is for before building it, letting the business drive the decision, bringing in experts when people resist change, and taking AI decisions up to the executive team. John Wurl started at the lowest level, as a systems engineer on Z80 processors, counting bits and capturing interrupts. What kept him in technology after he moved into IT is how solutions are found and implemented: "It's about the ecosystem that that technology is placed in." That view has gotten him in trouble, because people always go, "but I want this software." His habit is to step back and analyze, and reports are his favorite example: "What is this report going to tell us?" He makes the case for bringing technology into the upfront conversation, where he sees "almost this militant rejection" of the value technology people can add. His way in is to educate the people deciding on their options, then let them drive the decision. He notes that every change brings a new C title, though "leadership is an organization function." And he explains why "sometimes the best technology solution is not to implement technology": count the dollars and the new problems a solution brings before you commit. When a board pushes for an expensive system, he brings the case back to a financial impact, and the answer usually turns out to be "this, then that." On AI, he argues it "is misunderstood as a technology problem." He tells how billing issues started when people asked an AI tool outside the EHR for a CPT code, and why he keeps bringing those discussions back to the executive team. His county's AI governance team meets once a month to validate the tools and models staff use. He closes on his agency's mission, serving the underserved through its federally qualified health center (FQHC), and the advice he'd give his younger self: "be curious about things outside of what you're doing, outside of your responsibility." Key takeaways: Before you build the report or buy the software, ask what it is going to tell you and whether it fits into a workflow. The operational system may already hold the information; Count the problems a technology solution creates, in dollars and resources, along with the one it solves. Sometimes the right call is not to implement technology; Educate the decision makers on each option, then let them drive the decision so the team owns it; Make the business case in financial terms, mapped to the capabilities that create value for your end users, and offer a "this, then that" path when a big switch isn't the right move yet; When people resist a change, bring in the experts (John brought in a board member who teaches data analytics) and step back from the discussion; Take AI decisions up to the executive team: run an AI governance team that validates tools and models, and ask each leader how the AI in their products affects their workflow. Chapters: 00:00 Cold open, and a first computer built on a Z80 02:10 Coordination, processes, and AI as an amplifier 05:25 Solutions live in an ecosystem 08:53 What is this report going to tell us? 11:44 Making it their decision 15:31 Laying out the options, and repositioning staff with AI 20:06 A new C title for every change 21:01 Sometimes the answer is not to implement technology 22:19 When the system doesn't fit the clinic: this, then that 29:47 Boards, the financial case and the human at the end 38:39 Bring in the experts, and take AI to the executive team 50:56 Serving the underserved, and being curious

    477- When Not to Implement Technology w/John Wurl
  2. 1d ago

    476- You Have to Market Yourself w/Ron Ijack

    Ron Ijack, Head of Technology at ThirdLove, has been the external consultant who knows everything and the insider who knows nothing, and his lesson for IT leadership is that you have to market yourself. He and Phil Howard get into leading with data and wins, the tech debt he absorbs silently, meeting users where they are, and why being right doesn't always matter. Ron Ijack is a developer at heart who started writing code in the mid-90s and "almost fell into leadership roles along the way." He has sat on both sides of the table, and he knows how the welcome changes. In the interview, "you're the external guy who's coming to save us." Once you're inside, "you become the director that broke this." His answer is to keep fighting that battle: lead with data, lead with wins, and provide that value for the business. "It's marketing in a way. You have to market yourself." He calls himself the worst offender, because IT teams are so busy putting out fires that there's no time to keep track of everything they fixed. Phil reads out a playbook for IT leaders that he builds live with Claude, and Ron tests each point against his own practice. Tech debt is something he absorbs silently: when a project carries a bunch of it, he bumps up the time frame and fixes it, and he brings the executive team the money saved or the revenue added. He gives projects names people remember (his middleware integration layer was called Middle Earth), likes the idea of a funny video at every town hall, and makes the case for meeting users where they are, with a ticket raised from Slack or a Claude skill instead of a seven-page form. He is all for documentation, yet he pushes back on the risk register as a shield: if you need one to cover yourself, "there's something wrong with your culture." He closes with the advice he'd give his younger self: "Being right doesn't always matter." When the perception that you were wrong is strong enough, fighting it won't help, so "you have to change the perception," and your personal brand is "probably your biggest asset." He also explains how he learned to think like a business leader after moving from leading engineering at a software company into senior leadership at a brand: by learning what hits with the CEO and the board, and speaking to what's important to them. Key takeaways: Keep track of the before and after on every project, and get the metrics while the work is fresh, so you have something to show at the board meeting or the year-end review; Lead with data and wins, in the business's own numbers: the money you saved or the revenue you added; Fold tech debt fixes into the project's time frame, and report wins that carry a concrete number, like the dollars saved by removing vendors; Meet users where they are: let them raise a ticket from Slack or a Claude skill, and keep the seven-page form out of their way; On a two-way-door decision, decide and move on. Take your time on the one-way doors, like your architecture stack or your data warehouse; When people see you as the one who got it wrong, fighting it won't help. Work on changing the perception. Chapters: 00:00 Cold open 00:40 Why executives trust the outside voice 09:10 You have to market yourself 15:16 Keeping your voice after you join: the external guy 16:12 A Claude skill for IT wins, and why domain knowledge still matters 19:21 Business numbers and the tech debt he absorbs silently 22:27 Name your wins and make the town hall memorable 27:00 Warn early, own the losses, decide with what you know 37:41 Choosing vendors, and two-way doors 42:32 Meet users where they are, then make the ask and stop 48:34 Outside credibility, teaching, documentation and staying visible 59:21 Being right doesn't always matter, and learning to read people

    476- You Have to Market Yourself w/Ron Ijack
  3. 2d ago

    475- Levels of IT Optimization w/Peter Hogan

    Peter Hogan, the 2024 St. Louis ORBIE Enterprise CIO of the Year, wants IT to 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 picture of where IT should go: "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 moving IT to business value 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

    475- Levels of IT Optimization w/Peter Hogan
  4. 3d ago

    473- Go Live Is Just a Milestone w/Mahesh Adnani

    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

    473- Go Live Is Just a Milestone w/Mahesh Adnani
  5. Nov 12

    472- You Don't Want to Automate Chaos w/Chris Stierle

    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

    472- You Don't Want to Automate Chaos w/Chris Stierle
  6. Nov 10

    471- From Code Black to No Outages w/Shane Froebel

    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

    471- From Code Black to No Outages w/Shane Froebel
  7. Nov 9

    470- Being 100% Correct Isn't Enough w/Devon Simmons

    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

    470- Being 100% Correct Isn't Enough w/Devon Simmons
  8. Nov 5

    469- Not Just the Break-Fix Guy w/Desi Rodriguez

    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

    469- Not Just the Break-Fix Guy w/Desi Rodriguez
4.9
out of 5
51 Ratings

About

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.

You Might Also Like