The Cost of Staying Silent: AI, Leadership, and a Departure I Never Expected

TL;DR: When leaders fail to address real problems, and employees fear risking their positions by speaking up, silence can undermine an organization. In my case, I stayed quiet because I feared losing my job—and lost it anyway.

A Little Background

For nearly three years, I had the opportunity to work for a prominent university in the United States, helping develop an internally built learning management system, or LMS. By the time I joined, the platform had been in development for more than a decade and was already well established.

I arrived during a period of change. What had once been a team of four or five developers was expanding to include quality assurance, machine learning, and project management. It was an exciting time and a valuable opportunity to grow and contribute.

I also had the good fortune to experience the adoption of artificial intelligence firsthand. At first, AI was something we explored with curiosity and uncertainty. Before long, it began transforming how we developed software.

The revolution reached our doorstep. Leadership introduced an adoption plan, provided developers with Cursor accounts, and encouraged us to use it to improve our efficiency.

For me, that transition was difficult. It forced me to rethink the way I had worked for years and question practices that had helped me get where I was.

I was skeptical. I thought using AI would make me less capable because I would stop exercising the skills I had worked so hard to develop. How wrong I was.

When the organization began measuring AI adoption within our workflow, I felt pushed out of my comfort zone. But as I gradually changed my approach, I discovered that what I had seen as a threat could become an extraordinary tool.

Understanding that AI could amplify my abilities changed my perspective. I started exploring other options, and Claude became the first subscription I paid for out of my own pocket. I had learned how to improve my results and reclaim some of my time.

The team’s productivity began to increase. Leadership expanded access to AI tools for development, code review, and other tasks. The principle was simple: if a tool improved results, the organization was willing to invest in it.

A New Way of Working

AI did more than change how developers worked. It also changed how teams depended on one another.

While development accelerated, other departments continued operating through their existing processes. The bottleneck began shifting to the Product team: work that had previously been stalled was moving faster than new tasks could be prepared.

Who would have imagined it? In less than a year of adoption, one technology was putting pressure on processes we had relied on for years.

Leadership noticed the change, and its ambitions grew. New requirements emerged, along with a different vision for the platform. Until then, the system had primarily served the institution’s internal needs. Now, the goal was to turn it into a product with a broader purpose.

In my view, this is where one of the underlying problems began.

A system with that much development history accumulates technical decisions, dependencies, and complexities that are difficult to change. Our platform was no exception. Building new capabilities on that foundation meant working within constraints that did not always support the pace leadership expected.

From the beginning, I thought we should consider developing the new product separately if we wanted to make the most of AI. Over time, I came to believe that one of our mistakes was failing to make that case clearly enough.

I could see what we might accomplish, but I was cautious about expressing my ideas. Although I consider myself an optimist, I worked under leadership that prioritized stability and guarded it closely.

I consulted one of the team’s most knowledgeable members. His response made me understand that this was not the right time to raise the proposal and that it probably was not what leadership wanted to hear. I appreciated his candor, but the conversation also revealed a cultural problem.

My impression was that people working on-site understood an unwritten rule better than those of us working remotely: if something might upset the president, it was better left unsaid.

That perception shaped our conversations. In meetings, staying quiet seemed safer than disagreeing. Being the dissenting voice could put your job at risk. Fear of losing that job carried more weight than the need to raise a concern.

I was part of that silence, too.

I do not see the president as an authoritarian leader. I see him as someone with vision and a strong sense of direction. But I believe leaders can lose perspective when the people around them avoid challenging them or struggle to communicate problems effectively.

One lesson I take from this experience is that fulfilling our responsibilities sometimes requires respectfully challenging the person who gave us an opportunity. Being grateful for a position should not prevent us from saying what needs to be said to achieve better results.

Development and Its Constraints

Over time, the team went through several changes. AI had become part of our toolkit, and we were responding to new requirements more efficiently.

To build one of the most important features, a subgroup of five developers was formed. I will call it Team Delta. Each sprint began with its requirements, and each person worked on their assigned tasks.

But a tension soon became apparent: we had accelerated development without sufficiently adapting the process around it.

The problem was not Scrum itself, but how we were applying it. We continued breaking down work, assigning it, and putting it through review and approval stages that could take longer than implementation.

AI had changed our ability to execute, but the team still moved at the pace of its assignments and approvals. That pace did not match senior leadership’s expectations.

For several months, we tried to deliver results within that framework. Patience began to wear thin, and leadership brought in people from outside the department to move other parts of the project forward.

Initially, I thought this was a good decision. An experienced professional could help us identify obstacles, improve our processes, and make better use of the tools we already had.

That was what I expected.

How the Conflict Began

