Skip to content

Rituals of the Rubble: Why Your Spotify Squad is a Ghost Dance

Rituals of the Rubble: Why Your Spotify Squad is a Ghost Dance

The Cargo Cult of Big Tech and the obsession with borrowed efficiency.

The 13-Minute Lie

Dave is currently holding a digital marker over a virtual whiteboard that contains 53 different pastel-colored rectangles. He looks exhausted. He is explaining the ‘definition of done’ for a task that involves moving a database entry from one column to another. We are 43 minutes into a meeting that was scheduled for 13 minutes. This is a ‘stand-up,’ a ritual designed for brevity, yet we are all sitting down, staring at screens, feeling the slow heat of bureaucratic friction warming our laps. Dave calls us a ‘squad.’ It sounds like we should be fast-roping out of Black Hawks into a hot zone in Jakarta, but in reality, we are just a group of confused people trying to figure out how to use a Jira plugin that nobody actually asked for.

I sneezed seven times in a row before this meeting started, and each one felt like a small, violent exorcism of common sense. My sinuses are screaming, much like my professional intuition.

Consistency in Constraints

A

B

C

D

E

F

G

H

I

J

If 13-down doesn’t mesh with 23-across, the whole grid is a lie.

Revelation 1: The Cargo Cult of Big Tech

They are wearing the wooden headphones. They are waiting for the innovation to land. It’s not coming.

Buying the Fruit, Ignoring the Soil

We adopt OKRs (Objectives and Key Results) because Google uses them, but we turn them into a 333-page document that functions as a performance whip rather than a North Star. We forget that Google’s culture was the soil in which OKRs grew; you can’t just buy the fruit and glue it to a dead tree in your own backyard. It’s a superficial mimicry that ignores the underlying physics of how work actually gets done.

Adoption vs. Efficacy (The 333-Page Document)

33% Efficacy

33%

It’s easier to change the names of your meetings than it is to change the way you trust your people.

The Tailored Fit: Bespoke vs. Off-the-Rack

I’ve spent 23 years watching organizations try to skip the hard part. The hard part is looking at your own specific, ugly, unique problems and deciding to solve them with tools that fit. If you are a 33-person startup building a niche API, you do not need the same architectural overhead as a company that manages 103 petabytes of user data.

This is why I find the work of

Datamam

so refreshingly contrarian in the current climate. They operate on the radical notion that bespoke problems require bespoke development. They don’t try to force a client’s unique data needs into a pre-packaged ‘Spotify model’ template that has been recycled 53 times by a global consultancy firm. Instead, they look at the actual architecture of the problem.

Off-the-Rack Suit

Sleeves Down

Tripping Hazard

VERSUS

Tailored Fit

Perfect

Actual Shoulders

Most companies are walking around with sleeves trailing on the floor, tripping over their own borrowed brilliance.

Mimicry is the tribute that mediocrity pays to success.

The Tyranny of the Framework

When William C.-P. designs a crossword, he doesn’t start with the black squares. He starts with a core idea-a theme-and then he lets the words dictate the boundaries. The grid is the result of the content, not the other way around. In the corporate world, we have become obsessed with the grid. We define the ‘Agile Framework’ or the ‘Scrum Methodology’ first, and then we try to squeeze our human beings and our complex problems into those tiny, rigid boxes.

13 Product Owners

Organizational Symmetry on Paper

23 Days to Fix

Process Strangled Purpose

The ceremony of the process had completely strangled the purpose of the work. They were doing the dance, but the gods of uptime weren’t listening.

Revelation 2: Optimized for Deniability

If you follow the McKinsey-approved ‘Digital Transformation Roadmap’ and you fail, you can say, ‘Well, we followed the best practices.’ It’s a form of professional insurance.

The Mindset Fallacy

I asked if we had the automated testing infrastructure to support that. He looked at me like I had asked if we should sacrifice a goat in the server room.

43%

Sync Meeting Overhead

(Consultant: “We are adopting the mindset first.”)

That’s like saying you are adopting the ‘mindset’ of a marathon runner while sitting on a couch eating a bag of chips. The mindset is the byproduct of the discipline, not a substitute for it.

Why vs. How

We need to stop looking at the ‘How’ of Big Tech and start looking at the ‘Why.’ Why did Spotify create squads? Because they needed to decouple their release cycles to prevent one team from blocking another. If your teams aren’t blocking each other… then ‘squads’ are just a way to make your Org Chart look more like a Swedish art project.

What

Are we building?

👤

Who

Are we serving?

➡️

Path

Shortest route?

If the answer involves 13 daily stand-ups, then fine. But I suspect the answer is much simpler and much harder. It involves honesty.

Revelation 3: The Unconventional Success

It involves admitting that we don’t know what we’re doing and that copying Google won’t save us.

The Final Prayer

Dave is still talking. He is now explaining the ‘Velocity’ of the squad. He uses a chart with 33 data points. The line is going down, but he explains that it’s actually a ‘recalibration’ for a more sustainable future.

Velocity Trend (33 Data Points)

(Recalibration to sustainable future)

I look at the digital marker. I think about the Pacific islanders. I think about the 13-down clue in William’s next puzzle: ‘A false god made of straw and Jira tickets (10 letters).’

ANSWER: SUPERSTITION

We are all just praying to the wooden planes, hoping for a delivery that we haven’t earned the right to receive yet.

Maybe it’s time to stop the dance and start building something that actually flies, finally, finally, works in the real world.

Tags: