Field Note #12 ∷ The Rick & Morty Team Ritual

Most projects which ultimately fail do so already at the kickoff meeting — in the moment somebody promises a client, a board, or a steering committee that this one will be good, fast, and cheap.

Everything after is just the fallout of attempting to bypass thermodynamic constraints.

The Iron Triangle¶

The Iron Triangle is the oldest joke in project management. Good, fast, cheap — pick two. Everyone laughs. Everyone nods. And then a remarkable number of people walk straight back into projects scoped, sold, and staffed on the quiet assumption that this time, all three sides will hold.

They will not. They cannot. You can have good and fast — if you are willing to pay for it. You can have good and cheap — if you are willing to wait. You can have fast and cheap — if you don't mind doing it twice.

You cannot have all three, and the reason is structural. It's not vendor greed, lazy engineers, or poor planning. The same trade-off appears wherever coordination meets constraint. Distributed databases have the CAP theorem — consistency, availability, partition tolerance, pick two. Monetary policy has the Unholy Trinity — fixed exchange rates, free capital movement, independent interest rates, pick two. When unrelated fields keep converging on the same shape, you should suspect you are looking at a law rather than a proverb.

So what is the law?

Nomad's Razor¶

Underneath the Iron Triangle sits a ratio I call Nomad's Razor. Let R stand for "Project Resilience". Before a project can deliver anything at all, it must first survive, intact and on mission, all the way to the finish:

R = (C × M) / S

C is Coherence — mission alignment, shared context, mutual trust: the degree to which the team is actually one thing rather than a staffing chart. It is, at team scale, what the fourteenth-century historian Ibn Khaldun called asabiyyah (عصبيّة) at the scale of civilisations: the binding force, the felt solidarity that allows a diverse group to function as one. High coherence is why five aligned people routinely outbuild fifty micromanaged ones.

M is Mobility — the capacity to pivot midstream when reality disagrees with the plan: to re-decide, re-route, and re-assign roles without convening a committee. Mobility is the inverse of coordination drag. Every approval gate, every handoff, every "let me check with my chain" subtracts from it.

S is Surplus — everything the project must carry: budget, headcount, dependencies, tooling, process, meetings about meetings. All of this must be maintained — a standing tax, paid in the very coherence and mobility the surplus was meant to buy. Surplus is the unintuitive term, because our instincts insist that more resources must mean more resilience. They do not — and the proof has been in print for half a century.

In 1975, Fred Brooks — fresh from managing IBM's gargantuan OS/360 effort — published The Mythical Man-Month, possibly the most quoted and least obeyed book in software engineering. Its central observation, now known as Brooks's Law: adding people to a late software project makes it later. The reasons are arithmetic, not attitude. Every newcomer must be brought up to speed by exactly the same people who are currently productive and overworked. And each added person multiplies the lines of communication: ten people have forty-five possible pairs; twenty have a hundred and ninety. The work grows linearly while the coordination overhead grows roughly with the square of the team. Past a certain size, the project spends more energy synchronising itself than actually building the thing or accomplishing the mission. Amazon notably compressed this same arithmetic into their famous two-pizza rule: never field a team larger than two pizzas can feed. Bureaucratic ossification, in other words, is not a moral failure of large organisations. It is simply what surplus invariably tends toward at scale.

Now look back at the Iron Triangle. Good is high C — quality is coherence and coordination made visible. Fast is high M. Cheap is disciplined S. "Pick two" is not a negotiating posture; it is the ratio enforcing itself. Push any two terms toward their maximum and the third must give, because they were never independent dials. They are constituent elements of one thing.

The same ratio turns up at scales far beyond projects — in empires, markets, networks, and protocols — and that larger story, including the man who first glimpsed this concept while being lowered in a wicker basket over the walls of his besieged city to meet a conqueror known for building pyramids from the skulls of his enemies, deserves and will get its own Field Note on the perils of scale at the level of empire. Today, the question of project scale is enough.

Every project manager who ever said "pick two" was teaching physics without knowing it.

What You Cannot Buy¶

Here is the part kickoff meetings rarely cover.

Two of the corners can, within limits, be purchased. Speed can be rented — more people, better tooling, overtime, at least for a while. Frugality can be imposed — cut scope, cut features, cut corners. But the corner that decides whether the thing you ship is any good is made of coherence. And there is no dropdown in the procurement portal for coherence.

You can rent cloud. You can buy bandwidth. You can lease servers — heck, you can even lease developers. You cannot rent trust. An earlier Field Note made the long version of this argument at the scale of global incident response. The short version, at the scale of a single team, is this: coherence is built in small increments, through practice, over time — or it is simply absent on the day you need it.

So the Iron Triangle tells you what you cannot promise. It does not tell you what to do on Monday morning. What follows is one answer. This team ritual costs ten minutes a week.

The Ritual¶

During COVID, my team at the Belgian National CERT — the country's computer emergency response team, the people who answer when networks catch fire — was burning out. There was a lot going on in the cyber realm. Constant ransomware attacks and other firefights, chaos, cortisol, and social isolation. We needed a ritual that restored team coherence faster than the week destroyed it. I called it the Rick & Morty Team Ritual, after Rick and Morty — for readers of another era or another corner of culture: an animated series that premiered in 2013, about a chaotic genius grandfather who drags his anxious grandson through interdimensional misadventures. Morty's job, in essence, is to absorb the fallout of his grandfather's terrible decision-making. (Hold that thought.) I chose the name because naming things is free and laughter turns out to be load-bearing in a pandemic — and partly for a reason that requires a short detour through internet culture.

