Leading without a map

I’ve worked on projects that had a clear direction from day one and projects where the direction changed every week. The difference in how a team feels under each is hard to overstate. When people know what they’re building toward, they make better calls on their own. When they don’t, everyone works hard and very little of it compounds.

The worst version of this I’ve experienced was walking into a production with no shared roadmap at all. No milestones anyone had agreed to hit. People were adapting on the fly because that was the only option, and it looked like productivity from the outside. From the inside it felt like running on a treadmill.

Building something nobody wanted to hold

At one point I put a roadmap together myself. Milestones, priorities, a sequence that gave the team something concrete to aim for. It was well received in the room. Outside the room, nobody committed to it. Priorities shifted again, features got reshuffled, and the document quietly became something no one referenced.

The lesson I took from that is about the difference between ownership and authority. I owned the roadmap. I did not have the authority to hold people to it. When nobody above you enforces the plan, the plan is a suggestion, and suggestions lose to whatever feels urgent on a Monday morning. I’ve seen this happen at more than one studio, and the shape is always the same.

Problems without takers

There’s a specific kind of frustration that comes from flagging a problem clearly, being told to come back with solutions, returning with solutions, and watching nothing happen. Not rejection. Not disagreement. Just silence, and then the next fire.

That cycle teaches you something about how studios handle risk. When the culture rewards reacting over preventing, the people who try to get ahead of issues start to feel like they’re working against the current. After enough rounds you learn to stop swimming upstream, which is exactly the wrong outcome for the team.

What I’d want next time

A roadmap only works if someone with authority defends it. The person who builds it and the person who enforces it don’t have to be the same, but both have to exist. I came out of those experiences a better planner and a clearer communicator, and I also came out knowing that planning into a vacuum produces a very polished document and zero results.

I’ve had roles where the growth path I was promised got consumed by fires before it ever started. At some point I stopped expecting the role to teach me what I needed and started extracting the lessons myself. That turned out to be a more honest kind of growth anyway.