Two-speed IT: An introduction for the Enterprise

Racing alongside each other

Lately, we’ve been working on several transformations which use the concept of Two-speed IT. It has slowly gained acceptance as a valid alternative to full-scale Enterprise Agility (on which I’ll write something soon).

But being that there isn’t that much information on the subject, I wanted to do a quick write-up.

So, what’s a Two-speed IT approach to Enterprise Architecture?

The Two-Speed IT approach to enterprise architecture is a concept that was introduced by Gartner in 2014. The approach involves dividing an organization’s IT systems into two separate categories: the core systems and the agile systems.

Core systems are the foundational IT systems that support an organization’s critical business functions. These systems are typically stable, reliable, and have a long lifespan. They require a high degree of security, control, and standardization to ensure consistency across the organization. These systems are often expensive to build and maintain, but they are essential to an organization’s success.

Agile systems, on the other hand, are designed to be more flexible and adaptable to changing business needs. These systems are developed using agile methodologies and are designed to be more responsive to new ideas and market changes. They are often less expensive to build and maintain than core systems, but they may not have the same level of security and control.

The Two-Speed IT approach recognizes that different parts of an organization may have different needs and priorities when it comes to IT systems. By dividing IT systems into two categories, an organization can better align its IT strategy with its overall business strategy. The approach allows organizations to balance the need for stability and security with the need for innovation and flexibility, and to adapt to changing business requirements more quickly and efficiently.

Why would you use Two-speed IT?

There are several reasons why an organization should consider using a Two-Speed IT approach. The approach involves dividing IT systems into two separate categories: core systems and agile systems. The core systems are focused on stability and control, while the agile systems are focused on innovation and flexibility. Here are some reasons why an organization should consider using a Two-Speed IT approach:

  1. Balance the need for stability and control with the need for innovation and adaptability

By dividing IT systems into two categories, an organization can balance the need for stability and control with the need for innovation and adaptability. Core systems are designed to be stable and reliable, while agile systems are designed to be flexible and adaptable. This allows an organization to maintain the stability and reliability of its core systems while still being able to respond quickly to changing business needs with the Agile systems.

  1. Increase innovation and agility

Agile systems are designed to be more responsive to changing business needs, which can help an organization to innovate and adapt more quickly. By using agile methodologies, such as Scrum or Kanban, organizations can develop new systems and technologies more quickly and efficiently. This can help to keep the organization ahead of the competition and improve its ability to respond to changing market conditions.

  1. Improve time-to-market

Agile systems can be developed more quickly and efficiently than traditional systems, which can help an organization to get products and services to market more quickly. This can be particularly important in industries where time-to-market is a critical factor, such as technology or fashion.

  1. Reduce costs

Agile systems can be developed more quickly and efficiently than traditional systems, which can help to reduce costs. Agile systems typically require fewer resources and can be developed using lower-cost technologies. This can help an organization to reduce its IT costs and improve its overall profitability.

  1. Align IT with business goals

The Two-Speed IT approach allows an organization to align its IT systems with its overall business goals. By identifying the areas of the organization where agility and innovation are most needed, the organization can focus its resources on developing systems that will support these goals. This can help to improve the organization’s overall performance and competitiveness.

How would you go about implementing it?

Implementing a Two-Speed IT approach can be a complex and challenging undertaking for organizations. The approach requires the development of two separate IT systems: one that is focused on stability and control, and another that is focused on innovation and flexibility. The goal is to balance the need for stability and control with the need for innovation and adaptability. In this article, we will discuss the steps involved in implementing a Two-Speed IT approach.

Step 1: Identify Business Goals and Priorities

The first step in implementing a Two-Speed IT approach is to identify the business goals and priorities. This involves a thorough analysis of the organization’s overall strategy, business processes, and IT systems. The goal is to identify the areas of the organization where agility and innovation are most needed, as well as the areas where stability and control are critical. This analysis should involve input from key stakeholders, including business leaders, IT professionals, and end-users.

