Questions worth testing

A question worth putting to the test.

Applied technical research that turns an uncertain idea into evidence for a decision.

Discuss the work
Illustrative engineering experiment

Test the same edit.

Amend the same sample brief. Compare a saved position with finding the exact words.

JavaScript activates the edit controls. The original brief, comparison and method limits remain available below.

The brief as it was when the reference was saved.

Sample brief Reporting workspace
Reporting workspace A small operations team reviews daily reports in one workspace. The reporting view must remain usable offline. Changes should be clear to the person reviewing them. This fictional brief contains no customer information.

Highlight: the saved position, even when different words now occupy it.

01 / Saved position

Original words selected.

The saved character range stays 85–131. It still contains the original requirement.

02 / Exact words

One exact match.

The original words appear once in the current brief.

Study scope and methods

Synthetic sample · edits are local to this study and reset when it is reopened or the page reloads. Saved position keeps the original character range. Inserting text can move the intended words away from that range. Exact words uses case-sensitive matching only: repeated words are ambiguous and rewritten words are missing. It uses no context, fuzzy matching or meaning detection. This is not a complete web-annotation implementation.

Related standard: Web Annotation selectors ↗
01Inside the work

Ask something a test can answer.

Replace “explore the technology” with a specific question. For example: can a local process complete the required task without sending data to an external service? Name the result that would change the next decision.

02Inside the work

Use the right kind of evidence.

A prototype tests behaviour; a comparative run tests a difference; a literature review maps existing knowledge. Choose the method that can answer the question, using inputs and access that are available and authorised.

03Inside the work

Let the test fail.

Use representative tasks and difficult cases rather than a demonstration selected to succeed. Record versions, configuration, inputs and results. Separate what happened from what you think explains it.

04Inside the work

Say what the result changes.

Report the finding, its limits and the next action it supports. That may be a larger trial, a different architecture or a decision not to pursue the proposed approach. A result that prevents wasted work is useful.

05Inside the work

Bring the uncertainty.

Tell us the decision you face, what has already been tried and the evidence you can share. We can discuss an experiment, the material it needs and the result it should produce.

A CLEARER NEXT STEP

Frame a research question

From an unanswered question
to an engineered possibility.

Frame a research question
Chat on WhatsApp