Why Work Feels Fake - How big companies confuse activity with progress
Failed to add items
Add to basket failed.
Add to Wish List failed.
Remove from Wish List failed.
Follow podcast failed
Unfollow podcast failed
-
Narrated by:
-
By:
Why can an organization be full of intelligent people, enormous budgets, and constant activity — and still struggle to produce anything real?
Daniel and Maya go underneath the meetings and roadmaps, into the machinery that quietly turns work into the appearance of work: the wall between "the business" and engineering, the ticket-and-roadmap universe where progress is performed rather than made, architecture diagrams that describe a company that doesn't exist, and the finance, HR, and budgeting rituals that steer by the rearview mirror. Then the turn: AI is collapsing the cost of finding out the truth — and organizations built on ambiguity are about to find pretending very expensive.
CHAPTERS00:00 — Cold open: the meeting where everyone stays quiet03:45 — What this episode argues (and where it might be wrong)05:30 — Tech-company payroll, factory nervous system09:00 — Why reality is expensive and vagueness is cheap13:00 — The wall between "the business" and engineering17:00 — The restaurant where chefs never taste the food22:00 — Fourteen people approve an impossible plan27:00 — The parallel universe: tickets, roadmaps, fake progress30:00 — A €400k migration that changed nothing34:00 — Products that don't exist in the codebase39:00 — Microservices that share one steering wheel45:00 — Six weeks to add a text string48:00 — Why nobody writes reality down55:00 — AI as the unforgiving reader61:00 — Truth for cents, not millions64:00 — The resistance: finance, HR, budgeting71:00 — The alternative: teams that own reality end to end77:00 — What an AI would say your job actually is
Core models and further reading:
Daniel Reed and Maya Chen are fictional hosts performed with synthetic voices. Each episode is produced with AI-assisted research, writing, and audio tools, under human editorial direction and review.
Further Reading:
- Mel Conway — How Do Committees Invent? (1968) - the original statement of Conway's Law
- Fred Brooks — The Mythical Man-Month - why adding people and process doesn't make software faster
- Matthew Skelton & Manuel Pais - Team Topologies - designing team boundaries for flow and ownership
- Marc Andreessen - Why Software Is Eating the World (2011) - the moment every company became a software company
- David Graeber - Bullshit Jobs- the lived experience of work that produces nothing
- Goodhart's Law - "when a measure becomes a target, it ceases to be a good measure" - the one-line theory of ticket-driven work