How do I build a technical roadmap instead of just reacting?

Right now the work runs you. Things break, requests come in, and you react, with no larger plan pulling it all forward. That is exhausting, and it is a common place to be, not a personal failure. Reactive work fills every hour so completely that there is never time to lift your head and plan. That is exactly the trap. A roadmap does not have to be elaborate. It is just a short, honest answer to one question: where does this platform need to be in a year, and what are the few big things that get it there. Without that direction, every urgent thing looks equally important, and none of them build toward anything. Block two hours this week, away from the firefighting, and write down the three most important technical outcomes for the next six months. Just three. Then, when reactive work floods in, you have something to measure it against and protect a little time for. Direction is what turns a pile of tasks into a path.