liveBook · Manning

Workflow

As explained in Think Like a CTO

A defined and repeatable way of organizing work and making decisions within an organization.

A workflow is a defined, repeatable way to organize work and decisions. Within a department, it includes routines and business rules for serving clients. Small improvements can make work more efficient without replacing everything familiar. section 2.3.3

Workflows need enough structure to support a consistent customer experience. Too little structure can lead to unpredictable outcomes, while rigidly avoiding any risk can stall decisions and progress. section 1.2.2

A shared client tracker

A team emailed a spreadsheet to track each client’s status, but updates to the wrong version sometimes erased newer work. Moving the tracker to Google Sheets addressed the main problem while keeping a familiar workflow; a larger CRM solution was unnecessary. section 2.3.3

Look for practical improvements before redesigning a workflow:

  • Learn how the department currently works before proposing a change. section 2.3.3
  • Address a specific source of friction or human error with the simplest suitable change. section 2.3.3
  • Let solutions evolve instead of imposing a new workflow that disrupts the work. section 2.3.3

How Think Like a CTO covers it

How deep it goes
Defines workflows through organizational routines and a spreadsheet example, without offering a formal mapping method.
Examples
Compares emailed spreadsheet versions with a shared Google Sheets tracker for client status.
What it assumes
Assumes familiarity with a department’s existing work and recommends learning its routines before suggesting changes.
What you can do after
Apply small workflow changes, such as moving a shared client tracker to Google Sheets, without disrupting familiar work.
How it connects
Connects workflows to business rules, customer experience, process improvement, and human error.

Also explained in

Compare how 7 books explain workflow →

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Think Like a CTO. The section links point to the parts of the book it draws on.