The introduction of outside personnel and the search for a new way of working unfolded over several months. At first, it was unclear how the two teams would collaborate, but meetings with leadership began showcasing their results separately.

A comparison soon emerged that would shape everything that followed:

Why could one person show more results than a team of five?

It was an understandable question. But answering it required context.

During the last meeting we all attended together, an AI usage chart was presented that, from my perspective, did not accurately capture how our team used AI or the conditions under which we worked.

That is the meeting I most regret leaving without speaking up.

The results seemed to show that one person could accomplish much more than we could. Yet no one clearly explained that the teams did not have the same autonomy, constraints, or approval process.

At least four factors should have been discussed.

1. Different Processes. Team Delta remained subject to rules and reviews that did not apply in the same way to the outside contributors.
   
   We had to move through the department’s established stages and obtain Product approval before advancing certain features. The new contributors had greater freedom to make decisions and execute.
   
   That difference mattered. You cannot meaningfully compare two teams’ speed without considering how much each can decide independently.
   
2. Tasks That Were Too Small. On several occasions, I told my supervisor that the scope of our tasks was limiting our ability to benefit from AI.
   
   Breaking work into very small pieces could make documentation, coordination, and approvals take longer than development itself. Each completed task led to another waiting period.
   
   How much can you accelerate a Ferrari over a fifty-meter stretch? You barely have time to press the accelerator before you need to brake.
   
   That is what it felt like to work with tools capable of moving much faster inside a process that repeatedly interrupted their momentum.
   
3. A Failure to Communicate. I believe those familiar with the team’s work had enough information to explain the disparity. I did, too.
   
   Yet we failed to communicate it as clearly as the situation required. I cannot know how much fear, caution, or individual interests influenced each person. What I can acknowledge is the result: leadership received a comparison without the context needed to interpret it.
   
   Our silence left the problem unresolved and allowed the numbers to speak for us.
   
4. Support That Never Materialized. I expected the consultant to help the team adapt and communicate its difficulties. I thought his experience would help us all work under better conditions and achieve better results.
   
   My disappointment came from feeling that this never happened.
   
   From my perspective, his advantage ultimately strengthened his individual position while the team’s obstacles remained unresolved. I do not object to his demonstrating what he could accomplish. I question why that ability did not translate into the support I had expected to address the underlying problem.

The Consequences

As I write this account, I recognize signs I did not understand at the time. There were changes in the weeks leading up to the decision, including a canceled meeting that I now see differently. I do not have enough information to say what each person knew, but I remember sensing that something was changing.

Meanwhile, the team remained committed to its deliverables. We had managed to remove some of the bureaucracy and overcome obstacles that allowed us to deliver more in less time.

Perhaps it was already too late.

I do not know when the decision to let us go was made. What I do know is that the meeting where the usage report was presented was a missed opportunity to explain our working conditions. I should have raised the points I describe here.

Later, the consultant presented a solution developed by one person in a very short time. He had greater autonomy and could move forward without the same restrictions we faced. From my perspective, that difference helped explain his results, but it was not given the weight it deserved in the comparison.

The end came on August 25, shortly after four in the afternoon.

Our laptops were locked, and soon afterward we lost access to the services that were still available. Four members of the team, including me, were let go.

We received no direct explanation from the institution. There were no emails, messages, or calls from those who had made the decision. The HR team at the company that managed our contracts was there for us and responded to our concerns with compassion.

Thank you, ZipDev, and especially Mariana, for that support.

It was painful to feel that an institution I had served responsibly and wholeheartedly could not communicate its decision with the care the people affected deserved.

I do not know whether that approach came from one person, several people, or a broader organizational practice. But the way an organization ends a working relationship also expresses its values.

The Disappointments

The hardest part was dealing with the disappointment.

I understand that organizations make decisions that affect their employees. What hurt was how it was handled. After years of work, I felt we had been treated as resources that could simply be disconnected without a conversation.

None of the people who made the decision reached out to explain what had happened or directly acknowledge the work we had done.

My greatest disappointment was with my direct supervisor, the department director. I had always regarded him as someone with strong values and principles. His absence during our departure was difficult to understand.

I do not know what instructions he received or how much discretion he had. But other colleagues reached out to offer support shortly afterward, and as of this writing, he had not.

Thank you, JD, for your leadership and for what you built. It was precisely because I held you in such high regard that your silence hurt.

The other major disappointment was with the consultant. I had come to appreciate him and believed we shared values and good intentions. That made it harder to feel that his involvement had strengthened his position without helping the team overcome its difficulties.

Steve, I do not resent your demonstrating your abilities or the results of your work. What I question is that I did not see the same commitment to addressing the conditions that prevented us from moving forward. To me, that distinction carries ethical weight.

