How to Have Honest Conversations About Team Health as a CTO
You’re in a one-on-one. You ask how it’s going. They say fine.
You know something’s off. Maybe it’s the tone, maybe it’s a pattern you’ve noticed over the last few weeks, maybe it’s nothing you can articulate at all, just a feeling. But “fine” is the answer you get, and “fine” is where most of these conversations stop.
The problem isn’t that people don’t want to tell you what’s actually going on. It’s that “how’s it going” is a question with an obvious, low-effort, safe answer built into it. Nobody has ever gotten in trouble for saying fine. Plenty of people have regretted saying anything more specific than that.
If you want the real answer, you have to ask a different question.
Why the standard question fails
“How’s it going” is broad enough that almost any response is technically true. It puts the entire burden of deciding what’s worth mentioning on the other person, in the moment, without any structure to help them figure out what you actually want to hear. Most people, most of the time, will default to the safest possible answer rather than do that work on the spot.
It’s not dishonesty. It’s just that an open-ended, low-specificity question invites an open-ended, low-specificity answer. If you want something more useful, the question itself has to do more of the work.
The questions that actually get you somewhere
Over time, I’ve found a small set of questions that consistently get past the “fine” answer, because they’re specific enough to require a real response, but open enough that the person gets to decide what matters.
“What’s something that’s filling your cup right now?” This one matters because it’s not just about problems. Starting with what’s going well does two things: it gives you real information about what’s actually working, and it signals that this conversation isn’t an interrogation looking for what’s wrong. People open up more easily when the first question isn’t already bracing for bad news.
“What’s something that’s draining your cup right now?” This is the direct counterpart, and it works better paired with the first question than asked on its own. By the time you ask it, the conversation already has some momentum and some trust established. The answer here is usually where the real signal is, a blocked piece of work, a frustrating interaction, a growing sense that something isn’t sustainable.
“What question haven’t I asked that I should?” This is the one that does the most work, and it’s the one most leaders never think to ask. It hands the engineer control over what gets surfaced, instead of you trying to guess the right question. Sometimes the answer reveals something you had no way of anticipating, because it was never going to come up under any of your other questions. Sometimes the answer is “nothing, I think we’ve covered it,” which is itself useful information.
None of these questions are complicated. What makes them work is that they’re specific enough to require a real answer, while still leaving room for the person to decide what’s actually worth telling you.
What to do once you actually hear something real
Asking better questions only matters if what happens next earns the honesty. A few things make the difference between someone opening up once and someone opening up consistently.
Don’t react like it’s a crisis. If someone tells you something that’s draining their cup and your immediate reaction is visible alarm or a rush to fix it on the spot, you’ve taught them that sharing something real triggers an outsized response. Sometimes people just want to be heard before they want a solution.
Follow up later, specifically. If someone mentions something is frustrating them, bring it up again in a future conversation, even briefly. “Hey, how’s that thing you mentioned last time going?” tells them the conversation actually mattered beyond the moment it happened in. This is often the single biggest difference between a one-on-one that builds trust over time and one that resets to zero every single week.
Don’t make it only about you extracting information. These questions work best as a genuine two-way exchange, not an interview. If you’re only ever asking and never sharing your own version of what’s filling or draining your cup, the conversation starts to feel like a data-collection exercise rather than a real relationship.
Why this matters more than it might seem
A one-on-one that only ever produces “fine” isn’t just a missed opportunity for connection. It’s a genuine blind spot in how you understand your team. The things that eventually show up as disengagement, burnout, or attrition almost always had an earlier, quieter version that could have surfaced in a conversation like this, if the conversation had been built to actually surface it.
The three questions above aren’t a script to run through mechanically every single week. They’re a starting point for building a habit of asking in a way that gives people room to be honest, instead of asking in a way that makes “fine” the only reasonable answer.
Where structured signals fit in
One-on-ones are essential, but they’re not the only mechanism, and they shouldn’t have to be. Not every engineer processes things at the speed of a weekly conversation, and not everyone is comfortable raising something in a live, synchronous exchange, even a well-intentioned one.
This is part of why CrewPulse exists alongside good one-on-ones, not instead of them. A weekly, anonymous check-in gives people a lower-stakes way to signal that something’s off, whether it’s workload, unclear priorities, or feeling blocked, without needing to find the right moment in a conversation to bring it up. It doesn’t replace the trust that gets built by asking good questions directly. It catches the things that trust alone doesn’t always surface in time.
The bottom line
“How’s it going” will keep getting you “fine” for as long as you keep asking it. The fix isn’t complicated, it’s asking questions specific enough to require a real answer, and then actually doing something with what you hear.
What’s filling your cup. What’s draining it. What question haven’t I asked that I should. Three questions, and the discipline to follow up on what comes back.
CrewPulse gives your team a weekly, anonymous way to signal what’s going on, alongside the honest conversations you’re already having. Start your free trial here.