Running Biomechanics: My Stride Force Journey

Running biomechanics is the story of how my body creates, accepts, redirects, and reuses force during each stride. After 12 years of running, I do not use biomechanics to rank runners by appearance. I use it to understand where the work is going, how quickly the load arrives, and whether the runner has enough capacity for the task.

My framework follows one stride through a Stride Force Journey: Approach, Contact, Loading, Propulsion, and Swing. At every station I ask three questions: What direction is the force acting? How fast does it arrive? Which tissues and joints are sharing it?

That approach stops me from calling a heel strike, pronation, asymmetry, or low cadence “bad” in isolation. Biomechanics describes a system. A useful decision must include speed, fatigue, terrain, footwear, training load, symptoms, and the individual runner.

My short answer: what running biomechanics explains

Running biomechanics explains motion and force. Kinematics describes what moves: joint angles, cadence, step length, vertical motion, and timing. Kinetics describes what causes or resists that motion: ground-reaction forces, joint moments, work, power, and loading rate.

I need both languages. A foot may appear to land softly while force still arrives quickly. Two runners may show similar joint angles but share the work differently between hip, knee, ankle, calf, and foot.

Ken’s rule: I never change a visible pattern until I can name the load problem the change is meant to solve.

The three force questions I ask first

1. Where is the force going?

Force has direction. During ground contact, the surface pushes back against the runner. Part of that force supports body weight, part manages forward and backward motion, and part may act side to side.

I look beyond a single vertical number. Braking, propulsion, balance, and slope all change the direction of demand.

2. How fast does the force arrive?

Peak force and loading rate are different. The same broad amount of force can arrive more gradually or more abruptly. Contact time, landing position, limb stiffness, speed, surface, and footwear can affect that shape.

A lower peak or slower loading rate is not automatically safer. It tells me about one feature of one load, not the runner’s full injury risk.

3. Who is doing the work?

The body shares negative and positive work across joints and tissues. A change that reduces knee demand may increase ankle, calf, Achilles, or foot demand. A stiffer shoe may change what the foot and lower leg do without making work disappear.

This is why I call cadence, foot strike, slope, and footwear load shifters. They redistribute the job.

My running-force dictionary

Term	What it means to me	Common mistake
Peak force	The highest force measured during a chosen part of contact	Assuming the highest value alone predicts injury
Loading rate	How quickly force rises	Treating a quieter landing as proof of a lower internal load
Impulse	Force accumulated over time	Ignoring contact duration and focusing only on the peak
Joint moment	The turning demand around a joint	Calling it a direct measurement of one muscle
Work	Energy absorbed or produced through movement	Assuming less work at one joint means less total demand
Power	How quickly work is done	Confusing high power with poor form
Stiffness	The relationship between force and deformation	Treating more or less stiffness as universally better
Economy	The energy cost of holding a given speed	Assuming the prettiest stride is the most economical

No consumer watch measures this complete dictionary directly. Wearables estimate selected variables through sensors and algorithms. I use them for personal trends, not laboratory diagnoses.

Station 1 — Approach: how I arrive at the ground

Approach begins before the foot touches down. The leg swings forward, the lower leg prepares for contact, the arms counterbalance rotation, and the body continues moving over the ground.

I watch whether the runner reaches dramatically ahead, whether the lower leg is still moving forward at contact, and whether the trunk is organized for the current speed. I also watch the arms because they help manage angular momentum rather than merely decorate the stride.

My arm-swing guide explains how I adjust hand tension, elbow path, and cross-body motion only when the whole stride benefits.

Overreaching is not identical to heel striking

A runner can contact with the heel close to the body and manage load well. A forefoot runner can reach too far ahead and brake. I judge landing position, lower-leg orientation, knee compliance, and motion of the center of mass before the foot-strike label.

Station 2 — Contact: the first instant is not the whole landing

Initial contact is brief. The heel, midfoot, or forefoot label describes which region appears to touch first; it does not describe everything that follows.

