At C-level, Credibility Means Success
Know the Risk: Digital Transformation's Impact on Your Business-Critical Applications REGISTER >
Among the questions CIOS most frequently ask me are, "How do I contribute to our business strategy when I am not sure we really have one?" and "How do I get buy-in from my executive colleagues when linking our business and IT strategies?"
Two issues are usually intertwined here: the lack of an articulated or coherent approach to business strategy, and the level of your credibility as a CIO.
The processes discussed in earlier columns for unearthing business strategies, generating maxims and teasing out their IT implications work very well if you can bring the right players to the table at the same time.
As many CIOs well know, this may be impossible, especially if you are still in the process of building or rebuilding your own credibility. To compound the challenge, if the business strategy being discussed has inherent contradictions, any IT-related investments made in support of that strategy risk being wide of the mark.
Some smart CIOs have tackled these challenges by "reverse-engineering" their business strategy. One example is John Petrey, executive vice president and CIO of TD Banknorth Inc., a Portland, Maine-based bank with $1.3 billion in 2004 revenues.
When Petrey took the position in late 2001, he figured his first challenge was to come to terms with the bank's business strategy, so he could determine some IT maxims to help shape major IT-related investment decisions. But Petrey soon found that he could not immediately get the attention of the key executives he needed.
At the time, the IT leadership team at Bank-north was struggling with three challenges. First, IT was seen as not pulling its weight in the ongoing operations of the bank. There were problems delivering everyday services as well as new applications. Consequentlyproblem No. 2managers of the bank's business units didn't value the IT organization. The units often made IT decisions without involving Petrey's organization.
And third, Banknorth's most senior corporate executives were almost completely disengaged from IT and the work of Petrey's group.
While fixing the operational problemsdaily service delivery and applications developmentPetrey also began working on deeper underlying issues within IT, such as poor alignment with _the business, limited business acumen within IT, and opaque IT processes. As he worked on these problems, it became clear that the company lacked an IT strategy allied with a clear long-term business vision.
Determining an IT strategy quickly became a priority, but creating one proved to be more challenging than expected. The major obstacle: an unfocused business strategy that was poorly documented at a sufficiently detailed level.
Drawing out implications for investment priorities and IT services proved virtually impossible.
Petrey found plenty of what he called "artifacts" of strategy, such as e-mails, memos and public statements by executives, and these he augmented with personal conversations. But it was hard for Petrey to get a handle on the sort of detailed business direction that he needed, and he didn't want to develop a set of IT maxims in a vacuum.
If they were going to work, Petrey knew that his maxims had to be based on the business directions, and they had to be reasonably detailed.
So Petrey decided it was best to work backwards. He and his team reverse-engineered a set of business principles and maxims from the artifacts they could identify. And from those, they constructed a "what if" set of IT maxims.
After discussing the derived business strategy and resulting IT maxims with Banknorth executives, Petrey was able to come up with a set of formally validated and accepted IT maxims.
Today Petrey and his staff have much greater input into the tough decisions around their IT strategydecisions involving how much time, money and energy to invest to IT-enable the business over the next two to three years.