14 Personal Lean: Building habits
This chapter covers
- Converting failures into checklists that evolve toward automation
- Building learning loops calibrated for an AI-augmented industry
- Treating tickets, meetings, mentoring, and learning as a single WIP system
- Writing just-in-time documentation that serves humans and AI alike
- Building AI-resilient workflows anchored to specs, not tool behavior
- Evolving from T-shaped to Pi-shaped with AI as the accelerator
You open your laptop at 9:00 AM. By 9:07, you are in Slack. A thread about a flaky test. A question about a config value. A deploy notification. A DM from a product manager asking for a "quick update." You respond to four threads that all started after you finished the day previously, now to scan two channels, and read an incident summary from overnight. At 10:32, you open your IDE for the first time. You have written zero lines of code, reviewed zero pull requests, and moved zero tickets. You have, however, generated a comfortable illusion of productivity. This pattern repeats every morning. The day fills with fragments of attention scattered across conversations, context switches, and half-started tasks. Some of this is within your control. Some of it is systemic: the meeting culture, the Slack norms, the expectation of instant availability.