I ask how the foot is positioned relative to the moving body, how the knee and ankle prepare, and whether the runner can accept the contact without a visible jolt or loss of control. I do not prescribe one strike to everyone.

Different strike patterns tend to redistribute demand. A more forward strike can reduce some knee-related variables while asking more from the ankle plantar flexors, calf, Achilles, and foot. My foot-strike comparison maps those trade-offs without naming a winner.

Station 3 — Loading: how the body accepts and redirects force

After contact, the body must manage vertical support, braking, joint motion, and balance. The ankle, knee, hip, pelvis, and trunk do not work in isolation. Their timing determines how the demand is shared.

I watch whether the knee can bend, the pelvis stays controlled enough for the task, and the trunk responds rather than freezes. I also consider contact time. A runner can lower one peak yet accumulate substantial impulse through a longer contact.

Pronation is movement, not a diagnosis

Pronation is part of how the foot adapts and accepts load. The amount visible from behind does not reveal tissue stress, strength, comfort, or injury risk by itself. I become interested when the motion is connected to symptoms, poor control, or a meaningful difference between sides.

I do not prescribe stability shoes or insoles from a pronation screenshot alone. Footwear decisions require fit, comfort, history, and response under real running.

Station 4 — Midstance and propulsion: the body moves over and away

During midstance, the body moves over the support leg. The joints absorb and redirect energy while the calf–Achilles complex and foot contribute to elastic storage and later propulsion.

Propulsion is not simply “push harder.” The runner needs timing, stiffness appropriate to speed, and enough capacity in the hip and ankle system. Trying to force a powerful toe-off can create unnecessary calf tension and a longer contact.

I use strength training to expand the options available at this station: squat, hinge, split stance, calf, and trunk functions. My Runner Strength Floor builds that capacity without telling the runner to consciously squeeze through every step.

Station 5 — Swing and flight: I prepare the next contact

Once the foot leaves the ground, the leg must recover for the next step. At faster speeds, flight time and range usually change. The hip, knee, and ankle coordinate the leg’s return while the opposite arm helps balance the rotating system.

I do not force high knees during easy running. Knee lift is partly an outcome of speed, force, and timing. An exaggerated recovery can waste energy when the task does not require it.

I watch whether the leg returns smoothly and whether late-run fatigue changes the path. The next contact begins with what happened during swing.

How the body shares joint work

Region	Major biomechanical jobs	What can raise demand	What I refuse to assume
Foot and ankle	Adapt, stabilize, store and return energy, contribute to propulsion	Faster pace, hills, lower drop, forward strike, jumps	That visible pronation is automatically harmful
Knee	Accept load, control flexion, transfer force	Braking, speed, downhill running, deep flexion demand	That all knee load is damage
Hip and pelvis	Support the body, manage rotation, extend and redirect the limb	Speed, hills, fatigue, lateral demands	That one hip-drop frame proves weakness
Trunk and arms	Manage balance, rotation, posture, and breathing space	Speed, fatigue, wind, uneven terrain	That zero rotation is ideal

Joint demand is not the same as tissue damage. Healthy tissues need load to adapt. The problem is often a mismatch between the demand applied and the capacity available at that moment.

Cadence and step length: two parts of speed

Running speed comes from step length multiplied by step frequency. Both change naturally with pace. I do not assign 180 steps per minute as a universal goal.

When I increase cadence slightly at the same speed, step length usually shortens and several joint or loading variables can change. That may help a runner who overreaches or has a specific knee-related problem. It may also feel choppy or shift demand elsewhere.

I start from the runner’s normal rhythm and test a small change for a defined reason. My cadence guide explains how I measure, trial, and reject changes without worshiping one number.

I also separate per-step load from cumulative load. A small reduction in load on each contact comes with more contacts when cadence rises. Biomechanics needs both views.

Speed changes the entire force journey

Faster running is not easy running performed with more effort. Flight, contact time, step length, cadence, joint moments, muscle recruitment, and arm action all change.

