The Experts

David Boyle
+ About David Boyle

About David Boyle

David Boyle’s 30-year career in the IT industry includes consulting roles with Accenture and Ernst & Young, as well as CIO leadership roles with CBA and NAB. As a consultant, David delivered numerous large scale technology projects as well as provided IT strategy and advisory services. His clients include Westpac, CBA, NAB, AMP, BOQ, St George Bank, Standard Bank (Africa), Standard Chartered Bank (Asia), Macquarie Bank and IAG.

As a transformational CIO, David spent the best part of a decade at CBA and most recently served four years as Group CIO at NAB. Overall, as a CIO, David is known for delivering; • large portfolios of IT projects and programs • dramatically higher agility • improved reliability and stability • increased employee satisfaction • enriched gender diversity • enhanced vendor performance • improved financial performance • reduced IT complexity.

Now, as Managing Director of CAP2ITS, an IT Advisory firm, David’s focus is helping organisations get significantly higher returns from their IT dollar through better governance of both IT performance and IT risk.

Does your business need to change?

Friday, November 02, 2018

The agile enterprise is a hot topic at the moment, with almost everybody doing something in this space. The extent to which organisations are adopting agile ways of working seems to vary enormously. Some have small islands of agility, say in a digital team, while the rest of the organisation continues to operate in a more traditional, waterfall style project model. Others go all-in with an enterprise-wide transformation to agile ways of working.  

Regardless of where you are, let’s start with one of the most common questions: Does moving to agile mean I need to restructure?”

I can see why this question is top of mind for everybody. There is so much new language within the agile community and much of it implies organisational change. Terms like “cross-functional teams”, “autonomous, self-directed teams”, “long-running, persistent teams”, “squads”, “tribes”, “chapters”, “communities”, “scrums”, “scrum of scrums”, etc, all point to changes in the way teams operate but does it necessarily mean organisational structures need to change?

Well it might, but it might not. There are indeed massive changes required to an organisation’s operating model to be truly agile, particularly at scale. Rather than starting with just structure, I have found it important to look at all of the following seven dimensions of how change is executed within an organisation:

  1. Organisation structure
  2. People KPI’s and incentives
  3. Culture and values
  4. Governance forums and mechanisms that support decision making
  5. Property and facilities
  6. Processes and supporting tools
  7. Sourcing and partnering.

For example, in the largest change I have experienced to agile ways of working (more than 1,000 people), every one of the above elements of the operating model needed to change bar one:

  • we adjusted where people sat to co-locate people that needed to be co-located
  • we adjusted people’s KPIs
  • we actively worked on cultural change to encourage empowerment, experimentation and learning
  • we changed governance over funding, prioritisation and resource allocation
  • we implemented new tools support agile ways of working; and
  • we established new partnerships with suppliers.

We didn’t modify the organisation structure in the first instance. In this case organisation structure change would have slowed, not accelerated the journey to agility because there was nothing in the org structure that prevented or hampered all the other changes we needed to make. Conversely if we had modified the org structure it would have distracted key people from the task of implementing all the other changes listed above and likely would have slowed the path to scaled agile.  

In this example, after a year of operating in this new model, we did then do some organisation structure fine turning to simplify and align skills and resources with the various divisions that were vital to the new cross-functional, agile model.  In the scheme of things, this modification of the structure was minor compared to all the other changes I listed above.

The key message here is yes, moving to agile will likely mean a lot of change to your operating model, but it may or may not mean modification to your organisation structure in the first instance.

Feel free to contact David on