domain design Commons: 3/5

Two-Speed Development Model

Also known as: Bimodal IT, Two-Speed IT

1. Overview

The Two-Speed Development Model, also known as Two-Speed IT or Bimodal IT, is an organizational pattern for managing IT and software development by separating them into two distinct streams, or speeds. The first speed, often called the “fast lane,” is focused on customer-facing systems and innovation, characterized by rapid, iterative development cycles (Agile methodologies). The second speed, the “slow lane,” is dedicated to core, back-end systems of record, where stability, reliability, and security are paramount, and development cycles are longer and more traditional (e.g., Waterfall). [1] [2]

The primary problem this pattern addresses is the inherent tension between the need for businesses to be agile and responsive to market changes, while also maintaining the stability and integrity of their core operational systems. The Two-Speed Development Model allows organizations to innovate and experiment with new digital products and services at a high velocity, without jeopardizing the foundational systems that run the business. [3]

The concept of two-speed IT was popularized by the consulting firm Gartner in 2014, who termed it “Bimodal IT”. [4] It emerged as a response to the challenges faced by large, established enterprises in the digital age, as they struggled to compete with nimble, digital-native startups. The model provided a framework for these organizations to embrace digital transformation without having to completely overhaul their legacy systems and processes all at once.

2. Core Principles

  1. Dual-Modal Operation: The fundamental principle of the Two-Speed Development Model is the management of two distinct, yet coherent, modes of operation. Mode 1 is optimized for predictability and well-understood areas, focusing on exploiting what is known and renovating the legacy environment. Mode 2 is exploratory, designed for experimenting with new ideas and solving new problems in areas of uncertainty. [4]

  2. Prioritization of Speed vs. Stability: The model explicitly recognizes that not all parts of the IT landscape require the same pace of change. It provides a framework for categorizing systems based on their need for speed and agility versus their need for stability and reliability. This allows for a more strategic allocation of resources and a more tailored approach to development and operations. [1]

  3. Decoupling of Systems: A key architectural principle is the decoupling of fast-moving, customer-centric front-end systems from slow-moving, transaction-focused back-end systems of record. This separation allows for rapid innovation on the front-end without compromising the stability and integrity of the core systems. [3]

  4. Blended Methodologies: The Two-Speed Development Model embraces a hybrid approach to development methodologies. The fast-speed stream typically utilizes agile and iterative methods to facilitate rapid development and continuous delivery. The slow-speed stream, on the other hand, relies on more traditional, structured methodologies like Waterfall to ensure the quality and reliability of core systems. [3]

  5. Parallel Development and Governance: The model advocates for the parallel development of both the fast and slow-speed architectures. This requires a new organizational and governance model where business and IT work together in an integrated way, with clear segregation of platforms and domains. [3]

3. Key Practices

  1. Strategic Portfolio and Project Intake: Establish a process for scoring and ranking projects to align with strategic objectives. This allows organizations to decide which initiatives belong in the fast lane (Mode 2) and which belong in the slow lane (Mode 1). [5]

  2. Segregated Teams and Governance: Create distinct teams for each speed, with governance models tailored to their specific needs. The fast-lane team should be empowered with autonomy and a high tolerance for risk, while the slow-lane team should operate under a more structured and rigorous governance framework. [3]

  3. Capacity and Resource Planning: Implement capacity and resource planning modules that can simultaneously model resource allocations across both waterfall and agile areas of the organization. This provides a holistic view of resource utilization and helps to identify potential bottlenecks. [5]

  4. Microservices Architecture: Adopt a microservices architecture to decouple front-end and back-end systems. This enables the independent development, deployment, and scaling of services, which is a key enabler of the two-speed model. [3]

  5. Continuous Delivery and DevOps: Implement continuous delivery and DevOps practices in the fast-lane stream to automate the software development lifecycle and enable rapid, frequent releases. [2]

  6. Milestone-Based Planning and Tracking: Use milestone-based planning and tracking to provide a common language and a unified view of progress across both streams. This helps to align the two speeds and ensure that they are working towards the same overall goals. [5]

  7. Forecasting and “What If” Analysis: Utilize forecasting and “what if” analysis modules to predict delivery horizons and assess the potential impact of changes across both the fast and slow lanes. [5]

  8. Enterprise Financial Reporting: Implement enterprise financial reports to plan, measure, and report on the financial aspects of the software delivery process across both speeds. This provides a comprehensive view of the costs and benefits of the two-speed model. [5]

  9. Project-Based Dependency Model: Use a project-based dependency model to link high-level projects to delivery features. This helps portfolio managers to understand the dependencies between the two speeds and to plan accordingly. [5]

