FYTT enables you to build up a database of the following reusable components:
Exercises
Workouts
Sessions
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!)
Institution and team libraries
Content can be created at the institution level, as well as at the team level.
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.
Institution library
Each institution maintains a library of exercises, workouts, sessions, progressions, and programs that are available for use by all teams within the institution. This enables you to prescribe training across your various teams from a common library of content.
Institution-level content is created and managed from the institution's dashboard:
Team library
Teams can enable the "private database" option to maintain a team-specific library of programs, progressions, sessions, workouts, and exercises.
Team programs
Every team has its own library of programs, regardless of whether the private database setting is on or off. Team programs are accessed from the team's primary navigation menu.
To enable a team's private database, navigate to the team's dashboard, click settings, then turn on the private database option:
With this option enabled, the team still has access to all the institution-level data, but it also has the ability to create its own data that are only available within that team's context.
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 your masterpiece. The smallest component is an exercise; exercises combine together to make workouts; workouts are combined together into sessions; sessions are combined together into programs; and programs are combined together into plans.
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 workout. The workout builder allows you to write workouts free-form, and you only need to add exercises to the database if you want custom a video, description, or other metadata.
Workouts
A "workout" is a single, modular part of a session. For example, within a given session, you might have a workout called "Warmup," then a couple workouts named "Upper Body" and "Lower Body," then a workout called "Cooldown." By building a library of your most used workouts, you can save time by being able to insert them as part of a session.
Sessions
A "session" is a single bout of training composed of one or more workouts. You might generally think of it as a one or two hour training block where the athlete begins a session with a warm-up, practices some aspect of training, then ends with a cool-down. Sessions are used in two places: within programs and on the calendar. Program sessions ultimately end up scheduled on the calendar at some point as a training block 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 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.