Many jaded IT admins will get wind of the rudderless boondoggle, then settle in their chairs, wait for the inevitable, and resign themselves to having to deal with whatever mess has been cooked up by those who don't understand how these things work. In doing so, they're working against their own best interests.
It's universally better if deep IT is involved in the initial stages of a new solution, as the time and agony saved is all but guaranteed to be their own. If nobody is inviting IT to these meetings, invite yourself. If mysterious vendors are showing up and talking to management, make sure to figure out what's going on before it becomes a problem and POs are cut.
The opportunity to elegantly mesh together many existing and planned infrastructure and projects may not come around often, but the goal is to make that not quite so rare. A few instances of successfully corralling projects in their infancy, and the ensuing successful deployments, might resonate with the right people, and the projects that wind up flying off the rails due to poor initial planning will become the exception rather than the rule.
We can only hope because the sleep and stress saved will ultimately be our own.
This story, "IT projects should start with IT people," was originally published at InfoWorld.com. Read more of Paul Venezia's The Deep End blog at InfoWorld.com. For the latest business technology news, follow InfoWorld.com on Twitter.