Adapt, Don't Pivot

There is a word the startup world loves, and I have come to distrust the way we use it. Pivot. It sounds brave. It sounds decisive. A founder stands on a stage and says we pivoted, and the room nods like he just performed surgery on himself.

Changing direction is not the problem. Sometimes it is exactly what you need to do. The problem is when pivot becomes an instruction to throw away what you know: to treat your last decade as a sunk cost, a mistake to be corrected, a thing to apologize for. The older you get, the more that version of the word costs you, because you have more to throw away.

I started learning to build with AI in my late fifties, after a career spent running infrastructure most people never think about. Every reasonable voice told me some version of the same thing: that world is for the twenty-five year olds, the ground has shifted, you would be starting from zero. The honest translation was, pivot. Drop what you were. Become someone else.

I did not do that. I refused to treat thirty years of hard-won judgment as baggage. The young builders had the new tools and the speed. They did not have the scars. They had never sat in the room at two in the morning when the decision was real and the cost of being wrong was measured in something other than a metric. I had. That was not a liability to pivot away from. It was the entire point.

So I adapted instead. I kept the judgment and went and got the tools. I was the slowest learner in every room for a while, and I made my peace with that, because being two steps ahead in one thing and ten steps behind in another is exactly where the rare combinations get made.

Learning is how you weave it together.

But I do not want you to mistake that for a recommendation to collect tools. A little prompting here, a new app there, another saved tutorial you never use. That can keep you busy without making you more capable. The point is to understand how the tools work, connect them to each other, and put your experience in charge of what they are supposed to accomplish.

Think about something you already know how to judge. An operating report. A project review. A difficult decision. Learn how AI might help with one part of that work. Then learn how to check what it produces, how to connect the result to the next step, and where a person still needs to decide. You are weaving a way of working. The useful result matters more than the number of tools involved.

That is the invitation behind the academy: keep learning, apply what you learn, and connect it to the experience you already carry. I want others to make their own version of the journey I made. You do not need my career, and you do not need to become a different person. You need a learning path that helps you bring your own judgment into a changing technological world.

Keep moving. Keep learning.

Holding on to your experience does not mean holding still. Denial is not preparation. The tools will keep changing; no single course or application can finish the job of learning for you. Make learning a practice. Try something, examine the result, ask a better question, and use what you discover in the next attempt.

“

Learning never stops.

Hardeep AnandThe Systems Lens

If you are standing at the edge of your own second climb, wondering whether it is too late to learn the new thing, here is the advice I trust. Prepare yourself. Change direction when you need to. Adapt. Weave what you are learning into what you already know. Carry it all up the mountain with you. The scars are not weight. The scars are the map.

If you want help finding a learning path, ask about the academy and tell us what you want to learn. Start with your experience, the work you want to do, and the part you have not yet figured out. That is a useful place to begin.