FNDN Series

The episode delivers solid, actionable insights about HR tech infrastructure and operating model design that most HR practitioners wouldn't encounter in standard resources. Schofer's core arguments - that HR teams need to prioritize infrastructure and data capture before adopting point solutions, that the 'too many tools' objection is misguided, and that strategic prioritization enables better vendor selection - are substantive and contrarian. However, the episode suffers from repetition (the infrastructure gap argument cycles multiple times) and some abstract discussion that lacks concrete grounding, particularly when discussing future AI capabilities.

“the tech we have had traditionally stepped us up from admin paperwork, HR teams to maybe more modern people teams. I think the next step is where we need to go, which is more value adding tech infrastructure”

“we don't have the right infrastructure. I don't feel like we have the right tools for HR right now that we need and that's why we see the market exploding with more and more stuff because we're still not serving the needs properly”

Schofer presents a genuinely counterintuitive take on the 'tool proliferation' problem in HR - arguing it's not the quantity of tools but their lack of value that's the issue - which pushes against prevailing wisdom. The emphasis on infrastructure-first prioritization before adopting strategic tech is relatively fresh in HR discourse. However, the operating model framework (separating 'run' and 'change' functions) is not new, and much of the advice about stakeholder management, prioritization, and saying 'no' to leadership is standard change management practice. The AI commentary, while forward-looking, remains somewhat generic.

“I don't like this concept that well, we don't want people to log into too many tools. I think that is bs honestly. Look at your phone. How many apps do you have”

“the way the ways you wouldn't do it is probably how 90% of businesses are doing it, right? Because it's just not working”

Schofer is a relevant practitioner with credible hands-on experience in HR transformation and HR tech vendor evaluation. However, he's positioned as a founder/industry analyst rather than as a current operator scaling compensation or people operations at a major company. His background in change delivery and previous in-house HR roles provide legitimacy, but he's no longer operating within a business context, which limits his ability to speak from real-time, ongoing tactical experience. The expertise is solid but somewhat removed from immediate operational reality.

“I worked in companies and we'd be like, we need tech. And it's like, oh, the three biggest names that come to the top of your mind. And that's like your shortlist”

“I don't work in business at the moment. I think it's hard to know. Doing it right”

The episode is notably weak on concrete examples, metrics, and case studies. Schofer avoids naming specific companies doing infrastructure well ("I don't think..I'm not in house anymore"), instead offering generic observations like "the new modern, let's say lovable or the big headlines." There are no named vendors discussed in depth, no specific cost figures, no metrics on time saved by automation, and no data-backed claims about how many HR teams are struggling with data quality. The discussion of customer service analogies and future AI capabilities is illustrative but lacks specificity about existing implementations or measurable outcomes.

“I don't think, I mean as I'm not in house anymore, I don't. And I don't work in business at the moment. I think it's hard to know. Doing it right”

“I've got four people here doing contracts manually. You know, it doesn't really make much sense”

The host (Matt) asks competent foundational questions and does follow up on key themes like operating model design and vendor selection. However, he rarely pushes back on Schofer's claims or tests assertions. When Schofer makes broad statements ("90% of businesses are doing it wrong"), the host doesn't ask for evidence or pushback. The conversation lacks intellectual sparring; instead, it reads as affirmation ("I'm smiling because this is pretty much what you described..."). There's minimal challenge on the limitations of Schofer's infrastructure-first argument or the feasibility of his recommendations in truly resource-constrained environments.

“So Jesse, where can uh, where can people find you if they want to learn more or follow or any other sort of stuff?”

“Yeah, all the things that are feeding these tools actually need to be get rid of the noise, capture all the data”