ServiceNow Podcasts

A handful of genuinely useful ideas surface - the 'survival problem' for supporting functions as engineering velocity compounds, content atrophy feeding AI hallucinations, and tech debt from vibe coding - but they're spaced out by long stretches of analogy, feel-good generality, and repeated affirmations between speakers.

“the cost of building the wrong thing has climbed exponentially”

“content is not moving on at the same rate, it becomes less useful. right and where we are now is like an AI consumer of that content is just as important as a human consumer of it”

The framing that supporting functions (docs, design, research) face an existential productivity problem because of engineering's AI-driven speed is a moderately fresh angle, but the rest leans on well-circulated AI discourse - the Jarvis analogy, 'human element,' and the 'slow down to speed up' take are all standard fare.

“if they're building all of this new stuff, what are all the systems that are around that and all of the roles that you need around the building itself to make sure you're building the right thing”

“And I think as an industry we starting to realize in this first chapter of AI software development that slowing down becomes part of the process”

Three senior ServiceNow executives (GVP and SVP level) in directly relevant disciplines - design, product research, and content - who are actively doing the work described; however, as internal guests on a company-produced podcast they lack the independence and external battle-testing that would warrant a higher score.

“David Hoare, Group Vice President of Digital Content and Design. I've been at ServiceNow for five years”

“Anand Tharanathan. I am the group vice president heading up product research and insights to service now”

One concrete external data point - Andrew Ng's PM-to-engineer ratio shift cited by name with actual numbers - and a rough estimate of ideation time (nine concepts in a week vs. an hour) are the only real anchors; ServiceNow's own results are never quantified and most claims remain at the level of assertion.

“he's seen ratios of engineers to PMs changing from 1 PM to 14 engineers, to 1 to 7, to 1 to 1, to often he's got 2 PMs to every one engineer”

“rather than taking a week to create nine concepts for exploration and trying to find market viability, designers can create those nine concepts in an hour”

The host structures the conversation reasonably and surfaces a few genuinely interesting lines of inquiry (the survival problem, content governance), but consistently leads witnesses, openly telegraphs expected answers, and never pushes back on any claim - the explicitly self-described 'standard question' for the close is representative of the overall dynamic.

“David, I know your answer is going to be about where the rubber meets the road”

“18 months from now, I know that's the standard question”