What Leaders and Managers Can Learn from Palaces for the People
The whole book, compressed
This edition works through 4 core lessons — take them one at a time, not all at once.
What's different for your conditions
Tap whichever ones sound like you. Nothing here is sent or saved — it's just for your own noticing.
0 of 5 selected
The core lessons, applied to you
Seeing your workplace's gathering spots as real infrastructure
Leaders often see a break room, a shared lounge, or an open seating area as amenities to be trimmed when budgets tighten, missing that these spaces are doing real organizational work, letting people from different teams meet informally, hear about problems early, and build the trust that later speeds up hard conversations.
Walk your own workplace and name the two or three spots where cross-team contact actually happens, then treat protecting and lightly improving them, better seating, a coffee station people linger near, as a real management priority rather than a facilities afterthought.
How team connection quietly disappears
As teams grow or go remote, shared physical space shrinks or vanishes, meeting culture replaces hallway conversation, and the informal moments where people built cross-team trust get replaced by scheduled calls that only include people who already work together directly.
Before eliminating a shared space or defaulting every interaction to a scheduled meeting, ask what informal contact it was quietly producing, and build one deliberate substitute, an open office hour, a rotating cross-team lunch, that preserves some of that unplanned contact.
What strong team networks actually produce
Managers tend to reward and reinforce ties within a person's own immediate team, missing that the wider, looser connections built through shared common space are what let a team spot problems early, respond faster in a crisis, and draw on people outside their usual circle when something goes wrong.
Map who on your team has real working relationships outside their own immediate group, and if that map is thin, deliberately create one recurring cross-team occasion, a shared project, a mixed working session, rather than assuming those ties will form on their own.
Choosing to invest in what connects your team
An organization's resilience depends on more than its org chart or its stated values; it depends on whether leaders deliberately protect the ordinary spaces, physical or informal, where trust and information travel between people who would not otherwise work together. That is a design choice, not a byproduct of good intentions or a strong mission statement. A manager who treats a shared lounge, a cross-team ritual, or an open hour as worth funding and defending, even when it produces nothing measurable this quarter, is investing in the same quiet, connective capacity that determines whether a team can lean on each other when something breaks.
Sometimes protecting shared space collides directly with protecting output, a manager may need to cut the very open hour or shared lounge that built last year's best cross-team fix in order to hit this quarter's numbers. When these pull apart, treat connective space as a long-horizon investment competing on a different clock than quarterly output, and look for the smallest version worth preserving rather than eliminating it entirely.
Name one thing, honestly
- Which shared space in your workplace, if it disappeared tomorrow, would quietly cost your team the most trust? - Who on your team never crosses paths with anyone outside their own group, and what would change that? - What would it cost to protect one such space deliberately through the next budget cycle?
Good. Now look back at the "Try this" line under whichever lesson feels most connected to what you just wrote, and treat that as this week's actual assignment — not all 4 at once.
The practices from this edition
0 of 3 selected
Run this for seven days
Map who on your team has real working relationships outside their own immediate group, and if that map is thin, deliberately create one recurring cross-team occasion, a shared project, a mixed working session, rather than assuming those ties will form on their own.