It works like this.

Each week, one person is Rick — the anchor, the scribe, the keeper of decisions. Rick holds the context. Rick protects the team's deep work from interruption. Rick is Rick all week.

Someone else is Morty — the first-line shield. Morty absorbs the incoming chaos: the tickets, the pings, the drive-by requests. Morty filters the noise and routes what actually matters. Being Morty is bruising by design, hence Morty serves short shifts — never more than a day — and then the role rotates.

None of this is an invention; it is an instance. Sailors and soldiers have run a version of it for centuries — the watch system rotates the burden of vigilance precisely because nobody can be effective as Morty for long.

One rule binds the whole thing together: you cannot be Rick unless you have first been Morty. The best restaurant owners I have known routinely schedule themselves a dishwashing shift on a busy Friday night, and their dishwashers stay well-maintained and team morale high because of it. The best restaurants I know make everyone incoming start off in the dish pit to prove their ability to do the work, regardless of their culinary diploma. Same principle. The role that grants authority is gated by having first carried the role that grants an informed perspective.

Then, every Friday at 4:20 — yes, 4:20; if the meeting time makes your team joke around, the ritual is already working — you hold a ten-minute team meeting. No slides. No drama. The only output is a short email under four headings: Wins. Lessons. Gratitude. Next steps. Morty writes it and sends it to leadership, with the entire team in copy.

Two of those headings explain themselves. The other two are doing the invisible work. Lessons is the team updating its priors on a weekly cadence — a discipline institutions fail at, one small unmade decision at a time. Calcification forms in the quiet; ten minutes every Friday afternoon deny it the ability to spread. And Gratitude is social currency — when it is not just performance. Credit given publicly, in writing, with names attached, is how a team's trust fabric refreshes itself. The counterfeit — the visible gesture without the substance — is ritual mimicry, and teams detect it instantly. Generosity only works as a social currency when it circulates. If you really want to make someone's day, praise them in front of their boss, in writing.

The week ends with coherence instead of cortisol. And instead of someone shipping to production at 4:57 for the dopamine hit, the team collectively drops an appreciation bomb at 4:37 — ending other people's weeks on a high note too.

Longtime readers have observed an example of this: an earlier soliloquy closed by asking you to forward it, with a simple thanks, to the invisible people who keep your computer systems from flying apart. That was an appreciation bomb before this note gave the phenomenon a name. The ritual just puts it on a weekly schedule.

Why It Works¶

There is an old idea underneath the ritual — one that resurfaces throughout history wherever a group's environment changes faster than instructions can travel. In any sufficiently complex undertaking, you cannot transmit commands fast enough to keep up with reality. What you can transmit is intent: what we are trying to achieve, and why it matters — together with the doctrine and the trust that let the person closest to the problem choose how to fix it. The nineteenth-century Prussian coinage for this is Auftragstaktik, leadership by intent; but the practice is far older. This is how a good head chef runs an entire dinner service without ever plating a single dish, and how a healthy open-source project survives its own maintainer's downtime.

Doctrine travels where dictates cannot. Decisions stay local. Coherence is what results — not from everyone being told what to do, but from everyone knowing what the team is for.

The Rick and Morty Ritual is leadership by intent in miniature. Rick guards the team's attention, which is to say its coherence. Morty's rotation distributes the burden of chaos and teaches every member of the team to find their own voice — including the quiet ones, who often turn out to write the best Friday emails. And leadership receives measurable momentum instead of mayhem: weekly, in writing, in under five minutes of reading.

In the terms of the ratio: each Friday lowers Surplus a little — chaos processed, decisions recorded, noise routed — and raises Coherence a little, while Rick's guard duty keeps Mobility from being nibbled to death by interruptions. The weekly increments are small, but they compound. Brooks asked how a project gets to be a year late, and gave the only honest answer: one day at a time. Coherence accumulates the same way, nudging the balance in the other direction — one Friday at a time.

The Caveat¶

This works for small, high-trust teams. Above roughly a dozen people — right at Brooks's arithmetic and the two-pizza horizon — coordination overhead spikes and coherence gets exponentially harder to maintain. Even Jesus capped the team at twelve, and He still had a Judas situation to manage.

So do not just blindly adopt this template. Adapt the pattern. The pattern is: structured rotation, shared responsibility, leadership by intent — a small weekly rhythm that steadily builds the one thing no budget line can deliver. Your version may have different role names, a different meeting time, a different set of headings. It should.

The Iron Triangle tells you what you cannot promise. The ritual is an example of what you can build instead.

This Field Note publishes on a Friday, at 4:20 — naturally. So let it close the way a week should:

Wins: You now hold a useful ritual that costs ten minutes a week; I have been meaning to write this essay for six months.
Lessons: Pick two — and build the third; it was never for sale anyway.
Gratitude: To Fred Brooks, who did the arithmetic; and to my old CERT.be team that ran this experiment with me back when the weeks were heaviest.
Next steps: Your move.

Start Monday.

— Trey

If you received this via email, the canonical archive version lives here: propertools.be/fieldwork/field-note-12-the-rick-and-morty-team-ritual/