4. Application Context

Best Used For:

  • Large enterprises with significant legacy IT infrastructure: The model provides a pragmatic approach for established organizations to innovate without being encumbered by their legacy systems. [3]
  • Organizations undergoing digital transformation: It offers a phased approach to digital transformation, allowing companies to gradually modernize their IT landscape while continuing to deliver value to the business. [4]
  • Companies in industries with a high rate of digital disruption: The two-speed model enables companies in sectors like banking, retail, and telecommunications to respond more effectively to the challenges posed by nimble, digital-native competitors. [1]
  • Situations where there is a need to balance innovation with stability: It provides a framework for managing the inherent tension between the need for rapid innovation and the requirement for stable, reliable core systems. [2]
  • When a full-scale agile transformation is not feasible or desirable: The model offers a middle ground for organizations that are not yet ready or able to adopt agile methodologies across the entire enterprise. [5]

Not Suitable For:

  • Small, agile startups with no legacy systems: These organizations are typically better served by a single, high-speed development model.
  • Organizations where all systems require a high degree of agility: If all systems are customer-facing and require frequent updates, a two-speed model may introduce unnecessary complexity.
  • Situations where there is a high degree of interdependence between front-end and back-end systems that cannot be easily decoupled: The model relies on the ability to decouple the two speeds, and if this is not possible, it will be difficult to implement effectively.

Scale:

The Two-Speed Development Model is most applicable at the Organization and Department levels. It is a macro-level organizational pattern that is designed to be implemented across an entire IT department or even the entire enterprise.

Domains:

The model is commonly applied in industries that are characterized by a mix of legacy systems and a need for rapid digital innovation. These include:

  • Banking and Financial Services
  • Retail and E-commerce
  • Telecommunications
  • Insurance
  • Public Sector

5. Implementation

Prerequisites:

  • Clear strategic alignment: There must be a clear understanding of the business strategy and how the two-speed model will support it. [5]
  • Executive sponsorship: Strong executive sponsorship is essential to drive the organizational and cultural changes required to implement the model. [3]
  • Architectural vision: A clear architectural vision is needed to guide the decoupling of systems and the development of the two-speed architecture. [3]
  • Skilled resources: The organization must have access to the necessary skills and expertise in both agile and traditional development methodologies. [5]
  • Willingness to embrace a hybrid model: The organization must be willing to operate in a hybrid model, with two distinct modes of operation working in parallel. [4]

Getting Started:

  1. Assess the current state: Conduct a thorough assessment of the existing IT landscape, including the application portfolio, infrastructure, and organizational structure. [5]
  2. Define the two speeds: Clearly define the criteria for categorizing systems into the fast and slow lanes. This should be based on factors such as business criticality, rate of change, and customer impact. [1]
  3. Establish a pilot program: Start with a small number of pilot projects to test the two-speed model and refine the approach before rolling it out across the organization. [3]
  4. Create a dedicated team for the fast lane: Assemble a cross-functional team with the skills and autonomy to operate in the fast lane. [3]
  5. Develop a governance framework: Establish a governance framework that is tailored to the specific needs of each speed. [3]

