liveBook · Manning

Review process

A review process is a structured evaluation of work, performance, artifacts, or proposals against relevant criteria to assess quality, progress, correctness, or suitability.

How 3 Manning books explain it

Automating API Delivery

An API review process is a defined workflow for evaluating and approving API designs against stated principles, standards, and business needs.

How it is used
Evaluates API definition changes after automated checks, using human feedback to address usability and design decisions those checks cannot settle.
How deep it goes
Provides PR and meeting paths, a meeting sequence, review questions, and process-design goals; leaves exact governance rules to each organization.
Examples
Contrasts Slack’s review channel and office hours with Kubernetes’s mandatory-review criteria, triage board, and release-based prioritization.
What you can do after
Practice/perform a consumer-focused PR review and choose between asynchronous feedback and a meeting according to the change’s scope.

Read how Automating API Delivery explains review process →

Think Like a CTO

A review process is a structured evaluation of a person's work, performance, progress, or development over a defined period.

How it is used
Uses structured feedback to improve executive performance, leadership, and organizational alignment.
How deep it goes
Explains review criteria, recurring conversations, feedback mechanisms, and handover use, but stops short of prescribing a formal scoring system.
Examples
Uses CEO one-to-ones, team leadership feedback, a workplace sitcom scenario, and review-based CTO handover discussions.
What you can do after
Practice/perform regular reviews, request actionable feedback, set goals, and use review history to support leadership transitions.

Read how Think Like a CTO explains review process →

Coding with AI

A review is a systematic examination of an artifact or output to assess its correctness, quality, and suitability.

How it is used
Reviews AI-generated documentation, requirements, and tests before they are used in development workflows.
How deep it goes
Checks drafts for logical progression, accuracy, and fit, then edits useful content; test-review procedures remain unspecified.
Examples
Examines user-story drafts and extracts candidate requirements from a software design document.
What you can do after
Evaluate and revise AI-generated documentation and requirements, and maintain review processes for generated tests.

Read how Coding with AI explains review process →

Also covered in

What to know first

Related concepts

Questions about review process

What is review process?

A review process is a structured evaluation of work, performance, artifacts, or proposals against relevant criteria to assess quality, progress, correctness, or suitability.

Which Manning books explain review process?

Automating API Delivery, Think Like a CTO and Coding with AI.

What should I know before learning review process?

Manning books that teach review process usually introduce goal, code coverage, client and customer journey first.

What is the difference between review process and api linting?

A review process is a structured evaluation of work, performance, artifacts, or proposals against relevant criteria to assess quality, progress, correctness, or suitability. API linting is the automated analysis of an API description or design against rules for correctness, consistency, security, and maintainability.

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.