RheoData Blog | IT leadership mental health

TL;DR: Mental Health Awareness Month in tech gets treated as a wellness problem. It isn't. It's a workload problem. The senior DBA who hasn't slept in six months doesn't need a mindfulness app — they need the pager off their nights and the migration off their plate. If you lead a data or engineering team, the most direct mental-health intervention you can make this year is a staffing or scoping decision, not a newsletter. Fix the bowl, not just the fish. A friend sent me this drawing earlier this month. Two fishbowls. One upright, with a fish swimming in clean water. The other broken on its side, with a second fish stranded and gasping. The first fish has tipped its own bowl over to pour what water it had left into the broken one. The caption reads, Help others. Even when you know they can't help you back. It's a good image, and it's the right message for Mental Health Awareness Month. I wrote a personal note earlier this week saying as much. But I want to add something to it from the other chair I sit in. I run a data consultancy. I see burnout from two sides — what's happening inside our own team, and what's happening inside the client environments we work in. And the part of the image that nobody talks about is the bowl itself. The bowl that's broken. The reason that second fish is gasping isn't a lack of empathy from the other fish. It's that the container it was living in failed. That's what most tech team burnout actually is. Not a personal weakness. Not a lack of resilience. A broken bowl. A workload, an on-call rotation, a project plan, an org chart that finally cracked under the weight it was holding. What I See on the Other Side of the Table When I sit down with a CTO or a VP of Engineering, I usually hear some version of the same story. The team is stretched. There's an ERP migration on top of a Snowflake rollout on top of a compliance deadline on top of regular keep-the-lights-on work. Two of the senior people are quietly looking. One just gave notice. The on-call rotation has been reduced to four people because the others moved on, so each of those four is on every other week. The DBA who knows the GoldenGate configuration hasn't taken a real vacation in two years because nobody else can cover the pager. This isn't a wellness problem. It's an architecture problem. The bowl is too small for the fish, and the fish have been told to drink less water. By the time someone calls me, they usually aren't calling because they read a McKinsey report about burnout. They're calling because a person they cannot afford to lose is sitting across from them with a resignation letter. Why Another Wellness Email Doesn't Move the Needle Plenty of leaders do the right symbolic things this month. The newsletter goes out. The EAP gets re-promoted. Someone forwards an article about mindfulness. None of that is bad, and I'm not going to mock it. But if your senior DBA hasn't slept properly in six months because they're the only person on the team who understands the production replication topology, a mindfulness app is not the lever that helps them. The lever is taking that load off their plate. The lever is hiring, partnering, or automating the work that was costing them their evenings. The lever is changing the conditions that put them in the bowl in the first place. Mental Health Awareness Month is a useful prompt. It is a bad fix. The actual fix runs twelve months a year and shows up in capacity decisions, staffing decisions, and what you choose to outsource versus what you ask your existing team to absorb. What Actually Pours Water Back Into the Bowl I built RheoData around a specific belief — that the most valuable thing a consulting partner can do for a client is to remove the weight, not add to it. I'm going to be plain about what that looks like in practice, because if you're a leader reading this in May, you deserve more than platitudes. Take the migration off their plate. When your team is staring down a Snowflake rollout, an Oracle-to-OCI move, or a GoldenGate-based replication build, the choice isn't do it ourselves or do nothing. It's do it ourselves at the cost of our people, or bring in a team that's done this dozens of times. Our RedCore, FrostCore, and BlueCore accelerators exist for exactly that reason. They are the difference between a six-month grind that pushes your best people to the exit and a focused engagement that protects your team's calendar. Take the pager off their nights. If your replication, your warehouse, or your cloud database operations depend on two or three people who are quietly burning out, that is not a sustainable plan. Managed services and 24/7 coverage exist so that the person who knows the system best is not also the person whose phone goes off at 3 a.m. every weekend. That is one of the most direct mental-health interventions a leader can actually make. Assess before you commit. A surprising amount of burnout traces back to a poorly scoped project. The migration that was sold as four months and turns into fourteen. The lift and shift that turns into a full re-platforming. A proper assessment at the front of an engagement — which is how we open every project — protects your people from a death march that was built into the plan from day one. Right-size what you're already paying for. Cost optimization sounds like a finance topic, but it's a mental health topic too. The team getting beat up over a Snowflake bill or a cloud overrun is the team spending its weekends digging through queries instead of resting. Fixing the bill fixes the pressure on the people fielding the questions about it. None of this is exotic. It is the thing a good partner is supposed to do. I name it plainly because most of the marketing in our industry talks about transformation and never names the human cost of the projects that go sideways. The Business Case, Stated Plainly If you're a CEO, a CIO, or a board member, here is the case in language your finance team will accept. The fully loaded cost of replacing a senior data engineer or DBA in this market is not small. It isn't a recruiter fee plus a salary bump. It is the eighteen months of context that walks out the door with them. It is the project that slips because the bench got thinner. It is the security incident or the failed audit that gets caught later than it should have because the person who would have caught it left in March. Burnout is one of the most expensive line items on your operating budget that you are not currently measuring. The leaders I respect most are the ones who treat their people's capacity as a real constraint, not an infinite resource. They scope projects against what the team can actually carry. They bring in partners for the spikes. They invest in automation that gives time back. They retain their people for a decade instead of replacing them every eighteen months. That isn't soft. That's just management. The Point The fish in the picture is generous. That's the lesson most people will take from it. The lesson I want leaders to take is the one nobody says out loud — that even a generous fish can't fix a broken bowl by itself. Eventually somebody has to fix the bowl.

IT leadership mental health

The Bowl Is Broken: A CEO's Note on Mental Health Month and Tech Team Burnout

Recent Posts

The Bowl Is Broken: A CEO's Note on Mental Health Month and Tech Team Burnout

Migration vs. Replication with Oracle GoldenGate: One Tool, Two Very Different Jobs

Why Run Oracle Workloads on Google Cloud Compute?

Posts by Tag

Links