Episode 44 - Dungeon Masters, Fake Agile, and the Death of Project Management

Episode Summary

Back from an Easter break, Martin and Adam go from home DIY and swapping agent frameworks straight into some of their spiciest material yet: domain knowledge gatekeepers they call “dungeon masters,” a takedown of Agile as a corporate plausible-deniability machine, and the customers.ai story of a CEO who eliminated his entire project management layer using event modeling. Along the way, a workshop attendee quietly ports Martin’s Claude Code agent loop to Amazon’s Kiro in 15 minutes flat, and the hosts start seriously exploring what it means to branch and merge event models like git.

Main Discussion Points

• Switching Agent Frameworks — Adam is moving some agent work from OpenClaw to Hermes for its proper indexed memory instead of relying on ad-hoc markdown recall
• AI Is Eating the SaaS Layer — ClickFunnels got cancelled, flat files and folder renames are replacing paid tools, and both hosts describe most subscription software as “10-20% used, 100% paid for”
• Two-Day Client Workshop, Zero to Slices — A client workshop went from a blank slate to a fully specified use case on day one and working implemented slices by day two
• A Live Kiro Port During the Workshop — An attendee silently used AI to translate Martin’s Claude Code “rough loop” setup to Amazon’s Kiro in about 15 minutes, and both tools ran side by side building slices
• The Secret Club of DDD / “Dungeon Masters” — A LinkedIn post about DDD practitioners gatekeeping behind closed doors echoes Alberto Brandolini’s 2014 “Dungeon Master” archetype — the person who hoards schema knowledge as job security
• The customers.ai Success Story — CEO Larry Kim’s LinkedIn post describes eliminating the entire project management layer within months of adopting event modeling
• Agile as “Plausible Deniability” — A quoted LinkedIn post argues Agile spread because it lets every management level dodge blame for failure, not because it works
• Product Owners Find Their Job Gets More Meaningful — Two POs in the workshop feared irrelevance, then realized slices free them from story points and Jira busywork to actually talk to customers
• No Stand-ups, No Retrospectives, No Blame — A decade of event modeling has meant no daily status theater — a slice is either done or it isn’t
• Branching and Merging Event Models Like Git — The hosts discuss treating design divergence as branches, merging individual slices back into a shared catalog, and syncing at the concept level instead of the canvas

The Dungeon Masters of DDD

“The event model is the mechanism by which you implement. That makes it impossible to hide behind any secret knowledge of how something works. So that is the Achilles heel of the dungeon master — the secret information. There is no secret information.” - Adam

Agile’s Real Selling Point

“The reason Agile spread like wildfire in the business isn’t technical, but that it provides plausible denial in the face of failure at every management level. And the only thing management loves more than that is money.” - Adam

Fifteen Minutes to Port a Rough Loop

“One of those people in the workshop silently in the background used AI to translate my cloud code rough loop setup to Kiro. And just a few minutes later, they had it running on Kiro, and we had both systems at the same time building slices hand in hand. It was really cool.” - Martin

Product Owners, Freed

“They realized, ‘Oh my goodness, there will be time I can talk to clients. I can talk to customers. I no longer have to do story points and all those Excel sheets and this nonsense. This will all be gone.’” - Martin

Key Takeaways

1. Indexed memory beats ad-hoc markdown recall — Hermes’ proper indexing over agent memory is a meaningful upgrade over hoping the right MD file gets pulled in
2. Most SaaS subscriptions are dead weight — Teams are canceling tools they use at 10-20% capacity and replacing them with small, event-sourced, freely-deployed tools
3. A two-day workshop can go from zero to running slices — Full use-case specification on day one, implemented slices on day two
4. Event models make secret-keeping structurally impossible — Unlike legacy codebases, an event model is the implementation mechanism itself, leaving “dungeon masters” nowhere to hide
5. Removing the PM layer is now a documented success story — customers.ai eliminated its entire project management layer within months, not just in theory
6. Agile’s rituals function as an accountability-dodging machine — Standups, retros, and story points let every layer of management claim “we followed the process”
7. Slice-based work ends status-update theater entirely — Done or not done, with no room for the subjective performance of daily standups
8. Event models can branch and merge like source code — Design alternatives can diverge as branches and recombine slice-by-slice into a shared catalog, syncing ideas rather than canvas pixels