My trainer has been trying to teach me this for years. Every time a lift felt difficult, I drew the same conclusion: I’m not strong enough yet.
Every time, he stopped me. “Strength shows up fast. Form shows up when you’re tired.”
It took me a long time to understand what he meant.
In strength training, Form and Technique are not the same thing.
Form is structure—posture, positioning, alignment. It is how the body holds itself under load. A stable spine in a deadlift. Balanced knees in a squat. Form protects joints and prevents injury. Its goal is longevity.
Technique is execution — the sequence of movement: breathing, tempo, bar path, muscle activation. The technique helps you move the weight efficiently and perform at your best.
Technique is about performance. Form is about safety and structure.
You can learn the technique relatively quickly. Form takes much longer because it must be built into the body.
And here is the subtle part my trainer kept repeating: Good form does NOT look identical for everyone.
Two lifters can both squat safely with excellent form, yet the movement can look different. Their height, limb length, hip structure — their physical build — changes how alignment appears. The structure is sound, even if the posture is not identical.
Good form creates stability. Uniformity is not the same as stability.
It took me years to understand why that matters.
Because ERP implementations often make the same mistake.
ERP programs are excellent at teaching technique:
- which transaction to use
- which fields to fill
- which steps to follow
Users learn the screens. Training is completed. UAT is signed off. But what determines whether the system survives scale is not technique. It is form!!
A user once told us, “The system tells me what to do. It doesn’t tell me who is allowed to decide.”
That is not a training gap. That is structural misalignment. In an organisation, ERP form is:
- clear process ownership
- stable decision rights
- governance that resolves exceptions
- shared rules that apply consistently
Here is where organisations struggle.
They interpret “standardisation” as identical processes everywhere — across roles, locations, and realities. But just as different bodies lift safely in different ways, different parts of a business may legitimately execute a process differently while still respecting the same structure.
Technique must be consistent.
Form must be stable.
Execution need not be identical.
A sponsor later observed: “The system works, but people keep going around it.”
Often, that happens not because users resist discipline, but because the organisation enforces uniformity rather than building structure. When processes ignore context, people create workarounds to get their jobs done.
Just like lifting, poor form does not fail immediately.
It fails under repetition.
Under pressure.
Under growth.
ERP systems rarely break at go-live.
They break at scale — when volume rises, exceptions increase, and decisions need clarity.
That is why strong implementations focus on form before force:
They stabilise decision rights before enforcing compliance.
They define ownership before automation.
They align governance before scale.
Technique can be trained in weeks. Form must be designed.
It took my trainer years to get me to understand this: strength is never the starting point. Structure is.
Strong ERP programs scale on form, not force.
Processes, governance, and culture carry the load.
When form fails, strength gets blamed — but unfairly.
No comments:
Post a Comment