Forrester\n \n VP and research director Alex Cullen has seen all kinds of IT plans, the very best and the very worst.\n\n\n\n\n \n MORE ON Strategic Planning\n \n How to Get Real About Strategic Planning\n \n Anatomy of an IT Strategic Plan\n \n Four Strategic Planning Myths Debunked\n And he keeps files of both. "Most of them are pretty flawed," he says. One of the worst included a history of computing from 1960 on. Avoid these mistakes to make sure your next plan doesn't end up in his bad file.\n\nThe Doorstop PlanThis is not War and Peace. Aim for 15 pages, says \n\n\t\n Gartner\n \n VP Dave Aron, who saw one IT plan weigh in at 250 pages. Consider PowerPoint instead of Word as your medium of choice, says Cullen. It fosters brevity. And limit it to 25 slides.\n\n\n\nThe Shelfware Plan\n\nThere's nothing as worthless as what Aron calls the "write once, read never" plan. "The strategic plan needs to be a living thing," says IT consultant Laurie Orlov. To avoid seeing your plan become shelfware, keep the people who helped create it involved, have it handy and refer to it often. "One CIO I know starts every meeting with a strategy moment: He asks, how will our business win and how does this meeting help?" says Aron. "He had to cancel the meeting the first time because no one could answer the question. But everyone thought about it before the next."\n\nDon't Wait 'Til Next Year\n\nStrategic plans "require regular revalidation and refreshment," says Orlov. Michael Hites, CIO of \n\n\t\n New Mexico State University\n \n, updates his three times a year.\n\n\n\n\n\nThe Devil Really Is in All Those Details\n\nDetails don't belong in the strategic plan. It should be a stake in the ground, says Orlov. This is the year we introduce social networking tools in order to accomplish X, Y, or Z. It shouldn't include hard dates or product selections. "People start to turn strategic plans into project lists," says Cullen. "Then they don't know where to stop." If you feel you must include operational plans, put them in an appendix.\n\nCarved in Stone and Just as Heavy\n"You don't want to go the 'we-agreed-to-that-and-we'll-never-change-it' route," says Orlov. Expect the unexpected. "What if the company suddenly makes an acquisition or there's a leadership change?" Cullen asks. Want to really elevate your plan? Include scenario or contingency planning.\nThe English As a Second Language Trap\n\nToo many IT strategic plans are written in jargon. You're setting a direction for IT to support the business. Do so in business terms. "IT people that highlight buzzwords and product names are only doing an IT plan for their own department," says Orlov. Throw out the IT lingo. Connect your goals to key business drivers.\n\nOne Size Doesn't Fit AllIt sounds like a lot of work now, but it will save you time later: Create customized versions of your plan to address the differing needs of the plan's audiences\u2014the executive team, the IT department, business unit heads and vendors\/partners. At the very least, create a customized introduction or executive summary. The goal, says Cullen, is to have one strategy and several ways of presenting it.\nShooting for the StarsKeep it real. "Don't be too ambitious in your first plan," advises Cullen. "Don't try to change everything." When it doubt, underpromise and overdeliver.