top of page

Outlining My Scouting Skills Progression | Learning to Eventually Stat Everything

Sep 3, 2023
6 min read

tl:dr

  • I outline my scouting skills progression so I can eventually stat everything

  • Fully grading the defence is the first thing to learn

  • Coding subzones is the next thing to learn

  • Fully grading the block and setting is the last thing to learn

Introduction

I reflected in my performance analysis reflection blog back in May 2023 that I wanted to start statting the grade quality of the sets using Joe Trinsey’s (former USA scout) definitions of a good set (E#), set too far off (E+), set too far in (E!), set too wide (E-), set too tight (E/) and setting error (E=) (see link for more info).  This would give me the first chance to objectively analyse the setting performance of the setter.  I later thought I should really learn to fully grade the defence first since defence is the third most critical technical skill related to success in volleyball (see link).  

These thoughts led me to think about how I should really improve my scouting skills in a systematic way.  I should identify the list of things I want to code and then prioritise them, in relation to what I should learn first, according to their importance.  This blog post is about outlining my scouting skill progression so I can eventually stat everything.

Current Scouting Level

Before we can stat everything, we need to assess what our current scouting level is.  Below is a table showing my current scouting level.  As a reminder, there are seven technical skills that can be coded in DataVolley (serve, pass, set, attack, block, dig, free ball).  Each technical skill can be graded on a six-point scale.  You normally start with partial grades of point (#), in-play/ continuation (+), and error (=).  You then progress to full grades of best (#), good (+), medium (!), poor (-), worse (/), and worst (=).  You can also add zones (1-9) to those codes so you can do analysis such as attack and serve directions.  You can further divide the nine zones into subzones (A-D).  The other things you can add are extended code details. 

I’ve never laid out my scouting skill level in this way before.  It is interesting to see because I get to see what holes I have in my scouting skills.  It also helps me list what I need to learn and I can prioritise what I need to learn first.  

Things Currently Implementing

These are small changes I have started to implement.  You may have noticed that I have already written about some of these things already.  

Fully Code the Serve TechniqueI previously coded jump top-spin serves as Quick (Q) and all other serves (usually jump float and standing float serves) as High (H).  I will now code standing float, jump float, jump top-spin and other serves (e.g. standing top-spin, hybrid, side-arm) as Tense (T), High (H), Quick (Q) and Fast (N) serves, respectively.  You can read about it more on this link.  

Reclassifying the Shanked Pass as R/Shanked passes that the team has to chase down but are kept in play are graded the same way as poor passes that are still playable/ “set-able” (both R-).  However, the two types of passes are clearly not the same in terms of siding out.  I decided those shanked passes will now be coded the same as overpasses (R/) since the sideout % will both be similar (i.e. very low).  This should help me understand who is passing better thus I can make better decisions to enhance the team’s performance because of it.  You can read about it more on this link.  

Coding Missed Cover DigsI can’t calculate a Spike Cover Dig % as I don’t code missed cover digs.  So after a block kill, I will now code spike cover errors by coding it as D= but then using the Extended Codes (“W” button in my case) and pressing the “C” button for the Spike Cover option.  I will code spike cover digs as D! (see below to read more) so I can calculate a Spike Cover Dig %.

Coding Free Ball DigsI currently code all digs under the Dig (D) code.  The dig could be after a spike, spike cover, after a block, and after an opposition free ball.  This is not ideal because a player or team could have a higher Dig % simply because they made more free ball dig attempts.  

I have already described how I will differentiate the cover digs (see above).  The way I will differentiate free ball digs is to use the D code as normal but open up the Extended Codes window (“W” button in my case) and then press the “E” button for the Emergency option.  Emergency doesn’t mean Free Ball Dig but I can attach any meaning to it as long as it is consistent within myself.  It takes two extra buttons to code this way but since it is a free ball dig, I should have more time to type those two buttons.  With this, I can fully grade the free ball dig, like I would with the passing grades.  Using compound codes after a free ball (F) attempt and overdig (D/) will help with the coding efficiency.  

Coding Poor Sets as E/Grading the set is the very last thing to do.  However, I can start coding the poor sets that are unhittable as E/ rather than E-.  I may or may not follow Joe Trinsey’s way (see introduction) but since E/ is the second lowest grade (E= is a setting error), I can’t see myself changing that.  

Not Coding Second Ball Touches as Setting Attempts After a Shanked Pass or DigWhen I was learning to code setting attempts, I would just code every second ball touch as a setting attempt.  This could even be after a shanked pass (R/) or dig (D/) where the setter, or another player, is chasing down the ball just to keep it in play.  I wanted every touch accounted for and since I started coding this way, I wanted to be consistent throughout the season.  However, the downside is those “setting attempts” dirtied the setting stats.  A setter could have slightly worse setting stats if they kept more balls in play after a shanked pass or dig.  So now I won’t stat anything when a player is simply trying to keep a ball in play.  

First Thing to Implement

I still think fully grading the defence is the first thing to implement.  Defence is probably the third most important performance indicator related to success in volleyball (see link).  If we want to improve the level of defence analysis then we need to fully grade the defence performance.

Fully Grading the DefenceAs I said in the introduction, I essentially grade the defence as continuation or error.  After some research, I decided to grade the defence as below.  It is essentially grading the defence like passing except the perfect pass (R#) and positive pass (R+), i.e. middle player is available to attack, are combined together as the D# grade.  The spare medium grade (D!) is used for spike cover digs.  You can read about it on this link.  

Next Thing to Implement

Coding SubzonesThe volleyball court is divided into 9 zones (1-9) and each zone is divided into four subzones (A-D) (see below).  Coding subzones is really the next big thing to learn, after learning to fully grade the defence.  This will be more useful as you can create better heatmaps with 36 total subzones rather than 9 zones.  It would also cover a lot of holes in my current scouting level by learning one thing.  

DataVolley Zones (1-9) and Subzones (A-D)

Things to Learn Last

Fully Grading the Block Five of the grades are in use already: Block Kill (B#), Block Touch (B+), Rebounded Block (B!), Tooled Block (B/), and Block Error (B=).  I guess I only need to differentiate whether the block touch was positive (B+) or negative (B-).  How that’s defined may not be as easy as you think.  I also want to know how the pros do it, especially if they code whether a player makes a block attempt but does not touch the attacked ball.  

Fully Grading the Setting and Coding Setting ZonesThis will be the last thing to learn.  I will probably do another deep dive into what can be done and how the pros do it.  

Final Thoughts

It is really great to have an outline of what I am going to learn next in terms of what to scout.  However, since I dropped many of my teams for the upcoming 2023/24 season, due to ince I dropped many of my teams for the upcoming 2023/24 season, due to burnout and focusing on becoming a and focusing on becoming a Data Analyst, I won’t be statting that many matches so progression may be slow.  I will just focus on learning to fully grading the defence this season and go from there.  , I won’t be statting that many matches so progression may be slow.  I will just focus on learning to fully grading the defence this season and go from there.  

 
 
 

Comments


bottom of page