Research concept · Plain-language guide
What is technical uncertainty?
Technical uncertainty exists when a competent professional cannot determine a required technical outcome from available knowledge, information or experience, and evidence must be generated to establish whether or how it can be achieved.
01
What it means in practice
It concerns a technical outcome
The question is whether a defined behaviour or performance can be achieved under stated conditions.
It is assessed against available knowledge
The team’s unfamiliarity is not enough if the answer is established elsewhere.
It must be capable of investigation
A systematic test should be able to reduce the uncertainty and change the decision.
02
Examples
- An AI benchmark does not establish performance on sparse proprietary data
- Laboratory results do not establish a mechanism at production scale
- Component data does not determine the behaviour of a new building assembly
03
What it is not
- The team has not done it before
- The project has commercial risk
- Implementation is difficult or poorly documented
04
How Ignition Research applies the concept
We use the concept to improve technical decision-making, not as a label to place over ordinary development. We connect it to a defined outcome, appropriate evidence and a decision rule, then maintain that logic while the work is conducted.
The Ignition research value chain
One methodology, six steps — each with a named output
- 01FrameA testable research question
- 02DesignExperiment plan & controls
- 03ExecuteRuns & recorded findings
- 04IntegrateSpecialists, coordinated
- 05GovernEvidence log & audit trail
- 06ReturnValidated, claim-ready records
General information only. This page does not determine R&D Tax Incentive eligibility and is not tax, legal, financial or grant advice. Whether any government support pathway may be relevant depends on the project's specific activities, structure, evidence and the current program rules.
Next step
A researcher reads your description — not a salesperson.
Bring the operating problem, the result you cannot explain or the decision your team cannot make with confidence. You will get a reply within two business days — including when the honest answer is that a research pathway is not the right tool.