liveBook · Manning

Genesis

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

Genesis is the Wardley Mapping evolution stage in which a component is novel, uncertain, and shaped by experimentation.

Genesis is the earliest stage of evolution on a Wardley Map. A genesis component is new, rare, and poorly understood: people are still exploring what it could do and how to use it. Its potential value may be high, but the path toward that value is uncertain and unpredictable. section 5.3.1 section 5.4.1 section 5.2

When placing a component on a map, ask:

  • How many organizations have this capability? Rarity points toward genesis; widespread use points away from it. section 5.3.1
  • How well does anyone understand its use? Early exploration points toward genesis; rapid learning may suggest it has moved into custom built. section 5.3.1
  • Are people describing the wonder of the idea, or discussing how to build and use it? The language around a component offers another clue. section 5.3.1

An emerging delivery capability

Restaurant optimization—advice and recommendations to help restaurants grow—may sound novel. Yet a few organizations are already developing it, adoption is beginning, and teams are rapidly learning through new features. Those signals place it closer to custom built than genesis. Novelty alone is not enough to settle the classification. section 5.3.1

Treat a placement as a judgment to revisit, not a result produced by a precise flowchart. Industry knowledge and discussion matter because the signals can differ by component. Once mapped, a possible genesis component can prompt a strategic question: might it become a future differentiator, and is there enough demand for it to evolve? Components can move toward custom built, product, and commodity—or die along the way. section 5.3.1 section 5.4.1 section 5.6

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 ubiquity, certainty, and publication types across all four evolution stages before settling on a placement. section 5.3.1

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

How deep it goes
Defines genesis through evolution characteristics and judgment-based assessment, without offering a precise classification flowchart.
Examples
Contrasts restaurant optimization, assessed closer to custom built, with the familiar commodity-like menu in online food delivery.
What it assumes
Builds on identifying users, needs, and component value chains before assigning evolution stages.
What you can do after
Evaluate/understand whether a component belongs in genesis and discuss its potential to evolve into a differentiator.
How it connects
Connects Wardley Maps and value chains to custom built, product, commodity, competitive advantage, and supply and demand.

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.