THE POST-PROJECT WORLD PODCAST SERIES

Three interconnected publications are coming that reshape how institutional leaders measure, govern, and manage organizational structure.The Coordination Capital Doctrine (July 7, 2026) is a governance specification establishing measurement, structural floor derivation, and board-level interpretation of coordination capital—the material share of organizational cost consumed by coordination activity. Forty-six thousand words. Hardcover. For CFOs, audit committees, and boards of regulated financial institutions.The Coordination Capital Compendium (May 2027) operationalizes the Doctrine. Forty-seven thousand words across fourteen chapters. Shows how to implement coordination capital measurement at scale using AI-assisted infrastructure while maintaining human governance authority. For CFOs, governance teams, and audit committee chairs beginning implementation.The Post-Project World: A Book (End of 2026) is the narrative companion to the Doctrine. Written for COOs, CIOs, and transformation leaders. Explains why project-based organizational models are breaking down, what structures emerge to replace them, and how to lead through continuous adaptation instead of discrete delivery cycles.Together, these three books form a complete institutional offering: the Doctrine establishes specification, the Compendium operationalizes it, and The Post-Project World book makes it intelligible to broader organizational leadership.Key Concepts Explained:Coordination Capital = the organizational burden created by synchronizing, approving, reporting on, and managing dependencies across your operation. In most mid-market institutions, coordination capital represents 18–35% of total labor allocation.Coordination Capital Ratio (CCR) = coordination capital ÷ total organizational cost. A single number telling you whether your governance structure is proportionate or drifting.Structural Floor = the minimum coordination capital your institution cannot reduce without violating regulatory requirements, breaking risk governance, or abandoning governance structures required by law.Coordination Drift = change in CCR over time. The moment when governance structures move from necessary to bloated.Who This Matters For:Institutions operating under intensive regulatory oversight where coordination infrastructure has become materially costly. Organizations where committee proliferation, reporting redundancy, and decision-making inefficiency have escaped active governance. Boards and audit committees asking whether their governance burden is sustainable.On This Episode:Luigi Rondanini walks through all three publications, their audiences, their relationship to one another, and why the timing matters now. He covers the £40M+ coordination drift example that shows why this measurement is not theoretical. And he explains what happens when institutions measure and govern coordination capital actively—they operate with structural advantages that competitors cannot easily replicate.The Doctrine is available now for pre-order on Waterstones, Foyles, and all major UK booksellers. Street date July 7, 2026.

We've seen the evidence. Netflix, Spotify, Haier, GitHub, Tesla and SpaceX—all operating without traditional project managers. We've traced the history from craft guilds to algorithms. We've examined why even Agile isn't sufficient.Now the question: why does this matter now? Why is this moment different from every previous wave of automation hype?Because we're at a tipping point. Multiple forces are converging that make the transition from human coordination to algorithmic coordination inevitable and imminent.In this episode, I explore:→ The AI capability threshold: when machines cross from assistance to autonomy→ The economic pressure: why coordination overhead is no longer sustainable→ The generational shift: new workers who expect different organizational models→ The remote work catalyst: how distributed teams accelerated the need for digital-first coordination→ The network effects: why each organization that transitions makes it easier for the next→ The point of no return: when staying traditional becomes riskier than transformingTransitions don't happen gradually. They tip. For decades, traditional project management was the safe choice. That calculus is reversing. Soon, the risky choice will be staying with human coordination while competitors automate it.This episode closes Season One. We've built the case. The coordination tax is real. The evidence exists. The historical pattern is clear. The forces are converging.Season Two begins the solution: the OrbaOS methodology, the new roles, the practices that make autonomous coordination viable.The tipping point is now. The only question is which side of it you'll be on.🎧 Available now on Spotify and all major platforms.

The Agile Manifesto was a genuine revolution. It identified real problems with traditional management and gave us better ways to work. Scrum, Kanban, XP—these methodologies have improved millions of projects.But here's the uncomfortable truth: Agile didn't eliminate coordination overhead. It redistributed it.Daily standups. Sprint planning. Retrospectives. Backlog refinement. These are still humans coordinating with humans—just in different patterns. A developer on a Scrum team spends 5-7 hours per week in ceremonies alone—that's 12-18% of their time. We replaced waterfall ceremonies with Agile ceremonies. The coordination tax remained.In this episode, I explore:→ What Agile got right: why it was necessary and what it solved→ What Agile got wrong: the assumptions that limit its effectiveness→ The ceremony creep problem: how Agile implementations become what they sought to replace→ Why "doing Agile" became more important than "being agile"→ The coordination overhead that Agile never addressed→ What comes after Agile—and why it requires a different foundation entirelyIf you're an Agile practitioner, this episode might be uncomfortable. But it's not an attack on Agile. It's an honest assessment of what Agile can and cannot do—and why the next evolution requires us to move beyond it.🎧 Available now on Spotify and all major platforms.