This is why I compare mechanics at the pace that matters. A runner may look stable at an easy jog and lose control during 5K pace. Another may overreach only when running unnaturally slowly beside a friend.

I never diagnose a runner’s race mechanics from a single easy treadmill clip. The task must match the question.

Hills and surface change the direction of demand

Uphill running reduces speed, shortens the step, changes posture, and increases propulsion needs. Downhill running increases braking and eccentric control. The same runner should not look identical on both slopes.

My hill-running guide translates those changes into practical cues and progressions. I do not carry flat-ground rules blindly onto a steep descent.

Trails add variable foot placement, side-to-side control, traction, visual planning, and irregular grades. A wider step can be a useful stability response, not an inefficiency.

Hardness alone does not tell me how much internal load a runner experiences. Surface compliance, shoe behavior, speed, leg stiffness, and the runner’s adaptation interact.

Footwear is part of the system, not a force shield

Foam, stack height, heel-to-toe drop, rocker shape, plate stiffness, platform width, and upper fit can all influence sensation or mechanics. Their effects depend on the runner and pace.

A lower-drop shoe may increase demand on the calf and Achilles for some runners. A stiff plated shoe can change foot and ankle behavior. A broad platform can change the feeling of stability. None of these features erases load.

My heel-drop guide explains one of those load-shifting levers. I transition shoes gradually and judge comfort, performance, symptoms, and next-day response together.

Fatigue reveals capacity, not character

As fatigue grows, cadence, contact time, joint contribution, posture, and step placement may change. The direction differs between runners. I do not assume every late-run change is a form flaw.

I compare early and late clips at similar pace. If mechanics deteriorate only after a duration the runner has not prepared for, the first intervention may be training progression, fueling, recovery, or strength—not a constant cue.

Sleep and life stress matter because the nervous and muscular systems arrive at the run in a different state. My recovery framework helps me determine whether a movement problem is actually an under-recovered runner.

Running economy: useful output, incomplete explanation

Running economy is the energy required to hold a submaximal speed. Two runners can use different mechanics and achieve similar economy. A runner can also become more economical through training without an obvious visual transformation.

I prioritize consistent aerobic training, appropriate quality work, strength, fueling, and recovery before trying to engineer a prettier stride. A small mechanical change earns attention when it improves the actual task without creating a worse trade-off.

Economy is not identical to performance. Racing also depends on aerobic capacity, threshold, fatigue resistance, tactics, fueling, environment, and psychology.

Form coaching versus biomechanics

Form coaching asks what cue may help. Biomechanics asks what motion or force changed, why it may matter, and what else changed with it. I need the second question before I trust the first.

My Five-Camera Form Check is the practical coaching layer. This article is the map beneath it. The two should not be confused.

My at-home observation protocol

A phone can reveal timing, landing position, trunk behavior, arm action, step width, and how a pattern changes with fatigue. A video cannot directly measure joint forces, tissue stress, or produce a medical diagnosis.

1. I warm up and choose a familiar pace.
2. I place the camera near hip height and avoid a distorted wide-angle view.
3. I record several passes from the side, front, and rear when the location is safe.
4. I capture the pace or condition that produces the actual problem.
5. I compare early and late movement rather than selecting one dramatic frame.

If symptoms, persistent asymmetry, or return-to-running decisions are involved, I use a qualified assessment. My running gait analysis guide explains what cameras, treadmills, force plates, pressure systems, and clinicians can—and cannot—tell me.

My Observe–Map–Nudge–Reload–Retest method

Observe

I define the real problem: pain, braking, loss of control, performance limitation, or an unusual change. I do not start from a disliked screenshot.

Map

I locate the force journey and name plausible load trade-offs. I consider training, fatigue, terrain, and footwear before blaming anatomy.

Nudge

I choose one small change: a pace adjustment, modest cadence trial, quieter landing cue, terrain change, shoe transition, or strength target. I keep the rest stable.

Reload

