Why DevOps Teams Often Turn Into Tool Chains and What an Ideal DevOps Team Structure Looks Like

Several days ago a translated article listed nine DevOps team structures and seven anti‑patterns; after sharing it, many practitioners reported that their teams fell into the anti‑pattern of "DevOps as a tool team." This raised questions about why this happens and what a proper DevOps structure should be.

In a discussion group titled "DevOps Team Structure," two key questions were explored: (1) Why do many teams end up as tool chains or pipelines? (2) What should an ideal DevOps team look like?

Why DevOps becomes a tool chain

Participants noted that the definition of DevOps is vague, yet organizations demand measurable standards and concrete actions; tools provide visible, tangible results, making them an easy focus. The issue is not solely the tool chain itself but also the people: at the executor level, knowledge is divided into four layers—principles, methods, techniques, and tools—where tools are the easiest entry point (e.g., writing a "hello world" program). However, few truly delve into the underlying technology, leading to a reliance on tools and a "copy‑and‑paste" mindset.

At the organizational level, DevOps breaks traditional development‑operations silos, but the benefit is limited to easier communication between two small groups, not a full‑scale collaboration. Successful DevOps requires an experimental mindset, tolerant leadership, and sufficient resources—conditions most organizations lack. Additional challenges include insufficient micro‑service adoption, inflexible infrastructure governance, immature unit testing, and difficulty obtaining realistic test data, all of which hinder continuous integration and delivery.

What an ideal DevOps team should look like

A standard DevOps team diagram with six roles was presented, each linked to a color of the Six Thinking Hats:

White hat – objective facts and data.

Green hat – creativity and imagination.

Yellow hat – optimism and constructive viewpoints.

Black hat – critical thinking and error detection.

Red hat – emotions, intuition, and feelings.

Blue hat – process control and overall coordination.

Community members debated which role to cut if layoffs were necessary, offering four viewpoints: (1) eliminate the operations team and gatekeepers, relying on tool‑chain automation; (2) treat DevOps as a universal capability (DevOpsiblity) that everyone—from CEOs to janitors—should possess; (3) merge development and operations into a single DevOps talent; (4) replace dedicated development and operations teams with a service‑oriented approach.

The consensus was that there is no universal DevOps team template; structures must be designed to solve specific production and business problems. Agile, Lean, and DevOps practices are all means to that end, and management should not impose standards that exceed the current operational reality.

Finally, the article promoted an upcoming DevOps Hackathon in Beijing (September 7‑8), inviting companies to form teams and compete.