Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the woocommerce domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /var/www/wp-includes/functions.php on line 6114

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the antispam-bee domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /var/www/wp-includes/functions.php on line 6114

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the jetpack domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /var/www/wp-includes/functions.php on line 6114

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the wpforms-lite domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /var/www/wp-includes/functions.php on line 6114

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the responsive-addons domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /var/www/wp-includes/functions.php on line 6114

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the wp-smushit domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /var/www/wp-includes/functions.php on line 6114

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the responsive-addons-pro domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /var/www/wp-includes/functions.php on line 6114

Warning: Cannot modify header information - headers already sent by (output started at /var/www/wp-includes/functions.php:6114) in /var/www/wp-includes/rest-api/class-wp-rest-server.php on line 1893

Warning: Cannot modify header information - headers already sent by (output started at /var/www/wp-includes/functions.php:6114) in /var/www/wp-includes/rest-api/class-wp-rest-server.php on line 1893

Warning: Cannot modify header information - headers already sent by (output started at /var/www/wp-includes/functions.php:6114) in /var/www/wp-includes/rest-api/class-wp-rest-server.php on line 1893

Warning: Cannot modify header information - headers already sent by (output started at /var/www/wp-includes/functions.php:6114) in /var/www/wp-includes/rest-api/class-wp-rest-server.php on line 1893

Warning: Cannot modify header information - headers already sent by (output started at /var/www/wp-includes/functions.php:6114) in /var/www/wp-includes/rest-api/class-wp-rest-server.php on line 1893

Warning: Cannot modify header information - headers already sent by (output started at /var/www/wp-includes/functions.php:6114) in /var/www/wp-includes/rest-api/class-wp-rest-server.php on line 1893

Warning: Cannot modify header information - headers already sent by (output started at /var/www/wp-includes/functions.php:6114) in /var/www/wp-includes/rest-api/class-wp-rest-server.php on line 1893

Warning: Cannot modify header information - headers already sent by (output started at /var/www/wp-includes/functions.php:6114) in /var/www/wp-includes/rest-api/class-wp-rest-server.php on line 1893
{"id":3622,"date":"2013-10-09T22:28:12","date_gmt":"2013-10-09T12:28:12","guid":{"rendered":"https:\/\/functionalbasketballcoaching.com\/?p=3622"},"modified":"2013-11-09T14:11:31","modified_gmt":"2013-11-09T04:11:31","slug":"high-post-offense-stack-high","status":"publish","type":"post","link":"https:\/\/functionalbasketballcoaching.com\/high-post-offense-stack-high\/","title":{"rendered":"High Post Offense: Stack High"},"content":{"rendered":"

The High Post Offense<\/b> provides a valuable opportunities for teams to start by drawing the opposition\u2019s defence away from the basket. The High Post Offense Stack High Play looks to overload the Point Position on the floor by bringing an extra player to this High Post position. This in turn creates additional space and opportunities for players to move on the floor.<\/p>\n

 <\/p>\n

A real strength of the High Post Offense’s Stack High Play is that the positioning of the defence is moved well away from the basket. This sees the defenders who are off the ball having to work that little bit harder to cover the help positions especially from two and three passes adrift from the ball.<\/p>\n

\"High
High Post Offense: Stack High Diagram 1<\/figcaption><\/figure>\n

This High Post Offense starts will all the offensive players at or above the foul line.<\/p>\n

 <\/p>\n

Five (5) and Four (4) set-up as a stack at the top of the keyway<\/a> in the high post position.<\/p>\n

 <\/p>\n

One (1) pauses with the ball well above the three-point line<\/a> and this action triggers both wing players (Two and Three) to exchange positions on long cuts through the keyway.<\/p>\n

 <\/p>\n

This action can feature one player screening for the other or just a straight exchange action.<\/p>\n

\"High
High Post Offense: Stack High Diagram 2<\/figcaption><\/figure>\n

One (1) initiates a pass to either wing.<\/p>\n

 <\/p>\n

The top player in the stack (Five) lifts to screen one side of the split line and the bottom player in the stack (Four) screens the other. This will effectively create a staggered screen.<\/p>\n

 <\/p>\n

As the cutter (One) passes the shoulders of the first screener (Five) this player now lifts to fill the point position again in the High Post Offense.<\/p>\n

 <\/p>\n

The cut made by One (1) is very long and so if a strong cutting position is established then a very big advantage can be created.<\/p>\n

 <\/p>\n

The cut by One (1) can be to either side of the double screen. The important part is the for the offensive player to read what the defender is doing and to try and exploit an advantage from this situation.<\/p>\n

 <\/p>\n

Scoring Option:<\/b><\/p>\n

 <\/p>\n