liveBook · Manning

Product development

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

Product development is a growth strategy that creates new products or services for an existing market.

Product development is a growth strategy that builds new products or services for an existing market. It targets people already interested in, or likely to purchase, the company’s product category, often using offerings related to those already available. section 3.2.1

Product development creates architectural and organizational questions:

  • Identify shared capabilities, such as business rules, calculations, data, identity, or domain-specific services, where duplicating work would be expensive. section 3.2.1
  • Test the level of reuse carefully: extracting a capability from a single-product system can be difficult, while an overly generic domain model or interface can become a bottleneck. section 3.2.1
  • Plan for product integration and balance investment between new products and existing systems, since customers may expect synergies across products from one company. section 3.2.1
  • Use modernization to remove scaling constraints and improve innovation speed in strategic domains, rather than treating architecture as separate from growth ambitions. section 3.1.2

Console gaming

A console video gaming company can target the existing market of console players with new games or related services. That market can be segmented by factors such as preferred game types, while shared identity, data, or domain capabilities may support multiple products. section 3.2.1

Growth strategy should guide modernization priorities. Mapping the business ecosystem can reveal opportunities and threats early, while a portfolio approach balances near-term value with longer-term architectural problems. section 3.4

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

How deep it goes
Defines the strategy and examines reuse, integration, domain-model, interface, and investment trade-offs, while deferring detailed design treatment.
Examples
Uses console gaming, market segmentation, shared identity systems, domain capabilities, and product integration as concrete illustrations.
What it assumes
Builds from understanding markets, customer segments, existing products, and broad business growth strategies.
What you can do after
Evaluate architecture constraints, reuse risks, integration needs, and investment priorities for new products serving existing customers.
How it connects
Connects product development with market segmentation, shared capabilities, product integration, architecture modernization, domain modeling, and Team Topologies.

Also explained in

Compare how 2 books explain product development →

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.