Regardless of what our minds conjure up when we think of airline travel, one thing we can readily observe is that while the weather, the experience of the flight crew, the mechanical condition of the aircraft, and the destination of the flight are all variables, the system of getting an aircraft from one place to another, in one piece, is extraordinarily reliable. Herb Kelleher of Southwest Airlines once joked that the airline business is the only place where the capital assets travel at 500 miles per hour.
Every commercial flight starts with a flight plan, a flight crew, an aircraft, and a destination. The dispatcher creates the plan based on the expected conditions for the flight, the limitations of the pilot and passengers, and the capabilities of the aircraft. Time is built into the plan to climb to cruise altitude and to descend again to reach the destination safely. How much fuel will be required is built into the plan and pumped into the tanks. Every activity is done to achieve a singular purpose: getting the aircraft and its passengers safely to the destination, and everyone involved knows where the destination is. Aviation is a study in viable systems design.
How strange it seems then, that thousands of IT projects begin every day, but more than one-third of them crash enroute. Why? I would argue that it's because there is seldom a clear destination in mind, a rational plan to get there, or a viable system approach in place to execute the plan. Most of the time, the destination and the means to get there are only vague estimates, and the elements of the strategy are rooted in hope.