Nobody Majors in Transformation

Published 2026-08-13 · Updated 2026-06-26 · By Alan Wizemann

Topics: Team Building & Culture, Product Strategy & Development, Startup, Growth Leadership

When people ask me how to get into transformation work, I usually have to start by admitting that I did not get into it on purpose. There is no degree for it, no major you can declare, no clean ladder you climb until one day the title is yours. I came up as a startup founder and an entrepreneur, a developer by trade who still writes code and still loves the act of building something that did not exist the day before. I took a company from an idea to a Series B, raised a meaningful amount of money along the way, and eventually saw it acquired, and in the course of all that I had to wear every hat in the building and learn, at least passably, how to do everyone else's job. That, more than anything, is where the work actually came from. I am a systems thinker by temperament (I want to understand how every piece connects to every other piece before I am comfortable). A small company under pressure is the most honest systems classroom there is.

So when I look at who is actually suited to this, I have to be honest that I lucked into the path rather than chose it. But the longer I have watched people grow into transformation roles, the more a pattern repeats itself, and an overwhelming majority of them came out of product management and product ownership. That is not an accident. A product owner already sits on top of a large, public-facing, interconnected system, already has to hold the whole thing in their head at once, and is therefore positioned to see the bigger picture in a way most other roles are not built to see. The leap, when it comes, is mostly a leap of scope – not a change of skill. You stop thinking the product is the mobile app you are shipping and you start thinking the product is the company itself, the way it operates, the way its parts talk to each other, the way value actually moves through it. It is the same mindset I always had, just aimed wider, with different ways to manage the work and very different patterns for how you communicate it.

The other group I keep finding is engineering managers, the ones who think organically about how their work touches everything around it, who cannot help noticing that the thing they shipped has consequences three teams over. They are often the most naturally gifted people in the room and the most boxed in – too contained inside a role that was never sized for how they think. The move there is rarely to teach them something new. It is to let them breathe, to get them out of their lane and talking to people across the organization, and to widen the scope until it matches how they already see the world.

None of this is something you learn in college, and I say that as a person with a particular vantage point on the question, because I never went. I do not have a degree, I do not have an MBA, and to this day I get quietly flagged by the hiring systems that screen for those credentials before a human ever reads my name. The cleanest example I can give is that Target had to change a company policy in order to hire someone at my level without a degree, which is either a flattering story or an indictment of the screen, and honestly it is a little of both. The work is learned on the job, in the doing, in the rooms where the stakes are real, and there is no syllabus for it because every situation rewrites the rules as you go.

I also owe anyone who wants this an honest warning, which is that a transformation leader does not have long tenures, and you should make peace with that before you start. You will have ten jobs in a career, not two. The work is high stress by its nature, because you are, in the plainest terms, a salesperson selling change to an organization that did not ask to be changed and frequently does not want to be. That takes a specific and slightly contradictory temperament, enough ego to keep pushing when everyone around you would rather you stopped, and not enough ego to refuse to be corrected when you are wrong, which you regularly will be.

And here is the part I care about most, because it is the part the career advice usually leaves out. Nobody does this alone, and anybody who tells you they did is either lying or about to fail. The single most reliable thing I have learned is to find the partners and come at the whole thing as a team rather than a hero. You want an engineering translator who can render the technical reality to the business and back again, and a project and delivery partner who can actually land the work after the vision is set. I have worked with the same handful of people across many different jobs for a simple reason, which is that I will never be better than they are at what they do, and pretending otherwise would only get in the way of the work. You do not assemble a team like that to fill out a roster. You assemble it because the problem is genuinely too big for one head.

The last thing I will say is the thing that took me longest to understand, which is that you cannot get the range of learning this work demands by sitting at one company for ten years and waiting for it to teach you everything. The range comes from the change itself, from being thrown into a new system you do not yet understand and having to learn it whole, over and over, in industries and cultures and structures that share almost nothing but the shape of the problem. The constant change is the cost of the work, the part that wears on you and shortens the tenures and flags you in the hiring systems, and it is also, if I am being truthful about it, the entire point.