liveBook · Manning

Overabstraction

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

Overabstraction is the modeling failure mode of hiding important domain detail by representing too much complexity with overly general concepts.

Overabstraction hides important domain nuance by compressing substantial complexity into a few broad domain events. An event can be correctly phrased in the past tense and still reveal too little about how the business works. section 7.4.1

Use these questions to detect overabstraction during an EventStorming workshop:

  • Does one sticky note cover an entire process such as signing up, subscribing, or creating campaigns? section 7.4.1
  • Could the timeline reveal opportunities to improve the process, or has its complexity been hidden? section 7.4.1
  • Can the group tell a specific story about a real advertiser or persona instead of forcing one abstract model to cover every case? section 7.4.1

From broad events to a business story

A timeline containing only “signed up,” “subscribed,” and “created campaign” may look useful while concealing the decisions and variations within each process. Explore one real advertiser’s story and add the details that matter, while allowing the workshop scope to determine how deeply to proceed. section 7.4.1

Figure 7.17 Overly abstract events

Use the visual contrast between a compact event sequence and a more revealing story to discuss where abstraction has hidden domain complexity. section 7.4.1

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

How deep it goes
Defines the failure mode, contrasts four broad events with finer-grained process questions, and stops short of prescribing fixed rules.
Examples
Uses sign-up, subscription, and campaign creation as overly broad events, then redirects attention to a real advertiser.
What you can do after
Evaluate whether event timelines hide useful domain nuance and facilitate deeper storytelling without suppressing early participation.
How it connects
Connects domain events with EventStorming, workshop facilitation, process improvement, and personas.

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.