Common Challenges:

  • Cultural resistance: The two-speed model can be met with resistance from employees who are accustomed to a single way of working. [3]
  • Integration between the two speeds: Ensuring seamless integration and communication between the fast and slow lanes can be a significant challenge. [2]
  • Resource allocation: Allocating resources effectively between the two speeds can be difficult, and there is a risk of the slow lane being neglected. [5]
  • ‘Us vs. them’ mentality: The two-speed model can create a cultural divide between the fast and slow teams, leading to an ‘us vs. them’ mentality. [3]
  • Complexity: The model can introduce additional complexity into the IT organization, making it more difficult to manage. [2]

Success Factors:

  • Strong leadership and communication: Strong leadership and clear communication are essential to overcome cultural resistance and ensure that everyone understands the rationale behind the two-speed model. [3]
  • A collaborative culture: Fostering a collaborative culture that encourages communication and knowledge sharing between the two speeds is crucial for success. [3]
  • A flexible and adaptable governance framework: The governance framework should be flexible enough to accommodate the different needs of the two speeds, while also ensuring alignment with the overall business strategy. [3]
  • The right tools and technologies: The organization must invest in the right tools and technologies to support both agile and traditional development methodologies. [5]
  • Continuous improvement: The two-speed model should be viewed as a journey, not a destination. The organization should continuously monitor and refine the model to ensure that it is meeting the evolving needs of the business. [3]

6. Evidence & Impact

Notable Adopters:

While many companies have adopted the principles of the Two-Speed Development Model, they often do so under different names or as part of a broader digital transformation strategy. Some notable examples include:

  • A large international bank: To compete with fintech startups, the bank established a separate digital innovation unit (Mode 2) to rapidly develop and launch new mobile banking features. This unit operated with a high degree of autonomy and used agile methodologies, while the core banking systems (Mode 1) remained on a slower, more traditional release cycle. [1]
  • A major telecommunications provider: The company created a “digital factory” to develop new customer-facing applications and services. This fast-lane team was responsible for everything from ideation to deployment and was able to launch new products in a fraction of the time it would have taken using the traditional IT process. [3]
  • A global retail chain: The retailer implemented a two-speed model to support its e-commerce platform. The front-end team was able to continuously experiment with new features and user experiences, while the back-end systems that managed inventory and logistics remained stable and reliable. [2]
  • A national government agency: The agency used a bimodal approach to modernize its citizen-facing services. A dedicated team was created to develop new digital services using agile methods, while the legacy systems that managed sensitive citizen data were maintained under a more rigorous governance model. [6]
  • An insurance company: The company established a separate “insurtech” division to explore new technologies like AI and blockchain. This division operated like a startup, with a high tolerance for risk and a focus on rapid experimentation. [1]

Documented Outcomes:

  • Increased speed to market: Organizations that have adopted the two-speed model have reported significant reductions in the time it takes to develop and launch new products and services. [3]
  • Improved customer experience: By enabling rapid innovation in customer-facing systems, the model can lead to a more engaging and personalized customer experience. [1]
  • Enhanced agility and responsiveness: The two-speed model allows organizations to respond more effectively to changes in the market and to the evolving needs of their customers. [4]
  • Reduced risk: By decoupling the fast and slow lanes, the model helps to reduce the risk of innovation initiatives disrupting core business operations. [3]
  • Improved alignment between business and IT: The model can help to foster a closer working relationship between business and IT, leading to a better alignment of technology initiatives with strategic objectives. [5]

Research Support:

  • Gartner’s Bimodal IT: Gartner’s original research on Bimodal IT provides a comprehensive overview of the model and its potential benefits. [4]
  • McKinsey’s Two-Speed IT Architecture: McKinsey has published several articles on the two-speed IT architecture, providing detailed guidance on how to implement the model and navigate its challenges. [1, 3]
  • BCG’s The End of Two-Speed IT: While critical of the two-speed model as a long-term solution, a 2016 report from Boston Consulting Group acknowledges its role as an intermediate stage in the journey towards enterprise-wide agility. [7]

7. Cognitive Era Considerations

