Charles Duhigg describes the habit loop as

Triger
Routine
Reward

This loop that turns behaviors into habits. He asserts that the key to changing a habit is not changing either the trigger or the reward but the routine.

For example, the trigger could be work-related stress, the routine undeserved (etc. a cigarette, snacking), and the reward: a dopamine hit. Duhigg suggests only changing the routine, not the trigger or reward. Over time, that new routine will become a habit. For example, walking 1k steps.

There is a similar idea in programming. Refactoring modifies the code of a function or subroutine without changing the inputs or outputs, to avoid regression impact on the larger system. This is a laborious process, often overlooked due to the fact the eliminated technical debt is very difficult and is easier left ignored.

Can organizations be refactored?

Where the inputs and outputs remain the same but the undesired routines are changed.

Trigger: Client escalation or production outage
Routine: Assert pressure on staff
Reward: Temporary spike in productivity

Can this be refactored to:

Trigger: Input client escalation
Routine: Remove waste from the systems
Output: Increase in productivity

What is the major difference? The difference is felt over time. The former’s quick fix provides an immediate improvement with long term degradation, while the latter is the opposite.