Tuesday, three forty seven PM. Your phone buzzed. Terry asked if he could call you later. Terry is the fake name of the leader, but Terry could be you, or a friend of yours. There are a lot of Terrys right now.
You have known Terry for years. Ten years at their company. Joined right after the Initial Public Offering. You would grab drinks every few months, trading war stories about enterprise software. You told him yeah, after six. Terry said perfect, he had news.
Tuesday, six twenty three PM. Terry told you he got promoted. They want him to lead the AI transformation. Terry did not sound excited. Terry sounded tired. He asked if you saw TechCrunch today. Four Stanford kids just raised thirty million dollars for their Series A. Their product does exactly what Terry's company does. Twelve engineers. They are already processing the volume that takes Terry two hundred engineers to handle.
Terry said they just signed Meridian Financial. Your Meridian. Your first customer. The logo that got the company through the Initial Public Offering. Terry read you the quote from their Chief Technology Officer. They needed a partner who moves at AI speed, not committee speed.
You asked how long it takes Terry to deploy something. Six weeks. If nothing goes wrong. Product, Design, Engineering, Quality Assurance, Security, Legal, and a release committee that meets every other Thursday. There was a long pause.
Terry said it was funny. They are an agile company. They have done three transformations in ten years. Scaled Agile Framework, Spotify squads, objectives. Nine years of transformation. They have seven full-time agile coaches on staff. And they still take six weeks to ship a button. You asked what he was going to do. Terry said he did not know yet, but he would figure something out.
Friday, eight twelve PM. Terry asked if you were around. He needed to think out loud. The phone rang thirty seconds later. Terry found someone. An engineer named Sarah. She has been there six years. Terry has been watching her pull requests. She is closing tickets in hours that should take days.
He asked how. AI tools. She has been using them for three months. Nobody knows. She did not tell anyone because the last time she suggested changing how we work, she spent six weeks in meetings with the transformation team. They wanted to turn it into a pilot program with success metrics and a steering committee. She decided it was easier to just do it quietly.
You asked what the play was. Terry looked at the Git history. He found nine people shipping faster than they should be able to. Seven of them are using AI. Nobody is talking about it. All underground. You said he was building a shadow organization. Terry said he was building a band of misfits who can actually ship. He cannot change the company, but maybe he can route around it.
Sunday, three twenty two PM. Terry spent all day Friday with procurement and legal. You said that sounded terrible. Terry said it actually was not. He got them to approve enterprise licenses for AI tools. He ran it through security review and got legal sign-off on an acceptable use policy. It took four hours but now it is officially sanctioned.
You asked why he did that. Terry said because everyone he found is using AI tools they are paying for themselves. They are all terrified someone is going to find out and fire them for it. He needed to remove that risk. Now when he brings the band together, he can tell them this is legal, it is approved, and they are not going to get fired for using it. The only question is what they are going to build with it.
Monday, two thirty one PM. Terry got the band together. Ten engineers. He told them he got procurement to buy the tools and legal approved the use policy. Nobody is getting fired for this. That changed the whole conversation. The engineers relaxed. They have all been doing this independently. All sitting on techniques that could save everyone else weeks. All terrified to talk about it publicly. But now they know it is sanctioned, they opened up.
They are going to eliminate test environment maintenance in two weeks. Something everyone hates. Something visible.
Two weeks later, on Thursday at eleven forty seven PM. Terry said it works. Completely automated. It took thirty iterations on the prompt. They just stopped having test environment problems. You asked if he announced it. Terry said no. They just stopped having the problem. It took three days before another team asked them how they did it.
Tuesday, three fifteen PM. Terry asked if you could look at something for him. He sent you the link to an internal GitHub repository. It was brutally honest. It listed all thirty prompts they tried before finding one that worked. Why the first approach failed. The guardrails they built. The things they still do not trust AI to do. The actual time investment was eighty hours up front to save two hundred forty hours per team per quarter.
You told him it was really good and felt real. Terry said that was the point. He is making it internal open source. Anyone can contribute, but they have to show the production system they built with it. No theoretical examples. One of the agile coaches asked if they should create a Community of Practice with regular ceremonies and a charter. Terry said no. The repository has more contributions in two months than their last Community of Practice generated in two years.
Friday, four fifty two PM. Terry started a Slack channel called shipped with AI. If you ship something with AI, you post what you shipped, how long it took, a link to the pull request, and one thing that surprised you. You asked if there were celebrations. Terry said none. Just evidence.
Three weeks later, there were three hundred people in the channel. Posts every single day. They are getting competitive. A frontend engineer saw the backend team eliminating Application Programming Interface boilerplate. She asked if it would work for Redux actions. Two days later, she shipped it. You said that was viral. Terry said he did not mandate any of it. The culture is changing and he is not even trying to change it. Plus someone wrote a prompt for him to do his expenses.
Tuesday, two fourteen PM. Terry had a realization today. He cannot actually change the organization. Not at all. You asked if he was just figuring this out now. Terry said he knew it, but today he really internalized it. The Vice President of Engineering built the entire process. The Chief Product Officer controls the roadmap with commitments from two years ago. The General Counsel does not trust AI and she is not wrong. They are in healthcare and finance. If someone in the agile organization owns change, Terry just owns AI.
Terry said he is not trying to restructure the seven kingdoms. He is building a network underneath them. Engineers who know how to eliminate toil within constraints. You asked if something undeniable ships every three weeks. Terry said exactly. Last month they eliminated three hundred hours of manual test maintenance. This month they automated architecture decision records. Next month, deployment pipeline configuration. The board is no longer asking about headcount reduction. They are asking how to scale what Terry built.
Monday, eight forty seven AM. Terry told you that you would not believe this. The Stanford kids just lost their second customer. There was a production outage that lasted six hours. Their twelve engineers could not debug it fast enough. They built everything with AI, and when it broke in a way the AI did not anticipate, nobody knew how to fix it.
The customer came back to Terry's company. They said they need a partner who can move fast but also knows how to keep the lights on. They closed it in three days. Migrated them in two weeks. No outage. No drama.
Six months later, on Friday at six fifteen PM, you were finally getting that drink. You asked how it felt. Terry said it felt weird. The transformation they wanted would have taken five years. What he built is undeniable in six months.
You asked for the numbers. Deployment frequency is up forty percent. Toil is down twenty-five percent. They have one hundred fifty engineers actively using AI in production. They eliminated twelve hundred hours of toil last quarter. And he did not change the organizational chart. Terry said they did not change anything structural. They just stopped doing work that does not need doing. They shared what works. They built capabilities that compound.
Terry took a long sip. He said ten years from now, someone else sitting in his chair will inherit an organization that knows how to evolve. Not because they had a perfect strategy. Because they figured out what actually worked and they wrote it down.
You said the Stanford kids are building the future. Terry said they are, and his team is building the future that works when you have constraints. Both are necessary. But only one survives contact with enterprise reality. You said that was the bet he made. Terry said that was the job.
Your phone buzzed. Another text from another Terry at another company asking if you had time to talk. There are a lot of Terrys right now.
They are all figuring out the same thing. You cannot transform faster than your organization's immune system allows. But you can route around it. You can build networks underneath the organizational chart. You can make success contagious through evidence, not mandates.
The constraint is real. But so is the opportunity. The question is whether you are willing to lead a transformation that does not look like one.