Skip to main content

Scaling the infinite loop

This section will look at strategies that can help organisations scale their operations under the L∞P framework.

Multiple product teams

You can create multiple product teams with different focuses. The following list details some of the most common strategies:

  • User personas: Create one team for each UX persona. For example, you can have one team focused on making the product great for startups while you have another focused on helping large multinationals.

  • Subsets of features: If your product has different modules, this could be a promising approach for your organisation. For example, imagine that you are developing an end-to-end CRM solution. You could have a module for customer support and another for sales or marketing. You could have one product team for each of the modules.

  • Stages: The stages here refer to phases in a customer's lifetime. Different product teams could focus on each of the following stages:

    • Acquisition: This step is dedicated to attracting and acquiring new customers.

    • Activation: This step is dedicated to converting newly acquired customers into engaged and loyal ones.

    • Retention: This step is dedicated to keeping its existing customers satisfied and engaged so that they continue to do business with the company over a long time.

Loop of Loops (LoL)

Loop of Loops (LoL) can be used to coordinate and manage the dependencies between multiple Infinite Loop teams working on a large, complex project. It is a way to scale the Infinite Loop beyond a single team to handle the communication, coordination, and integration challenges that arise when multiple teams work together. The Loop of Loops typically involves the PMs from each Infinite Loop team meeting regularly to discuss and resolve cross-team dependencies.

In this approach, the PMs communicate what their teams are working on, what they need from other teams, and what roadblocks they are facing. This helps to ensure that all teams are aligned on the project goals and are making progress towards the same end goal. The Loop of Loops also acts as a forum for cross-team coordination and problem-solving. For example, if one team is blocked on a certain aspect of the project, they can bring the issue to the Loop of Loops meeting to find a solution with the help of other teams. The Loop of Loops is also a place for sharing information and updates, such as customer insights and changes in priorities.

Platform engineering

A platform engineering team is a group of software engineers, developers, and other technical experts who are responsible for building and maintaining the technical infrastructure that supports the development and deployment of software applications. The primary goal of a platform engineering team is to create a stable, scalable, and efficient platform that enables other teams within an organisation to build and deploy applications quickly and reliably.

A well-functioning platform engineering team can bring several benefits to an organisation, including:

  • Increased efficiency: A platform engineering team can streamline the software development process by providing a stable, scalable, and efficient infrastructure for building and deploying applications. This can help reduce development time and improve the overall efficiency of the software development lifecycle.

  • Increased innovation: By providing a solid foundation for software development, a platform engineering team can free up other teams to focus on innovation and new initiatives, which can help an organisation stay ahead of the curve and maintain a competitive edge.

  • Improved reliability: By implementing best practices for platform design, maintenance, and operations, a platform engineering team can ensure the reliability and stability of the platform and reduce downtime for applications.

  • Enhanced security: A platform engineering team can implement robust security measures to protect sensitive data and prevent security breaches, which can help protect the reputation and credibility of the organisation.

  • Scalability: A well-designed platform can be scaled easily to accommodate the changing needs of the organisation, which can help the organisation stay ahead of the curve as it grows and expands.

The scope of a platform engineering team's responsibilities may vary depending on the size and needs of an organisation. Some common tasks and responsibilities of a platform engineering team include:

  • Designing and implementing a scalable and highly available infrastructure for hosting applications.

  • Building and maintaining a continuous integration and deployment (CI/CD) pipeline for software development.

  • Developing and managing platform services, such as databases, caching systems, and messaging queues, to support the needs of applications.

  • Implementing security measures, such as authentication, authorisation, and encryption, to ensure the confidentiality and integrity of data.

  • Monitoring and optimising the performance of the platform and applications running on it.

  • Providing support and guidance to other teams that are building applications on the platform.


InnerSource is a growing trend in high-performing engineering teams that adopt open-source processes to work and collaborate more effectively. When teams use InnerSource, they develop proprietary software and open up the work internally between teams so that everyone — from developers to product managers — can contribute to the source code.

InnerSource is a software development strategy that applies open-source practices to proprietary code. InnerSource can help establish an open-source culture within an organization while retaining software for internal use. Teams use InnerSource to increase visibility, strengthen collaboration, and break down silos.

By setting the default to open for internal projects within an organization, teams can reuse existing solutions, minimize redundancy, empower team collaboration, and leverage talent across the workforce.

In large organizations and companies, development teams are often spread across different departments or time zones. Multiple developers may never meet or have access to the same departmental strategies. Innersource can help create a learning culture and encourage developers to collaborate across teams and departments, leading to more efficient communication and knowledge sharing.