A few months ago, I had to cut back on a key technology project due to budget constraints, which meant reallocating some team members to other priorities. It was tough because the project was close to my heart, and the team had invested a lot of effort. I approached the communication with full transparency—I explained the financial realities and how this shift aligned with our broader company goals. I held a team meeting where I listened to their concerns and encouraged open dialogue. Then, I worked closely with each affected member to map out new roles that leveraged their strengths, so they still felt valued. Being upfront and empathetic helped ease frustration and kept morale intact, even as we adjusted our focus. I believe honesty and a clear connection to the bigger picture are key when delivering tough news to any team.
A few years ago, while leading the tech team at OSP, we were building a predictive analytics module to detect early signs of sepsis using patient data from EHRs. The project showed early promise, and the leadership was eager to showcase it in an upcoming release. However, during internal audits, we uncovered significant concerns related to data quality, model bias, and the lack of clinical interpretability—issues that could have real consequences in a clinical setting. It was a tough decision, but I chose to pause the launch. I knew this would impact morale—my team had invested months into the project and was excited about its potential. I called for a team-wide meeting, acknowledged their efforts, and walked them through the risks, not just technically but ethically. I emphasized that in healthcare, moving fast is important, but never at the cost of safety or trust. I also communicated transparently with stakeholders across legal and clinical teams, referencing FDA guidelines around AI in medical devices to frame our reasoning. In hindsight, that pause gave us the space to implement explainability features, strengthen model validation, and win over skeptical clinicians. When we relaunched, it wasn't just a tech win—it was a win for trust. That experience taught me that hard decisions, when communicated with empathy and clarity, can unify teams instead of dividing them.
Yeah—I had to let go of a project that a few of our engineers were really passionate about. It was technically impressive, but the business case wasn't there. We were burning time on something that wasn't going to move the needle. Tough call, but the way we handled it made the difference. I pulled the team in, walked them through the metrics, the opportunity cost, and the bigger picture. I didn't sugarcoat it, but I also gave them space to ask questions and be heard. The key was honesty and context. When people understand why a decision is made—and that it's about focus, not failure—they bounce back faster. In the end, that same team shipped something more impactful just weeks later.
In the early stages of scaling our backend infrastructure, we realised that our legacy tech stack, though familiar, was slowing down deployment and causing bottlenecks. I made the hard call to sunset a tool the team was deeply comfortable with and transition to a more scalable, cloud-native architecture. It meant re-training, longer sprints, and discomfort in the short term. Before anything changed, I gathered the team in a roundtable and laid out performance data, infrastructure costs, and the long-term roadmap. I didn't sugarcoat the challenges, but I made space for pushback, questions, and collaboration in refining the transition plan. Weekly check-ins and a shared migration dashboard kept transparency alive. It wasn't painless, but it reinforced a culture of trust, where tough calls weren't mandates but shared missions rooted in technical logic and strategic clarity.