Will ‘cloud’ adoption impact IT transformation lifecycle?
The existing transformation approach could be impacted in two ways
- Re-distribution in accountability between business & IT and as a consequence a slight but significant shift in the governance.
- Changes to build , migrate , deploy processes and as a consequence , changes in tools/ capabilities/Infrastructure supporting these.
While most commentaries on cloud architecture focus on point 2 above, it is not sufficient. While the tooling & foundational infrastructure aspect is critical, a key take away from observing organizations function is that tooling adoption is a by-product of broader organization change and not vice-versa. So, as a next measure , lets consider that point 1 might happen and then looking at the way AS-IS transformation process is organized , hypothesise what the impact might be.
I have organized the AS-IS transformation cycle in two parts. Part 1 depicts the planning & budgeting cycle. Part 2 depicts the operational governance of transformation.
A cloud architecture lends to buying onus shifting in favour of business teams. Its implications on the transformation process ( referencing Part 1 and Part 2 As-Is process) is schematically represented below
While this represents a subtle shift , the implication is significant – particularly as it relates to service and solution partnerships in the transformation cycle. Business teams may look for solutions to manage this governance that are domain and outcome led.