One of the most misunderstood parts of modern IT leadership is that every meaningful technology project depends on the people outside of IT just as much as the people inside it. The challenge is that many non technical leaders unintentionally pull back from the early planning because they assume their job title exempts them from the messy parts. They are not trying to dodge responsibility, but the distance they create slows everything down. The truth is that they know the laws, policies, workflows, exceptions, and real world conditions far better than IT does. Without their knowledge, whiteboarding turns into guesswork.
The question I wish more leaders asked at the start is simple. What problem are we trying to solve, and who owns the vision for it after it goes live. Sustainability is not an upgrade cycle. Sustainability is a mindset that accepts that every system eventually needs to be maintained. When no one is thinking past the launch, the burden quietly falls on IT and the cracks show up later.
Another gap appears when the target audience is unclear. Who is using the system, what do they expect, and how do they experience the information created by it. When no one can answer that, the project drifts. Wrong assumptions pile up. People work hard but work in the wrong direction.
The tension that shows up in these moments is predictable. IT feels pressure to move fast, while executives feel overwhelmed and want the topic to disappear as quickly as possible. Both sides get tired and both sides feel misunderstood. That is when communication gets short and decisions get rushed.
As a seasoned IT professional, the most productive projects I have seen are the ones where leaders stay engaged even when the work is uncomfortable. Asking better questions does not require technical expertise. It requires curiosity, ownership, and the willingness to stay in the discussion long enough to shape the outcome.
What questions do you wish people asked before bringing you a new project?