liveBook · Manning

Component evolution

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

An evolution stage is a phase describing the maturity and evolutionary position of a component in a Wardley Map.

Component evolution positions a capability on a Wardley Map according to its maturity and evolutionary position. The usual stages are genesis, custom built, product, and commodity, but assigning a stage requires contextual judgment rather than a precise formula. section 5.3 section 5.3.1

Assess a component through three weak-signal characteristics:

  • Ubiquity ranges from rare capabilities in genesis to widespread, stabilizing capabilities in commodity. section 5.3.1
  • Certainty ranges from poorly understood use in genesis to commonly understood use in commodity. section 5.3.1
  • Publication types shift from describing a thing’s wonder, through building and operating it, toward guidance focused on use. section 5.3.1

Menus, restaurant optimization, and Miro

In online food delivery, menus are widespread and commonly understood, so they resemble a commodity. Restaurant optimization, by contrast, is being developed and tested by only a few organizations, placing it nearer genesis. Miro demonstrates that movement is not necessarily gradual: pandemic-driven demand helped it reach 30 million users by January 2022 after growing 500% in two years. section 5.3.1 section 5.4.4

Table 5.1 The three evolution characteristics (view table figure)

  

Genesis

Custom built

Product

Commodity

Ubiquity

Rare

Slowly increasing consumption

Rapidly increasing consumption

Widespread and stabilizing

Certainty

Poorly understood

Rapid increases in learning

Rapid increases in use/
fit for purpose

Commonly understood (in terms of use)

Publication types

Normally describe the wonder of the thing

Build/
construct/
awareness and learning

Maintenance/
operations/
installation/ features

Focused on use

Compare genesis, custom-built, product, and commodity stages across ubiquity, certainty, and publication types. section 5.3.1

Treat stages as signals, not a guaranteed sequence. Examine how quickly components have evolved, watch for changes in pace, and identify architectural or organizational bottlenecks before the landscape intensifies. section 5.4.4

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

How deep it goes
Defines four stages and three weak-signal characteristics, but stops short of a precise flowchart or objective classification.
Examples
Uses online menus, restaurant optimization, and Miro’s pandemic-era growth to illustrate maturity and changing evolutionary pace.
What it assumes
Requires contextual judgment, industry expertise, and practice rather than reliance on a fixed classification procedure.
What you can do after
Evaluate component positions, evolutionary pace, bottlenecks, risks, and opportunities when working with Wardley Maps.
How it connects
Connects Wardley Maps with genesis, custom built, product, commodity, ubiquity, certainty, and publication types.

Also explained in

Compare how 2 books explain component evolution →

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.