What Data From 10 Million Workflows Reveals About Great Engineering Teams, According to Luca Rossi

In a recent LinkedIn post, 🌀 Luca Rossi shares key takeaways from a conversation with Rob Zuber, CTO of CircleCI, offering insights gleaned from data spanning over 10 million workflows. Rossi frames the discussion as an exploration of what truly distinguishes high-performing engineering teams in the software development landscape. He highlights Zuber’s unique perspective, derived from one of the industry’s largest CI/CD platforms, to dissect the core elements of effective software creation.

One of the foundational points Rossi relays from Zuber is a critique of over-reliance on superficial metrics. As 🌀 Luca Rossi notes, quoting Zuber’s perspective:

“𝗠𝗲𝘁𝗿𝗶𝗰𝘀 𝗼𝗻𝗹𝘆 𝗴𝗲𝘁 𝘆𝗼𝘂 𝘀𝗼 𝗳𝗮𝗿 — the worst and best teams often look the same on paper. Great teams don’t obsess over process cleanliness; they obsess over the customer.”

This observation, according to Rossi, suggests that while process is important, the ultimate measure of success for an engineering team lies in its impact on the end-user and the business objectives. Rossi elaborates that Zuber’s data implies a need to shift focus from internal process purity to external customer value.

Shifting Focus from Debates to Experiments

🌀 Luca Rossi further illuminates Zuber’s approach to decision-making within engineering teams. Instead of getting bogged down in protracted debates about hypothetical solutions, Zuber advocates for a more agile, test-driven methodology. Rossi explains this principle:

“𝗘𝗺𝗯𝗿𝗮𝗰𝗲 𝗵𝘆𝗽𝗼𝘁𝗵𝗲𝘀𝗲𝘀, 𝗻𝗼𝘁 𝗱𝗲𝗯𝗮𝘁𝗲𝘀 — instead of arguing between options A and B, just test them. You can talk all day or put it in front of customers and see what works.”

This emphasis on rapid experimentation, as highlighted by Rossi, allows teams to quickly validate ideas and gather real-world feedback, thereby accelerating the development cycle and reducing the risk of investing in suboptimal solutions. Rossi frames this as a crucial shift towards embracing uncertainty and learning through action.

The Non-Negotiable Value of Business Acumen

A significant theme explored in Rossi’s post is the critical importance of engineers understanding the broader business context. 🌀 Luca Rossi quotes Zuber’s assertion that:

“𝗕𝘂𝘀𝗶𝗻𝗲𝘀𝘀 𝘂𝗻𝗱𝗲𝗿𝘀𝘁𝗮𝗻𝗱𝗶𝗻𝗴 𝗶𝘀 𝗻𝗼𝗻-𝗻𝗲𝗴𝗼𝘁𝗶𝗮𝗯𝗹𝗲 — engineers make thousands of decisions daily. The more informed they are about business goals, the faster you move.”

Rossi interprets this to mean that equipping engineers with a clear understanding of business objectives empowers them to make more effective, aligned decisions at every stage of the development process. This, in turn, leads to increased efficiency and a more direct contribution to organizational success.

Prioritizing Learning Velocity in Hiring

The discussion, as presented by Rossi, also touches upon hiring philosophies. Zuber, according to Rossi, prioritizes a candidate’s capacity for rapid learning over their existing skill set. Rossi articulates this point:

“𝗛𝗶𝗿𝗲 𝗳𝗼𝗿 𝗹𝗲𝗮𝗿𝗻𝗶𝗻𝗴 𝘀𝗽𝗲𝗲𝗱 — Rob cares more about how fast people can acquire new skills than the skills they already have. The world changes too quickly to hire for specific expertise alone.”

This perspective, shared by Rossi, suggests a forward-thinking approach to talent acquisition, recognizing that adaptability and the ability to acquire new knowledge are paramount in a rapidly evolving technological landscape.

Standardization and Autonomy: Finding the Balance

Finally, Rossi relays Zuber’s insights on the strategic application of standardization within engineering teams. Zuber advocates for standardizing core elements that impact global throughput, while allowing flexibility in areas of local optimization. Rossi explains:

“𝗦𝘁𝗮𝗻𝗱𝗮𝗿𝗱𝗶𝘇𝗲 𝘄𝗵𝗮𝘁 𝗺𝗮𝘁𝘁𝗲𝗿𝘀 — programming languages, observability, CI/CD patterns: standardize. Developer environments and IDEs: let people choose. Too much local optimization kills global throughput.”

This balanced approach, as interpreted by Rossi, aims to streamline critical processes and reduce friction across the organization, while still providing engineers with the autonomy to optimize their personal workflows. The overarching message, according to Rossi’s coverage of Zuber’s insights, is that great engineering teams are customer-obsessed, experiment-driven, business-aware, adaptable, and strategically balanced in their standardization efforts.