Humanity has organised work in fundamentally different ways across history. Understanding this arc helps us see where we're headed—and why this moment is different.In this episode, I trace the evolution of coordination through four distinct ages. Each transition seemed impossible until it happened. Each displaced roles that seemed essential. And each ultimately created more human value than it destroyed.I explore:→ The Craft Age: when masters coordinated through apprenticeship and guild membership→ The Industrial Age: when hierarchy and scientific management replaced craft knowledge→ The Knowledge Age: when networks and collaboration replaced command-and-control→ The Algorithmic Age: when machines begin coordinating what humans used to coordinateWe're living through the transition from the third age to the fourth. The signs are everywhere—if you know what to look for.Every previous transition was resisted by those who benefited from the old model. Every previous transition happened anyway. The question isn't whether algorithmic coordination will replace human coordination for routine work. It's whether you'll be ready when it does.This episode provides the historical context to understand what's coming—and why the post-project world isn't a break from history, but its continuation.🎧 Available now on Spotify and all major platforms.

Several listeners asked for a recap episode that ties together everything we learned from the case studies. This bonus episode is my response to that request.We've examined five radically different organizations—Netflix, Spotify, Haier, GitHub, and Tesla/SpaceX. Different industries. Different cultures. Different approaches. But they all point in the same direction.In this special recap episode, I synthesize what we've learned from each organization and identify the five common patterns that enable coordination without coordinators:→ Autonomous units: Stable, empowered teams rather than temporary projects→ Transparent information: Widely shared data that eliminates the need for status intermediaries→ Clear context: Shared understanding of purpose that enables aligned decisions→ Platform-enabled coordination: Technology handling routine coordination tasks→ Trust: Organizations trusting people to make good decisions with proper accountabilityThese aren't nice-to-have cultural attributes. They're architectural choices—decisions about how to structure work, information, decision-making, and human relationships.If you've been following along and want a consolidated view before moving into Season 2, this episode is for you. And if you're just discovering the podcast, this recap will bring you up to speed on the evidence that traditional project management is already being replaced.Thanks to everyone who requested this. Your feedback shapes the show.🎧 Available now on Spotify and all major platforms.

Elon Musk runs multiple complex organisations with significantly fewer middle managers than traditional competitors. Love him or hate him, there's something worth understanding here.SpaceX builds rockets with a fraction of the management overhead that NASA contractors require. Tesla scaled faster than any automotive company in history with an organisational structure that defies conventional wisdom.How do they coordinate without the usual layers of management?In this episode, I explore how mission-driven alignment can replace hierarchical coordination. When everyone understands the goal with crystal clarity—put humans on Mars, accelerate sustainable energy—you need less management overhead to keep people moving in the same direction.I examine:→ Why clarity of mission reduces coordination costs→ The first principles thinking that eliminates unnecessary process→ Flat hierarchies and direct communication across levels→ The "work wherever you're needed" culture that replaces rigid role boundaries→ The very real human costs of this approach—and why it's not a model to copy blindly→ What traditional organisations can learn without adopting the extremesMission as coordination mechanism isn't about working people to exhaustion. It's about alignment so strong that coordination becomes almost automatic.The question for your organisation: is your mission clear enough to coordinate?🎧 Available now on Spotify and all major platforms.

Linux is one of the most complex software systems ever built. Over twenty thousand developers have contributed to it. In a single year, more than four thousand developers submit changes across thousands of companies and every continent.And there's no project manager. No Gantt charts. No status meetings. No resource allocation spreadsheets.How is this possible?In this episode, I explore how GitHub turned coordination into infrastructure. The platform doesn't just store code—it replaces the project manager entirely for routine coordination.I break down:→ How issues, pull requests, and automated tests eliminate coordination overhead→ The Kubernetes example: bots doing the work of dozens of project managers→ A real case study: a PMO reduced from twelve people to four→ The principle that applies beyond software: work in systems can be coordinated by systems→ What remains for humans when platforms handle the routineThe GitHub model shows us the future. Platform handles the routine. Humans handle the exceptional. Platform provides visibility. Humans provide judgment.This isn't about making humans obsolete. It's about making humans more valuable.🎧 Available now on Spotify and all major platforms.

