Banner
Incorporating the Power Dribble: Advanced
This is my site Written by Rick Torbett on July 3, 2009 – 12:11 AM

Q: We will primarily be using the 3 OUT formation, but we will incorporate others as season goes on. Can you give me some ideas on how I could incorporate the power dribble layer into 3 OUT 2 IN? Is it for only when bigs touch ball on perimeter? When one post gets the ball, we have a rule that the other goes to the top of the key and backscreens so we are essentially 4 OUT 1 IN on all post feeds. I guess I just need some ideas on how to incorporate power dribble.

A: I will use your post rule as one example of how to use the Power Dribble: When one post gets the ball and the other post sets a backscreen up-top, let’s pretend that both defenders play the cut off the backscreen and leave your post open at the top of the key. Your post with the ball passes to the other post at the top of the key. If your post was a good 3-point shooter, then this would be a good opportunity. But let’s assume not. The post at the top of the key can now Power Dribble toward either wing and initiate a pick and roll.

But let’s go further: If the Up-top-post-player Power Dribbles to the wing on the side where your low post player is located, then your low post can step out and set a screen on your other post who is rolling to the basket - a “screen the screener” action. On the other hand, if the Up-top-post-player Power Dribbles to the other wing (opposite your low post player), then when the pick and roll occurs, the opposite post player can set a backscreen for the other wing player who is filling the open spot at the top of the key.

This serves two purposes: it occupies two weak-side defenders who might otherwise be helping to stop the pick and roll AND it gives the wing player with the ball TWO options when coming off the Power Dribble Pick and Roll: (1) he has all the options from the pick and roll he’s engaged in and (2) he is coming off the Power Dribble facing the backscreening action at the top of the key.

Generally speaking, your post(s) will have to be on the perimeter with the ball in order to initiate the Power Dribble. So the question becomes: Can you find a way to use your posts that they occasionally (by accident or by design) find themselves on the perimeter with the ball? If your post(s) can step out of the posting area and set a backscreen or a flarescreen, then they have a chance to get the ball on the perimeter.

Picture 3 OUT 2 IN with both posts at the high post. Your point passes to the wing. We know that your point is going to basket cut, so why not have your closest high post step out and screen for the point as soon as the pass is made. If the guard is not open, then pass to the post (who is now on the perimeter). The other post can dive into the lane looking for a high-low post-to-post feed. If that’s not open, the post on the perimeter can now Power Dribble to the next perimeter player.

You might incorporate this “planned Power Dribble action” into your Quickhitters - stuff you use coming out of time-out or in a dead ball situation where you have time to call it. Here’s an example: Start with 3 OUT and 2 IN; your posts set double backscreens on the two wings; if the cutters are not open, then your point passes to the post who is most open; after the point basket cuts (assuming he’s not open), the post can now Power Dribble toward one of the perimeter players who have filled an open spot. If the Power Dribble pick and roll doesn’t give you anything, then nothing’s lost and your offensive action can continue with your post player now inside.

So, you either allow your posts the freedom to go inside and out and thus make the Power Dribble a possibility or you use some type of planned action, like a quickhitter, to get them on the perimeter with the ball.

Hope this helps.

Leave a Reply

After clicking “Submit Comment” you should notice your pending comment appear below the previous comments. All comments are reviewed prior to publication and could take up to 12 hours before becoming visible to the R&R community. Thanks for your comments.