Make code changes economically. See code in a new way and fix code problems in a risk- and ROI-aware way.

Organization ROI: Allow more change. Address technical debt while remaining within acceptable cost and risk limits.

Engineer ROI: Gain management support for addressing technical debt. Fix debts more quickly. Work on both features and design flaws.

Habit: Start Refactoring Safely

Organization ROI: Code changes become cheaper and less bug-prone. Improves intra-team learning.

Engineer ROI: Code reviews are much easier. Gaining permission to refactor is easier. Make fewer mistakes.

Habit: Naming as a Process

Organization ROI: Reduces cost and bugs for any story that touches existing code.

Engineer ROI: Trust your names. Finish stories faster. Reduce impact of interruptions.

Habit: Know When to Stop

Organization ROI: Trust devs to do just the right amount of refactoring in each story. Minimize cost of each story.

Engineer ROI: Be trusted to decide when to refactor. Know when to stop.