What the instrument is, and what it is not yet

Current validation status

This instrument has not undergone formal psychometric validation. It is not a validated psychometric instrument, a clinical assessment, or a performance measure. Treat scores as a structured conversation input, not a measurement of individuals.

Pilot v0.1 has not completed psychometric validation. We have not established test-retest reliability, factor structure, or predictive validity at the standard required to call it a validated psychometric instrument. We are transparent about this status with every organization that uses it, and it is not to be represented otherwise in any customer-facing or internal material.

Binding Constraint: the primary interpretation

The core output of a diagnostic cycle is the Binding Constraint — the single condition, among the nine, that the evidence indicates is most limiting the team right now. This is deliberately not an average productivity score. Averaging across nine conditions would hide the one condition that actually matters for action, and BrainEng does not compute or present such an average as a headline figure.

The Binding Constraint is selected using condition means, dispersion (how divided the team's experience is), and the gap between leader and team perception, all defined in a versioned scoring configuration so that results stay interpretable over time. It is a prioritization signal for where to focus the next six-week experiment, not a certified measurement of organizational health.

Team Flow Propensity is a separate, exploratory construct

Some reports surface a construct we call Team Flow Propensity. This is exploratory and distinct from the Binding Constraint. It must never be described as a probability, a prediction, or a validated predictor of performance or outcomes. It is one additional lens for a team's own conversation, not a scored forecast.

What we do not claim

• We do not claim a validated return on investment or percentage of capacity recovered.
• We do not claim a guaranteed time to resolve a constraint. Six weeks is the design of the experiment cycle, not a guarantee of resolution.
• We do not collect passive telemetry, load monitoring, or any form of continuous behavioral surveillance.
• We do not produce individual performance rankings or automated classifications of people.

Ongoing work

As more organizations complete cycles, we intend to study reliability and construct validity properly, and we will update this page and the instrument version when that work changes what can be claimed.