liveBook · Manning

Chapter 14: Personal Lean: Building habits

What you will learn in chapter 14 of Build High Value Software Systems

The chapter introduction applies Lean thinking to personal work habits, contrasting busy but fragmented days with deliberate, measurable improvement.

After this chapter you will be able to

What it builds on

Section by section

Introduction

The chapter introduction applies Lean thinking to personal work habits, contrasting busy but fragmented days with deliberate, measurable improvement.

Key terms: illusion of productivity, context switches, systemic, personal discipline, value stream, feedback loop, measurable results

14.1 Your cognitive value and the eighth waste

This section shows how unused engineering judgment becomes personal waste and how a brief work log can reveal opportunities to free it.

Key terms: cognitive value, eighth waste, unused talent, cognitive context, cognitive value log, personal eighth waste, kaizen card, standard work

14.2 Personal standard work

This section shows how a personal checklist protects recurring work from missed steps under pressure and can evolve into automated standard work.

Key terms: personal standard work, checklist, personal routines, automated: false, kaizen backlog, CI steps, standard work

14.2.1 Building checklists from failures

This section shows how to build a personal checklist from real failures and keep it useful as checks move into automation.

Key terms: personal checklists, checklist item, personal failures, teammate's mistake, team-level incident, living document, manual items, automated enforcement, CI, pre-commit hook

14.3 Learning loops and skill development

The section explains how AI shifts developer value away from routine coding skills and creates an opportunity to develop harder-to-automate skills deliberately.

Key terms: syntax fluency, system design under ambiguity, failure mode analysis, cross-team tradeoff evaluation, routine work, skills that actually compound

14.3.1 Learning from patterns

The section shows how to turn individual failures into reusable judgment by finding shared defect patterns and deciding where proactive fixes are worthwhile.

Key terms: learning loop, incidents, patterns, classes of defects, Read, Extract, Search, Apply, regressions, test coverage

14.3.2 A regular cadence

A short weekly review turns experience into skill by identifying knowledge gaps and calibrating where AI helps or falls short.

Key terms: learning loop, cadence, weekly review, hansei, skill gap row, personal curriculum, production problems, AI calibration, AI's strengths and blind spots

14.4 Managing your personal WIP and flow

This section explains why personal work-in-progress limits must account for commitments beyond tickets and how making those commitments visible helps developers manage overload.

Key terms: WIP, personal WIP, tickets, cognitive space, invisible layer, capacity, context-switching, deep work, personal Kanban board, WIP limit

14.4.1 Holistic WIP limits

This section applies WIP limits to a developer’s whole workload: keep ticket work focused, account for non-ticket commitments, and plan against actual capacity.

Key terms: WIP limit, one ticket in active progress, blocker, backlog, independent task, holistic WIP limits, non-ticket commitments, ticket capacity, deep work, planned capacity

14.4.2 Flow and mindset

This section explains how developers and teams can protect deep work by aligning work with focus patterns, designing meeting schedules deliberately, and tracking where cognitive capacity goes.

Key terms: flow, deep work, best thinking window, meeting windows, maker days, meeting load, WIP, cognitive space, waste, personal flow tracker

14.5 Staying Lean as AI evolves

The section explains how to keep an AI-assisted development workflow productive when models change by anchoring it to stable specifications, adjusting reusable instructions, verifying output, and learning from friction.

Key terms: AI-resilient workflow, non-deterministic, brittle dependency, spec, adjustable layer, AI skills, prompt templates, project rules files, prompt changelog, acceptance criteria

14.5.1 AI and the T-shaped developer

This section explains how AI can help a developer broaden their working knowledge and build depth in a second discipline, while experience and judgment remain essential.

Key terms: T-shaped developer, Pi (π) shaped developer, vertical stroke, horizontal stroke, second vertical, routine learning, depth, judgment, weekly learning review, continuous improvement

14.6 Exercise: Create your personal standard work guide

The exercise guides readers through a five-day audit and setup, then combines the results into a personal standard work guide that they use daily and improve weekly.

Key terms: personal activity ratio, cognitive value log, end-of-session capture, low judgment tasks, deployment checklist, recurring task, automated, learning log, post-mortem, incident report

14.7 Summary

Concepts explained in this chapter

← Chapter 13: Lean team culture Chapter 15: Leading Lean change →

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.