How Large Engineering Teams Can Move With Small-Team Agility

getty

Small development teams are often praised for their speed, agility and ability to deliver meaningful results with limited resources. Larger engineering organizations face different pressures, including added complexity, broader coordination needs and higher stakes, but that doesn’t mean they can’t learn from the way smaller teams work.

For bigger teams, the challenge isn’t to copy small-team practices wholesale but to adapt the underlying habits that make them effective. Below, members of Forbes Technology Council share lessons larger engineering organizations can take from small development teams and why doing so can make a meaningful positive difference.

Own The Full Customer Journey

Large engineering organizations should steal the small-team habit of “owning the whole guest journey,” not just the ticket. Tiny teams feel the wobble when their code hits a real customer. Bigger teams should rotate engineers into support calls monthly; empathy is the cheapest observability tool. - Joel Frenette, TravelFun.ai

Give Top Contributors More Autonomy

Adopt extreme programming methodology with AI agents replacing the pair. A talented solo software engineer can now replace an entire small department. Give individuals more freedom, yet maintain corporate procedures to maintain high reliability at scale. - Vlad Malanin, SpeedSize

Forbes Technology Council is an invitation-only community for world-class CIOs, CTOs and technology executives. Do I qualify?

Organize Large Teams Into Smaller Networks

The productivity of small, competent teams is all too well known—the question is, how can larger teams do the same? Decentralization is the only way. Every large team should be viewed as a collection of smaller teams with logical boundaries. If the interfaces, APIs and so on are agreed upon, every sub-team can become independent, with their own specs, targets and QA—and they all come together at the end. Leadership’s role is to facilitate and stay out of the way. - Krishna Govindarao, LightMetrics

Reduce Dependencies Across Teams

Minimize cross-team dependencies by adopting the “two-pizza team” model. Small, autonomous squads reduce cognitive load, cut bureaucratic friction and streamline decision-making by eliminating lengthy approval chains. When teams own a service end-to-end, building, testing and maintaining it, accountability rises naturally, driving faster, higher-quality delivery. - Asad Khan, TestMu AI

Keep Decisions Close To Delivery

Small teams succeed because those responsible for delivery are also the decision-makers. Command and control organizations institutionalize decision-making away from those responsible when they should be designing effective and efficient controls. - Paul Gresham, Paul Gresham Advisory LLC

Cut Out Unnecessary Handoffs

Large organizations should learn to eliminate the Pipeline Tax. Small teams win because one engineer owns a feature from start to finish—they build it, test it and ship it. There’s no waiting around for separate QA or DevOps teams to approve it. By building guardrails directly into the tools, big teams can regain that small-team speed. It cuts out the endless handoffs that slow everything down. - Mahendran Chinnaiah

Favor Direct Conversation Over Process

Small teams talk to each other instead of updating tickets. The feedback loop between building something and learning whether it works is almost instantaneous. Big organizations should study that. The goal is not to eliminate structure, but to ask themselves honestly how much of their process exists to move work forward versus how much exists just to make work visible to management. - Marc Fischer, Dogtown Media LLC

Protect Space For Experimentation

As companies grow, avoiding mistakes often becomes a bigger priority than discovering opportunities. Small teams operate with the opposite mindset because innovation is often their only path to success. Large organizations should preserve some of that mindset and dedicate resources to exploring ideas that may not fit neatly into the current roadmap but could define the next one. - Benedetto Biondi, Folks Finance

Bring Engineers Closer To Customers

Small teams move fast because they stay close to the customer, the product and decision-making. As organizations scale, layers and handoffs often slow execution. Modern engineering leadership is about simplifying the system by reducing friction, increasing accountability and leveraging AI to help teams move faster without compromising quality or reliability. - Murali Swaminathan, Freshworks

Design Systems For Change

Small teams treat architecture as a living negotiation, not a document frozen in a repository. Design choices are revisited when reality changes because the same people feel the cost of yesterday’s assumptions. Large organizations can learn to fund architectural reversibility instead of architectural certainty. Systems that are easier to change stay valuable longer than systems designed to be right! - Jagadish Gokavarapu, Wissen Infotech

Shorten Feedback Loops With Users

The reality is that small teams ship faster because they can’t afford much overhead. Every layer of process adds distance between engineers and the user. When you have five people and a production incident, you talk to the customer, fix the code and deploy. Big organizations lose that signal in tickets and games of telephone. Teams need feedback loops short enough to fit in a Slack thread. - Yasmin Rajabi, CloudBolt

Choose Simplicity Over Complexity

One lesson is the value of speed through simplicity. Small development teams often make decisions quickly, maintain clear ownership and focus on delivering outcomes rather than managing layers of process. Larger organizations can improve innovation and execution by reducing unnecessary complexity, empowering teams and keeping decision-making close to the work. - Sanjoy Sarkar, First Citizens Bank

Build Momentum Through Incremental Wins

One lesson larger engineering organizations can learn from small development teams is the power of incremental wins. Smaller teams tend to break complex initiatives into manageable milestones, creating faster feedback loops, clearer accountability and steady momentum. Instead of waiting for massive “big bang” transformations, they focus on continuous progress and adaptability. - Anthony Lobretto, 11:11 Systems Inc.

Give Teams End-To-End Ownership

Enterprises must adopt decoupled ownership from small teams using the “two-pizza” model. Owning a feature end-to-end eliminates engineering bottlenecks and dependencies on central infra teams. This narrow focus drastically reduces cognitive load, boosting software development velocity and enabling developers to iterate faster, test continuously and ship higher-quality code. - Mudit Singh, TestMu AI (LambdaTest)

Ship Faster To Learn Faster

Shipping code solves lots of problems. Large organizations are conservative by nature and strive for perfection. Smaller engineering teams focus on shipping code to get real-world feedback. Ship often to generate a rapid feedback loop. - Marc Kermisch, Protolabs

Don’t Let Perfection Delay Progress

To strive for perfection is a common engineering trait, yet perfection is the enemy of speed to market and can, as a direct consequence, result in a loss of market share for new products. An Agile development and product testing model will allow an organization to fail fast and succeed fast while ensuring that development and engineering budgets can be optimized to meet extended engineering project needs. - Mark Brown, The Mark of Security Ltd.

Empower Teams To Move Quickly

Small teams ship because they have to. No endless meetings, no design by committee. They build, see what breaks and fix it fast. Larger organizations should stop optimizing for every edge case. Empower smaller groups to own decisions. Ship imperfect solutions that work now instead of perfect ones that arrive too late. The winners aren’t the most rigorous; they’re the ones willing to move. - Narendra Lakshmana Gowda, Walmart Global Tech