What Actually Drives You? The Question Review Season Rarely Asks

Before you can design your career roadmap, you have to answer something harder: what do you actually want, and does that answer still hold?

I Didn't Plan Any of This

It is the end of Q1, which means annual performance review season is either already here or arriving fast for most of us. Calendars fill up with 1:1s, self-assessments get drafted and redrafted, and everyone is suddenly very focused on how the last year looked on paper.

What most people do not do is stop and ask the harder question underneath all of it: is this still what I want? And if it is, why?

I did not set out to build a career in games. I left consulting because I knew I needed out, took a chance on Zynga, and somewhere in the middle of building features for millions of players, something shifted. It stopped feeling like a job I had landed in and started feeling like work that genuinely mattered to me. I could not have told you that was going to happen in advance. Which is exactly the point.

Review season has a way of making us perform clarity we do not actually have. We frame our accomplishments, position ourselves for the next level, and move on without ever sitting still long enough to do the real reflection. Most people skip that entirely. I think that is a mistake, and I have made it myself.

The Startup Years That Taught Me What I Valued

After Zynga I spent time in startups, and it was disorienting in ways I didn't expect. Not because the work was harder, but because something I had taken for granted in games was suddenly missing.

In games, there is a shared orientation that I didn't have a name for until I left it. Everyone is pulling toward the same thing. The player experience, the product, the game itself, these are things people genuinely care about beyond their job description. When a feature doesn't land, it's personal in a productive way. When something works, the energy in the room is real.

In the startups I joined after Zynga, that orientation was fractured. Smart people, good intentions, but a constant undercurrent of individual agendas, territorial behavior, and complaints that seemed to take priority over the actual goal. I remember sitting in a meeting thinking: we have a clear objective, we all want this to succeed, why are we fighting about this?

That friction taught me something I couldn't have learned any other way. I wasn't just someone who happened to work in games. I was someone who was genuinely motivated by the kind of culture and creative energy that games, at their best, produce. That's different from having a passion for games as a consumer. It's a professional orientation, and it's worth knowing yours.

The Honest Tension Nobody Writes About

Here is the part that usually gets left out of career advice: passion is not always sustainable, and pretending otherwise does people a disservice.

There are seasons of life where chasing what energizes you most is the right call. And there are seasons where you have real financial obligations, where big tech's compensation dwarfs what games can offer, where the romantic idea of working on something you love starts to feel like a luxury you can't quite afford. Both of those realities are legitimate. Neither one cancels the other out.

I have watched people burn out not because they stopped loving games, but because they never gave themselves permission to admit that the equation had changed. They kept optimizing for passion at a moment in life when stability was actually what they needed. And I have watched the opposite, people who stayed in comfortable, well-paying roles long past the point where the work was giving them anything back, because they never stopped to ask whether the trade-off still made sense.

Review season is a useful forcing function precisely because it creates a moment to check in on this. Not just what have I accomplished, but what am I getting from this work, and what do I need it to give me right now?

Motivation Isn't Static

In a previous post I laid out a framework for designing your career roadmap intentionally, thinking in arcs, understanding your core PM mode, and knowing where you are in a product's lifecycle. If you haven't read it, it's worth doing alongside this one because the two fit together. The roadmap framework gives you the tools to navigate. This post is about making sure you know where you actually want to go before you start navigating.

Because what the framework doesn't address is the layer underneath all of it: your motivations, and the fact that they shift.

Early in my career I was motivated by mastery — staying in environments where I could learn fast, even when the title or compensation wasn't optimal. The trade-off made sense because the learning was the point. Now I find myself motivated most by impact, by whether the work creates something that outlasts my direct involvement. That is a very different calculus, and it took me a while to notice the shift had happened.

Neither phase was wrong. But each one required me to actually know what I was optimizing for, not just react to whatever opportunity was in front of me.

The Questions Worth Sitting With This Review Season

Not the questions your manager is asking. The ones you ask yourself, preferably before you open your self-assessment doc.

What is the work giving me right now? Not what it gave me two years ago, not what it might give me eventually. Right now.

What would I be reluctant to give up if I left tomorrow? The answer to that is often more honest than anything you'll write in a performance review.

Am I here because this is genuinely where I want to be, or because leaving would require making a decision I've been avoiding?

And the one that requires the most honesty: has my motivation shifted, and have I updated my choices to reflect that?

Games is a passion-driven industry, which is one of its great strengths and one of its quiet hazards. The culture attracts people who care deeply, and that caring is real. But it can also make it harder to have clear-eyed conversations about what you need from work at a given point in life, because admitting that passion alone isn't enough can feel like a betrayal of something.

It isn't. Knowing what you need is not a weakness. It is the foundation of every good career decision you will ever make.

Before You Write the Roadmap

Once you have done this reflection, the career roadmap framework becomes significantly more useful. Knowing your arc, your core PM mode, and where you are in a product's lifecycle are powerful lenses, but only if they are pointed in the right direction. Motivation is the compass. The framework is the map. You need both, and in that order.

So before you open your self-assessment doc this review season, before you think about your next title or your next role, do this first. Sit with the questions above. Be honest about what you are getting from your work right now and what you need it to give you. Then bring that clarity into the roadmap.

The decisions you make from that place will be better ones. I say that from experience.