FYTT enables you to build up a library of the following reusable components:
Exercises
Blocks
Workouts
Progressions
Programs
As your library grows, you become more and more efficient, because you're creating less and less from scratch. (Although building from scratch in FYTT is fast too!)
Library location
If you have multiple teams, content can be created for the institution, as well as for individual teams.
Institutional content is available to all teams and coaches within the institution. This enables you to share a library of components that everyone can use to build their training instructions to help create a streamlined, unified performance operation.
Team content is only available within the context of the given team. This enables coaches to create content that is isolated to their individual teams when necessary.
Best practices
Most organizations opt to manage the majority their content at the institutional level. For larger performance teams, this does require some level of collaboration and consistency among staff. But if all team members can agree to a unified content management approach, a well managed institution library can greatly help with team efficiency.
Content types
Think of the various objects in FYTT as components or modules that you can mix and match in order to compose training instructions quickly. The smallest component is an exercise; exercises combine together to make blocks; workouts are combined together into workouts; workouts are combined together into programs; and ultimately, programs are combined together into plans.
Each component builds upon the last, but none of them are dependent on the other. You can build blocks, workouts, progressions, and programs completely from scratch. You only need to build something into your library if you want to reuse it again and again.
Exercises
Create a database of exercise metadata that helps with automation and individualization. This metadata includes info like written and video exercise instructions, as well as default and backup metric associations. You don't need to create an exercise in the database in order to use it in a block. The block builder allows you to write blocks free-form, and you only need to add exercises to the database if you want custom a video, description, or other metadata.
Blocks
A "blocks" is a single, modular part of a workout. For example, within a given workout, you might have a block called "Warmup," then a couple blocks named "Upper Body" and "Lower Body," then a block called "Cooldown." By building a library of your most used blocks, you can save time by being able to insert them as part of a workout.
Workouts
A "workouts" is a single bout of training composed of one or more blocks. You might generally think of it as a one or two hour training session where the athlete begins a workout with a warm-up, practices some aspect of training, then ends with a cool-down. Workouts are used in two places: within programs and on the calendar. Program workouts ultimately end up scheduled on the calendar at some point as a workout session with a start and stop time.
Progressions
The progressions feature is a powerful tool that enables you to quickly map out an isolated plan for adaptation within a program. For example, suppose a program has a track for "Upper Body" on Mon/Wed and a track for "Lower Body" on Tue/Thu. You can build a separate progression for each track within the program. The point of progressions is to make it easy to create and visualize a model for inducing a specific adaptation within the context of the broader program.
Programs
A "program" is a collection of training workout sessions organized within a finite timeline (usually a few weeks to a few months). This most often correlates with the familiar concept of a mesocycle, but you are by no means limited to that framework. Programs are very flexible and modular, so you can build anything from individual progressions to full macrocycles.