01
It reduces noise before scoring starts
Not every raw stat deserves equal weight on its own. This layer helps organize production into a more stable structure so the later BIQ model is not reacting to messy, isolated, or misleading values.
Interactive Model Walkthrough
THE BIQ
STACK IN
MOTION.
Each card represents one layer of BIQ, from the data foundation to the scoring model, interpretation, and final experience.
Manual Control
Use the on-screen arrows or your keyboard left and right arrow keys to move through the stack.
Layer 01Raw inputs, made usable
Data Foundation
BIQ starts by organizing NBA player data into a cleaner structure so comparisons are more stable, readable, and actually useful.
01
Normalizes scattered stats into one analytical base
02
Supports dashboards, rankings, and comparison views
03
Creates cleaner inputs for the BIQ model
Layer 02Custom scoring logic
BIQ Model
The core score combines burden, creation, efficiency, and impact into one framework meant to reflect usefulness more clearly than raw totals.
01
Balances volume with efficiency
02
Rewards creation and offensive pressure
03
Keeps the final score interpretable
Layer 03Rankings with reasoning
Insight Layer
The goal is not just to output a number, but to explain why a player lands where they do through supporting metrics and context.
01
Shows the signals behind the BIQ score
02
Makes comparisons easier to understand
03
Turns ranking into explanation
Layer 04Analytics UX that stays readable
Experience Design
The interface is designed to feel sharp and analytical without becoming dense, cluttered, or spreadsheet-heavy.
01
Editorial hierarchy over dashboard overload
02
Readable structure and visual grouping
03
Product thinking applied to sports analytics
Layer 05Sharper reads on player value
Outcome
BIQ becomes more than a stat page: it is a system for reading player value through burden, impact, and offensive usefulness.
01
Better bridge between numbers and interpretation
02
More thoughtful player evaluation flow
03
Model and interface reinforce each other
Active Layer 01
Data Foundation
What this layer is doing
Before the BIQ score can mean anything, the data has to be shaped into something consistent and comparable. NBA stats live across many categories, and players operate in very different roles, tempos, and usage environments. This layer is about building a foundation that the rest of the product can trust.
02
It creates a common frame for comparison
A high-usage initiator, a secondary creator, and an efficient finisher should not be read exactly the same way. The data layer helps group and present player information so comparison is fairer and more interpretable.
03
It supports the entire product, not just the score
This same structure powers rankings, player pages, and comparison tools. That matters because BIQ is meant to be more than a number — it is a system for exploring why value shows up the way it does.
Key Takeaway
This layer turns raw NBA information into something structured enough to support real evaluation instead of stat grazing.
What The Model Is Trying To Measure
Engine
Usage + pressure
Measures how much offensive work a player can carry without the entire possession collapsing.
Creation
Advantage generation
Captures who bends the defense, creates clean looks, and turns possessions into real scoring chances.
Impact
Winning signal
Looks beyond raw totals to ask how strongly a player’s possessions translate to team value.
What Came Out Of It
01
A scoring model built to reward useful offensive burden, not just volume.
02
Player pages that explain why someone grades highly instead of only displaying a rank.
03
A cleaner analytics experience that feels more editorial than spreadsheet-heavy.
Why This Page Exists
BIQ is meant to feel like both a product and a point of view. This page gives the model more narrative context: what problem it is solving, how the layers connect, and how the interface supports the scoring logic rather than hiding it.
Portfolio Context
Product design, analytics thinking, interface systems, and full-stack implementation all meet here.