GovLove

The episode contains a handful of genuinely non-obvious ideas - capability vs. capacity as distinct levers, innovation tools as 'apps' rejected by the underlying OS of government culture, and prototyping meaning different things at different developmental stages - but these are surrounded by extended conversational meandering, incomplete thoughts, and motivational sentiment that dilutes the per-minute yield of actionable ideas.

“human centered design is an app and process improvement is an app and applied behavioral science is an app and uh, sort of agile and digital perspectives. They're apps and oftentimes the core operating system, um, of government rejects those apps”

“blunt tools lead over time to blunt people”

Baskin synthesizes interesting frameworks - adult developmental theory applied to government, sortition as democratic reform, the design-for/with/by progression - but most ideas are borrowed from named authors (Laloux, Kegan/Lahey, Heath brothers) rather than first-principles thinking; the 'apps vs. OS' framing is the most original contribution and is moderately fresh for the local government context.

“from an expanded form of mind, that same prototype, it's a hypothesis. You know, here's a prototype, a test for my theory. I can handle being wrong if it leads to another, a better version”

“we really needed to have design by which M is. You know, when we hired Civic Design leads, their job was not to go and be designers. Their job was to hold the space for the people in the program to design their own features”

Baskin is a genuine practitioner who has run real programs across multiple governments at meaningful scale - outcomes-based budgeting in Chattanooga, a functioning Innovation Accelerator in a county of over a million people - rather than a career thought-leader; his credibility is operational and his experience is directly relevant to B2B operators navigating organizational change in large institutions.

“Montgomery county is over a million people. We got 9,000, um, amazing folks”

“we launched our performance data program, we launched our outcomes based budgeting program to change to make sure every dollar was tied to an outcome”

The episode features several well-chosen concrete anecdotes (the procurement director and the locked pen closet, the transportation-police accident report overlap) and some named references (300 cities on What Works City standards, Fort Collins and Dayton citizen assemblies, Elizabeth Linos's Public Servant Pulse), but there are no outcome metrics from the Accelerator program itself, no cost or timeline data, and the anecdotes are illustrative rather than evidentiary.

“these people are trusted with signing and approving the contracts for millions and millions of dollars. But if they want a pen, they have to ask someone at the front desk to unlock the supply closet to get a pen”

“we've had people eliminate their own jobs because someone in transportation and someone in police realized that they were in the same course in the same cohort working on the exact same accident incident report that was for 80% of it”

The host asks a few structurally decent questions (on how innovation has changed over careers, on preparing leaders for complexity) and occasionally attempts a follow-up, but the interview is dominated by affirmations and summary-and-validate responses rather than probing or productive disagreement; no speculative or abstract claims are challenged, and several genuinely debatable assertions pass unchallenged.

“Yeah. Yeah. No, I, I love that you're. You're different. I had a bunch of stuff I want to talk about, but I. There's something you said there that I don't want to leave”

“I'll make, I'll turn that I statement again. I don't know that I've been exposed to, like, good tools or ways of thinking to sit in that, that, uh, kind of complexity”