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

Phil Howard & Mahesh Adnani

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

THE IT LEADERSHIP PODCAST
EPISODE 473

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

20
1 X
20
00:00 | 00:00

Short Clips

Episode Highlights

Mahesh Adnani

GUEST BIO

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."

Network Assessment

Your monthly IT spend should be boring.If it's not, something is wrong.

Network Friction Score
BoringChaotic
Do you have provider/support numbers handy, or is it 1-800-GO-POUND-SAND?

We review circuit consolidation, contracts, security, outage visibility, billing, and future flexibility to reduce chaos without forcing change.

▸Circuit consolidation
▸Contracts & pricing
▸Firewall management
▸Outage alerts
▸Edge security
▸Billing & licensing
Boring results. Reputable savings.
Consolidation that makes sense.
Show Notes

Episode Show Notes

Navigate through key moments in this episode with timestamped highlights, from initial introductions to deep dives into real-world use cases and implementation strategies.

[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

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.
473- Go Live Is Just a Milestone w/Mahesh Adnani
logo

You’ve Been Heard

You’ve Been Heard is where IT leaders stop being sidelined and start being amplified. We’re the triple-threat platform: podcast, community and vendor-neutral advisory that elevates your voice, your value, and your influence because when IT leaders rise, so does everything else.

© 2026 You've Been Heard. All rights reserved.