Step 2: Develop a Two-Speed IT Strategy

Once the business goals and priorities have been identified, the next step is to develop a Two-Speed IT strategy. This involves defining the roles and responsibilities of the different teams involved in the approach, as well as the processes and methodologies that will be used. The strategy should be aligned with the organization’s overall business strategy and should take into account the needs of different business units and departments.

Step 3: Create Separate Teams for Core and Agile Systems

The Two-Speed IT approach requires the development of two separate teams: one for core systems and one for agile systems. The core team is responsible for maintaining the stability and reliability of the organization’s foundational IT systems, while the agile team is responsible for developing and implementing new systems and technologies that are more flexible and adaptable to change.

Step 4: Adopt Agile Methodologies

To implement the agile component of the Two-Speed IT approach, organizations should adopt agile methodologies, such as Scrum or Kanban. These methodologies are designed to facilitate collaboration, flexibility, and innovation, and are well-suited to the development of new, innovative systems and technologies.

Step 5: Invest in Training and Development

Implementing a Two-Speed IT approach requires specialized skills and expertise, particularly in the area of agile methodologies. Organizations need to invest in training and development to ensure that all team members have the skills and knowledge necessary to work effectively within the Two-Speed IT framework. This may involve hiring new staff or providing training for existing staff.

Step 6: Integrate Core and Agile Systems

Once the core and agile systems have been developed, the next step is to integrate them. This involves ensuring that the systems can communicate with each other and that data can be shared across systems. This integration should be carefully planned and executed to minimize disruption to business operations.

Step 7: Monitor and Refine the Two-Speed IT Approach

Implementing a Two-Speed IT approach is an ongoing process that requires constant monitoring and refinement. Organizations should track key performance indicators (KPIs) to evaluate the effectiveness of the approach and make adjustments as necessary. This may involve making changes to team structures, methodologies, or technology solutions.

What are the key issues in implementing in, in my experience?

Implementing a Two-Speed IT approach can present several challenges to organizations. Some of the major challenges include:

  1. Resistance to change: Traditional IT departments may be resistant to change and may be hesitant to adopt agile methodologies, which can slow down the implementation of agile systems.
  2. Cultural differences: The Two-Speed IT approach requires different teams with different cultures and ways of working to collaborate effectively. Core IT teams may be more focused on stability and control, while agile teams may prioritize flexibility and innovation.
  3. Integration issues: Integrating core systems with agile systems can be complex, especially if they use different technologies or have different data models.
  4. Governance and oversight: Balancing the need for agility with the need for governance and oversight can be challenging. Organizations need to ensure that agile teams are following appropriate processes and procedures to maintain the quality and security of their systems.
  5. Skill gaps: Developing and implementing agile systems requires specialized skills and expertise that may not be present in the organization. Hiring and training staff to work with agile methodologies can be time-consuming and expensive.
  6. Budget constraints: Implementing a Two-Speed IT approach can require significant investments in recent technology, training, and staffing. Organizations need to balance these investments with other priorities and budget constraints.

Overcoming these challenges requires a thoughtful and strategic approach to implementing a Two-Speed IT approach. Organizations need to prioritize communication, collaboration, and alignment between teams, and ensure that all stakeholders are engaged and committed to the approach.

Conclusion

Implementing a Two-Speed IT approach can be a challenging but rewarding process for organizations. By dividing IT systems into two separate categories, organizations can balance the need for stability and control with the need for innovation and adaptability. To be successful, organizations need to carefully plan and execute the implementation of the Two-Speed IT approach, investing in training and development, adopting agile methodologies, and monitoring and refining the approach over time. With a thoughtful and strategic approach, organizations can realize the benefits of a Two-Speed IT approach, including increased innovation, flexibility, and agility.

So, what are your thoughts? Is it a viable alternative to full on Enterprise Agility models like SAfe for your Enterprise?

Let me know in the comments!

Please note: I reserve the right to delete comments that are offensive or off-topic.

Deja un comentario

Tu dirección de correo electrónico no será publicada.