The Friction Project

Notes: Reducing organizational drag, clarifying ownership, removing blockers, making the right thing easier.

Takeaways: Eliminate recurring friction, fix the system not the person, make handoffs explicit.

How it shows up in projects: Better handoff sequencing, tighter ownership boundaries, and less avoidable churn in delivery work.

The Pragmatic Programmer

Notes: Craftsmanship, incremental improvement, feedback loops, automation, clear code and clear thinking.

Takeaways: Keep it simple, build for change, invest in tools, make knowledge executable.

How it shows up in projects: Reusable scripts, cleaner validation routines, and documentation that mirrors real execution paths.

The Phoenix Project

Notes: Flow, constraints, operational maturity, the cost of unplanned work, dev and ops alignment.

Takeaways: Reduce WIP, protect the bottleneck, prioritize reliability, make work visible.

How it shows up in projects: Runbooks that reduce cognitive load, checklists that prevent repeat failures, automation that removes repetitive toil.

Living Notes

These are living notes. They are revised as projects evolve and new lessons are tested in real environments.

Want to suggest a book? Send a note through the Contact page.