Friction vs. Inertia in Change Management
The Physics: Static friction is the force required to start moving a stationary object, and it is universally higher than kinetic friction (the force required to keep it moving).
The Scar: A brilliant engineering manager failing to implement automated testing because they assumed the initial push would require the same energy as maintaining the new process.
The Lesson: The first 5% of a cultural shift requires 50% of the effort. You must deliberately engineer a massive spike in energy to overcome the static friction of "We’ve always done it this way."
The Physics of Staying Put
If you want to push a heavy box across a concrete floor, the hardest part isn't the long slide to the other side of the room. The hardest part is the very first millimeter.
In physics, the coefficient of static friction (the resistance holding an object in place) is always significantly higher than the coefficient of kinetic friction (the resistance pushing back once the object is sliding). Starting motion requires an intense, concentrated burst of energy. Maintaining motion requires far less.
Engineering organizations are heavy, high-friction systems. Every process, every deployment pipeline, and every unwritten coding standard contributes to the mass of the organization. When you attempt to change how the team operates, you aren't just suggesting a new idea; you are attempting to push a very heavy box across a very rough floor. The default state of the organization is rest. The default response to change is, "We've always done it this way." This is pure, unadulterated static friction.
The Illusion of Gradual Change
The most common mistake new engineering leaders make is attempting to enact cultural shifts gradually.
Consider a well-meaning manager trying to introduce mandatory unit testing to a team that has never written one. The manager gently suggests writing tests in 1:1s. They add a soft recommendation to the code review guidelines. They allocate 5% of the sprint to "testing."
Six months later, coverage is still at zero. The "push" was never strong enough to overcome the team's baseline inertia.
You cannot ease an organization out of its static state through gentle nudges. A gradual push against a heavy box doesn't eventually move the box; it just tires you out.
Generating the Initial Spike
To overcome static friction, you must engineer a massive, disproportionate spike in organizational energy.
If you want to implement automated testing, you cannot do it gently. You must pause all feature work for an entire sprint to focus exclusively on test infrastructure. You must secure loud, unwavering executive sponsorship. You must make the CI pipeline aggressively reject pull requests without coverage.
For a brief, painful window of time, the entire system must be shocked out of equilibrium. The organization will groan. Velocity will temporarily plummet. But the box will break free from the floor.
Settling into Kinetic Friction
The good news about physics is that once the static friction breaks, the energy required to maintain the motion drops by an order of magnitude.
Once the box is sliding, the leader's job changes entirely. You are no longer providing massive thrust; you are simply guiding the slide. Once the developers have written their first ten tests and the infrastructure is seamless, writing the eleventh test is easy. The new kinetic friction is just the standard overhead of the job.
Stop expecting linear effort in culture change. If you want to move the organization, you have to hit it hard enough to break the friction, and then keep your hand on the box so it never stops sliding.