You've Been Heard

Scott Kutz runs IT at a construction equipment dealership where excavators connect to the internet and OEMs move faster than the infrastructure can follow. His answer isn't to be the hero. It's to make himself unnecessary.

Scott Kutz is five months into his role as IT Manager at Brooks Tractor, a construction equipment dealership where service managers remote into customer excavators in real time and OEM vendors push cloud platforms faster than most dealers can upgrade their bandwidth. He came from a larger privately held construction company where he watched IT people hoard knowledge, refuse to explain their work, and position themselves as irreplaceable. He decided early on that wasn't going to be him. Scott's approach comes from his father, a twenty-year Marine veteran in communications who taught him that slow is smooth and smooth is fast. "It's okay to not know, but it's not okay to stop learning and it's not okay to stop teaching. Because knowledge kept to yourself isn't being kind." That line runs through everything Scott does. He lets his team push buttons on decommissioned systems knowing things will break. He asks people what they do for fun so he can explain IT problems using their language. He told one coworker he fixed their computer by changing the spark plug in their engine. We get into how construction equipment dealerships are quietly becoming high-tech environments, why Scott turned a frustrated coworker into an ally who championed a company-wide bandwidth upgrade, and how he earned a seat at the leadership table five months in by learning the dealership's service operations before touching the IT. Scott's test for himself is straightforward. If he wins the Powerball tomorrow or gets hit by a bus, the business should keep running without him. If it can't, he's not indispensable. He's a single point of failure disguised as expertise.

Key takeaways: Make yourself unnecessary. The business should run without you.; Let people fail in low-risk environments. They learn faster that way.; Learn the business before you try to change the IT.

Piotr Mlodecki spent years watching business leaders hide behind software limitations. Then AI removed all the excuses and exposed the real problem: bad process architecture.

Piotr Mlodecki is Chief Transformation Officer at SOL-MILLENNIUM Medical Group, where he's learned that AI's biggest threat isn't replacing humans—it's exposing bad business design. For years, companies could blame slow software delivery for operational failures. Not anymore. "The ROI does not come from the question answered. It comes from a task executed, the job done." Piotr argues that most companies are treating AI like a faster layer on top of broken processes instead of rebuilding how the business actually operates. We get into why feasibility is no longer the bottleneck, how to design agents like real employees with KPIs, and why your data architecture determines whether AI transformation succeeds or becomes expensive automation theater. The prediction? In 18 months, we'll be competing on who built the better agentic enterprise, not whether we should use AI at all.

Key takeaways: ROI comes from tasks executed, not questions answered; Design agents like employees with job descriptions and KPIs; Data architecture determines AI success more than the models

Stephen Salaka has a PhD in psychology and builds nuclear weapons systems. Then he learned the hardest truth in tech: AI can't fix what humans won't adopt.

Stephen Salaka wanted to build nuclear bombs. A lab accident sent him to computer science. A stint in Japan taught him his real superpower: making humans actually use the technology he builds. Now he's a CTO with a PhD in Industrial/Organizational Psychology. That combination makes him dangerous to every AI myth floating around C-suites. "The biggest fundamental misconception is AI is going to be a panacea for everything," he says. "The real trouble most organizations face is the people." We get into why UPS's maintenance system failed for years until Stephen added change management, how vibe coding should stop at the prototype stage, and why the AI bubble collapse is coming faster than anyone thinks. Plus his framework for bringing order to chaos without mandates. The payoff: Stephen's lived at the fault line between brilliant technology and stubborn humans. He knows which one wins.

Key takeaways: Change management isn't optional - it's the actual product you're delivering; Vibe coding works for prototypes, then convert to proper backend components; Smooth processes first, then speed follows - not the other way around

Tim Armstrong runs IT for a construction company with a team of four serving 175 staff. His take on the biggest mistake IT makes: gatekeeping support behind ticket systems instead of helping people first.

Tim Armstrong is 90 days into his role as Manager of IT at PROCON, a design-build construction company in Hooksett, NH. With a four-person team serving 175 staff, he has had to build trust fast, deploy Kanban sprints from scratch, navigate shadow AI, and figure out what technology means at a company that builds buildings for a living. His philosophy: IT exists to serve, not to gatekeep.

Key takeaways: Not everything requires a ticket. Help first, document later.; Deliberately undercommit on your first sprint to calibrate real velocity.; IT leaders need to know enough to have an intelligent conversation, not enough to do everything themselves.

Nathan Kaufman built CMMC compliance from scratch at a defense contractor with SSH open to the internet and no Active Directory. Then he learned the hard way that technical wins mean nothing if you can't communicate your value.

Nathan Kaufman walked into a $100 million defense contractor with 80 employees, zero IT infrastructure, and two years to become CMMC Level 2 compliant or lose all DoD contracts. No Active Directory. SSH open to the internet. Engineers buying equipment with personal credit cards. A flat network running on unpatched switches. He built it all from the ground up. Deployed CrowdStrike across 350+ endpoints. Migrated to Azure GCC High. Survived a merger, acquisition, and divestiture simultaneously. Grew the team from one person (him) to five across three locations and 260 employees. Passed the CMMC audit in November 2025. Then he got fired in August. We get into the technical path for CMMC compliance, why "permission to play" became his rallying cry with executives, and the SBI framework for communicating IT value. Nathan shares his biggest lesson: you can have amazing technical skills, but if you don't advocate for yourself, nobody else will. The brutal truth about building compliance infrastructure while life happens around you.

Key takeaways: "Permission to play" - compliance isn't optional for DoD contractors; SBI framework: Situation, Behavior, Impact for communicating IT value; Technical wins mean nothing without executive communication skills

Bill Markut, IT Director at Gränges Americas, built a five-year roadmap to transform manufacturing IT. From the Department of No to the Department of No, But. And why AI won't fix a decade of infrastructure neglect.

Bill Markut spent 36 years avoiding management, preferring hands-on technical work. Then he became IT Director at a manufacturing company running 25 years behind the tech curve and discovered something that changed everything: the power of getting IT and OT to actually talk to each other.

Key takeaways: Manufacturing IT runs 20-25 years behind the technology curve. That gap is the opportunity.; The event storm exercise gets IT and OT in one room. That is where silos actually break.; Hire for initiative, not just technical skill. Addition by subtraction is real.