RJ · Force-Plate Self-Coaching · generated 2026-06-20 · Smart2Move · TPI · Measured Golf

Force-Plate Cockpit

Generated from the knowledge base — edit the markdown cards and re-run build_site.py.

The interpretation + working layer for the force-plate comeback. Five tabs:

The three source lenses (why they sometimes diverge)

The kinetic ↔ kinematic backbone

Everything traces to one chain: forces (kinetic, Smart2Move) cause motion (kinematic, TPI). The kinetic sequence lateral → rotational → vertical drives the kinematic sequence pelvis → trunk → arms → club. Read both: force = input, segment speed = output.

How to run an analysis → the Diagnose tab / /fp-analyze

The full diagnostic method lives in ANALYSIS-PROTOCOL.md (rendered in the Diagnose tab). Run it with /fp-analyze: a cascading read — high-level + trend first, double-click deeper only as needed — that prioritizes by your ball-flight miss, is club-aware, ties every step to the cards, confirms with Trackman, and saves each run to analyses/ so you can see how your focus, outputs, and ball flight shift over sessions. Capture solid and mishit swings; your own solid-strike data beats any textbook number.

Updating the cards from a new transcript (protocol)

The repeatable loop whenever a new lesson/source transcript lands: 1. Fetchpy fetch_transcript.py --out "<Source folder>" <url> (add --cookies-from-browser firefox if the IP is throttled). 2. Place it — which concept does it cover? Existing card → add this source's take; new concept → copy a template (_concept-template.md or club-delivery/_club-delivery-template.md). 3. Add the source's position — a row in Source positions / Coaching takes with a citation (video_id, mm:ss), and note agreement vs conflict with other sources (conflicts are expected → they surface in the Conflicts tab). 3b. Preserve the nuance in the card's Details & nuance layer (collapsed in the cockpit): worked examples with numbers, the mechanism/analogy, caveats & exceptions, and key quotes (source · timestamp). The summary row is for scanning; this layer is so the tidbits don't get distilled away. 4. Tag itsource:, goal:, verdict: untested, and the worked/hasn't table (you fill it from your data over time). 5. Register a new source in the registry below (one-line lens) the first time a coach appears. 6. Regeneratecd "Analysis Protocol" && py build_site.py → refreshes Force Plate Concept Cards.html. 7. Verify the card shows under the right tab and its links resolve.

The generator indexes cards by id/category wherever they live under concepts/, so folder moves (this OneDrive tree reshuffles them) don't break the build.

This is the single, canonical method for analyzing a Smart2Move capture. Run it the same way every time — even after a context reset or on a new computer. Invoke with /fp-analyze (the slash command loads this file + your last analysis, runs the steps below, saves the output, and diffs vs last).

Folder map (short paths below are relative to these roots): - Analysis Protocol/ — this file + build_report.py + build_site.py. - Golf Knowledge Repository/ — the knowledge: concepts/ cards, source transcripts, site/, _index.md. - Analysis Sessions/one folder per session, named by ISO date (YYYY-MM-DD/): the dropped photos + that session's .md record + .html report all live together. Plus a catch-all _Cross-Session/ that spans sessions: _tracker.csv, data/, correlations/, journal/, practice/, _template.md. So below, _tracker.csv/data//correlations/ = under _Cross-Session/; concepts/… = Golf Knowledge Repository/concepts/….

Core principle — grounded in the concept cards

