liveBook · Manning

Baseline workflow

As explained in "Looks Good to Me"

A baseline workflow is a documented representation of the currently understood steps in a process that serves as a reference for comparison and revision.

A baseline workflow is a shared, documented outline of the steps a team believes currently define a process. In code review, it makes responsibilities, approvals, conditions, and merge readiness visible so observed practice can be compared with an agreed starting point. section 9.2.1

Create and revise a baseline workflow with the team:

  • Draft the basic steps, including who reviews, who approves, and which conditions allow approval or merging. section 9.2.1
  • Ask the team to confirm and modify the high-level steps until everyone agrees on a baseline. section 9.2.1
  • Gather observations for a defined period, recording pain points, skipped steps, deviations, and related anecdotes. section 9.2.1
  • Use the notes to correct, add, or remove steps, then consolidate repeated comments into distinct weaknesses and address them with team-approved solutions. section 9.2.1

How "Looks Good to Me" covers it

How deep it goes
Explains drafting, team validation, observation, revision, and weakness consolidation, while leaving detailed annotations for later.
Examples
Uses workflow drafts, team annotations, observation notes, consolidated comments, and revised code review diagrams.
What it assumes
Assumes participation in code review while allowing teams to begin with incomplete or uncertain process knowledge.
What you can do after
Practice revising a code review process until its documented steps reflect team-observed behavior and agreed solutions.
How it connects
Connects code review processes with team agreement, process observations, weaknesses, and approved solutions.

Related concepts

This explainer was generated by Manning's knowledge graph from the text of "Looks Good to Me". The section links point to the parts of the book it draws on.