In 2012, Zhang Ruimin fired ten thousand middle managers. Not because Haier was failing—because he saw where the future was heading.Today, Haier is the world's largest appliance maker. Inside it operate over four thousand micro-enterprises, each functioning like an independent startup. No traditional hierarchy. No central coordination bureaucracy. Just small teams competing and collaborating simultaneously.This episode tells that remarkable story.I explore:→ The burning platform: why Zhang dismantled a structure that was already working→ Micro-enterprises: how teams of ten to fifteen people operate with full profit and loss responsibility→ The internal market: how micro-enterprises buy and sell services to each other→ Rendanheyi: the philosophy of zero distance between employees and customers→ What happened to the ten thousand middle managers (it's not what you'd expect)Haier proves that radical decentralization works at massive scale—eighty thousand employees across multiple continents, coordinating without traditional project management.If Netflix shows that tech companies can operate differently, Haier shows that manufacturing giants can too. No industry is exempt from this transformation.The coordination tax isn't inevitable. Haier stopped paying it.🎧 Available now on Spotify and all major platforms.

Microsoft just revised its AI growth targets by 50%. The Carlyle Group cut their Copilot spending. Gartner predicted 30% of AI projects would fail. The actual rate? 70 to 85%.In this bonus episode, I confront the question some of you have been asking: was I wrong about the post-project world?The short answer is no. The longer answer is more interesting.I break down what actually happened with Microsoft, why enterprise AI is harder than consumer AI, and what the current LLM landscape looks like for practitioners trying to get real work done. Claude, ChatGPT, Gemini, Copilot. Which one works for what. And why the gap between using AI and getting value from AI is exactly where human professionals need to be.The post-project world is still coming. We are just in the messy middle.This episode connects the theoretical future we explored in Parts One through Four with the reality of December 2025.Find me at sites.rondanini.net or on LinkedIn.

Spotify's Squad Model has been copied by thousands of organisations worldwide. Most implementations miss the point entirely.In this episode, I examine what Spotify actually did—and what they've learned since publishing their famous engineering culture videos.The model looks simple on paper: autonomous squads, chapters for functional excellence, guilds for knowledge sharing, tribes for coordination at scale. But the magic isn't in the structure. It's in what the structure enables.I explore:→ Why squads work: end-to-end ownership and the elimination of handoffs→ The chapter model: how Spotify maintains technical excellence without traditional management→ Guilds: voluntary communities that spread knowledge without coordination overhead→ The problems they don't talk about: what happens when the model scales beyond its original context→ Why copying the structure without understanding the principles usually failsSpotify didn't eliminate coordination. They redesigned it. The lesson isn't to reorganise your teams into squads tomorrow. It's to understand why autonomous teams with clear missions need less management overhead than traditional hierarchies.If your organisation is considering "going Spotify," listen to this first.🎧 Available now on Spotify and all major platforms.

Netflix has no traditional project managers.Let that sink in. One of the most successful companies in the world, operating in one of the most competitive industries, running complex technology and content production at massive scale, has eliminated the role we've been told is essential to organisational success.How do they do it?In this episode, I break down Netflix's "context, not control" philosophy—the radical idea that if you give people the right information, you don't need to tell them what to do.I explore:→ Radical transparency: why strategy documents are published internally before external announcements→ Decisions in memos, not meetings: how written communication eliminates coordination overhead→ Highly aligned, loosely coupled: the structure that enables autonomy without chaos→ What "adequate performance gets a generous severance" really meansNetflix proves that coordination without coordinators isn't just possible—it's more effective. The lessons here apply far beyond Silicon Valley.

Gartner predicts eighty percent of project management tasks will be automated by 2030. In this episode, I confront what that means for our profession—and why it's not the disaster it sounds like.I walk through every core function of traditional project management—scheduling, reporting, resource allocation, risk management, meeting facilitation—and examine which actually require human involvement. The honest answer is uncomfortable.But here's the twist: the death of the project manager role is not the death of human value. It's the opposite. When machines handle coordination, humans are finally free to do what we do best.If you've built your career on project management, this episode will challenge you. And then it will show you where the opportunity lies.

Welcome to The Post-Project World. In this opening episode, I share a disturbing discovery from a five million dollar treasury transformation programme: twenty-eight percent of the budget went to coordination overhead, not value creation.I introduce the Four M Framework—Meetings, Messages, Management, and Movement—and break down exactly how organisations hemorrhage resources on the friction of humans coordinating with other humans.You'll learn why the coordination tax scales faster than your organisation, why large companies feel so slow, and what a typical day looks like today versus what it could look like tomorrow when machines handle coordination.This isn't about eliminating human contribution. It's about redirecting it to work that actually matters.Visit OrbaOS.com to calculate your own coordination tax.