Seeing a signal is the start. Choosing the correct response is the next challenge.
Loading dimension detail data…
UNDERSTAND YOUR RESULTS
Here, decision performance means selecting responses under task rules and conflicting signals. It is not a measure of real-life judgment, personality or career ability. Read response speed alongside accuracy and the specific rule.
A simple reaction task observes response initiation after a cue. Choice tasks can also require stimulus discrimination or a specified rule. Different demands mean their score difference is not a direct ranking of ability.
Stroop records can involve correct-response times by condition and differences between conditions. A historical single number needs an identified meaning; do not automatically treat it as a full choice-response time.
Dynamic reaction tasks include stages with different demands. Review stage-specific responses and hit performance before considering a summary. Arbitrarily combining stages does not create a global decision rank or establish real-life decision ability.
| Observation | Question it can address | What it cannot establish alone |
|---|---|---|
| Accuracy | How many responses followed the rule | Real-life judgment or fixed personality |
| Correct-response time | Time needed to respond under the specified rule | A direct ability ranking across tasks |
| Condition or stage differences | How performance changes with task demands | A calibrated composite decision percentile |
The demands differ. A choice task can add stimulus discrimination or rule selection. Two times alone cannot precisely separate every processing stage or establish real-life decision quality.
Speed alone cannot answer that. Compare accuracy and correct-response time under matching rules, and consider strategy changes. A single speed change does not establish improvement.
Not directly. Their metrics, protocols and stages differ. A composite rank needs a defined combination method and an applicable reference sample, not a simple average of different numbers.
Not by itself. It describes particular task observations, not a career assessment or personality diagnosis, and does not guarantee decisions in complex real-life situations.
Start with recorded scores. Historical coverage and comparable results may count different records.
Milliseconds, levels and item counts come from test records saved in this browser. Latest and personal-best scores are different observations, not fixed abilities.
Current reference scales use provisional project rules, not validated population norms. Estimated Top does not describe an observed population proportion; combining reference scores does not establish an overall population percentile.
The ordinary Profile overview and dimension details use the same production record-eligibility rules. Historical records remain visible, but records without comparable conditions do not contribute to reference scores. Saved history is not automatically a valid same-condition result. Distinguish all linked tests from the core tests contributing to a dimension.
Prefer the same task, mode, version and input method. Similar dates or scores alone cannot establish comparability when these conditions were not saved.
These notes do not read personal scores. Public HTML and page structured data contain no personal records. Sharing the page URL does not transfer your locally saved results.
Keep task conditions and dynamic-reaction stages separate rather than averaging unlike metrics into a global decision percentile.
Notes reviewed: 2026-10-21 · public-method-v1 (notes version, not a calculation model version)