Every judgment routes to the concept + Details cards (concepts/**) — our transcript-derived core knowledge (Smart2Move · TPI · Measured Golf · Shauheen, cited, with nuance in each card's Details). The protocol interprets via the cards; it never invents. Each step names its card(s) + the Trackman metric that confirms it.

Knowledge stack (grows over time): 1. Core: concept cards + Details (transcripts). 2. + Observations: the dated session folders (one per session) + correlations/ (your cause→effect map). 3. + Tested outputs: validated worked/hasn't + correlations/<lever>.mdflow back into the cards, overriding textbook matchups with your confirmed truths.

Inputs

Input Required? Notes
Club Required Sets the reference bands — driver ≠ 6-iron ≠ wedge for magnitudes and setup pressure.
Ball-flight issue / focus Required Your miss or what you're trying to improve → drives prioritization.
P1–P10 screenshots Required (L1); more for deeper L1 = combined Kinetic-Sequence + pressure view. L2/L3 need P1–P10 for each sub-force (lateral/rotational/vertical) showing individual feet.
Trackman shot data Optional (the conclusion) Pulled from Trackman Scraper/ exports, matched by date+club, to grade the prediction.
Concept cards Always (AI ref) The interpretation layer.

How a run works (cascading — stop when the miss is explained)

  1. Read the last analysis (latest dated session folder) so this run is relative to it.
  2. Ball-flight router → from your miss, jump to the likely suspects/levels first.
  3. Level 1 (high-level) + trend → does it explain the miss? If yes → fix. If not → double-click down.
  4. Continue L2 → L3 → L4 only as needed.
  5. Fix loop: prioritize what to work on + how (→ card fix).
  6. Save: write Analysis Sessions/<date>/<date>-<club>.md, append _tracker.csv, log metrics to data/measurements.csv, and (if a change is observed vs last) append correlations/_observations.csv.
  7. Trackman conclusion (optional): attach the actual shot's ball flight → grade the force prediction.

Ball-flight router — start here

Your miss Check first (level · items) Likely root Cards
Pull / pull-hook + stuck L1 pressure → L2 trail-load timing + line of pressure at transition + AP couple late load → non-positive line → thrust/early-ext line-of-pressure, trail-pressure-load, anterior-posterior-forces
Push / block L2 lead-side post + AP couple; line of pressure stuck/under, lead not posting anterior-posterior-forces, cop-trace, lateral-force
Slice / fade / over-the-top L1 sequence (rotation before lateral?) → L2 line of pressure (negative early) early rotation / negative line kinetic-sequence, line-of-pressure
Hook (non-pull) L2 line of pressure (too positive?) + AP; L3 over-shallow over-shallow / face-to-path closed line-of-pressure, shallowing-methods
Fat / thin (compression) L2 trail-load timing (hang-back?) + COP forward; lead post late/weak shift, low point off trail-pressure-load, cop-trace
Lacking distance L1 magnitude + timing → L3 net impulse low/late vertical, low impulse, late forces vertical-force-peak, impulse, kinetic-sequence
Lower-back pain L4 physical screen FIRST + L2 early-extension pattern thrust/side-bend save; physical limit anterior-posterior-forces + physical screen

The cascade

LEVEL 1 — High-level read + trend

Inputs: P1–P10, combined Kinetic-Sequence + pressure view. - Forces — Order · Timing · Magnitude (combined). - Order = lateral→rotational→vertical, vertical last & tallest? - Timing = does each force peak at the right time in the swing (per the card windows): lateral ~transition (P4), rotational ~lead-arm-45°→lead-arm-parallel (P5), vertical ~lead-arm-parallel→shaft-parallel (P5.5–P6)? Vertical peaking at impact (late) is the classic amateur miss → can't use the ground (and it reads low because it's late). Greg Rose: lateral ~0.23 s / vertical ~0.1 s before impact. - Magnitude = each peak vs the club-adjusted bands? - → kinetic-sequence (timing windows live here), lateral-force, rotational-force, vertical-force-peak. - Pressure — COP path + line of pressure. Trail load early & decreasing before top? Line positive at transition? → cop-trace, line-of-pressure, trail-pressure-load. - Output = a status table with a FIXED row set (same rows every run → trendable). Columns: Read (a good / okay / concern chip) · Field · What we see (the read + card link). The rows are always, in order: Sequence · Timing · Magnitude · Pressure (COP) · Line of pressure, then a Verdict row (does it explain the miss?). Don't invent fields — fold sub-reads (e.g. forward shift / lead post, trail-load timing, cuboid-vs-heel) into Pressure (COP). So good vs. bad is glanceable. Explained? → fix. Else → L2. - Trackman confirm: club speed, smash, path, low-point trends.

LEVEL 2 — Localize (individual forces & pressure, both feet, P1→P10)

Inputs: P1–P10 for each sub-force (lateral/rotational/vertical) showing individual feet, + pressure both feet. - For each force & pressure, split lead vs trail and walk P1→P10: which foot, which force, which phase breaks. - Point of application: trail-load amount + timing (cuboid vs heel), line-of-pressure sign at transition, lead COP ball-of-foot vs heel. - → trail-pressure-load, line-of-pressure, cop-trace, anterior-posterior-forces, the force cards. - Trackman confirm: path, face-to-path, low point, (video) early extension.

LEVEL 3 — Net impulse & duration

Inputs: same per-foot, per-force views (set the impulse time points). - Net impulse per channel (direction + size): AP net (negative = space / positive = thrust), torque net, lateral net. - Duration / area under curve / rate of force development — long-and-low vs short-and-hard. - The force → club-delivery → ball-flight bridge. - → impulse, anterior-posterior-forces, force-to-ballflight. - Trackman confirm: speed/quantity of motion, path/curve.

LEVEL 4 — Root / Why (off the plate)

When the forces show the fault but not the cause ("force shows HOW, not WHY"): - Physical screen (TPI mobility/stability — esp. lead-hip internal rotation). - Fundamentals · Equipment · Mental (the 4 whys). - 3D / video kinematic cross-check (driver → 3D matters more; iron → force plate). - Output: technical vs physical vs equipment → sets the fix path. (Inputs off-plate — handoff checklist.)

Club-adjusted reference bands (directional — calibrate to YOUR solid strikes per club)

Metric Driver Mid-iron (6i) Wedge
Vertical peak (Fz) ~190–210%+ (elite 230–250) ~150–185% ~150–160%
Unweighting valley ~63–65% moderate shallow (~90%+); chip = stay up
Lateral peak ~20% lower low
Rotational (Tz) ~85 N·m/kg ref lower low
Setup L/R pressure trail-biased (behind ball) ~50/50 centered / slight lead
> Card thresholds are driver-ish defaults. Adjust down for irons/wedges, then trust your own solid-strike numbers for that club over any textbook number.

Fix loop — what to work on + how

Output format (what /fp-analyze saves)

Each run writes the record into that session's dated folder: Analysis Sessions/<YYYY-MM-DD>/<YYYY-MM-DD>-<club>.md (use _Cross-Session/_template.md; leave inputs_folder blank — photos are already in this same folder): - Inputs: club, ball-flight focus, Trackman (if any). - Level read(s): L1 as the fixed good/okay/concern status table (Read · Field · What we see · Verdict). Down-clicks (L2–L4) use the same table — but no fixed rows: sorted by concern (worst first), each Field tagged with its level (**L2** / **L3** / **L4**). Map each to its card (in the record; stripped from HTML). - Top priority — what to work on + how (the fix). Every top priority must be pinned to the image — add ≥1 evidence line naming the exact frame and where on it the read comes from: - format: - evidence: <IMG_file> @ <x>,<y> — <what's visible here> where x,y are percent (0–100, top-left origin) of where to drop the numbered pin on that frame. - a priority can carry multiple evidence pins (e.g. the same fault at the top and through impact), and they can point at different frames. Use the actual readouts (load %, line-of-pressure angle, the force trace, or the video posture) — quote the number you see. - Since last session: what changed → how each metric moved → how ball flight moved (the cascade). - Trackman conclusion (optional): predicted vs actual → match?

Then: append a row to _tracker.csv (trend scan), log metrics to data/measurements.csv, and append any change→outcome to correlations/_observations.csv (+ update correlations/<lever>.md).

Review report (the consumable output)

Finally, generate a self-contained 4-tab HTML report for review: cd "Analysis Protocol" && py build_report.py "<YYYY-MM-DD>-<club>.md" → writes the .html next to the record in Analysis Sessions/<YYYY-MM-DD>/. - Tab 1 · Analysis — built for fast reading, in this order: 1. Working on (the ball-flight focus) — plain text at the very top, no framing. 2. Top priority — numbered cards. Each priority is color-coded and its pin(s) on the image use the SAME color (priority 1 ↔ pin 1, priority 2 ↔ pin 2 …) so the card↔image mapping is obvious at a glance. 3. Evidence — the frames with the colored numbered pins dropped exactly where each read comes from, plus a Hide / Show pins toggle so the frame can be seen clean. 4. Level 1 — high-level read — the fixed good / okay / concern status table (rows above). 5. Deeper levels (L2–L4) — the same status table as L1, but sorted worst-first (top concerns at the top, each row tagged with its level) — and the Trackman conclusion; both collapsed by default. - No concept-card citations in the reader-facing tabs. The → card-id references stay in the markdown record (grounding/traceability for the AI) but build_report.py strips them from the Analysis / Trend / Inputs tabs (strip_card_refs). The Protocol tab keeps them, since naming the cards is the method. - Tab 2 · Inputs — the screenshots provided (embedded from inputs_folder) + Trackman + next-capture. - Tab 3 · Trend & new concepts — the since-last diff + the cross-session _tracker.csv table + emerging correlations/. - Tab 4 · Protocol — this method, so anyone can see how the analysis was conducted. (Set inputs_folder in the record's frontmatter so the screenshots embed.)

Foundation — the vocabulary

Ground Reaction Force (foundation)

foundation

Definition

The force the ground pushes back with in reaction to your muscles pushing into it (Newton's 3rd law). Force precedes motion — you build the force before the body part moves.

The one distinction that prevents misreads

Force (GRF) Pressure
Measures how hard you push (magnitude — e.g. 2× BW vertical) how you distribute push between feet (%)
Tells you power / quantity of motion timing & location
Trap high pressure % ≠ high force

S2M is explicit: pressure can look perfect while force is weak. Always read magnitude (force) separately from distribution (pressure). (Ep.2 13:02–14:09; Ep.5 13:34)

The three forces + three torques (Greg Rose's "third-grade" language)

Forces (how you push): Lateral (side-to-side → lateral-force) · Vertical (up/down, the jump → vertical-force-peak) · Anterior–posterior (toward/away the ball → anterior-posterior-forces). Torques (how you twist): Twist (around the spine → rotational-force) · Rock-and-roll (side-bend/frontal plane) · Bend (forward/back).

Tour players are mostly "rockers" — "a rocking sport converted into twisting," not primarily rotary (Greg Rose).

Source positions

Source Ref Position Conf
Smart2Move Ep.2 13:02–14:09 GRF = reaction to internal forces; force ≠ pressure; three force directions. high
TPI full-vs-short 4OZ7Fh1u2MQ GRF = force vs gravity; you can read "lighter" than body weight (unloading) — force changes with how you move, not just standing weight. high
Measured Golf FchySrmv9do It's pressure you move, not mass. Centre of pressure (COP) ≠ centre of mass (COM) — you can move COP fast without moving COM much. "Weight shift" is really a pressure transfer. high
TPI – Greg Rose GRF Summit (_9Qa_ixVggg, TdH9Ve-jfHM) Force plates show HOW you move — "step inside the player's body and feel what they feel." 3 forces (lateral/vertical/AP) + 3 torques (twist/rock/bend). Forces precede motion. high

Consensus / divergence

  • Agree: force/pressure ≠ static "weight"; all three separate what you do to the ground from standing weight.
  • MG sharpens it: adds the COP vs COM axis — the practical key to not over-sliding → see center-of-mass-vs-pressure.

What / How / Why — read this before you "fix" anything (Greg Rose)

Force plates tell you HOW you move. They do not tell you WHY. Find the why first — it's one of four: 1. Fundamentals (grip, stance, alignment, ball position, posture — "98% of tour-player work"). 2. Physical (a body limitation — e.g. lead-hip internal rotation; TPI's specialty). 3. Equipment (lie angle, fit). 4. What the player's thinking (their mental model).

A force-plate fault shows you where to look, not the cause — "don't turn these tools into vices."

Forces precede motion (Newton's 1st law)

The GRF is visible before the body moves — pressure going right ≠ "moving right," it means you're pushing on the right foot (you might be about to move left). Read it as where you push, not weight shift. That's why force plates are predictive.

Tour magnitudes — reference (Greg Rose, n≈125 PGA/KFT/DP/LIV/LPGA)

Channel Tour value
Lateral peak ~20% BW (combined)
Vertical ("jump") peak ~202% BW (≈2×)
Torque mix rock > twist > bend (rock > twist ~140%) — most pros are rockers
Lead vs trail — lateral brace lead ~142% of trail
Lead vs trail — AP (twist) lead ~163% of trail (amateurs reversed → early extension)
Lead vs trail — vertical lead ~212% of trail
> Body-normalized; reference only — calibrate to your own. Torque = force × moment arm (men out-torque women mostly via a bigger moment arm, not more force).

Notes

This is the vocabulary card — read it first if a force vs pressure claim ever looks contradictory.

Details & nuance

Worked examples

  • "Step inside Scotty Scheffler's body": video/3D show his positions, not how it feels; the force plate gets close. Asked to keep one tech, Greg Rose & Mark Blackburn both chose force plates over 3D.
  • Greg's first plates (2003) were composite (non-metal) so they wouldn't interfere with the magnetic 3D field — plates "rarely go bad, last 20–30 years."

Mechanism / why

  • Newton's 3rd: push 100 lb, the ground pushes 100 lb back. Newton's 1st: you can't move unless a force moves you — and the GRF is visible before you move.
  • Force through your center of mass → straight (a vertical jump); off-center → twist/torque.
  • Torque = force × moment arm (men out-torque women mostly via a bigger moment arm, not more force).

Caveats & exceptions

  • Force plates show HOW, not WHY. A fault tells you where to look, not whether it's fundamentals / physical / equipment / mind. "Don't turn these tools into vices."

Key quotes

  • "If you want to step inside your player's body and feel what they feel, then you should be interested in ground reaction forces." — Greg Rose (_9Qa_ixVggg ~06:44)
  • "Forces precede motion… this ain't weight shift, this is where you're pushing." — Greg Rose (_9Qa_ixVggg ~20:40)

Centre of Mass vs Centre of Pressure

foundationpriority: high

Definition

Centre of pressure (COP) = where you're pushing on the ground. Centre of mass (COM) = where your body mass actually is. They are different and move differently: you can shuttle COP quickly between the feet without moving COM much. What golfers call "weight shift" is really a pressure transfer.

Why this is the resolver

This is the distinction that reconciles the lateral-force debate (lateral-force): - Shift the lateral PRESSURE (COP) early → everyone agrees (S2M, TPI). - Don't slide the MASS (COM) → Measured Golf's caution. So "move your weight to the trail side" is a trap if you read it as mass — you over-slide, lose low-point control, and sway. Read it as pressure and you load without sliding.

Source positions

Source Ref Position / target Conf
Measured Golf FchySrmv9do It's pressure you move, not mass. Keep COM relatively still; actively push the trail leg to send COP to the trail cuboid. Over-moving mass → can't manage low point / slide off the ball. Stability (loaded base) → mobility (turn). high
Smart2Move Ep.2 (force vs pressure) · Ep.3 (COM, moment arm) Distinguishes force from pressure; treats COM via moment-arm. Doesn't frame the "don't move mass" cue as directly. med
TPI not covered by name (consistent with body-first stability)

My data — current state

COM staying centered? Last measured

Matchups — more / less

Direction Club / strike effect Ball-flight effect Offset
Move MASS too far trail low point hard to manage; slide; sway off ball fat/thin, inconsistent keep mass centered, push pressure instead
Keep MASS still, transfer PRESSURE stable base → repeatable low point; room to turn compression, consistency — (this is the target)

Read it on the plate

  • Watch the COP dot travel trail→lead while the body (COM) stays comparatively centered. Big COM/body slide with the COP = over-shifting mass.

Seen in the data (validation)

  • Wyndham Clark (iron): over-goes lateral and starts late; TPI's fix is turn/load (coil the trail hip), not slide — so the shift starts earlier. Pressure/coil over mass-slide — exactly this card's point.

Dependencies & links

  • Underlies: lateral-force, trail-pressure-load, cop-trace.
  • Related: ground-reaction-force (force vs pressure).

Notes

Measured Golf's signature point, and arguably the single most clarifying idea across all three sources for the lost-strike problem: load by pressure + leg push, not by moving your body off the ball.

Details & nuance

Worked examples

  • Measured Golf demo: keeping the mass relatively still and actively pushing the trail leg sent pressure to the trail cuboid → 76% trail on the plates without moving the COM (FchySrmv9do ~02:51).
  • Wyndham Clark (iron): over-goes lateral / starts late; TPI's fix is turn & load, not slide.

Mechanism / why

  • Stability → mobility: a loaded, stable lower body gives the upper body something to turn against — drop the lead shoulder toward the trail foot and you get a big dynamic shoulder turn (MG ~03:39).
  • "One spine, two legs": use the legs opposite and equal to keep a neutral spine, so the club swings around a central point.
  • Forces precede motion (Greg Rose): the pressure trace shows where you push, before the body moves — so COP ≠ "weight shift."

Caveats & exceptions

  • Don't shoot the lower body at the target in transition — that's moving mass, and it drops the trail hip → the plane drops underneath → "hit the ground before the ball" (MG ~08:06).
  • Measured Golf's quiet pushback on "horizontal force is the secret sauce": lots of lateral without torque leaves you sliding.

Key quotes

  • "I want to keep my mass relatively still while moving my pressure to that right side… I have to actively push that trail leg." — Measured Golf (FchySrmv9do ~02:27)
  • "Use the ground to create stability for the lower body, so I can create mobility with the upper body." — Measured Golf (FchySrmv9do ~03:39)

Sequence — order & timing (check this first)

Kinetic Sequence & Timing

sequencepriority: critical

Definition

The order the three forces peak and when each peaks. Piece #1 of the Performance Pie and the first thing to check — a sequence error poisons every magnitude/point-of-application read below it.

The order (must hold)

# Force Peak timing window Source
1 Lateral around transition (P4), before big COM move Ep.6 14:54 / 18:06
2 Rotational lead arm 45° → lead arm parallel (downswing) Ep.7 12:37 / 13:35
3 Vertical (tallest) lead arm parallel → shaft parallel (downswing) Ep.8 09:07 / 09:26

Source positions

Source Ref Position Conf
Smart2Move Ep.4 + Ep.6–8 Lateral → Rotational → Vertical; vertical last & tallest. Faster players peak vertical a touch earlier; amateurs peak it too late (at impact). high
TPI "Ernie Els" H3tfA3AeDUA · "JT" r9d Tracks the KINEMATIC sequence (segment SPEEDS: pelvis→trunk→arms→club, the "whip") + the deceleration/firing order. Vocab: weight shift→rock→twist→jump = same ground-up order. JT: order holds even when compressed; finishing GRFs early = more transfer time. high
Measured Golf FchySrmv9do Lower-body stability → upper-body mobility: load a stable base, then turn against it. med
TPI – Greg Rose GRF Summit (_9Qa_ixVggg, TdH9Ve-jfHM) 70% rule: lateral → rock&roll → twist → bend → jump (simplified lateral→twist→jump; 30% incl. majors differ). Shallow early to steepen late. Lateral first = power. Amateurs' forces are too late. high

Consensus / divergence

  • Agree on the order: S2M (forces: lateral→rotational→vertical) and TPI (weight shift→rock→twist→jump) describe the same ground-up sequence.
  • KEY distinction — kinetic vs kinematic: S2M's kinetic sequence = the forces (cause; force plate). TPI's kinematic sequence = the segment speeds (effect; 3D capture). Forces cause motion — the kinetic sequence drives the kinematic one. Don't conflate the terms → see kinematic-sequence.
  • Timing insight (TPI/JT): finishing the GRFs early (lead arm parallel, shaft still back) leaves more time to transfer energy up — complements S2M's "vertical peaks before impact, not at it."

Greg Rose: the 70% / 98% rule, timing & the lead-foot brace

70% sequence (largest pro DB): lateral → rock-and-roll → twist → bend → jump. 70% of pros (30%, incl. major champions, don't — not mandatory). Simplified 98% rule: lateral → twist → jump. - Lateral first — for sequence and power (Newton: a weight shift lets you push harder → more force). - "Shallow early to steepen late" — the rock-and-roll shallows the club early so you can steepen late; great players don't steepen early then scramble to shallow. (Directly your stuck/shallow battle.) - Then twist (club to the front) → bend / jump (post + release).

Timing numbers: lateral peaks ~0.23 s before impact, vertical ~0.1 s. The last force (vertical) finishes ~lead-arm-parallel / shaft-vertical, mid-downswing (Greg prefers lead-arm-parallel — "more hand path, farther from the wall"). Earlier = more time to transfer ("push from 30 ft from the wall, not 1 ft"). Amateurs: forces & torques way too late. The whip: if the tip cracks first, who cares how hard the handle moved — sequence > magnitude.

Lead-foot brace — the "75% rule" (advanced): on the lead foot, ~75% of big hitters peak AP first, then lateral-brake + vertical together, within ~0.05 s — clustered right before release. This anchors you to convert linear → angular (release; a 150 mph swing can pull you forward ~200 lb). Best players use all three lead-foot mechanisms (lateral brake, vertical, side-bend); weaker players use one.

My data — current state

Order OK? Lateral peak Rotational peak Vertical peak Last measured

Matchups — failure modes

Fault Effect Fix
Rotational before lateral over the top, steep re-order: shift before turn
Vertical peaks at impact (late) can't use the ground → lost speed, low point wanders move peak earlier (shaft-parallel)

Read it on the plate

  • One graph does it: the kinetic-sequence graph shows all three peaks; confirm order, eyeball each peak's swing position, and each has its own threshold dotted line (sequence + timing + magnitude in one view, Ep.6 21:43).

Seen in the data (validation)

  • Justin Thomas (r9d): starts his GRFs late but finishes early (shaft still back at lead-arm-parallel) — the order holds even compressed. Lesson: finishing early beats starting early.
  • Wyndham Clark (iron): his lateral starts after the top — TPI: "if we started your forces earlier it'd be better." Late sequence = speed left on the table.

Dependencies & links

  • Governs: lateral-force, rotational-force, vertical-force-peak (their timing lives here).
  • Related: line-of-pressure, vertical-unweighting.

Notes

Fix order → timing → point of application → magnitude → shape. Don't add force to a mis-sequenced pattern.

Details & nuance

Worked examples

  • Justin James (longest hitters): finishes his GRFs mid-downswing — "20 ft from the wall"; weaker players finish later, "2 in from the wall."
  • Live scan (volunteer, bad back, misses driver right): sequence good, but vertical ~10 frames late (shaft-parallel, not shaft-vertical) → peak vertical only 169% vs 202% norm. Greg's hypothesis: lead-hip internal-rotation limit (physical, tied to the back) → can't vertical/break on the lead → uses the back. Late ≠ always technical — could be physical.

Mechanism / why

  • The whip: if the tip cracks first it doesn't matter how hard you moved the handle — out of sequence = no crack. Sequence > magnitude.
  • Lateral first = power (Newton: a weight shift lets you push harder → more force).
  • "Shallow early to steepen late" — the rock-and-roll shallows the club early; great players don't steepen early then scramble to shallow.

Caveats & exceptions

  • 70% of pros follow the order; 30% — incl. major champions — don't. "This isn't 'I have to do this to win the Masters.'" Exceptions usually have the first-two or last-two simultaneous.
  • "In general, forces and torques are way too late on amateurs."

Key quotes

  • "They shallow early so they can steepen late. They don't steepen early and then try to figure out how to shallow late." — Greg Rose (_9Qa_ixVggg ~15:29)
  • "If the tip moves first, who cares how hard you're moving the handle." — Greg Rose (_9Qa_ixVggg ~13:23)

Kinematic Sequence (segment speeds)

sequencepriority: high

Definition

The order and speed of the body segments — pelvis → trunk → arms → club — and how each transfers energy to the next (the "whip"). This is the motion/output side. It is caused by the kinetic (force) sequence — see the distinction below.

Kinetic vs Kinematic — don't conflate them

Kinetic (kinetic-sequence, Smart2Move) Kinematic (this card, TPI)
Measures the forces into the ground the speeds of body segments
Tool force plate 3D motion capture
Role the cause the effect

Forces (kinetics) drive motion (kinematics). A clean kinetic sequence is how you produce a clean kinematic one. They're two lenses on the same chain, not competing models.

Source positions

Source Ref Position / target Conf
TPI "Ernie Els" H3tfA3AeDUA Two checks: (1) each segment adds speed to the next (pelvis→trunk→arm→club, each peak higher & faster); (2) the deceleration / "firing" order — pelvis slows first (trunk fired), then trunk (arm fired), then arm (club fired). Proper slow-down order = energy was transferred. high
Smart2Move (kinetic counterpart) Doesn't track segment speeds; provides the forces that produce this.
Measured Golf FchySrmv9do Stability → mobility enables the upper-body speed this measures. med

My data — current state

Speed gain each segment? Deceleration order OK? Last measured

Matchups — failure modes

Fault Effect Likely cause (kinetic)
Two adjacent segments same speed no energy gain → lost club speed a force not firing / mis-sequenced
Wrong slow-down order energy leaks, not transferred up poor kinetic-sequence

Read it

  • The 3D kinematic-sequence graph (4 lines: pelvis/trunk/arm/club). Check progressive speed gain + the left-to-right deceleration order.

Seen in the data (validation)

  • Ernie Els (H3tfA3AeDUA): textbook — each segment adds speed, clean deceleration/firing order. The reference picture.
  • Jamie Sadlowski 2010→2024 (xrvg8NiUY3I): traded thoracic lift + posture-loss + more X-factor separation (52°→45°) — i.e. power — for staying down / maintaining posture — i.e. accuracy. A 2× long-drive champ living the power↔consistency matchup.
  • Wyndham Clark: TPI — "driver → 3D matters more, iron → force plate matters more; you need both." Validates reading kinetics + kinematics together.

Dependencies & links

  • Caused by: kinetic-sequence (forces).
  • Feeds: club-head speed.
  • Related: vertical-force-peak, rotational-force.

Notes

TPI's home turf (3D capture). When force data (S2M) and segment-speed data (TPI) are both available, read them together: force = input, speed = output.

Details & nuance

Worked examples

  • Ernie Els ("one of the best ever"): textbook — each segment peaks higher & faster than the last, then a clean deceleration order pelvis→trunk→arm→club (H3tfA3AeDUA).
  • Jamie Sadlowski 2010→2024: lost thoracic lift, kept posture, X-factor separation 52°→45°traded power for accuracy. Even a 2× long-drive champ lives the trade-off (xrvg8NiUY3I).

Mechanism / why

  • The whip: energy passes up the chain; each segment accelerates, then decelerates as the next "fires" and grabs it. That deceleration (pelvis slows first) is the proof energy transferred — not a flaw.
  • It's the effect of the kinetic (force) sequence — forces cause motion.

Caveats & exceptions

  • Read both lenses: Greg Rose — driver faults show better in 3D, iron faults in the force plate; you need both.
  • Two adjacent segments at the same speed = a power leak (a force not firing).

Key quotes

  • "Each segment should add speed to the next… then who slows down first — the lower body crossed the finish line first." — TPI, on Ernie Els (H3tfA3AeDUA ~01:48)
  • "Driver, 3D is more important; with your iron, your force plate is more important — you need both." — Greg Rose to Wyndham Clark

The forces (lateral · rotational · vertical · A–P)

Lateral Force

lateralpeaks 1thr 20priority: high

Definition

Side-to-side ground-reaction force. It initiates the shift, then the lead leg uses it as a brake. The first force to peak — it sets up everything after it.

Source positions

Source Ref Position / target Conf
Smart2Move Ep.6, 14:54 / 18:06 / 20:15 Peaks 1st, positive, around transition before large COM movement. Threshold 20% body mass. high
TPI "Hiking" BT_FQfPYxuA · "JT" r9d Lateral weight shift comes FIRST, slightly before the top. Skipping it (rotating early) = "hiking" → right hip high & stays high → steep, over-the-top, back strain. JT starts lateral late but finishes early; order still holds. high
Measured Golf FchySrmv9do Caution: don't over-use lateral. Many golfers lean on horizontal force without torque; shooting the lower body/hips at the target drops the trail hip → plane drops → ground before ball. Shift pressure, keep mass still. high

Direction convention

  • Positive = push away from target → ground pushes you toward target → COM moves to target (what you want at transition).
  • Negative = the reverse → COM drifts away from target (hang-back). A line isn't positive until it crosses zero (Ep.6 11:38).

Consensus / divergence

  • Agree (S2M + TPI): lateral peaks FIRST, at/just before transition; its absence (early rotation) is the fault — over-the-top / "hiking" / early extension.
  • Apparent CONFLICT (MG): Measured Golf pushes back on "horizontal force is the secret sauce" and warns against over-sliding at the target.
  • Why + reconciliation — pressure vs mass: all three want the lateral pressure shift first; MG's caution is against over-shifting mass (sliding) and using lateral magnitude as a substitute for torque. So lateral-pressure-first = yes (all); lateral-mass-slide / horizontal-only = no (MG). Not a true contradiction — a depth/over-application warning. See center-of-mass-vs-pressure.

My data — current state

Baseline Current Best Trend Solid vs mishit Last measured

Interventions tried

Date Drill Trace moved? Outcome moved? Keep?
step-back / lead-leg brake (Ep.6 33:08)

Matchups — more / less (matchups.md → L2)

Direction Club / strike effect Ball-flight effect Offset
MORE / earlier low point forward → ball-first; too much = slide past ball, hips stall better compression; over-slide → thin/leftward ball back slightly if AoA steepens
LESS / negative at transition hang-back → low point behind ball; can't set up rotation or the jump fat/thin, dispersion ↑ — fix the shift, don't compensate

Read it on the plate

  • Graph: yellow = total, blue = lead, red = trail; the 0-axis splits positive/negative.
  • Kinetic sequence: lateral should be the 1st peak; threshold dotted line at 20%.
  • Vector tilts toward target when positive.

Seen in the data (validation)

  • Cameron Tringale (BT_FQfPYxuA, "hiking"): little/no lateral shift at the top → rotates early → right hip high & stays high → steep. The lateral-skip fault, on tour.
  • Justin Thomas (r9d): lateral peaks late yet works — because he finishes early. The window is personal; the order is not.
  • Wyndham Clark (iron): lateral starts after the top; TPI's fix = turn/load the trail hip so the shift can start earlier (load enables the shift).

Dependencies & links

  • Feeds: sets up rotational-force and vertical-force-peak; governs low point.
  • Related: kinetic-sequence, trail-pressure-load, impulse (lateral impulse).

Notes

Below 20% it's "very unlikely they're doing what they need" and it inhibits everything later in the swing (Ep.6 21:24).

Details & nuance

Worked examples

  • Greg Rose's QB golfer: "lazy lateral" then "shoves everything forward" + braces. Improving the lateral impulse (engaging the legs earlier), not the peak, helped unlock +25 yds carry (Tf69XfspOr4).

Mechanism / why

  • Lateral does two opposite jobs: it initiates the shift, then the lead leg uses it as a brake to stop and post (Ep.6). At setup, "active tension" — both feet already pushing in opposite directions (a basketball-defender ready position) so force can precede motion (Ep.6 ~02:37).
  • Lateral first = power (Newton): a weight shift lets you push harder into the ground → more force back (Greg Rose).

Caveats & exceptions

  • Not positive until it crosses zero — a line tilting back up toward the axis isn't positive yet (Ep.6 11:38). Common misread.
  • Impulse can matter more than peak: Justin James pushes lateral only ~15% BW but ~4× the tour impulse — long, not hard (Greg Rose).

Key quotes

  • "Before they even finish the back swing they're already creating this shift of pressure forward." — S2M Ep.6 (~04:17)
  • "A weight shift always increases your force." — Greg Rose (_9Qa_ixVggg ~15:29)

Rotational Force (horizontal-plane torque)

rotationalpeaks 2thr 85 N·m/kgpriority: high

Definition

The force couple — trail foot pushes one way, lead foot the other — that spins you around the vertical axis and brings the club from behind you to the front.

Source positions

Source Ref Position / target Conf
Smart2Move Ep.7, 12:37 / 13:35 / 15:33 Peaks 2nd, between lead arm 45° → lead arm parallel. Threshold 85 N·m/kg. Built from a positive line of pressure. high
TPI "Hiking" BT_FQfPYxuA · "JT" r9d "Rock & roll torque" / "twist" — must come after the lateral shift; rotating early = hiking / over-the-top. high
Measured Golf FchySrmv9do Torque is the missing piece — many golfers over-use horizontal force and never build torque; create it via lower-body stability → upper-body mobility. high

Direction convention

  • Positive = rotation toward target (orange circle in app). Negative = away (black circle).
  • Generated from a positive line of pressure (lead COP ahead of trail), which flips negative as you release into the finish (Ep.7 14:15–15:14).

Consensus / divergence

  • Agree: rotation must follow lateral (peaks 2nd); rotating early = over-the-top (S2M & TPI's "hiking").
  • MG emphasis: under-developed torque is the common amateur miss — build it from a stable, loaded trail side, then turn the upper body against it.

My data — current state

Baseline Current Best Trend Solid vs mishit Last measured

Interventions tried

Date Drill Trace moved? Outcome moved? Keep?

Matchups — more / less (matchups.md → L1)

Direction Club / strike effect Ball-flight effect Offset
MORE / turn harder path moves left start slightly left; fade bias if face lags close face to match path to hold curve
TOO EARLY (before lateral) / negative line over the top — thrown out & around steep, pulls/slices, glancing strike re-sequence (lateral first), not a face band-aid
LESS arms stuck/behind, club late to the front blocks, pushes, lost speed

Read it on the plate

  • AP-force graph: red & blue lines push opposite directions = the couple; yellow circle = net rotation (orange = positive).
  • Kinetic sequence: rotational = 2nd peak; threshold dotted line at 85 N·m/kg.
  • Check the line of pressure is positive while it's building.

Seen in the data (validation)

  • Cameron Tringale (BT_FQfPYxuA, "hiking"): rotates before the lateral shift → right hip stays high, steep/over-the-top — rotation-too-early on tour.
  • Wyndham Clark: power comes from coiling/loading the back hip first ("loading the gun") — torque needs the load before it.

Dependencies & links

  • Requires: positive line-of-pressure; follows lateral-force in sequence.
  • Feeds: club path, face-to-path, delivery.
  • Related: kinetic-sequence, line-of-pressure.

Notes

Peaking before lateral is the classic over-the-top fault — "throwing things over and around the ball" (Ep.7 12:58). Sequence beats magnitude here.

Details & nuance

Worked examples

  • Greg Rose's torque-graph reads: the trace should cross zero ~arm-parallel on the backswing (fast players sooner), peak ~arm-45° in the downswing (value ~102), and net torque impulse hit net-zero just after transition — late = "turn forever then throw it over the top" (TdH9Ve-jfHM, Tf69XfspOr4).
  • Cameron Tringale (hiking): rotates before lateral → over the top, on tour.

Mechanism / why

  • Inner-tube / bottle-cap: flip the direction of one foot's push and you create a couple that spins you around the vertical axis (Ep.7 ~02:07; Greg Rose's bottle-cap = twist both at once for max torque).
  • Torque = force × moment arm — you increase torque by widening the distance from your center of mass, not just pushing harder (Greg Rose ~15:12).

Caveats & exceptions

  • "Rocking sport converted into twisting" — most tour players rock more than they twist; don't over-index on pure rotation (Greg Rose).
  • Rotating too early (before lateral peaks) is the over-the-top engine — re-sequence, don't band-aid the face.

Key quotes

  • "If it occurs too early… we get into trouble of throwing things over and around the golf ball." — S2M Ep.7 (~13:17)
  • "Most tour players are rockers. You think this is a rotary sport? Not really." — Greg Rose (TdH9Ve-jfHM ~09:13)

Vertical Force — Peak Magnitude

verticalpeaks 3thr 165priority: high

Scope: full swing. Vertical force in chipping/putting is a different concept (stability, not a jump) — those get their own cards under concepts/chipping and concepts/putting.

Definition

The up/down ground-reaction force at its peak — the "jump." Of the three full-swing forces it's the one most highly correlated with club-head speed, and the one amateurs most often leak.

Source positions

Source Ref Position / target Conf
Smart2Move Ep.8, 13:01–14:30 Threshold 165% body mass = floor. Strong amateurs 190–200%+; elite/fast 230–250%+ (e.g. Zubac). Lead foot dominates at peak (ex. 134% lead vs 85% trail). high
TPI full-vs-short 4OZ7Fh1u2MQ · "JT" r9d PGA norm ~200% BW (player example 211%). Vertical = the power/speed force, peaks last. JT: starts GRFs late but finishes early (shaft still back) = more transfer time. high
Measured Golf FchySrmv9do Less direct: vertical needs torque to match against — don't lean on vertical + horizontal without rotation. med

Consensus / divergence

  • Agree (S2M + TPI): vertical = the speed force, peaks last/tallest. Thresholds line up — S2M 165% floor / 190–200% strong / 230–250% elite; TPI tour norm ~200% (211% example).
  • TPI adds: finishing the vertical/GRFs early matters as much as magnitude (JT).
  • MG caution: vertical without torque is wasted — sequence/rotation first.
  • Divergence axis: TPI's body-first lens — mobility/strength may gate output; a countermovement-jump test on the plates separates force-capacity from technique.

My data — current state (summary; full series in data/measurements.csv)

Baseline Current Best Trend Solid vs mishit Last measured

What my data shows — outcome links

  • Trackman (proximate): does my peak vertical track with club speed / smash / low point in MY data?
  • On the course (lagging): should surface in SG: Off-the-Tee / SG: Approach — tracked at the program dashboard level, not attributed to this card alone.
  • My observed correlation: e.g. "vertical peak vs club speed r≈?, n=?"

Interventions tried

Date Intervention / drill Trace moved? Outcome moved? Keep?

Matchups — more / less (full map in matchups.md → L3)

Direction Club / strike effect Ball-flight effect Offset to hold flight constant
MORE (toward 190–250%, well-timed) + club speed; early arrival can change AoA/steepness more ball speed → distance; launch/spin shift with AoA if AoA steepens, ball fwd / tee up to reset launch
LESS (<165%, or peaks late / off the heel) speed left on table; heel-based peak → early extension, low point wanders thin/low strikes, distance loss, dispersion ↑ — fix the cause, don't paper over it

Read it on the plate (Smart2Move app)

  • Kinetic-sequence graph: vertical = 3rd and tallest peak.
  • Threshold line: dotted line at 165% — peak should clear it.
  • Point of application at peak: lead-foot COP (blue dot) in the ball of the foot, not the heel.

Seen in the data (validation)

  • Ryan Gerard (4OZ7Fh1u2MQ): peak ~211% BW (vs PGA norm ~200%) — clears S2M's 165% floor comfortably.
  • Wyndham Clark: the harder he swings, the better his mechanics get (early extension drops, timing improves) — a real "more can be better" matchup for certain players. TPI: don't leave 20% on the table.

Dependencies & links

  • Requires: positive line of pressure (line-of-pressure), lead-foot ball-of-foot COP (cop-trace), unweighting valley ~63–65% (vertical-unweighting).
  • Feeds / affects: club speed, attack angle, low-point location, strike quality.
  • Related cards: kinetic-sequence (timing), vertical-unweighting, cop-trace — all full-swing.

Notes

Magnitude is piece #3 of the Performance Pie — chase it only after sequence, timing, and point of application are right (Ep.8). Force on a good pattern = speed; on a bad one = injury risk.

Details & nuance

Worked examples

  • The numbers ladder: S2M floor 165% → strong amateurs 190–200%+ → elite/fast (Jason Zubac) 230–250%+ (Ep.8 ~13:43). TPI tour norm ~202% (Greg Rose); Ryan Gerard 211%; the QB golfer peaked 243%.
  • Lead foot dominates: example 134% lead vs 85% trail (Ep.8); tour lead = 212% of trail (Greg Rose).

Mechanism / why

  • The dunk: you jump from the balls of your feet, not your heels — same in golf; that's why the lead-foot COP must be ball-of-foot at peak (Ep.8 ~12:24).
  • Vertical is "very highly correlated to speed" — the clearest power lever once the sequence is intact.

Caveats & exceptions

  • Amateurs peak it too late (at impact) → can't use the ground → the force reads low because it's late (live scan: 169% vs 202 norm).
  • Pressure % ≠ force: you can have textbook lead-pressure timing and still produce weak vertical (Ep.5 13:34).

Key quotes

  • "It's rare that I see someone not approaching 190 or even over 200%… guys like Zubac get 230, 250%+." — S2M Ep.8 (~13:43)
  • "That's our jump — 202%, just think 2× body weight. That's what the best players in the world do." — Greg Rose (TdH9Ve-jfHM ~09:13)

Anterior–Posterior Forces (rotation + pelvis space)

appriority: high

Definition

The toward/away-the-ball forces. Anterior = positive = toward the ball; posterior = negative = away. They do two jobs at once: (1) form the rotational couple that creates twist, and (2) drive the linear motion of the pelvis toward/away the ball — i.e. whether you create space or thrust into the ball.

Source positions

Source Ref Position / target Conf
Smart2Move (Net Impulse) Tf69XfspOr4 The couple: lead leg pushes AWAY from ball (−), trail leg pushes TOWARD ball (+) → twist. Rule of thumb: ~2× more AP force in the LEAD leg. Good player: lead −5.3 / trail +1.9 impulse → net −3.6 = pelvis opens / creates space. Amateur: trail-dominant → net +2.6 = pelvis thrusts toward ball → early extension, club thrown out/around. high
TPI (Greg Rose) TdH9Ve-jfHM "Bottle-cap" — twist both feet at the same time for max torque; if not simultaneous, lead must be 2nd AND bigger. If the trail wins, the ground shoves your hip toward the ball → early extension. Tour: lead AP 163% > trail (lead ~30% BW vs trail ~18%); most amateurs are reversed (trail > lead) → why they early-extend. high

Why this is your lever

This is the force-plate root of stuck / pull-hook: if your trail AP dominates, the pelvis thrusts toward the ball → early extension → "slack in the boat" (Greg Rose) → you can't deliver the club → trapped/stuck → flip to save → pull hook. The fix is to get the lead leg pushing away from the ball so the pelvis creates space to deliver from.

My data — current state

Lead AP Trail AP Net AP impulse Last measured
— (want negative)

Matchups — more / less

Direction Effect Note
Lead AP dominant (net −) pelvis opens / creates space → room to deliver the target — lead ~2× trail
Trail AP dominant (net +) pelvis thrusts to ball → early extension → stuck → hook your suspected pattern

Read it on the plate

  • AP graph: trail above the line (+, toward ball), lead below (−, away). Check lead > trail and the net AP impulse is negative.
  • If the lead line stops pushing away / trail carries it → thrust/early-extension pattern.

Dependencies & links

  • Feeds: rotational-force (the couple), club path, low point, early extension.
  • Related: impulse (net impulse), hips-spinning-open, center-of-mass-vs-pressure, line-of-pressure.

Notes

The single most direct force-plate read for your miss — if it's trail-dominant, that's the early-extension engine behind the stuck/flip.

Details & nuance

Worked examples

  • Good player (S2M Net Impulse): lead AP 41% BW pushing away from the ball; impulse lead −5.3 / trail +1.9 → net −3.6 → pelvis opens, creates space, "pulls away from the ball." The model.
  • Amateur (same video): trail-dominant — impulse lead +2.7 / trail −0.6 → net +2.6; past a point his lead leg stops pushing away entirely → all rotation from the trail → pelvis thrusts toward the ball → early extension, club thrown out & around. (Check yourself against this.)

Mechanism / why

  • Bottle-cap (Greg Rose): you open a cap by twisting both sides at once — max torque. The AP couple is the same: trail pushes the right hip forward, lead pushes the left back → twist.
  • AP forces do two jobs: the rotational couple and linear pelvis motion (space vs thrust).

Caveats & exceptions

  • "If the trail wins, the ground shoves your hip toward the ball → early extension. If the lead is more, it pushes you back → space." Want both at once, lead > trail.
  • Most amateurs are reversed (trail 163% > lead) — the early-extension epidemic.

Key quotes

  • "If the trail one wins here, you're going to really extend… I want the lead more than the trail." — Greg Rose (TdH9Ve-jfHM ~06:09)
  • "That thrust of the pelvis toward the ball instead of creating that space." — S2M Net Impulse (Tf69XfspOr4 ~08:49); the "slack in the boat" idea (Dr. Rose).

Pressure & centre of pressure

Trail-Side Pressure (backswing load)

pressurethr 80priority: high

Definition

How much of your pressure is on the trail foot at its peak in the backswing — and, just as important, when that peak happens. This is distribution, not force (see ground-reaction-force).

Source positions

Source Ref Position / target Conf
Smart2Move Ep.5, 04:15–04:56 Peak ~80% trail (example 81%), reached early — around P2–P3 — then already decreasing before the top. high
TPI not covered by name (body-first lens; the "trail hip up/back/around" idea is 3D-capture knowledge MG leans on)
Measured Golf 3_IhRYFvvAI · 6VBOPRrXF1I · FchySrmv9do 75–80% min into trail (76% shown). Load by actively pushing the trail leg & loading the trail HIP (up/back/around) — not by sliding mass over. Hold posture (don't "sit on a bar stool" / push the glute back). Feel the push up through the ball of the foot; pressure to the cuboid, not the heel. high

The timing is the point

Best players load and start shifting back before the top. A late peak (or pressure stuck on the trail into the downswing = hang-back) is the classic strike-killer.

Consensus / divergence

  • Agree: ~75–80% trail at peak (S2M ~80–81%; MG 75–80%). Both stress it's pressure, not "weight."
  • MG adds the HOW (body-first): load the hip (up/back/around) by pushing the trail leg and holding posture — don't shove mass right (that wrecks low-point control; see center-of-mass-vs-pressure).
  • Conflict (location): trail pressure to the heel (S2M) vs cuboid/midfoot, not heel (MG) — see line-of-pressure.
  • Tool note: MG uses Swing Catalyst (pressure mat); S2M uses force plates. Pressure % is comparable; true force is S2M-only.

My data — current state

Baseline Current Best Peak phase Solid vs mishit Last measured

Interventions tried

Date Drill Trace moved? Outcome moved? Keep?

Matchups — more / less

Direction Club / strike effect Ball-flight effect Offset
Late / stuck on trail low point behind ball fat/thin, toe/heel scatter get the peak earlier (P2–P3)
Too little load weak coil, no shift to brake against loss of speed & sequence

Backswing setup → enables the transition shift · fix the backswing first

The downswing slide/stuck is mostly a compensation for a poor load. The backswing is slow and controllable, so fix it first — a good load removes the need for the difficult downswing saves. A backswing that sets up a clean shift shows up as: - Load early, ease back before the top — trail % peaks ~75–80% by P2–P3 and is already dropping before P4. Still loading at the top = late shift = rushed slide → stuck. - Pressure, not mass — push the trail leg/hip with COM centered (no sway) so you're already positioned to push off forward (center-of-mass-vs-pressure). - To the cuboid/midfoot (not heel/toes) — you can only push from the midfoot → enables the shift and a positive line-of-pressure. - Posture + trail-knee flex held — a loaded spring to push from (stand up = nothing to push off). - Enough turn — fuller turn → hands deeper → matches downswing rotation → less need to slide (Shauheen, hips-spinning-open).

Backswing target: load ~75–80% trail, to the cuboid, mass centered, peaking by P3 and easing back before the top. Light / late / toe-based / swayed = why transition feels rushed and you get stuck.

Read it on the plate

  • Pressure distribution % (lead vs trail) and the COP dots; scrub to P2–P3 and read the trail %.
  • Remember: high pressure % ≠ high force (Ep.5 13:34).

Seen in the data (validation)

  • Wyndham Clark: "load the gun" — coil/load the back hip first; without loading the trail hip "you haven't loaded the chamber" → no power. Loading it also lets the lateral shift start earlier.

Dependencies & links

  • Feeds: the forward shift (lateral-force), line-of-pressure, cop-trace.
  • Related: cop-trace, kinetic-sequence.

Notes

~80% is a reference, not a mandate — calibrate to your own solid strikes. The early-then-decreasing shape matters more than the exact number.

Details & nuance

Worked examples

  • S2M example: 81% trail at P3, then already decreasing before the top (Ep.5 ~04:56).
  • Measured Golf: got to 76% trail on Swing Catalyst by actively engaging the trail cuboid (pushing the trail leg), mass staying centered — not by sliding over (FchySrmv9do ~03:15).
  • Wyndham Clark: "load the gun" — coil/load the back hip first or "you haven't loaded the chamber."

Mechanism / why

  • Load by pushing the trail leg into the ground → pressure goes to the cuboid/midfoot while the body (COM) stays put. The trail hip works up/back/around (3D-capture finding).
  • The peak crests early (P2–P3) then eases back before the top — that early-then-decreasing shape is what lets the shift start smoothly.

Caveats & exceptions

  • Heel vs cuboid conflict: S2M says "toward the heel," MG says "to the cuboid, NOT the heel" (heel → trail-leg extension → can't push). Likely wording; net = back from the toes, not into the heel.
  • Pressure % ≠ force (Ep.5 13:34) — and the timing matters more than the exact %.

Key quotes

  • "We need to get a minimum of 75 to 80% into our trail side… move toward the heel where the cuboid bone would be." — Measured Golf (6VBOPRrXF1I ~02:16)
  • "Get that max pressure on the trail side… around P3, a nice and early point in the swing." — S2M Ep.5 (~04:36)

Line of Pressure

pressurepriority: high

Definition

The tilt of the line connecting trail-foot COP (red) and lead-foot COP (blue) — i.e. the "angle of pressure." It's the point-of-application input to rotational force.

Source positions

Source Ref Position / target Conf
Smart2Move Ep.5 05:17–05:56 · Ep.7 14:15 At transition, want a positive line ("at least a little"), made by biasing the trail-side push toward the heel. More positive = more rotational potential. Lateral-style players run flatter but still slightly positive. high
TPI – Greg Rose GRF Summit (_9Qa_ixVggg) Calls it the "force alignment line" — the line between your two feet's pressure. You can stand feet-square yet have it in-to-out or out-to-in. Wants it level or slightly in-to-out (like Justin for driver); out-to-in → path/plane issues. "Force alignment matters more than your stance alignment." high
Measured Golf "Pressure Transfer" (6VBOPRrXF1I) Positive line built by moving trail pressure to the cuboid (midfoot / back-of-arch), NOT the heel; needs 75–80% trail. Negative or neutral line → early extension. Reframes "shift" as "transfer." high

Consensus / divergence

  • Agree: want a positive line at transition to enable torque + shallowing; a non-positive line → over-the-top / early extension.
  • CONFLICT — where the trail pressure sits: S2M says bias the trail push "toward the heel." Measured Golf says move toward the heel but stop at the cuboid/midfoot — explicitly NOT the heel.
  • Why MG differs: full-heel load forces the trail leg to extend → pressure in the heel "where you can't push/jump" → early extension (MG says this reverses their own 2018 "load the heel" cue, crediting Dr. Joe Lacaus / Fast Eddie Fernandes).
  • Reconciliation: likely wording, not physics — S2M's "a little toward the heel" ≈ MG's "to the cuboid, not all the way." Net target: back from the toes/ball, toward—but not into—the heel. Confirm on your own trace.
  • Greg Rose adds the direction: the line ("force alignment") should run level or slightly in-to-out through the swing — out-to-in → path/plane issues, and it can be wrong even with square feet. He rates it above stance alignment. (For your stuck/pull-hook: also watch it's not too far in-to-out = over-shallow.)

My data — current state

Baseline Current Best Trend Solid vs mishit Last measured

Matchups — more / less

Direction Club / strike effect Ball-flight effect Offset
More positive feeds rotation; shallower delivery; path-left tendency draw bias / more turn available match face to path to hold curve
Negative / flat at transition over the top; starves rotation steep, pulls/slices, glancing re-bias trail push to the heel; re-sequence

Read it on the plate

  • The line between the red (trail) and blue (lead) COP dots; look for a positive right-to-left slope at the top.
  • The app also outputs a numeric line-of-pressure value — track that number against your own swings.

Seen in the data (validation)

  • Cameron Tringale (BT_FQfPYxuA, "hiking"): early rotation without lateral = the negative / over-the-top pattern this card warns about.
  • Wyndham Clark: ~3" of early extension on driver (only 1.7" when he swings harder) → block-right / occasional-left misses — early extension is the downstream symptom of a non-positive line.

Dependencies & links

  • Feeds: rotational-force (point of application).
  • Related: trail-pressure-load, cop-trace, kinetic-sequence.

Notes

This is the trace tied to over-the-top. Given the lost-strike history, a negative/flat line at transition is a prime suspect.

Details & nuance

Worked examples

  • Justin (Greg Rose): force-alignment runs slightly in-to-out for the driver (good) and stays level / in-to-out throughout the swing — "you're never going to see out-to-in."

Mechanism / why

  • You can stand with feet perfectly square yet have your force alignment in-to-out or out-to-in — it's independent of foot/shoulder alignment. Out-to-in → path/plane issues.

Caveats & exceptions

  • Greg Rose rates force alignment above stance alignment — "more important than your alignment."
  • For your stuck/pull-hook: the usual fault is non-positive/out-to-in (over-the-top); but watch the opposite too — a line too far in-to-out = over-shallow → under-plane/stuck.

Key quotes

  • "I think your force alignment is more important than your alignment." — Greg Rose (TdH9Ve-jfHM ~13:25)
  • "This force alignment creates all kinds of path-plane issues." — Greg Rose (TdH9Ve-jfHM ~13:49)

Centre-of-Pressure Trace

pressurepriority: high

Definition

The path of the overall COP (the yellow dot) and each foot's COP through the swing — where on the feet you're pushing, moment to moment.

Source positions

Source Ref Position / target Conf
Smart2Move Ep.5 06:19–07:00 Early downswing: lead-foot COP into the ball of the foot, early; max lead-side pressure appears early, not late. high
Smart2Move (styles) Ep.5 07:22–08:22 Traces differ by player: lateral players wider, COP migrates heel↔toe; vertical players stay in the balls of the feet. No single "correct" trace — don't force one. high
TPI not covered by name (body-first lens; ball-of-foot push echoed across TPI)
Measured Golf FchySrmv9do Move COP without moving COM; push the trail leg to send pressure to the cuboid; stay up on the balls of the feet, dynamically stacked; finish into the lead cuboid. high

Consensus / divergence

  • Agree: push from the balls of the feet (not heels); COP migrates while COM stays relatively stable.
  • MG link: the COP vs COM distinction is the practical core → see center-of-mass-vs-pressure.

My data — current state

Baseline Current Best Trend Solid vs mishit Last measured

Matchups — more / less

Direction Club / strike effect Ball-flight effect Offset
Lead COP into ball of foot, early strong vertical push available; stable low point compression, consistent strike
Lead COP in heel / max pressure late early extension, posture loss, low point wanders thin/inconsistent, lost speed get pressure to ball-of-foot earlier

Read it on the plate

  • Watch the yellow COP dot migrate; check the lead (blue) dot is in the ball of the foot as you hit peak vertical.
  • Compare your solid-strike trace vs your mishit trace — that's your template, not a textbook shape.

Dependencies & links

  • Feeds: vertical-force-peak (point of application), low point.
  • Related: trail-pressure-load, line-of-pressure.

Notes

Style-dependent on purpose. The non-negotiable is ball-of-foot, early on the lead side — you can't push vertically off your heels (Ep.5/Ep.8 dunk analogy).

Details & nuance

Worked examples

  • Two valid styles (Ep.5 ~07:22–08:22): a "lateral" player runs wider, COP migrating heel↔toe and the feet working; a "vertical" player stays in the balls of the feet and barely migrates to the heels. Different traces, both fine.

Mechanism / why

  • Lead COP into the ball of the foot early = "a really powerful place to push vertically" — it's what lets the lead leg post and jump (Ep.5 ~06:19). Then the COP lands in the lead heel as you finish (Ep.5 ~07:00).
  • Fastest way to shift pressure to one side: lift the other foot — every bit of pressure goes to the loaded foot (Ep.5 ~15:39).

Caveats & exceptions

  • No single "correct" trace — S2M used to think everyone should match one; they don't. Calibrate to your solid strikes.
  • The trap: lead COP stuck in the heel / max pressure late → early extension, posture loss.

Key quotes

  • "For a while we kind of thought that everyone should have a similar pressure trace…" (then explains they shouldn't) — S2M Ep.5 (~07:22)
  • "Land into the ball of their foot pretty early… a really powerful place to push vertically." — S2M Ep.5 (~06:19)

Curve shape — continuous

Vertical Unweighting (counter-movement valley)

verticalthr 65

Definition

The dip in vertical force below body weight in transition — the mini-squat / "offloading" that loads the spring before the big vertical spike. It's the load, not a flaw.

Source positions

Source Ref Position / target Conf
Smart2Move Ep.8 17:49–19:13 Vertical drops to a valley ~63–65% BW; vertical-style players like 65–75%. The dip is the counter-movement that enables a higher peak after. high
TPI full-vs-short 4OZ7Fh1u2MQ The dip = a squat-jump / stretch-shorten cycle (pre-stretch the legs → more power). Big hitters ~65% (example 72%); reading <100% = accelerating down. high
Measured Golf not covered directly

Consensus / divergence

  • Strong agreement: S2M valley 63–65% ≈ TPI ~65% (big hitters). TPI names the mechanism: a stretch-shorten cycle (squat before the jump) storing elastic energy for a bigger peak.

My data — current state

Baseline Current Best Trend Solid vs mishit Last measured

Matchups — more / less

Direction Effect Note
No / shallow dip no counter-movement → lower peak vertical → less speed you can't spike high without first unloading
Too deep / late dip timing thrown off; peak arrives late depth is player-dependent (vertical players go deeper)

Read it on the plate

  • On the vertical-force graph, find the lowest valley (yellow line below the 100% "new zero") in transition; read the %.

Seen in the data (validation)

  • Ryan Gerard (4OZ7Fh1u2MQ): unloads to ~72% (TPI says big hitters ~65%) before spiking to 211% — the squat-jump / stretch-shorten cycle in a tour swing.

Dependencies & links

  • Feeds: vertical-force-peak (no valley → low peak).
  • Related: kinetic-sequence.

Notes

Depth is individual — set your own target from your best strikes, not a fixed number.

Details & nuance

Worked examples

  • Ryan Gerard: unloads to ~72% (TPI: big hitters ~65%) before spiking to 211% — the squat-jump in a tour swing (TPI 4OZ7Fh1u2MQ).

Mechanism / why

  • The squat-jump / stretch-shorten cycle (TPI): breaking the knees & hips pre-stretches the leg muscles (like loading a spring) → more power out. The dip also means the force is below bodyweight = the body is accelerating down, which forces a big reversal up = the peak.
  • S2M calls the dip an "offloading" / mini-squat — same idea (Ep.8 ~18:10).

Caveats & exceptions

  • Depth is player-dependent — pure "vertical" players go deeper (65–75%); don't force one number.
  • No dip → no spring → a lower peak. The valley isn't a flaw, it's the load.

Key quotes

  • "You're not just going to jump, you're going to squat first before you jump… that pre-stretch activates the stretch-shorten cycle." — TPI, Greg Rose/Corey (4OZ7Fh1u2MQ ~01:34)

Impulse (force × time)

impulse

Definition

Force multiplied by the time it's applied = area under the curve = the actual quantity of motion produced. Peak force alone doesn't tell you how much you transferred. Piece #4 of the Pie (curve shape).

Source positions

Source Ref Position / target Conf
Smart2Move Ep.9 09:24–10:18 Measured between two events (e.g. start → impact), normalized N·s/kg. Lateral impulse: high > 7.5, low < 5 (ex. 6.5 ≈ good). Net impulse = positive − negative; want net positive toward target. high
Smart2Move Ep.9 02:23–03:11 Grow it two ways: more force (Rahm/Finau, short backswing) or more time (long-drive, long backswing). high
Smart2Move (Net Impulse) Tf69XfspOr4 Direction of net impulse matters, not just size. AP net impulse: want negative (lead away from ball → pelvis creates space); positive = thrust → early extension. Torque net impulse: more positive than negative, reaching net-zero just after transition (late = "turn forever then over the top"). Impulse can double even if peak timing doesn't move. high
TPI – Greg Rose _9Qa_ixVggg · TdH9Ve-jfHM 3 ways to hit it farther: force · velocity · impulse (apply force/velocity longer — the "running start at the wall"). For some channels impulse > peak: Justin James pushes lateral only ~15% BW but ~4× tour impulselong, not hard. Trail leg esp.: push long, not hard. high

Net impulse — three reads that matter

  • AP (linear) net impulse: negative = good (lead away from ball → pelvis opens / space). Positive = thrust toward ball → early extension (your miss). → anterior-posterior-forces.
  • Torque net impulse: positive = good (net rotation toward target); reach net-zero just after transition, not late.
  • Lateral net impulse: net positive toward target (high > 7.5, low < 5 N·s/kg).

Impulse can improve when the peak doesn't. Greg Rose: in ~2–3 years impulse will be most of what we talk about — it's how much you actually delivered, not how big the spike was.

My data — current state

Lateral + impulse Net impulse Best Trend Solid vs mishit Last measured

Matchups — more / less

Direction Effect Note
Higher net (toward target) more quantity of motion → more speed/compression the goal start→impact
Low / leaky (negative chunk) motion bleeding the wrong way check direction & timing, not just peak
Rate of force development sharper, well-timed peak transfers better how quickly force builds

Read it on the plate

  • Set the two time points (three-dots dialog), read the shaded area and the +/- impulse values (N·s/kg). Net = positive − negative.

Dependencies & links

  • Summarizes: the shape of lateral-force, rotational-force, vertical-force-peak over time.
  • Related: kinetic-sequence.

Notes

The continuous counterpart to the discrete peaks — it's how much you actually delivered, not just how big the spike was.

Details & nuance

Worked examples

  • Greg Rose's college golfer (ex-QB): ~125–126 mph; "lazy lateral" then "shoves everything forward" + braces; peak vertical 243%, but attack −3° with driver → drives never >20 ft up. 23 min of work doubled his impulse (trail 6→11, total 2.6→5.1) by engaging the legs earlier in the backswing — even though peak lateral timing didn't move (36%→48%, same frame). Then lead-leg-early + tee higher → attack −3°→+1°, carry +25 yds.
  • Justin James: lateral peak only ~15% BW (vs 20% tour) but ~4× the tour impulsepushes long, not hard.

Mechanism / why

  • Chair-at-the-wall (Greg Rose): a shove from 1 ft can hurt you; a running start can kill you — more time to apply force/velocity. That's impulse.
  • 3 ways to hit it farther: more force (strength) · more velocity (hands faster) · impulse (apply it longer).

Caveats & exceptions

  • Impulse can improve when the peak doesn't — don't judge a session only by peak numbers.
  • Some forces are more about impulse than peak (esp. the trail leg — push long, not hard).

Key quotes

  • "He doesn't push as hard, he just pushes four times longer." — Greg Rose on Justin James (TdH9Ve-jfHM ~11:17)
  • "In two or three years, impulse is probably the majority of what we're going to be talking about." — Greg Rose (TdH9Ve-jfHM ~11:38)
Goal-first: distance control → start line → curve → distance. For each goal — the metrics that move it, the swing change to make, and the compensation cascade it triggers elsewhere. Sourced from your lessons (multiple coaches → expect conflicts; the Conflicts tab + your data settle them).

Your goal hierarchy

Club & Ball — Goal Hierarchy

frameworkgoal: distance control, start line, curve, distanceverdict: workingaffects: start line, curve, distance, spin, strikesrc: RJ's working priority order

The order I'm working toward · control before power

Nail these in order — each assumes the one above it is owned: 1. Distance control — repeatable carry numbers (tight distance dispersion). Scoring lives here. 2. Start line — a reliable launch window (≈ face angle). 3. Curve — first get the ball curving one direction dependably (a one-way miss), then reduce the amount. 4. Distance — add raw speed/carry last, once control is owned (don't trade control for yards).

The chain for every goal

GOAL → the metrics that drive it → the swing change that moves the metric → the implications/compensations on the rest of the swing. The last column is the whole point: a change is never free.

Goal Driving club/ball metrics Primary swing change Watch-outs / compensation cascade
Distance control center strike / smash, spin consistency, low-point & AoA repeatability low point forward & repeatable (pressure fwd, line-of-pressure); consistent face delivery over-managing tempo kills compression; chasing perfect strike can flatten speed
Start line face angle (~85% of start) face control: grip, lead-wrist condition, release timing over-shut → hook; push face too far right → body flips hands to square it → face timing & path go variable
Curve face-to-path (face relative to path) manage path (shallow/steepen, in-out) and face together shallow to move path right also moves low point back → fat/thin; closed face needs a matching path or it hooks
Distance club speed → ball speed, AoA, smash, spin vertical force / "jump", sequence, width, lag (vertical-force-peak, kinetic-sequence) adding speed can degrade strike & face timing; more effort can steepen AoA → launch/spin shift

Per goal — quick read

  1. Distance control — own a tight band of carry numbers. Mostly strike (center face + repeatable low point) + spin consistency. Force levers: forward pressure + ball-of-foot COP (trail-pressure-load, cop-trace). Never sacrifice this for distance.
  2. Start line — own the face at impact. Lives in grip, lead-wrist, release timing (face-vs-start-line). The classic trap is the cascade below.
  3. Curve — own face-to-path. Step 1: a one-way shape (pick draw or fade, never see the other side). Step 2: reduce the gap to tighten it (ball-flight-laws, shallowing-methods).
  4. Distance — own club/ball speed. This is where the Force tab pays off (vertical force, sequence, finishing GRFs early). Add it once 1–3 hold.

The compensation cascade (why a change is never isolated)

RJ's example: open the face → start line right (direct). But push it too far right and the body senses the miss and releases/flips the hands to square the face → face timing becomes variable, path swings left from the save, strike thins, and the start line you were chasing gets less repeatable. Map the cascade — don't chase a metric in isolation. Every lever card carries a "Compensation cascade" section.

Sources & conflicts (expect a mess — that's handled)

This priority order is RJ's. The swing changes to hit each goal come from his lessons (multiple coaches) → a new source repo Lesson Transcripts/. Conflicting advice is expected and fine: each lesson is a source, conflicts surface in the Conflicts tab, and the worked/hasn't verdict + your Trackman data settle which coaching actually held up for you.

Links

  • Levers: ball-flight-laws, face-vs-start-line, shallowing-methods, force-to-ballflight.
  • Force levers feed Distance & Distance-control: vertical-force-peak, line-of-pressure, trail-pressure-load, kinetic-sequence.
Details & nuance

Mechanism / why

  • Control before power: each goal assumes the one above it is owned — you can't tighten curve until you own a start line, and adding distance before control just makes a bigger, less repeatable miss.
  • Curve in two steps: first own a one-way miss (pick draw or fade, never see the other side) → then reduce the gap to tighten it. Direction first, magnitude second.

Caveats & exceptions

  • This priority order is yours — a sensible default, not a universal law. A different player (e.g. a bomber) might prioritize distance differently.
  • A change is never isolated — the compensation-cascade column is the whole point; map it before chasing a metric.

Key quotes

  • Your framework, not a source — the test is whether working it in this order moves your scores (track via the program dashboard / SG).

Levers — the swing change, its effect, and what it costs

Ball-Flight Laws (the anchors)

lawgoal: start line, curveverdict: workedaffects: start line, curve, spinsrc: Ball-flight laws (TrackMan / D-plane)

The rule / what it is

Every club/ball relationship below reduces to two laws: - Start direction ≈ mostly FACE (~85% face, ~15% path). - Curve ≈ FACE-TO-PATH (face open of path → fade/slice; face closed of path → draw/hook). - (Strike + AoA + dynamic loft set launch/spin/low-point, but start & curve are the anchors.)

Cause → effect

  • Move the face → start line moves with it (and curve, via the new face-to-path gap).
  • Move the path → curve moves (face-to-path), start line barely (path is only ~15%).

Cross-implications (what else moves)

You can't change face or path in isolation — changing one changes the face-to-path gap, so curve moves unless you move the other to match.

Offsets (to hold a target outcome)

  • Hold the curve: keep the face-to-path gap constant (move face and path together).
  • Hold the start line: keep the face roughly constant (it's ~85% of start).

Source

Ball-flight laws / D-plane — the physics everything else is measured against.

Worked / hasn't (my verdict)

Date Tried Result Keep?
the framework itself ✔ reference

Links

  • Used by every other Club & Ball card; force version in force-to-ballflight.
Details & nuance

Mechanism / why

  • Start ≈ ~85% face / ~15% path (not 100% face — that's why path nudges the start a little). Curve ≈ face-to-path (the gap, not the absolute face).
  • Strike, AoA and dynamic loft set launch/spin/low-point, but start & curve are the two anchors everything else routes through.

Caveats & exceptions

  • Off-center strikes break it: gear effect (toe/heel, high/low) adds its own curve/launch independent of face-to-path — so a heel/toe miss can fool you.
  • The 85/15 split is a driver-ish rule of thumb; it shifts a bit with loft.

Key quotes

  • Physics, not a coach — D-plane / ball-flight laws. Treat as the reference everything is measured against.

Closing the Face → Start Line (and the shallow interaction)

relationshipgoal: start line, curveverdict: untestedaffects: start line, curve, pathsrc: Lesson — (fill coach + date)

The rule / what it is

RJ's own example, encoded: close the face → start line goes left (face is ~85% of start) — unless I shallow it out early, in which case the path goes more right, which changes what the closed face does to the curve.

Cause → effect

  • Close face, nothing else: start left; face-to-path opens closedmore draw/hook.
  • Close face + shallow early (path moves right / more in-to-out): start still ~face (slightly left), but face-to-path gap widens closed → bigger draw, and low point/AoA shift with the shallower path.

Cross-implications (what else moves)

  • Shallowing to move the path right also tends to move low point back / AoA up (watch fat/thin, hooks).
  • A closed face + righter path is the hook recipe if overdone.

Compensation cascade

  • Open the face → start right (direct, all else equal).
  • Push it too far right → the body senses the miss → flips/releases the hands to square it → face timing now variable, path swings left from the save, strike thins → the start line you were chasing gets less repeatable, not more.
  • Takeaway: change the face only within a range the body trusts, or pair it with a path change — don't force a number the hands will fight to undo.

Offsets (to hold a target outcome)

  • Hold a straight-ish start: if you close the face, you must accept a left-er start or open the path back (steeper) to keep face near target.
  • Hold the same curve: match path to face — close the face and move the path left by the same amount (face-to-path constant).

Source

Lesson concept — fill in which coach taught it + date so we can track which coaching held up.

Worked / hasn't (my verdict)

Date Tried Result (Trackman start/curve) Keep?

Links

  • ball-flight-laws (the anchors) · shallowing-methods (how the path moves right) · force version: force-to-ballflight.
Details & nuance

Worked examples

  • Your own example, encoded: close the face → start left; unless you shallow early → path right → bigger draw. (Log the Trackman start/curve deltas when you test it.)

Mechanism / why

  • Start ≈ face; close the face and the start goes with it. Shallowing to move the path right widens the face-to-path gap (more draw) and shifts low point/AoA — two things move at once.

Caveats & exceptions

  • The body fights a face you force: push it too far and the hands flip to square it → face timing variable, less repeatable. Change the face within a range the body trusts, or pair it with a path change.

Key quotes

  • (fill in the coach + date who taught this — that's how we'll see which coaching held up against your data.)

Ways to Shallow — methods & trade-offs

levergoal: curve, distance controlverdict: mixedaffects: path, AoA, face, low pointsrc: Lessons — multiple coaches (fill names

The rule / what it is

Several different moves all "shallow" the club (less steep, path more from the inside) — but each has different side effects elsewhere. Same outcome, different costs. Match what's worked vs hasn't for me.

The methods → what each drags with it

Method How it shallows Cross-implications (the cost) My verdict
Hands / wrists (lead-wrist flex, trail-wrist ext) re-routes the shaft early tends to shut the face → hooks; precise but timing-sensitive fill
Arms / forearm rotation (let arms drop, supinate) drops club behind hands can get stuck/under → blocks or flips fill
Trail shoulder / side-bend (drop trail shoulder, 2° tilt) tilts the swing plane risk early extension / hang-back → fat-thin, push fill
Lead wrist bow flattens + closes strong face-closing → hook bias fill
Force through the ground (forward pressure + positive line of pressure) the body shallows it from the ground up needs proper sequence or it becomes a slide; the S2M/MG way fill

Compensation cascade

  • Shallow via trail shoulder / side-bend → trail side hangs back → body stands up (early extension) to make room → two-way miss (block and hook).
  • Shallow via hands / lead-wrist → face shuts → brain adds a hold-off to stop the hook → blocks creep in.
  • Takeaway: every shallowing method creates its own save. Pick the one whose compensation you can live with — and confirm which it is on your data.

Offsets (to hold a target outcome)

  • Most shallowing moves open the AoA / move low point back → if so, play the ball slightly back to re-center strike.
  • Face-closing methods (hands, lead-wrist) need a path that matches or you hook it — see face-vs-start-line.

Source

Came from multiple coaches over the years — fill in who taught which method + date, so we can see which one actually held up under your own data (the whole point of owning the process).

Worked / hasn't (my verdict)

Date Method tried Result Keep?

Links

  • Ground method ties to line-of-pressure, lateral-force, center-of-mass-vs-pressure.
  • face-vs-start-line (path-right interaction) · ball-flight-laws.
  • Shauheen: the backswing forearm structure gates whether you can shallow at all → backswing-shaft-forearm; the hip/chest matchup that leaves you stuck → hips-spinning-open.
Details & nuance

Worked examples

  • (fill from your lessons — which coach taught which method, and what it did to your numbers.)

Mechanism / why

  • Several different moves all "shallow" the club (re-route the shaft from inside) — but the source of the shallow (hands vs arms vs shoulders vs ground) decides the side effect.
  • Shauheen's gate: even the right transition move can't shallow a club that's laid off at the top — fix the backswing first (backswing-shaft-forearm).

Caveats & exceptions

  • Over-shallowing is its own miss (your stuck/under-plane) — shallow is not a free good; you can have too much.
  • Every method creates a save somewhere; pick the compensation you can live with and confirm on data.

Key quotes

  • (add the coach quotes as you log lessons — this card is yours to populate.)

Force Levers → Ball Flight

levergoal: start line, curve, distanceverdict: untestedaffects: path, face, AoA, low point, speedsrc: Smart2Move + ball-flight laws (migrate

The rule / what it is

The force-plate levers mapped to club/ball outcomes — the bridge between the Force tab and ball flight. Each is a hypothesis to validate against your Trackman deltas (confidence rises once your own data confirms it). RH golfer.

Cause → effect (the matrix)

Lever ↑ Path Face-to-path AoA Low point Speed Offset to hold flight
Rotation (turn harder) ◄ left opens (fade bias) fwd + close face to match path
Forward shift (lateral) slight ◄ steeper fwd ball back / shallow to reset AoA
Vertical (jump) timing-dep timing-dep ++ reset launch via ball pos / spin loft
Trail heel/line ↑ (more +) ◄ left opens shallower + close face to match path

Cross-implications (what else moves)

  • "Turn harder" is the headline case: path left → fade bias unless you close the face to match — your own example lives in face-vs-start-line.
  • Forward shift is the low-point lever; vertical is the speed lever; both interact with strike.

Compensation cascade

  • Turn harder → path left. If the face doesn't keep up you start fading; the body may flip to hold the line → face timing variable. Pair the turn with a face/grip change instead of letting the hands save it.

Offsets (to hold a target outcome)

  • Hold the curve (default when changing a power lever): keep face-to-path constant — move the face to match any path change.
  • Hold the start line: keep the face near target; accept the curve change.

Source

Migrated from matchups.md (L1–L4) + ball-flight laws. Anchored on ball-flight-laws.

Worked / hasn't (my verdict)

Date Lever changed Trackman delta (path/face/AoA) Confirmed?

Links

  • Force cards: rotational-force, lateral-force, vertical-force-peak, line-of-pressure.
  • ball-flight-laws · face-vs-start-line · shallowing-methods.
Details & nuance

Worked examples

  • Turn harder → path left (the headline). Greg Rose's AP-couple version: lead pushing away from the ball is what lets you rotate without thrusting/early-extending — see anterior-posterior-forces.
  • (log your own lever→Trackman deltas here as you test.)

Mechanism / why

  • Force levers move the club delivery (path/face/AoA/low-point), which the ball-flight laws then turn into start/curve. Hold-the-curve = keep face-to-path constant.

Caveats & exceptions

  • These are hypotheses, not laws — confidence rises only when your Trackman confirms them. A lever's effect can differ for your body/pattern.
  • Default goal when changing a power lever is hold the curve, not chase a new shape.

Key quotes

  • Synthesis card (S2M force language + ball-flight laws) — no single source quote; validate empirically.

From your lessons — your swing tendencies (Shauheen)

Hips Spinning Open Too Fast → Stuck

relationshipgoal: curve, distance controlverdict: untestedaffects: path, low point, shaft planesrc: Shauheen Nakhjavani (51dgDbSqOVY)

The rule / what it is

"My hips spin open too fast" is usually a matchup problem, not a hip-speed problem. Shauheen: slowing the hips is rarely the best fix — the real issue is that the backswing turn and the downswing rotation (hips vs chest) don't match.

Coaching takes (by source)

Coach Position Conf
Shauheen (51dgDbSqOVY) Don't auto-slow the hips. Two patterns: (1) restricted backswing hip turn → hands stay shallow/in-front → fast downswing hips → hands kick out, shaft steep → over-the-top. Fix = bigger backswing turn (trail-leg extension) so hands get deeper and match the fast downswing. (2) chest can't keep up with fast hips → chest lags → club drops under plane → stuck, too in-to-out. Fix = speed the chest up to match the hips. high
(other coaches) add as they agree/conflict

Cause → effect

Hand path follows body rotation: more backswing turn → hands deeper/flatter; more downswing rotation → hands move out. Mismatch → steep + over-the-top (pattern 1) or under + stuck (pattern 2).

Compensation cascade

Pattern 2 (likely yours): hips fast → chest lags → hands/club drop under → stuck → you flip/save to square it → hooks or blocks. Slowing the hips "works" but caps speed; matching the chest keeps the speed and removes the stuck.

Offsets (to hold a target outcome)

Want to keep hip speed for power? Deepen the backswing turn and/or speed the chest — don't throttle the hips.

Source

Shauheen Nakhjavani — "Hips Spinning Open Too Fast" (51dgDbSqOVY).

Worked / hasn't (my verdict)

Date Tried Result (stuck? path? strike?) Keep?

Links

  • backswing-shaft-forearm, shallowing-methods; force side: rotational-force, kinetic-sequence.
Details & nuance

Worked examples

  • Shauheen's most-asked Q&A: a player trying so hard to slow the hips down. His read: the hips aren't the problem — the backswing turn doesn't match the downswing speed (51dgDbSqOVY).
  • Pattern 1 (restricted backswing turn): 15–25° hip turn → hands stay shallow/in-front → fast downswing hips → hands kick out, shaft steep → over-the-top.
  • Pattern 2 (chest lags — likely yours): decent backswing, but hips spin so fast the chest can't keep up → chest falls back → club drops under → stuck, too in-to-out.

Mechanism / why

  • Hand path follows body rotation: more backswing rotation → hands deeper/flatter; more downswing rotation → hands move out. A mismatch sends the hands the wrong place.
  • The chest is the big driver of hand path — if it lags the fast hips, the club gets dumped under.

Caveats & exceptions

  • Slowing the hips is rarely the best fix. For some players (who feel through the hands) it's fine — "not the only solution."
  • Pattern 1 vs Pattern 2 need opposite fixes (bigger backswing turn vs faster chest) — the plates/video tell you which.

Key quotes

  • "It's not that your hips are spinning open too fast — it's that your backswing's hip turn doesn't match the speed you're rotating in the downswing." — Shauheen (51dgDbSqOVY ~05:28)
  • "Rather than slowing down the hips, why don't you work on speeding up the chest?" — Shauheen (~08:32)

Backswing Forearm Rotation & Shaft (laid-off vs across-the-line)

levergoal: curveverdict: untestedaffects: shaft plane, pathsrc: Shauheen Nakhjavani (oBkFMpbareU)

The rule / what it is

Lead-forearm rotation in the backswing sets the shaft at the top and gates whether you can shallow in transition. Pronation (lead palm turning down) → laid off; supination (palm up) → across the line / steep/vertical.

Coaching takes (by source)

Coach Position Conf
Shauheen (oBkFMpbareU) Forearm = an elastic. Max out pronation going up (too laid off) → no room to shallow → the only move down is to rebound into supination → steepens the club → over-the-top, or a pivot save (stand up / hang back). Fix for laid-off: counter-roll — feel you supinate the lead forearm going up (palm toward sky), club more vertical at the top → now there's room to shallow via forearm rotation in transition. The backswing structure must allow the shallow. high
(other coaches)

Cause → effect

  • Too laid off at the top → forced steep / over-the-top coming down (no room to shallow).
  • Across the line / steep at the top → can be shallowed, but is its own miss.

Compensation cascade

Laid off → rebound supination on the way down → steep → body compensates (stand up / hang back / early extension) to avoid chunking → two-way miss. (Ties to your across-the-line + stuck tendencies.)

Offsets (to hold a target outcome)

Don't chase "shallow it on the way down" without fixing the top — a laid-off backswing makes shallowing nearly impossible.

Source

Shauheen Nakhjavani — "Forearm Rotation and Shaft Issues in the Backswing" (oBkFMpbareU).

Worked / hasn't (my verdict)

Date Tried Result Keep?

Links

  • shallowing-methods (the forearm method — this gates it), hips-spinning-open.
Details & nuance

Worked examples

  • Shauheen's student: neutral takeaway, then too much lead-forearm pronation late in the backswing → way laid off ("a very Ricky Fowler-type move"). Fix: drills counter-rolling (feel the lead forearm supinate, palm to sky) to get the club vertical at the top → now there's room to shallow (oBkFMpbareU).

Mechanism / why

  • The elastic: max out pronation going up and the only move down is to rebound into supination → that steepens the club. The backswing structure gates whether you can shallow at all.
  • Pronation (lead palm down) → laid off; supination (palm up) → across-the-line/steep.

Caveats & exceptions

  • It's not only the forearm — trail-arm internal/external rotation also drives the shaft; look at the whole match-up. Forearms roll in both directions throughout the swing, not just early.

Key quotes

  • "Too much pronation going to the top gives you absolutely no space to shallow the club after." — Shauheen (oBkFMpbareU ~02:49)
  • "A lot of golfers try to shallow on the way down, but their backswing structure isn't doing them any favors." — Shauheen (~05:07)

Active focuses, newest on top. Each ties a problem → the lever/concept I'm drilling → the intent → my practice data → what's actually happening. Settle each against the data, then mark it solved or adjust. (Force plates not in hand yet — data fields fill once capturing begins.)


FOCUS 1 · Restore solid contact (the comeback)


FOCUS 2 · (open a new block per lesson / experiment)

Practice sessions (from data/sessions.csv)

No sessions logged yet — fields fill once you start capturing (data/sessions.csv).

Measurements (from data/measurements.csv)

No measurements logged yet — fields fill once you start capturing (data/measurements.csv).

Your lab notebook. Each item is a place the sources differ — or a lever worth dialing — turned into an experiment. The rule: change one thing, capture solid vs mishit, pair with Trackman, find your truth. Overwrite the experts with your own data.

TEST 01 — Heel vs cuboid: where does trail pressure go?

TEST 02 — Lateral pressure vs mass: how much shift?

TEST 03 — Your vertical-force number

TEST 04 — Does swinging harder make you better?

TEST 05 — GRF timing: finish early?

TEST 06 — Line of pressure: your over-the-top tell

TEST 07 — Trail load: amount & timing

TEST 08 — Read both lenses: force vs 3D


Logging: every result goes in data/measurements.csv (tag solid Y/N) and the weekly journal's feel-vs-real table. A test isn't done until the number is written down.

Generated by Analysis Protocol/build_site.py from the markdown cards + CSV data. Thresholds are body-normalized starting points, not prescriptions — calibrate to your own solid-strike data.