BTW, I think we talked about this when I was looking at CIO behavior for SAP a year or so ago. My take is that too many CIOs are obsessed with becoming "strategic" (aka "Partner Players" by your taxonomy). This obsession leads to the syndrome you identified because:
1.) They're acting out according to an archetype they want to be, not what is required.
2.) They have a disinterest in building a solid foundation in core functions, so they get distracted by problems with utility functions like e-mail, voice, etc.
3.) They believe game changing initiatives have to be big, so none of them question a multi-year timeline.
As you noted in "The Three Archetypes of IT," CIOs need to realize that "[a]spiring to be an archetype is different from being one."
Rating:
Hi Laurie,
Strong post...
BTW, I think we talked about this when I was looking at CIO behavior for SAP a year or so ago. My take is that too many CIOs are obsessed with becoming "strategic" (aka "Partner Players" by your taxonomy). This obsession leads to the syndrome you identified because:
1.) They're acting out according to an archetype they want to be, not what is required.
2.) They have a disinterest in building a solid foundation in core functions, so they get distracted by problems with utility functions like e-mail, voice, etc.
3.) They believe game changing initiatives have to be big, so none of them question a multi-year timeline.
As you noted in "The Three Archetypes of IT," CIOs need to realize that "[a]spiring to be an archetype is different from being one."
Best, Paul