Cognitive Augmentation Potential:

  • AI-powered development: AI and automation can be used to accelerate both speeds of development. In the fast lane, AI-powered tools can be used for automated testing, code generation, and continuous deployment. In the slow lane, AI can be used to automate regression testing and to identify potential risks and vulnerabilities in core systems. [8]
  • Intelligent portfolio management: AI can be used to enhance the portfolio and project intake process by analyzing data to identify the projects with the highest potential ROI and to recommend the optimal allocation of resources between the two speeds. [8]
  • Predictive analytics for risk management: AI-powered predictive analytics can be used to identify potential risks and to proactively manage them. This is particularly valuable in the slow lane, where the cost of failure is high. [8]

Human-Machine Balance:

  • Strategic decision-making: While AI can provide valuable insights to support decision-making, the ultimate responsibility for strategic decisions, such as which projects to fund and how to balance the two speeds, will remain with human leaders. [8]
  • Creative problem-solving: While AI can automate many routine tasks, creative problem-solving and innovation will remain the domain of human developers, particularly in the fast lane. [8]
  • Ethical considerations: As AI becomes more prevalent, it will be important to consider the ethical implications of its use in both speeds of development. This includes issues such as bias in algorithms and the impact of automation on the workforce. [8]

Evolution Outlook:

  • The blurring of the two speeds: As AI and automation become more sophisticated, the distinction between the two speeds may begin to blur. The slow lane will become faster and more agile, while the fast lane will become more stable and reliable. [8]
  • The rise of the “no-code” and “low-code” platforms: The rise of no-code and low-code platforms will empower business users to create their own applications, further blurring the lines between business and IT. [2]
  • A shift towards a more holistic approach to agility: The two-speed model is often seen as a transitional step towards enterprise-wide agility. As organizations mature in their agile journey, they may move beyond the two-speed model to a more holistic approach where all parts of the organization are able to operate at the speed of business. [7]

8. Commons Alignment Assessment

1. Stakeholder Mapping:

The Two-Speed Development Model primarily focuses on internal stakeholders, namely the IT department and the business units it serves. The model’s success is heavily dependent on the alignment and collaboration between these two groups. Customers are secondary stakeholders, who benefit from the faster delivery of new products and services. However, the model does not explicitly consider other stakeholders, such as suppliers, partners, or the wider community.

2. Value Creation:

The model creates value by enabling organizations to innovate more rapidly while maintaining the stability of their core systems. This can lead to a number of benefits, including increased speed to market, improved customer experience, and enhanced agility. However, the value created is primarily captured by the organization itself, in the form of increased profits and market share.

3. Value Preservation:

The model helps to preserve value by protecting core systems from the risks associated with rapid innovation. By separating the two speeds, organizations can ensure that their mission-critical systems remain stable and reliable. However, the model can also create a two-tier system, where the slow lane is seen as less important and is at risk of being neglected.

4. Shared Rights & Responsibilities:

The model creates a clear division of rights and responsibilities between the fast and slow lanes. The fast-lane team is given the autonomy to experiment and innovate, while the slow-lane team is responsible for maintaining the stability and integrity of the core systems. However, this can also lead to a lack of shared ownership and a sense of ‘us vs. them’ between the two teams.

5. Systematic Design:

The model is a systematic approach to managing IT and software development. It provides a clear framework for categorizing systems, allocating resources, and governing the development process. However, the model can also be rigid and may not be suitable for all organizations.

6. Systems of Systems:

The Two-Speed Development Model is a system of systems, with the fast and slow lanes operating as two distinct, yet interconnected, systems. The success of the model depends on the effective integration and coordination of these two systems. However, the model does not explicitly consider how it interacts with other organizational systems, such as finance, HR, and marketing.

7. Fractal Properties:

The principles of the Two-Speed Development Model can be applied at different scales, from a single department to the entire enterprise. However, the model is not truly fractal, as it is not designed to be applied at the individual or team level.

Overall Score: 3 (Transitional)

