The Data & AI Chief

A handful of operationally specific insights emerge (restructuring team ratios, removing junior titles, capability framework build-out) but they are surrounded by substantial padding - host personal anecdotes, a lengthy lightning round, Vegemite banter, and generic change management platitudes. The ratio of novel ideas to filler is low for a 36-minute runtime.

“we removed the junior roles from our titles...we found that the junior aspect of the title could be removed”

“we needed to slim down the engineering ratio in a team. Typically we'd have like six to eight engineers per team. And now we're looking at three to four engineers per team”

The distinction between supervised-agent coding and 'vibe coding' is a mildly fresh framing, and the capability-framework-in-moments concept is interesting, but the episode otherwise recycles standard change-management advice (involve people, be transparent, democratic vs. authoritarian leadership) and the well-worn SaaS moat / build-vs-buy debate without adding any contrarian or first-principles angle.

“a SaaS company will bring software to the table, but that's the outcome. That's not necessarily everything that they're bringing. They bring deep expertise on the subject matter”

“being collaborative and working in that sort of more democratic style of leadership is slower”

Josh McKenzie is a genuine practitioner who has actually restructured his engineering organisation around AI agents at a real SaaS company (19,000 customers), giving him credible first-hand experience; however, ELMO is a mid-market HR platform rather than a hyper-scale operation, and several answers stay at a level of abstraction that doesn't fully leverage his seniority.

“we fundamentally rethought our software development life cycle and all of our roles and responsibilities”

“we increased the number of teams that we had by reallocating resources out”

There are some concrete data points (team size 6 - 8 → 3 - 4, 86% headcount-reduction survey stat, 80% first-pass target, named clients Pret A Manger and Cafe Nero, 12-month transformation timeline), but the episode never surfaces hard ROI numbers, cost savings, velocity improvements, or deployment metrics that would let a listener benchmark their own situation.

“86% of organizations are expecting headcount as a result of AI changes”

“Typically we'd have like six to eight engineers per team. And now we're looking at three to four engineers per team”

The host is the ThoughtSpot representative whose company sponsors the show, creating an obvious conflict that produces an awkward mid-episode advertisement and zero pushback on any claim; personal host anecdotes consume several minutes, the lightning round (motorbikes, Vegemite, Wireguard, reading with a six-year-old) eats the back third of the episode, and follow-up questions consistently validate rather than probe.

“I went from being popular at dinner parties. Everyone's like, oh, yay, you work in AI...to now like, a mom went off on me”

“I tried. I had the opportunity to experience a nascar, um, trial around the track and the driver told me I was driving too dangerously slow”