Software Delivery in Small Batches

The proto-epic concept as a named liminal artifact between discovery and delivery has genuine operational value, and the idea of dynamic, team-owned exit criteria for the proto-epic column is useful. However, the episode is heavily padded with informal filler and the core ideas could be conveyed in two minutes, leaving the density low for a 12-minute runtime.

“These proto-epics only need to be sufficient for participants of the delivery process to transform them into the real epics.”

“the team writes the exit criteria for that column and they and it's dynamic they change it all the time based on what they're discovering about what needs to be done”

The 'proto-epic' label is a mildly fresh framing for a staged handoff artifact, but the underlying mechanics - WIP-limited queues, Kanban entry/exit policies, staged refinement - are well-established Kanban and SAFe concepts. The guest himself concedes 'this is probably not new or revolutionary,' and the episode doesn't offer contrarian or first-principles arguments.

“Jocko coined the term, and this is probably not new or revolutionary.”

“There's nothing revolutionary here. You just visualizing part of it.”

Jocko Selberg presents as a thoughtful practitioner who has applied these ideas on real teams, but his stated credentials are limited to co-hosting a YouTube show and participating in a Flow Collective community. There is no evidence of scale, executive seniority, or a notably consequential track record.

“Jocko also hosts his own show, The Complexity Lounge.”

“Jocko and I met in the Flow Collective. When I learned that he was also in Hawaii, we met up for a drink to talk Flow.”

The episode is almost entirely abstract process discussion with no named companies, no metrics, no timelines, and no dollar figures. The only concrete artifacts mentioned are Google Docs and Figma as informal containers, and the WIP limit is described only as 'x number of things' - never quantified.

“it's just this Google Doc and maybe there's an associated like Figma with it”

“those are WIP limited very tightly, again, so that you are not flooding the system”

This is an informal snippet between two friends rather than a structured interview, and it shows: there are no sharp host questions, no productive pushback, and the exchanges are largely mutual agreement and riffing. The host's interjections are reactive rather than probing, and claims go entirely unchallenged.

“Yeah. Okay. So you do all that. You get that point.”

“you're nailing it though that's that's exactly described it better than i could”