To paraphrase the Bard: “To understand or not to understand,” that is the question.
In one of Pavel’s first books, he has a statement: “Understanding is a delaying tactic. The drowning person does not want to understand hydrodynamics; he/she just wants to swim.”
It is common for people to say that they want or need to understand something before they do it.
And when it comes to brain surgery and other complex tasks, I agree. But does it apply to training?
In his latest article and program, Fabio Zonin, StrongFirst Certified Master Instructor, lays out the Cruiser program he designed for his wife, who did not need or want to “understand” the program. She wanted to “swim” and do the program.
In answering a question about the article and program on the article page, Fabio responds: “Alice was looking for a “plug and play” plan that allows her to simply pick up the bells and do the work without needing to spend time setting up the rack, loading the bars, etc. She needs the ability to do her sessions whenever she has 30-45 minutes of spare time between her appointments and housewife commitments, without being tied to a set schedule…the kettlebells and a corner are always available. And, in the worst-case scenario, she can pick up the bells she needs and got to train in our living room or in the back yard of our house.”
But what about understanding the program? Why not both?
Enter Programming Demystified:
Fabio explains in the article: “The BTS-RND is the foundation for the Crusier and the Battleship plan. BTS, of course, stands for Built Strong and RND is an acronym used in computer science that stands for random.
Although it may seem that this strategy breaches any rule dictated by the logic of progression and simply assigns a series of random practices, this is not so. First, unlike most Western training strategies which comply with the principles of progressive overload, Built Strong and its father Plan Strong™ comply with the principles of variable overload. Second, rather than random, I would define the BTS-RND strategy as “random within railroad tracks.” While there is a random component, the way the grid is designed and the rules for applying the results of the die rolls ensure that the ongoing sessions comply with all the principles of the Plan Strong and Built Strong systems.
Of course, during Programming Demystified we will not limit ourselves to just sharing the grid, but will explain in detail how it is structured and teach participants how to create their own plan based on the target goal, volume, intensity, etc.
If you want to learn more about the Battleship plan, do not miss the upcoming seminar Programming Demystified, during which Pavel, Hector, and I will share this and countless other programming strategies to take your results and those of your students to the next level.”
Do the program (“plug and play”) and understand the program.
The best of both worlds.
While the live event is sold out, you can still attend Online.
