BQ-301a · Module 3
Profile Discrepancy Diagnosis
3 min read
The most valuable diagnostic moment is when a profile does not match observed behavior. The person who scores high-S but behaves like a high-D in meetings. The person who scores high-I but is visibly uncomfortable in group settings. The discrepancy is not an error — it is the most interesting data point in the assessment. Every discrepancy has a cause, and finding the cause produces deeper insight than the profile itself.
- Cause 1: Performance Layer The person has learned to perform a different profile at work. Common in organizations that reward specific behavioral styles. A high-S in an all-D team learns to present as high-D to survive. The tell: the performance cracks under fatigue, surprise, or sustained pressure. The natural profile reasserts.
- Cause 2: Context Mismatch The assessment was taken in a different context than the observed behavior. A person who took the assessment during a calm period but is observed during a crisis will show a discrepancy because the stress-shift profile is active. Retesting in the current context resolves this.
- Cause 3: Developmental Transition The person is genuinely in the process of behavioral development. A high-S who has been deliberately building dominance skills for two years may assess as S-primary but behave as D-secondary. The transition is real but incomplete — the assessment captures the core tendency while behavior reflects the developing capability.
Do This
- Treat discrepancies as diagnostic opportunities — the gap between score and behavior is rich data
- Investigate the cause before adjusting the profile — performance layers, context mismatches, and developmental transitions require different responses
- Document discrepancies in your assessment notes — they are the most valuable observations you will make
Avoid This
- Dismiss the assessment when behavior contradicts it — the contradiction is the finding
- Force-fit observations to the profile — "she must be doing high-D things because she scored high-D"
- Assume discrepancies mean the instrument failed — they usually mean the context shifted or a performance layer is active