The first direction typically parceled out for writing an IT strategic plan is to start with the business plan. Here's a bit of heresy: "Start with the business plan" is misleading advice for two reasons.
First, he who waits for the business plan to hit his desk is starting too late. In fact, that CIO may never get started at all - in the aforementioned study by Arlington, Mass.-based Cutter Consortium, almost a third of the respondents had no formally articulated business plan at all. But even at organizations that do formal business-strategy planning, the CIO needs to participate in the creation of that plan rather than waiting for it. CIOs play a crucial role in counseling executive leaders about new business possibilities opened by technology - a classic example being the new business channel opened by the emergence of the Web. If the CIO doesn't fill the function of advanced technology scout, the competitors' CIO will, giving the competition a huge advantage.
"Historically, strategic planning for the CIO has meant discerning the business's strategy and then trying to achieve it. Today I think [the CIO's role] cannot be reactive," says Darrell Rigby, a director at consultancy Bain & Co. in Boston. "The CIO has the capability to see where the basis for competition will be." That is not to say that CIOs should write their IT strategy independently and then attempt to force the business strategy to match it. Rather, the point is that both the business plan and the IT plan should be written collaboratively by the entire executive team, including the CIO.
The second problem with the "start with the business plan" mantra is that even formal business plans are often incomplete for IT purposes. Business strategies are typically written at a very high level. They frequently talk about markets, sales and distribution channels, and growth targets - but rarely address how the company gets its work done. Business processes - that's a place where IT can drive vital change and add enormous value.
That is precisely Fields' focus in writing Hon Industries' three-year strategic plan. Hon comprises seven operating companies. Fields wants to know how each of Hon's business units intends to conduct business. To understand that future state, Fields says, "we work with the operating company presidents and their direct reports. Take a business process like make-to-ship - how are we going to handle production and distribution in three to five years?" That discussion yields ideas and goals that aren't spelled out in the corporate strategic business plan. (Fields says he uses a formal methodology called Value Stream mapping for capturing current and intended future process definitions.) From there, Fields follows the typical steps of gap analysis and risk analysis. "From all this we derive a plan that says we have to move off of this system or modify that one," he says. In Hon Industries' case, the IT strategic plan will come in the form of a set of small booklets, one for each of the company's business units.