I expose the runner gradually. A new mechanic is a new load even when it looks smoother. I do not force it through an entire long run on day one.

Retest

I repeat the same task and compare movement, comfort, performance, and the next-day response. A prettier video without a better outcome is not enough.

Four decisions I make with the force map

A comfortable runner with visible asymmetry

I document it and ask whether it is stable across pace and fatigue. If the runner is comfortable and progressing, I do not “correct” asymmetry simply because symmetry looks cleaner.

A runner who reaches far ahead at easy pace

I first check whether the pace is artificially slow. Then I test a modest rhythm change or a shorter-and-quieter cue. I do not command forefoot striking.

A runner whose knee hurts less with quicker steps

I may keep a small cadence change in short doses while monitoring calf and ankle response. The cue changed load distribution; it did not cure every cause of knee pain.

A runner who collapses late in long runs

I examine duration progression, fueling, sleep, and strength before prescribing constant posture cues. The pattern may be the visible result of depleted capacity.

Injury: biomechanics is one layer of the risk picture

Biomechanical variables can be associated with symptoms or injury in selected groups, but association does not prove that one angle caused the problem. Injuries emerge from exposure, tissue capacity, history, recovery, health, and context as well as movement.

I do not promise injury prevention through one cadence, foot strike, shoe, or gait score. My injury-prevention framework places mechanics beside progression, sleep, strength, and symptom response.

When pain is sharp, worsening, present at rest, associated with swelling or weakness, or changing gait, I stop treating it as a camera problem. My pain-monitoring rules set the boundaries for continuing, modifying, and seeking assessment.

The biomechanics mistakes I avoid

Diagnosing from one frame

I use sequences, multiple views, repeat trials, and the correct pace. One image removes timing and context.

Calling every heel strike an overstride

I separate contact region from landing position and braking.

Treating pronation as a defect

I treat it as movement and ask whether it connects to symptoms, control, or a fit problem.

Chasing 180

I start from the individual baseline and use cadence only for a defined reason.

Assuming lower load is always better

Tissues need appropriate load. I care about dosage and capacity, not eliminating force.

Changing form, shoes, and training together

I keep experiments readable. Multiple simultaneous changes hide which load shift mattered.

Using lab numbers as a verdict

A measurement describes a test condition. I still need the runner’s history, symptoms, goals, and response.

Frequently asked questions

What is running biomechanics?

Running biomechanics is the study of motion and force during running. I use it to understand how a runner creates, accepts, redistributes, and reuses load across the stride.

What are the phases of a running stride?

I organize the stride as approach, initial contact, loading and midstance, propulsion, swing, and flight. The phases overlap as the body prepares one leg while the other manages support.

Is heel striking bad biomechanics?

No. Heel contact can occur close to the body with controlled load acceptance. I evaluate landing position, braking, knee and ankle behavior, comfort, and task before the strike label.

Is 180 steps per minute ideal for every runner?

No. Cadence varies with speed, leg length, terrain, fatigue, and the runner. I test a modest change only when it may solve a defined problem.

Does pronation cause running injuries?

Pronation is normal foot motion and does not diagnose injury by itself. I consider symptoms, control, training load, footwear fit, history, and the rest of the stride.

Can a phone video measure running forces?

No. A phone can show movement and timing, but it cannot directly measure joint forces, tissue stress, or loading rate. I use video to form questions, not to produce a medical diagnosis.

Should I change my biomechanics if I am not injured?

Usually I need a clear performance, comfort, or control reason. If a runner is healthy and progressing, I do not rebuild the stride merely because one feature looks unusual.

My final decision

I read running biomechanics as a force journey: Approach, Contact, Loading, Propulsion, and Swing. At every station, I ask where the force goes, how quickly it arrives, and who shares the work.

When a problem is meaningful, I Observe, Map, Nudge, Reload, and Retest. I change one lever and watch the trade-off rather than chasing a universal gait.

The best use of biomechanics is not making every runner look the same. It is making a specific decision clearer, safer, and easier to evaluate.