liveBook · Manning

Standard

As explained in Architecture Modernization: Socio-technical alignment of software, strategy, and structure

Standardization is the practice of making technologies, processes, or interfaces consistent across teams or systems.

Standardization makes technologies or processes more consistent across teams. It can improve collaboration and reduce the effort of supporting diverse tools, but too much can constrain teams and slow their workflow. The right balance depends on the organization’s context. section 6.2.4 section 13.4.4

HMRC’s Multi-channel Digital Tax Platform

In 2015, HMRC required teams to use Scala and Play for microservices and frontend applications. Though the choice was contentious and created hiring challenges, common tools and structures let teams focus on delivery and inherit services without learning each one from scratch. By contrast, Netflix encouraged paved-road adoption through a better developer experience rather than strict mandates. section 13.1.5 section 13.4.4

When deciding how much to standardize, consider:

  • Will supporting more languages or cloud providers stretch platform teams too thin to provide a good developer experience? section 13.4.4
  • Could shared technologies ease collaboration, or would they add friction to teams’ workflows? section 6.2.4
  • Can teams deliver value while refining their choices, rather than over-designing up front or rushing into delivery? section 6.2.4

How Architecture Modernization: Socio-technical alignment of software, strategy, and structure covers it

How deep it goes
Explains organizational trade-offs through examples and diagnostic questions, without prescribing a universal level of standardization.
Examples
Contrasts HMRC’s Scala-and-Play platform with Netflix’s voluntary paved roads.
What you can do after
Evaluate whether shared technologies and platform paths justify reduced choice by weighing delivery, collaboration, workflow friction, and support capacity.
How it connects
Connects standardization to autonomy, technology sprawl, internal developer platforms, paved roads, and developer experience.

Also explained in

Compare how 6 books explain standard →

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Architecture Modernization: Socio-technical alignment of software, strategy, and structure. The section links point to the parts of the book it draws on.