Sources: 2026-09 / week-2
Claim ledger for "A Low Score Is Not a Weak Leader."
| Claim (as written) | Source | Link | Status |
|---|---|---|---|
| The Agile Neuro-Index reports a fit against a chosen change, not a grade against other leaders; a profile places a leader in one of three zones (stable, adaptive, agile) read as fits, not a ranking; a low reading is a mismatch with the change, not a defect. | Vanaya NeuroTech, Partner Certification Module 01, Neurometric Essentials v1.0 (three agility zones read as fits, not a ranking) | Internal document | internal |
| Instruments that share a method (such as self-report perception) share its blind spot, so agreement among them confirms the perceived state and does not reach the cause; a perception survey cannot read an individual's capacity against a specific demand. | Podsakoff, MacKenzie, Lee & Podsakoff, "Common Method Biases in Behavioral Research," Journal of Applied Psychology 88(5), 2003 | https://experts.arizona.edu/en/publications/common-method-biases-in-behavioral-research-a-critical-review-of-/ | verified |
| A change makes a specific demand on the capacity for novel, uncertain work, and leaders differ in that capacity, so the same change can fit one leader and not another. | Fluid vs crystallized ability (individual differences in novel-problem capacity), extending week-1's citation | https://www.sciencedirect.com/science/article/pii/S0749596X25000415 | verified |
Handling notes
- The fit-not-grade reading is the module's, and it is the load-bearing claim. The
three zones read as fits and not a ranking come straight from Module 01, logged
internal. The whole article is built to keep this from tipping into a ranking, per the guardrail's Positioning section and the "a diagnostic result is a fit, never a grade" house rule. - No prediction claim. The article never says the Agile Neuro-Index predicts who will succeed. "Agile Neuro-Index predicts job performance" is a forbidden claim. The reading is framed throughout as a present fit against a chosen change, a decision input, not a forecast of an outcome.
- Villain control on the survey point. Perception instruments are treated as valid and precise about what they read. The gap is located as a structural boundary of the perception method, not a defect, and no instrument or provider is named. This matches August week 4's handling of the same source.
- Zones described without grading. The three zones are named and given a plain, non-hierarchical gloss (hold a settled system, adjust within a known frame, work best in flux). No zone is defined as better, and the article states explicitly that an agile profile can be the wrong call for a stable mandate.
Blade discipline
- Week 2 lands the reading as a present fit. It does not say the fit can be developed; that is week 3, and the close poses the "is that the end of it" question without answering it. The whole force of week 3 depends on week 2 landing the mismatch as an honest present reading.
- The common-method source (Podsakoff) is shared with August week 4, which owns the organizational-diagnostic version of the point. Here it is used only for the narrower "a perception survey cannot read an individual's fit" contrast, so the two do not blur.
Reused from August
- Podsakoff (common-method) verified in August week 4. Fluid-vs-crystallized source verified in August week 2 and week-1 of this month; used here only to support that leaders differ in the capacity a change demands, which is why fit varies. Both carry their August wording.