Example · Technical standards body
What should a candidate test description make explicit?
A standards working-group member investigates how communication performance claims could be compared more carefully
The situation
Making tests comparable
You are preparing a fictional standards working-group discussion about reporting BCI communication tests. Published claims may describe different tasks, settings and assistance. Before proposing a common reporting approach, you want to identify which contextual details a reader would need to understand what each test actually establishes
What this example starts with
- Available
- The public catalogue provides relevant case leads and links to source material
- Unresolved
- You have not established whether test conditions or outcome definitions are consistently reported
- Constraint
- A reporting proposal must retain differences between applications rather than force unlike tests into one ranking
Working through the question
Choose a bounded comparison
Use Monitor to locate cases relevant to a specific communication task. Record the catalogue scope and inspect original sources. Group only tests whose purpose is sufficiently similar, while making population, environment, system boundary and assistance differences visible before comparing any reported result
Trace the meaning of a claim
For each source, ask what counts as a successful action, which errors are included and what support the task requires. Note whether training, setup and interrupted sessions are described. Missing reporting is a reason to request clarification, not evidence that a test omitted those conditions
Draft a testable proposal
Use the comparison to draft a candidate reporting requirement and explain which ambiguity it addresses. Specify its intended applications and limitations. Ask the working group to examine feasibility and counterexamples before treating the draft as a consensus requirement or an adopted technical standard
An illustrative take-away
A candidate reporting requirement
Your working note makes the proposed requirement and its rationale open to review
- Describe the task, success definition and handling of errors
- Report the assistance and setup included in the test
- State which conditions remain outside the reported claim
Written for this example to show what the reader could take into their next conversation
A draft reporting requirement is not an adopted standard, a completed test or evidence of conformance
Try this with your own question
Your guide explains the steps, access requirements and limits for your role