‘“a lack of connection between innovation teams and their parent organization. Teams form/and are taught outside of their parent organization because innovation is disconnected from other activities. This meant that when teams went back to their home organization, they found that execution of existing priorities took precedence. They returned speaking a foreign language (What’s a pivot? Minimum viable what?) to their colleagues and bosses who are rewarded on execution-based metrics. Further, as budgets are planned out years in advance, their organization had no slack for “good ideas.

‘“a lack of connection between innovation teams and their parent organization. Teams form/and are taught outside of their parent organization because innovation is disconnected from other activities. This meant that when teams went back to their home organization, they found that execution of existing priorities took precedence. They returned speaking a foreign language (What’s a pivot? Minimum viable what?) to their colleagues and bosses who are rewarded on execution-based metrics. Further, as budgets are planned out years in advance, their organization had no slack for “good ideas.

‘“a lack of connection between innovation teams and their parent organization. Teams form/and are taught outside of their parent organization because innovation is disconnected from other activities. This meant that when teams went back to their home organization, they found that execution of existing priorities took precedence. They returned speaking a foreign language (What’s a pivot? Minimum viable what?) to their colleagues and bosses who are rewarded on execution-based metrics. Further, as budgets are planned out years in advance, their organization had no slack for “good ideas.

“As the company decides on its objectives and turns them into a definition of business value, the CIO takes this vision and works with the teams to implement these objectives thereby connecting the team to the goal and giving constant feedback on progress. The CIO is the enterprise architect and arbitrates the quality of the IT systems in the sense that they promote agility in the future. The systems could be filled with technical debt but, at any given moment, the sum of all the IT systems is an asset and has value in what it enables the company to do in the future.

“As the company decides on its objectives and turns them into a definition of business value, the CIO takes this vision and works with the teams to implement these objectives thereby connecting the team to the goal and giving constant feedback on progress. The CIO is the enterprise architect and arbitrates the quality of the IT systems in the sense that they promote agility in the future. The systems could be filled with technical debt but, at any given moment, the sum of all the IT systems is an asset and has value in what it enables the company to do in the future.

“As the company decides on its objectives and turns them into a definition of business value, the CIO takes this vision and works with the teams to implement these objectives thereby connecting the team to the goal and giving constant feedback on progress. The CIO is the enterprise architect and arbitrates the quality of the IT systems in the sense that they promote agility in the future. The systems could be filled with technical debt but, at any given moment, the sum of all the IT systems is an asset and has value in what it enables the company to do in the future.

“The UK Government Digital Service recently wrote about how they understand legacy and suggested a number of factors that contribute to technology being considered legacy: being poorly supported, hard to update, poorly documented, non-compliant or inefficient. The range of breadth of these negative characteristics runs counter to an often passive view of legacy: stable historic technology that is intended to be replaced. Organisations should begin to think of this technology as toxic: actively harmful to the health of the organisation.

“The UK Government Digital Service recently wrote about how they understand legacy and suggested a number of factors that contribute to technology being considered legacy: being poorly supported, hard to update, poorly documented, non-compliant or inefficient. The range of breadth of these negative characteristics runs counter to an often passive view of legacy: stable historic technology that is intended to be replaced. Organisations should begin to think of this technology as toxic: actively harmful to the health of the organisation.

“The UK Government Digital Service recently wrote about how they understand legacy and suggested a number of factors that contribute to technology being considered legacy: being poorly supported, hard to update, poorly documented, non-compliant or inefficient. The range of breadth of these negative characteristics runs counter to an often passive view of legacy: stable historic technology that is intended to be replaced. Organisations should begin to think of this technology as toxic: actively harmful to the health of the organisation.

“The UK Government Digital Service recently wrote about how they understand legacy and suggested a number of factors that contribute to technology being considered legacy: being poorly supported, hard to update, poorly documented, non-compliant or inefficient. The range of breadth of these negative characteristics runs counter to an often passive view of legacy: stable historic technology that is intended to be replaced. Organisations should begin to think of this technology as toxic: actively harmful to the health of the organisation.