LTC-OSLibrary
Module·Chapter 10·Updated 17 Sept 2026

Sensei – Flow Optimization

Run dated flow workshops on your value stream, from a frozen baseline to a close, with the software holding the numbers.

Figure 10.1 — The Flow workshop baseline — current-vs-future KPI picture and “where flow hurts most”, with the reason in plain words.
Figure 10.1 — The Flow workshop baseline — current-vs-future KPI picture and “where flow hurts most”, with the reason in plain words.

The second Sensei module rides on the Value Stream Map the way the first rides on the analysis.

It runs dated flow workshops on your own value stream, with the software holding the numbers between sessions — so the work survives the gap between one workshop and the next, which is where flow programmes usually die. Nobody rebuilds the spreadsheet from memory.

A workshop runs from a frozen baseline to a close. The baseline is kept exactly as it stood on the day while the live view recomputes on every visit, so you always see what moved against what you actually started from, not against a number someone has since edited.

It does not turn the loop. What it does is make move three's output worth coming back to: the map stops being a poster from a good week in March and becomes something you work against on a rhythm.

Read the chapter →

Chapter 10 walks through this module screen by screen.