‘One day your company announces: stop everything, it’s AI Week. Build something with AI. ‘
Han Lee, The AI Great Leap Forward
Obviously, this quote was included my official AI Week introduction slides.
To sketch the rapid developments in AI since the take-off with Opus 4.5 in November 2025, I showed a bunch of different quotes I’d come across via Hacker News in recent weeks. Some elated, some depressed, some judgmental, some histrionic.
This one got some laughs.
So yes, we organized an AI Week.
I’m not a developer but I lead a team of developers. I’ve been using Claude Code since December 2025, building little apps, automating things, generally feeling the future reaching out from the clouds and putting working software in my hands.
But nobody on my team seemed to be doing that. And I kept thinking: Why is nobody talking about this? Am I the only one seeing this?
Make some room
The answer was obvious, once I stopped to think about it. People might be trying it out on their own time. But during work hours, we ask our people to work on specific features and client requests. There’s no room in that schedule for “go explore new technology.” And you can’t really expect everybody to study this stuff at home.
At the same time, I kept reading about how AI is going to change software development dramatically. The productivity gains I was seeing myself. I was vibecoding really decent apps in 4-5 evenings. If programming gets that much faster, everything downstream has to keep up. Testing, releases, client contact. The whole pipeline. How?
Our parent company is also doubling down on AI adoption, which gave me a nice tailwind. But even without that: our team needed to thoroughly engage with the most important technology development of our lifetimes. You can’t watch this one from the sidelines, and you can’t do it in a day.
So we organized a full AI Week. It was great.
What happened
So many chores are baked into software development that we’ve just accepted as the cost of doing business. Things we never got around to automating because we were always too busy building the next thing. Agents can handle a lot of that now. You just have to set them up.
So after some inspiring demos from advanced users, teams split up and spent two days on self-chosen projects. Real client work continued, it wasn’t a total shutdown. But the focus was on exploring what was possible.
Non-developer roles surprised me all week. They came in without preconceptions about what “proper code” looks like, or worries about maintainability and testability. They just went straight for what the technology could actually do for them. One customer support officer built an AI toolbox for checking clients’ bug reports, documentation (‘could be a feature!’), tone of voice, etc.
Beginner’s mind, in the best possible sense.
Obviously there were also skeptics going in. Some came around. Some still have doubts. That’s fine. The goal was never to convert everyone. It was to experiment as a team and build some shared experience. We did that. And we made a really good start on automating away those chores.
Once every few months, at least
I want to do this regularly. Every three to six months. People need time to adapt to new technology — and honestly, even before AI, I hadn’t done enough to just step back and let the team improve their own tools and processes. An AI week creates the permission to do that.
If you’re thinking about organizing something like this: do it. You don’t need an agenda. You need a week, a shared focus, and people who are curious enough to try.