[xaedes]

> It puts a name to a considerate consensus-based way to approach change

When reading about nemawashi I immediately thought about its usage in software refactoring.

This is something you often intuitively do when making bigger refactors. Lay the foundations before actually doing it. Affected code parts and stakeholders should not be surprised by one big change. Instead they should be consulted before hand, building consensus, modify the planned big refactor itself and preparing the individual parts for it by small changes. Otherwise you will encounter a lot of friction, introduce bugs, etc.

It is very nice to have a proper term for this.