The Two-Speed Development Model is a transitional pattern that can help organizations to bridge the gap between traditional IT and the agile enterprise. It is a valuable tool for large, established organizations that are struggling to adapt to the demands of the digital age. However, the model is not a long-term solution, and organizations should aim to move beyond it to a more holistic approach to agility. The model’s focus on internal stakeholders and value capture, and its potential to create a two-tier system, limit its alignment with the principles of the commons.

9. Resources & References

Essential Reading:

  • Bossert, O., Ip, C., & Laartz, J. (2014). A two-speed IT architecture for the digital enterprise. McKinsey & Company. This article provides a comprehensive overview of the two-speed IT architecture, including its key principles, building blocks, and implementation challenges. It is a foundational text for anyone seeking to understand the model.
  • Gartner. (n.d.). Bimodal. Gartner. This is the original source of the Bimodal IT concept. It provides a concise definition of the model and its two modes of operation.
  • Rüßmann, M., et al. (2016). The End of Two-Speed IT. Boston Consulting Group. This report offers a critical perspective on the two-speed model, arguing that it is a transitional step towards enterprise-wide agility. It provides valuable insights into the limitations of the model and the future of IT.

Organizations & Communities:

  • Gartner: As the originators of the Bimodal IT concept, Gartner is a key resource for research and analysis on the topic.
  • McKinsey & Company: McKinsey has published extensively on the two-speed IT architecture, offering practical guidance and case studies.
  • Boston Consulting Group (BCG): BCG provides a critical perspective on the two-speed model and its role in the broader context of digital transformation.

Tools & Platforms:

  • Jira Align: A platform for enterprise agile planning that can be used to manage both waterfall and agile projects in a bimodal environment.
  • Workload Automation Tools: These tools can be used to automate and orchestrate workflows across both the fast and slow lanes of IT.

References:

[1] Bossert, O., Ip, C., & Laartz, J. (2014). A two-speed IT architecture for the digital enterprise. McKinsey & Company. Retrieved from https://www.mckinsey.com/capabilities/tech-and-ai/our-insights/a-two-speed-it-architecture-for-the-digital-enterprise

[2] ThoughtWorks. (n.d.). Two-speed IT. ThoughtWorks. Retrieved from https://www.thoughtworks.com/en-us/insights/decoder/t/two-speed-it

[3] McKinsey & Company. (2015). Making a two-speed IT operating model work. Retrieved from https://www.mckinsey.com/~/media/McKinsey/Industries/Technology%20Media%20and%20Telecommunications/High%20Tech/Our%20Insights/Organizing%20for%20digital%20acceleration%20Making%20a%20two%20speed%20IT%20operating%20model%20work/Organizing%20for%20digital%20acceleration%20Making%20a%20two%20speed%20IT%20operating%20model%20work.pdf

[4] Gartner. (n.d.). Bimodal. Gartner. Retrieved from https://www.gartner.com/en/information-technology/glossary/bimodal

[5] Atlassian. (n.d.). Bimodal development: A mixed approach. Atlassian. Retrieved from https://www.atlassian.com/software/jira-align/bimodal

[6] Infosys Public Services. (n.d.). Two-Speed IT - Architecture for Digital Organizations. Infosys. Retrieved from https://www.infosyspublicservices.com/insights/two-speed-it.html

[7] Rüßmann, M., Lorenz, M., Gerbert, P., Waldner, M., Justus, J., Engel, P., & Harnisch, M. (2016). The End of Two-Speed IT. Boston Consulting Group. Retrieved from https://www.bcg.com/publications/2016/software-agile-digital-transformation-end-of-two-speed-it

[8] PYMNTS. (2025, November 27). Agentic AI Adoption Creates a ‘Two-Speed’ Enterprise Landscape. PYMNTS.com. Retrieved from https://www.pymnts.com/artificial-intelligence-2/2025/agentic-ai-adoption-creates-a-two-speed-enterprise-landscape/