Within digital evolution projects, do the IT team lead or support? This issue (not surprisingly) comes up a lot. However, given the core driver for all these conversations are around people, their employees, clients, stakeholders etc, the process is ultimately a people-first approach rather than technology first. IT (of course) has its place at the table as evolution programmes are discussed and planned, due to their inherent knowledge about the business and current systems therein. IT departments understand how these systems currently work and how they can be developed and used to greater effect. Digital evolution projects run parallel with BAU activities and the BAU environment is a core part of that evolution discussion, as it is ultimately about improving on what you currently do.
IT departments hold a lot of knowledge and insights which should be included in transformation programme discussions, however, it is important to remember that IT departments will also have developed their own departmental road-maps surrounding their department's offering within the business and technology infrastructure. They may bring with them a technology first bias. While Steve suggests that there are opportunities to merge evolution projects (IT and the rest of the business), the imperative should always be to address the organisation and end-consumer needs.
Great transformation programmes require a partnership mindset, with input from across the business with sales and marketing often being the custodians of road-map, as they tend to own those client relationships and understand the pain points and opportunities. When asked about what makes the ideal mix of departmental disciplines, Steve suggests that from an organisational perspective, we need to break down the silo thinking within and that the three C's, (Culture, Collaboration and Coalition) are central to the success of digital evolution project development and the delivery of a truly, transformational road-map.