Β 

Β 

Module 1Β 

Β 

Β 

Β 

OLDBULL Performance  Β·  Building a Performance Operating System  Β·  Module 1 of 4

Know
The Room

Audit your people, your knowledge gaps, and your technology before you build anything else. The foundation every high-performance department skips β€” and pays for later.

Format1 Webinar Β· 3 Labs Β· 1 Podcast
Module1 of 4
Est. time~4 hours
M1 β€” Know the Room
β†’
M2 β€” From Noise to Signal
β†’
M3 β€” Control the Room
β†’
M4 β€” Information to Action

Most departments don't fail because of bad technology. They fail because of the people operating it β€” and the leader who never looked clearly at either.

1Webinar
3Labs
1Podcast
6Outcomes
30+Years behind the frameworks

The problem

Four failure patterns
every department repeats

No shared language

Coaches, physios, and S&C staff argue about exercises instead of outcomes. Means and modality are the same word to them.

Tech before discipline

Dashboards bought before procedures exist. Data collected before anyone knows what a real change looks like.

Invisible handbrakes

One staff member who won't learn, won't shift, and won't leave β€” and the leader hasn't named it yet.

Noise called insight

Numbers reported without reliability evidence. Leaders can't defend the call. Athletes pay the price.

What's inside Module 1

One webinar. Three labs.
One podcast.

Webinar Β· 60 min
From Milo to Machine Learning: What's Changed?
  • Knowledge–Application framework: Handbrake / Pawn / Practitioner / Operator
  • Knowledge–Behaviour framework: Misaligned / Coasting / Catalyst / Beacon
  • Why people determine the ceiling on every tech investment
  • Rogers Innovation Adoption Curve applied to your department
  • Live Q&A: what's blocking your environment right now
Labs Β· Γ—3 micro-videos
Building, Auditing & Checking Your Reality
  • Lab 1a β€” Building a common language: means vs modality and the CMΒ² model
  • Lab 1b β€” People and effective ops audit: know yourself, know your people
  • Lab 1c β€” Tech stack reality check: what you have and whether you can trust it
Podcast Β· 20 min
The False Promise of Technology Without Discipline
  • Protocol drift β€” when the test name stays but the test changes
  • Maths-free interpretation β€” declaring change you can't defend
  • Communication chaos β€” dashboards without decisions
  • Three rules: standardise before you scale, define real change, make decisions the product

Core framework 1

CMΒ² Model

Control Β· Movement Β· Capacity Β· Maximum. A shared progression map so every staff member can locate any athlete in the system β€” without a 15-minute explanation each time.

  • Control β€” single joints, early rehab, low training age
  • Movement β€” linked patterns, viable whole-system function
  • Capacity β€” volume, tolerance, robustness
  • Maximum β€” peak intensity, performance push

Core framework 2

K–B Matrix

Knowledge Γ— Behaviour. Map every staff member across two axes and make honest decisions about who needs development, who needs responsibility, and who needs to move on.

Knowledge axis

Handbrake β†’ Pawn β†’ Practitioner β†’ Operator

Behaviour axis

Misaligned β†’ Coaster β†’ Catalyst β†’ Beacon

Outcomes

What you walk
out with

Not theory. Actual deliverables you can use in your department the week you complete the module.

01

A shared framework (CMΒ²) your whole department can use to locate any athlete in the system β€” without lengthy explanation

02

An honest knowledge–behaviour map of yourself and every key staff member around you

03

A written tech stack inventory β€” what you have, what it truly measures, and whether you can trust the numbers

04

One procedure document for your highest-priority tool β€” the starting point for repeatable, trustable testing

05

Clarity on who needs development and who needs a difficult conversation β€” with the language to have it

06

A decision standard applied to your actual environment: if you can't repeat it, you can't learn from it

Who this is for

Mid-career practitioners
ready to be honest

S&C coaches stepping into leadership and inheriting a department they didn't build

HPMs resetting a performance department that's producing noise, not decisions

Sport scientists drowning in dashboards but unable to defend a call under pressure

Physios navigating the S&C interface who need a shared language that holds up

Anyone who has bought expensive technology and received expensive noise in return

Leaders who know something's off in their department but haven't been able to name it

Start here

Know the Room.
Then build the system.

Module 1 of 4. The first step in Building a Performance Operating System β€” developed by Jason Weber from 30 years at the elite end of sport.

Also in this course M2 β€” From Noise to Signal M3 β€” Control the Room M4 β€” Information to Action

Up next in the course

Module 2 β€” From Noise to Signal

Audit your technology stack, establish what each tool truly measures, and build the procedures that separate real change from random variation.

β†’
OLDBULL Performance Building a Performance Operating System Β· Module 1 Β· Know the Room Β· Β© OLDBULL Performance 2026

Get Early Access

If you want to be notified when courses open - and receive a free copy ofΒ Rethinking Athlete Monitoring.


Sign Me Up

Start with the conversations

Explore ideas through the Two Coaches and a Coffee, whereΒ we talk openly about the realities of high-performance sport, leadership, and decision-making.

Listen to Podcast