Even so, it would be unfair to reduce my entire experience at the institution to this ending. I worked alongside extraordinary professionals, and I am deeply grateful to have been part of that team.

What This Experience Taught Me

Since leaving, I have taken time to revisit what happened, recognize my mistakes, and try to understand other people’s perspectives.

From senior leadership’s position, I can understand the need to use resources efficiently and achieve better results. If one person delivers more in less time, it is reasonable to ask what needs to change.

But answering that question well requires examining the conditions behind those results.

How much autonomy does each team have? How many approvals does it need? What previous work is it building on? How much time is spent developing, and how much is spent waiting?

In our case, I believe those differences were neither communicated nor examined thoroughly enough.

There was another factor that, in my view, deserves recognition: the consultant had access to the code and work the team had developed during the preceding months.

That work included architecture, implementation, debugging, and requirements we had already clarified. It provided a valuable foundation for accelerating delivery with AI.

I do not question his technical expertise. But I believe that results built on a team’s efforts should acknowledge that starting point. In my opinion, delivering in two weeks would have been much harder without that foundation.

Another lesson concerns how people are treated. Communicating a difficult decision to someone who has worked diligently for years takes character. Showing up, explaining, and listening are responsibilities of leadership.

Finally, this experience gave me a significant professional advantage. I had the opportunity to adopt technologies early that transformed how I work. I learned to use AI thoughtfully, explore its possibilities, and achieve results that previously would have taken much longer.

That, too, is part of this story and deserves its place.

Acknowledgments

Despite what happened, I am grateful for my time at the institution and for the people I worked with. Many of them helped me become a better professional.

AW, thank you for showing me the quality and depth of knowledge that talent and discipline can produce. Without your contribution, that platform might not exist as we know it.

JM, thank you for your excellent work managing the project. Your commitment and ability to coordinate multiple responsibilities were essential to bringing the team together and keeping the project moving. You are a vital part of what we built.

JY, thank you for helping me grow through our differences. Your character and approach showed me how much you care about your work. Working with you taught me to respond more methodically, focus on the facts, and explain my work clearly.

Above all, thank you for how you treated me when I left. You were the first person at the institution to reach out in solidarity. You also supported my search for new opportunities by posting recommendations on my professional profiles. My friend, you are an exceptional person. God bless you, and I wish you every success.

HN, thank you for your leadership during the final stage. You helped the team stand out through hard work and results, without ego or grandstanding. Your architectural contributions were fundamental to the new product and created a foundation others could build on. I also appreciate your support during my departure.

TW, AV, PV, and all my other colleagues, thank you for demonstrating the value of teamwork and making the department a place where I could learn and grow. Thank you for challenging me to become a better professional.

JD, I recognize that you built a department filled with exceptional professionals and fostered a stable infrastructure that was open to change. Your absence at the end left me with a different impression from the one I had formed over those years. I do not know whether that departure reflects your values, but I do know that how we treat people is part of the example we set.

To the institution’s president, I recognize your vision and your decision to adopt new technologies early. That investment expanded our capabilities and gave us lessons that continue to serve me today.

I hope you surround yourself with people willing to tell you the truth, even when it is uncomfortable. Those of us who understood the team’s work had a responsibility to explain what was holding back its results. That conversation should have happened more clearly and at the right time.

What I Can Say Today

It took me time to finish this article. There were many emotions surrounding my departure, and the uncertainty of feeling that my stability had been shaken left me angry and disoriented for several days.

Today, I feel I have made peace with the experience. That does not mean I have stopped questioning what happened. It means I can acknowledge both the pain and the value of what I lived through.

I was fortunate to be part of that team. My knowledge of AI and the way I work would not be the same without that opportunity. I carry forward lessons, relationships, and tools that will continue to shape my career.

I also carry a responsibility of my own: I should have spoken up.

I believe all of us who understood the problem shared some responsibility for not raising it in time. We might not have changed the decision, but we would have put information on the table that deserved to be heard.

Sometimes fear convinces us that staying silent protects our stability. In my case, the irony was painful: I stayed quiet because I feared losing my job—and lost it anyway.

I understand that leadership needed better results. I understand that AI makes it possible to do more in less time and that this changes business decisions. But that speed also demands a review of processes, an understanding of differences, and recognition of the work that makes new results possible.

Leadership reveals itself in those conversations—and in how it says goodbye to people who have contributed.

Today, a chapter closes. I thank God for allowing me to experience it and appreciate it while it lasted.

May this closed door mark the beginning of a new chapter in which I will continue giving my best, carrying a lesson I hope never to forget: when I see a problem that matters, I have a responsibility to speak up.