liveBook · Manning

Adoption

Adoption is the uptake and continued use of a technology, product, system, or practice by individuals or organizations.

How 3 Manning books explain it

Decision Engineering

Adoption is the extent to which people or organizations take up and use a technology.

How it is used
Assess open-source dependencies by using adoption as one signal of traction and likely project evolution.
How deep it goes
Distinguishes interest from actual use and cautions that neither alone establishes stability, maintenance, or production suitability.
Examples
Compares Preact, SolidJS, and Qwik using GitHub stars, npm weekly downloads, and release dates.
What you can do after
Evaluate open-source dependencies by interpreting usage indicators alongside the commitment and impact of adopting them.

Read how Decision Engineering explains adoption →

Machines that Think

The uptake and integration of an AI system or technology into an organization's activities and practices.

How it is used
Frames adoption as the movement of conversational AI from experimentation into work and everyday routines.
How deep it goes
Surveys adoption drivers and the transition to dependency, stopping short of implementation guidance.
Examples
Compares ChatGPT’s user growth with earlier technologies and describes search shifting toward conversational answers.
What you can do after
Evaluate how ease of use and repeated integration can reshape workflows despite AI reliability limits.

Read how Machines that Think explains adoption →

Test Driven: Practical TDD and Acceptance TDD for Java Developers

Change adoption is the process by which individuals or groups come to understand and take up a proposed change.

How it is used
Frames adopting TDD as personal and organizational change, including helping colleagues take it up.
How deep it goes
Explains personal and group adoption factors, change-agent roles, resistance, and interventions without detailing their procedures.
Examples
Uses adopting TDD and supporting a colleague or team as practical cases, without a worked code example.
What you can do after
Understand how to support adoption by allowing time, sharing champion responsibilities, and addressing resistance.

Read how Test Driven: Practical TDD and Acceptance TDD for Java Developers explains adoption →

Also covered in

Related concepts

Questions about adoption

What is adoption?

Adoption is the uptake and continued use of a technology, product, system, or practice by individuals or organizations.

Which Manning books explain adoption?

Decision Engineering, Machines that Think and Test Driven: Practical TDD and Acceptance TDD for Java Developers.

What is the difference between adoption and dependency?

Adoption is the uptake and continued use of a technology, product, system, or practice by individuals or organizations. A dependency is a component, resource, or prerequisite that another software component or activity relies on to function, build, or proceed.

What kinds of adoption are there?

Kinds of adoption include electronic health record adoption and brownfield adoption.

What are the parts of adoption?

Adoption includes proof of concept.

These guides are generated from the text of Manning books by Manning's knowledge graph and link to the sections they draw on. The full books are available on liveBook and at manning.com.