Gustavo's newsletter landed in my inbox this week with a phrase that's been rattling round my head since: conversational debt. His framing is simple and a bit uncomfortable. Every crucial conversation your team avoids, or handles badly, doesn't disappear. It compounds, like a loan you keep not paying off, until the bill comes due at the worst possible moment.
Gustavo splits it into three flavours:
- Alignment debt - when people nod along in a meeting but walk out with three different understandings of what was agreed.
- Belonging debt - when speaking up starts to feel pointless or even disloyal, so people quietly stop trying.
- Collaboration debt - when decisions don't actually land anywhere, nobody owns the outcome, and the same problem gets rediscovered a few weeks later.
None of that is abstract to anyone who's run a team health check. It's the exact thing PETALS is trying to catch before it compounds. So I want to take two of the patterns Gustavo calls out and run them through two hypothetical teams, to see where psychological safety actually intervenes, and where it doesn't.
Two teams, same organisation, different debt
Picture a mid-size product company running two engineering teams against different OKRs, in different offices, each with its own product manager.
🗺️ Team Atlas has nine engineers, working out of the larger office. They're carrying three concurrent projects with long delivery times, the kind where a quarter can pass before anyone outside the team can see whether a bet paid off. Meetings are well attended, decisions get discussed at length, and on paper the team looks fine.
🪁 Team Kite has four engineers in the smaller office, down from six after two people left in the same quarter and weren't replaced. What used to be spread across six people is now carried by four, and the backlog hasn't shrunk to match.
Same company, same framework, two completely different flavours of conversational debt building underneath.
🗺️ Atlas: alignment and collaboration debt
At nine people, Atlas sits above the point where group dynamics start working against honest conversation. Google's Project Aristotle research found psychological safety was the single biggest factor separating its highest-performing teams from the rest, more than who was on the team. Above a certain size, that safety gets harder to sustain, because the more vocal people naturally dominate and quieter ones learn to hold back.
Gustavo's first sign shows up here almost exactly as he describes it: the people who used to push back in planning have gone quiet. Not because they agree now, but because raising a concern stopped changing anything, so they stopped raising it. That's belonging debt, and it's easy for a lead to mistake it for the team finally getting aligned.
The deeper problem for Atlas is collaboration debt. With three long-running projects and long feedback loops, decisions in planning get discussed, half-agreed, and then quietly revisited a sprint later because nobody was totally sure who owned the call. McKinsey's research on decision effectiveness found this kind of "decision decay" costs a typical Fortune 500 company around 530,000 days of management time a year. Atlas is a much smaller version of the same failure: agreement in the room, but nobody actually holding the decision once the room empties.
Gustavo's own research backs up how common this is: his Forward Talk study found 71.2% of executives admitted to disagreeing internally while agreeing publicly. Atlas doesn't need more meetings. It needs someone asking, before the meeting ends, "what are we agreeing to, and how does it change what you're doing on Monday?"
🪁 Kite: belonging and collaboration debt, from a different angle
Kite's problem doesn't look like Atlas's on the surface, but it's the same underlying failure to have a conversation that needed to happen.
After the two departures, the honest conversation was "we're carrying too much with too few people, and something has to give." Nobody said it out loud. Partly because a team of four doesn't want to be the one asking for help when leavers already made headcount a sore subject, and partly because everyone assumed things would settle down once the backlog cleared. It didn't.
This is belonging debt wearing a different mask; not people staying quiet because dissent gets punished, but because admitting you're underwater feels like admitting you can't keep up. The team's PM, sitting in a different office to the wider leadership team, doesn't see the day-to-day strain directly, only the missed dates. Without a deliberate channel for it, the actual cause never reaches the people who could fix it.
That silence has a cost that shows up in stress and burnout, not just delivery dates. CIPD's Health and Wellbeing at Work report found UK employees took 9.4 sick days on average last year, up from 7.8 in 2023, with weak wellbeing and feedback cultures named as a driver. A team that's quietly overloaded and not saying so is exactly the pattern that report is describing.
Where PETALS actually catches this
PETALS measures team health across five factors, Productivity, Enjoyment, Teamwork, Learning and Serenity, each scored regularly rather than surfaced once a year in an engagement survey. That cadence matters more than any individual question, because conversational debt is, by definition, a thing that builds quietly over weeks. A framework that only checks in occasionally will always be measuring the debt after it's already compounded.
For 🗺️ Atlas, Teamwork and Productivity are the petals that would move first. If the same people who used to challenge decisions start scoring Teamwork lower, or scores stay flat while the written comments get shorter and less specific, that's the early version of Gustavo's "your most vocal colleagues stop fighting" sign. Catching it in a snapshot means a lead can go and ask about it directly, rather than discovering it three sprints later when a decision unravels.
For 🪁 Kite, Serenity is the petal that would flag first, and probably weeks before anyone said "we're understaffed" in a meeting. A consistent dip in Serenity, especially concentrated in two or three people rather than spread evenly, is exactly the kind of signal that's easy to miss in daily standups but hard to miss in aggregated snapshot data. It gives Kite's PM something concrete to raise with leadership, instead of a vague sense that the team seems tired.
Neither example works if the psychological safety underneath it is missing. A snapshot only surfaces honest answers if people believe honesty won't cost them something. That's the same conclusion CIPD's evidence review on trust and psychological safety reaches: in psychologically safe environments, people are more willing to share views or admit mistakes without fear of punishment. The measurement tool and the safety it depends on aren't separate problems, they're the same one.
The debt doesn't clear itself
Gustavo's closing point is the one worth sitting with: teams don't choose conversational debt, they just don't notice they're taking it on. 🗺️ Atlas didn't decide to stop challenging decisions, and 🪁 Kite didn't decide to stay quiet about being short-staffed. Both drifted there one avoided conversation at a time.
What a regular health check changes isn't the conversations themselves, it's how early you notice they need to happen. Whether that's a lead learning their team has gone quiet, or a PM in another office finally seeing why delivery's slipping, the value is the same: catching the debt while it's still small enough to talk about, rather than after it's already due.
This is the kind of thing our newsletter subscribers hear about first. If you'd rather get product updates and insights like this straight in your inbox instead of waiting for the blog, subscribe below.