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.
During my time scaling ShipDaddy, our in-house 3PL that eventually grew to a 140,000-square-foot operation, I faced a pivotal technology decision that affected our entire engineering team. We were operating on a custom-built warehouse management system that had served us well in our early days, but was becoming increasingly unstable as we scaled to handle thousands more orders daily. The difficult decision was whether to continue patching our existing system or undertake a complete rebuild with a more scalable architecture. This meant potentially disrupting our operations during peak season and reassigning our entire tech team from feature development to system architecture for several months. I approached this by first gathering comprehensive data on system failures, developer time spent on maintenance versus new features, and projected growth. Then, I scheduled individual conversations with key engineers before bringing everyone together. These one-on-ones revealed insights I might have missed in a group setting and helped me understand each person's concerns. When communicating the final decision to rebuild, I was transparent about both the business case and my awareness of how it would impact their daily work. Rather than simply announcing the decision, I walked through our system failure rates, the cost analysis of maintaining versus rebuilding, and our growth projections that made the rebuild necessary. What worked well was creating space for the team to express frustration while also inviting them to shape the new system architecture. This ownership transformed what could have been viewed as a burdensome project into an opportunity to build something truly innovative. The experience taught me that technical decisions are ultimately human decisions. Engineers don't just want to know what to build, but why it matters and how their expertise is valued in the process. This approach has carried over to how we build our technology at Fulfill.com today—always balancing business needs with engineering realities through open communication.
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.
One of the hardest decisions I had to make at Zapiy involved sunsetting a legacy feature that a portion of our users—and a few members of our tech team—were deeply attached to. It was a feature that had history with us. Some of our early engineers had built it from scratch, and it carried emotional weight internally. But from a product standpoint, it was no longer aligned with our direction, added technical debt, and was draining valuable resources we needed for innovation. I didn't take that decision lightly. Before making the call, I spent weeks meeting with our product managers, engineers, and customer success leads to get the full picture—usage data, performance bottlenecks, customer sentiment, and future development costs. When it was clear that keeping the feature would hurt our agility and long-term vision, I knew it had to go. The communication part was critical. I didn't want to present this as a top-down decision. So I gathered the tech team and walked them through the data, the trade-offs, and most importantly, the why. I acknowledged their effort and the pride they had in building it. But I also made it clear that our mission demanded clarity and focus—and holding onto outdated elements for emotional reasons wasn't fair to the rest of the product or our customers. I also invited feedback and made room for honest discussion. Some people were disappointed, which was expected, but they appreciated the transparency and the fact that we didn't sugarcoat it. The result? Morale didn't drop the way I feared it might. In fact, the clarity gave the team room to rally around what came next. We redirected those resources toward building a new, streamlined feature that better served our users—and it's now one of our top-performing modules. The lesson for me was this: when you're transparent, data-driven, and respectful of the people behind the code, even tough decisions can lead to renewed focus and alignment.
One approach in such situations is to lead with clarity and empathy. When a difficult decision—like halting a project, reducing scope, or shifting priorities—impacts the team, the first step is to explain the why behind it. Avoid sugarcoating. People respond better when they understand the rationale, even if they don't like the outcome. Communicating it directly to the full team, followed by smaller group or one-on-one conversations, can help manage emotional reactions. It also gives space for questions that might not come up in a larger setting. Framing the decision in the context of broader business goals or constraints helps reinforce the bigger picture. It's also helpful to shift focus quickly to what's next—what roles will change, what opportunities still exist, and how support will be provided during the transition. That steadies the team and keeps momentum.
One of the toughest decisions I've had to make as a product and growth lead was to sunset a legacy feature that the tech team had spent months building—something they were genuinely proud of. The feature wasn't broken, but usage data told a clear story: it wasn't solving a real customer problem. Retention in that flow was flat, conversion rates were low, and support tickets were rising. Meanwhile, we were gearing up for a leaner, more focused roadmap and needed to free up engineering capacity for what actually moved the needle. I didn't go in swinging with just numbers. Before communicating the decision, I had 1:1s with engineers and designers who'd worked on the feature to understand their emotional investment and surface any unseen edge cases or technical debt tied to it. Then, in our team-wide meeting, I led with the why: not just the metrics, but the vision—where we were going, the customer outcomes we were prioritising, and how this shift would unlock the team's time for more meaningful work. I was transparent, gave room for frustration, and let the team challenge the decision. In the end, what helped was showing that I respected the craft while staying brutally honest about trade-offs. Great teams don't just want praise—they want purpose. And communicating hard decisions with empathy, context, and clarity is how you get their buy-in for the next challenge ahead.
We had to sunset a product that a part of our tech team had spent months building because it wasn't gaining traction and was eating up resources needed for a more promising project. It was a tough call because the team was emotionally invested and had done great work, but the data made it clear we had to pivot. I brought the team into the conversation early, walked them through the performance metrics, and shared the opportunity cost of not reallocating those hours. Instead of framing it as a failure, I made it about growth and impact. We shifted the focus to what we learned and how their skills would be critical to the new build. That honesty and respect kept morale intact, and the transition was smoother than expected.