"Ranked 30th but going 55th" sounds like a bargain. It can be. It can also tempt you to wait one pick too long. A ranking and average draft position answer different questions, and neither can promise who will still be available in your room.
Josh Lloyd draws this distinction in his fantasy-season guide: projections estimate performance, while ADP describes where players have been selected. Your draft decision needs both, plus the settings of the league you are actually drafting.
Three numbers, three different jobs
A projection estimates a player's stats, minutes, and games for the coming season. A ranking orders those projections under a scoring method or category model. ADP summarizes previous draft selections on a platform. It describes the market. Your next draft room may behave differently.
Before comparing rank with ADP, align the formats. A points-league rank should use your league's weights, including any shooting penalties and bonuses. A nine-category rank needs the category set, turnovers treatment, and a stated method for percentage impact. Check whether the list values projected totals or per-game production. Our scoring guide shows why even two published points defaults can produce different orders from the same NBA stats.
Then check the ADP source and date. Platform draft rooms, auto-pick behavior, and league formats can produce different markets. ADP is especially blunt when your next pick is many selections away: an average says little about the spread around it.
When you are on the clock
Put your candidates in tiers rather than treating every rank as a hard boundary. Ask how much value you lose if you miss the target, what alternatives are likely to be there later, and whether the player fits a starting slot. A small projection gap often does not justify ignoring a player you strongly expect to disappear before your next pick.
Also look at the rest of the roster. In a category league, your team's category shape may move a player up or down. In a points league, projected games, position eligibility, and the available replacement at that position can change the pick. Use the public list to narrow choices, then judge the players left on your draft board.
A pick-35 decision
Consider this illustrative draft-room scenario. You pick at 35 and again at 59. Your league-adjusted board has a player at 30; his platform ADP is 55. ADP suggests he often lasts past 35, but it cannot tell you whether he survives another 23 selections.
If your next tier has several comparable players, you might take a stronger value now and accept the chance that your target is gone. If he is the only player in his tier for your build, taking him at 35 may be reasonable despite an ADP of 55. Think about what you lose if he is gone at 59. A pick that beats ADP on the receipt can still leave you with a weaker roster.
There is no universal number of picks you should reach or wait. The answer changes when draft behavior differs from the ADP pool, the available alternatives shrink, or the player’s projection changes.
A draft-room checklist
- Confirm that your ranking matches the league's scoring, roster slots, and format.
- Read the projected stats and games behind the rank; check the update date.
- Label the platform and date of the ADP you are using.
- Find your next pick and the players you would take if the target is gone.
- Choose the pick that leaves you with the best realistic roster, not the prettiest rank-versus-ADP gap.
About the example: The distinction between expected value and draft cost is drawn from Josh Lloyd's September 2026 episode. The pick-35 scenario is illustrative; no live ADP or player rank is asserted here. Recheck platform ADP, player availability, and StatDunk's projection date before a 2026-27 draft. Reviewed September 29, 2026.