There's a question worth asking about every pod you run. Not on a set schedule, just whenever you stop to take real stock of where things stand.

A pod, if you're not familiar with how this works, is a dedicated team built around a client: a project manager, a set of developers, QA, the same people every sprint, working as an extension of the client's own team rather than a rotating cast of contractors. It's a small, durable unit, which means the relationship lives or dies on trust between a handful of specific people, not on a logo or a contract.

If a client emailed you right now with bad news, would you feel dread, or would you feel fine? That one gut-check tells you more about the real health of a pod than any dashboard ever will.

The Metrics We Default To

Most of us measure pod health the way we were trained to: velocity, tickets closed, NPS scores, renewal probability models. Those aren't wrong. But they all measure the relationship after something has already gone right or gone wrong. They're lagging indicators dressed up as leading ones. The real test measures something upstream of all of it: whether the client trusts the pod enough to hear bad news early, while it's still small, instead of finding out once it's already the reason they don't renew.

It's an easy trap early in a career: believing the job is making sure clients only ever hear good news, and that if something isn't going well, the job is to fix it quietly before anyone has to feel uncomfortable. Most people take longer than they'd like to realize clients don't actually want a relationship free of bad news. They want a relationship where bad news travels fast, in plain language, from someone they trust to tell them the truth.

Why This Matters

There's real research behind why this matters more than it might seem. Amy Edmondson's work on psychological safety found that the teams that perform best aren't the ones that never have bad news, they're the ones where people feel safe enough to surface it early, without fear of blame. A pod is a small, tight-knit unit for exactly this reason. If the team doesn't feel safe bringing a problem to the client, the client doesn't find out about it until it's much bigger and much more expensive to fix.

That kind of trust isn't built in the big, visible moments, the annual business review, the recovery plan after a rough quarter. It's built in a hundred small ones nobody's grading you on:

Ask Yourself

Do you surface a slipping deadline the day you know, or the day before it's due? The gap between those two says almost everything about whether a client is a partner in solving problems or the last to find out about them.

Do you say "I don't know, let me find out" instead of guessing to fill the silence? A confident guess feels better in the moment. An honest "I'll check" is what actually gets remembered as trustworthy six months later, when the guess turns out to have been wrong.

Do you follow up on the thing nobody would have noticed if you hadn't? This is the one that's hardest to fake, because it only happens if you were actually paying attention in the first place, not just waiting for the client to ask.