Description
On this episode of The Innovator’s Playbook, Seth Narayanan talks with Brian Hiatt, former CIO, CTO, entrepreneur, and longtime tech leader with over three decades of experience at Xerox, HP, CSC, and fast-scaling startups. Brian shares how his unconventional path from accounting to software leadership shaped his approach to innovation, cloud adoption, and building technology that actually solves business problems.
They dive into what real innovation looks like (hint: it’s not about chasing the latest tools), how to choose the right tech for your growth stage, the future of software engineering in an AI-driven world, and the growing role of cloud services beyond infrastructure. If you’re building or leading tech teams, this is a conversation worth tuning into.
From Accounting to Engineering: A Business-First Technologist
“Everything I built was about solving business problems not just using tech for the sake of it.”
Brian’s tech career didn’t start in computer science – it began in accounting. But that foundation gave him the one advantage many engineers lack: business fluency. He self-taught programming, built early EDI systems, and helped retailers automate inventory management – resulting in a 20% revenue bump for his company’s wholesale clients.
His lesson? Knowing why you’re building something is just as important as knowing how.
Innovation Isn’t a Toolset – It’s a Mindset
“We’re not here to build IT empires. We’re here to solve what the business actually needs.”
Brian sees the word “innovation” overused and misunderstood. For him, innovation is right-sized execution – choosing the tech and approach that match a company’s stage, budget, and market need. He became known among startup founders and CEOs as the CTO who wouldn’t overbuild. That discipline drove real ROI.
Choosing the Right Tech (Not the Shiniest One)
“We don’t get paralyzed by options. We analyze, decide, and move.”
Whether it’s PHP, Node.js, or AI-native frameworks, Brian stresses the importance of staying adaptable. He and his teams regularly evaluate their stack based on outcomes, maintainability, and technical debt. One non-negotiable: don’t adopt a tech tool just because it’s trending.
And yes, ecosystem maturity and talent availability matter. No use picking a tool no one can hire for.
The Execution-Vision Balance: Reset Early, Reset Often
“Without resets, long projects drift. We stayed agile – even inside a 2-year enterprise rollout.”
Brian described a massive enterprise project: 1,200 server migrations, 40,000 email users, and a full IT outsourcing initiative. His key to success? Quarterly resets – structured check-ins that revalidated the vision, allowed for course corrections, and maintained business alignment.
Cloud Strategy: Where It’s Going
“The future of cloud isn’t infrastructure – it’s intelligent business services.”
While cloud costs remain a challenge for most clients, Brian believes the next evolution lies in AI-integrated services. He envisions a future where cloud platforms help teams ideate, design, build, and even deploy working prototypes – based on a simple description of a business need.
That future, he says, isn’t as far off as we think.
AI and Engineering: A Radical Shift
“More than 50% of entry-level engineering jobs could disappear. But the opportunity lies in senior roles.”
AI tools like Copilot, Codex, and Cursor are already changing how software is written. Brian estimates that they’re 65 – 70% of the way to building MVPs with minimal human input. But that last mile – the critical 15 – 30% – still requires human insight, business context, and refinement.
The result? Fewer junior developer roles, and a surge in demand for architect-level thinkers who can steer, interpret, and extend AI-generated code.
Final Advice: Let Business Lead the Way
“Technology doesn’t drive innovation. Business does.”
The most valuable advice Brian leaves us with is this: stay close to decision-makers. Challenge assumptions. And keep one foot firmly planted in business strategy, not just product architecture.
Because at the end of the day, innovation isn’t about being first to adopt a tool – it’s about solving a real problem better than before.
