Method
A closed loop, run every six weeks
BrainEng is a disciplined cycle: find the one condition limiting a team, design a focused experiment against it, and review the evidence before choosing what to engineer next.
The loop is deliberately narrow. Instead of tracking dozens of metrics at once, each cycle commits a team to one binding constraint and one intervention, run as a time-boxed experiment.
1. Diagnose
Every member of a team, plus its leader, completes the nine-condition diagnostic. Responses are collected privately and scored on the server.
2. Prioritize
The scoring engine identifies the single binding constraint for the team — the condition most limiting progress right now — rather than producing an average score across everything.
3. Engineer
The team and its leader design one focused intervention addressed directly at the binding constraint, using the Intervention Studio.
4. Run a six-week experiment
The intervention runs as a bounded, six-week engineering experiment. Six weeks is the design of the experiment cycle — it is not a guarantee that the constraint will be resolved in that window.
5. Prove
At the end of the cycle, the team reviews what evidence was actually gathered against the original constraint: what moved, what did not, and what should happen next.
6. Repeat
The team re-runs the diagnostic, and the loop selects the next binding constraint. Capacity engineering is a standing discipline, not a one-off project.
On the instrument itself
Brainload Engineering Diagnostic — Pilot v0.1. 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.
Read more in Research & Methodology, or see a fictional walk-through of the whole loop on the interactive tour.