The Snow Day That Never Came

By Rod Berger PsyD | N2N Services Inc. & LightleapAI | Storyteller in Residence

On a Thursday in late January, a man sat in his house in Atlanta, watching a forecast promise snow that never arrived, growing more impatient by the hour. His dog did not care about the weather.

He did.

Twenty-five days out, more than three hundred people were about to fill a room to celebrate the company he had spent fifteen years building. By his own admission, he had almost nothing he was proud to put on the screen.

I have sat across from many founders in exactly that state. The dream is vivid. What they can actually show you is not. Most of them keep selling the dream and quietly hope the gap closes on its own.

You’ve likely been in that room before, on either side of the table. The pitch that emphasizes the product’s potential, or a story that mostly promises. But observe what this person chose to do instead: he opened his laptop and began to build.

The Thing He Hadn’t Done in Fifteen Years

In fifteen years of running his own company, Kiran Kodithala had never once pushed a line of code into the codebase. He had made a deliberate choice years earlier to stay out of the work and live in the strategy, the architecture, the big dreams. That choice let him sell a vision. It also meant that when the vision finally had to become a shipping product, he had no muscle for building, and neither, it turned out, did the company he had taught to work the old way.

He had spent months trying to change that. He shared videos. He started channels. He told people, half jokingly, that he would fire anyone who opened a code editor before opening a prompt. Nothing changed. Then he stopped talking about it.

On January 30th, I stopped talking about it and decided to do it myself.

Kiran Kodithala

His son, Varoon Kodithala, who builds software for a living, had been telling him the same thing for months: start with the prompt.

So he did.

Within minutes, he was closing requests that had sat open for weeks. By the next day, he had shipped his first one. And then the most instructive part of the entire story happened.

Nothing.

He showed his team what a single weekend had produced and told them they could do it, too. They nodded. They smiled. They went back to business as usual. It took four of them two weeks to review and approve the work he had done alone. He watched that happen and concluded that this routine was the real crux of the story.

I couldn’t persuade the company to adopt a new way of working. I had to lead it there.

Why the Videos Never Worked

This is the part most companies get wrong, and the research is blunt about it. McKinsey’s global survey on AI found that adoption is now the norm, yet impact is nearly absent. More than 80% of organizations report no real effect on their bottom line from the AI they have implemented. Of the twenty-five factors the researchers tested, the single strongest predictor of actual financial impact was not the tools or the budget. It was whether a company had fundamentally redesigned how the work itself flows.

Only about one in five had.

So the videos were never going to work. The channels were never going to work. You cannot bolt a faster engine onto a process built to move slowly and expect it to keep up. The company has to be rebuilt around the new way, and somebody has to go first. That same survey found that when a CEO personally owns how AI is deployed and governed, the financial impact is measurably higher. Having the leader go first is not a motivational strategy. It is the variable that moves the result.

The Week That Beat the Year

What happened next reads like a different company. Kiran pulled a handful of his newer engineers into a small, deliberately secret team and handed them a deadline that should have been laughable. Kiran called his effort Project QLYAN and named his engineers Omnia Builders.

In a week, that tiny group did what a room full of developers and architects had failed to do in a year. Then they kept going.

Audio.

Video.

Live connections to the systems colleges actually run on. A voice assistant that had existed only in a vision document weeks earlier suddenly listened and answered out loud. Every time they raised the bar, they cleared it in days rather than months.

The gap between ‘impossible’ and ‘shipped’ is now measured in days.

Speed Has a Shadow

Let me name the part nobody likes to say out loud in a moment of triumph. Speed has a shadow, and those who study it for a living have measured it. Google’s DORA team, which has researched how software is actually delivered for more than a decade, found that as organizations adopt AI, individual developers get faster, happier, and more in flow, while the systems they build become less stable and less reliable. Their conclusion is not that AI is the problem. It is that the old fundamentals, careful testing, and small reversible changes, matter more in a fast world, not less.

Sit with those four developers who took two weeks to approve a weekend of work. In the new story, they are the bottleneck. In an older, equally true story, they are the rigor. They are part of why a platform that, by Kiran’s account, protects more than a billion dollars in student aid has not yet shipped something it cannot take back. He is careful to insist that the three million lines his team wrote this spring were not, in his words, AI slop.

I believe him.

The harder question is who gets to decide the difference when the distance between an idea and a live product has collapsed to a few days, and the person making the call is also the fastest builder in the building.

There is a quieter cost, too. When the founder proves it can be done, he proves something inspiring and something uncomfortable in the same motion. He shows the team a new ceiling. He also becomes, for a while, the single point everything routes through. And there is a less flattering truth that the best leaders learn the hard way: the ones who lift a team’s performance are the ones who make themselves less necessary, not more.

Going first is leadership.

Staying first is a trap.

What the Snow Day Actually Means

None of this diminishes what happened. A fifteen-year-old company moved like a four-month-old one, and it did so without throwing away the trust that took fifteen years to earn. That is rare. The people who pulled it off earned every bit of credit, and I would not hand the old pace back to anyone who lived through that January.

But the snow day is worth keeping for a reason beyond the obvious one. The obvious reading is that a leader stopped waiting and started, and so should you. The truer reading is harder. The moment you can build almost anything in days is the same moment you have to decide, faster than ever, what is worth building and what should stay on paper a little longer.

Here are the questions I keep turning over, the ones I would ask anyone standing where Kiran stood in late January.

· When the gap between impossible and shipped narrows to a few days, what happens to the people on your team whose value was their caution?

· If going first is what frees your team to move, what happens to that team the day you cannot let go of being first?

· You can now build nearly anything you can describe. So what will you refuse to build, and how will you know the difference between the dream that should ship and the one that should wait?

· And the one that stays with me: the snow never came, and he built anyway. What are you still waiting for a forecast to give you permission to start?

Check out Kiran’s full LinkedIn article.

The opinions expressed are solely those of the author and not a direct representation of N2N Services, Inc. or LightLeapAI.