liveBook · Manning

Repeating divergence

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

Repeating divergence is a modeling heuristic that looks for a previously observed distinction between process paths recurring later in the timeline.

Repeating divergence is a modeling heuristic: when a process first splits according to a characteristic, look for that same characteristic causing later splits in the timeline. section 7.4.1

Advertiser experience

An advertiser’s sign-up path diverges according to startup or enterprise affiliation, then later diverges again when a poorly performing advert leads to generic advice for startups but expert help for customized enterprise plans. section 7.4.1

Figure 7.19 A timeline that converges and then diverges at some point later based on the same characteristic

Use the timeline to inspect where paths converge and later diverge again according to the same characteristic. section 7.4.1

Apply the heuristic by:

  • Starting with specific customer stories rather than abstract models. section 7.4.1
  • Comparing different personas or segments and tracing their experiences across the timeline. section 7.4.1
  • Treating later divergence as a prompt to investigate whether the original characteristic still shapes outcomes. section 7.4.1

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

How deep it goes
Explains the heuristic through a converging-and-diverging timeline and advertiser scenarios, without formal modeling mechanics.
Examples
Uses startup and enterprise advertisers whose support paths diverge again after poor advert engagement.
What it assumes
Assumes familiarity with process timelines while encouraging movement between specific stories and abstract models.
What you can do after
Apply the heuristic by tracing whether an initial domain distinction produces later differences in customer experience.
How it connects
Connects customer personas, process timelines, EventStorming, and abstract-versus-specific modeling.

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.