From operational uncertainty to a research pathway
We can’t tell whether this is engineering or experimentation
New products usually contain known work and unknown work side by side. The risk is treating everything as research, or treating a critical uncertainty as just another feature to build.
01
What may actually be uncertain
Teams close to the problem often hold the most knowledge and the strongest assumptions. We make those assumptions visible, separate unfamiliar work from unresolved technical outcomes and identify the decision that better evidence must support.
- Which technical properties are already achievable
- Which assumption carries the value proposition
- Which failure would invalidate further investment
- Which unknown must be resolved before secondary features
02
What we look at first
- The job and operating conditions of the product
- Prior evidence from prototypes, suppliers and literature
- The smallest test capable of changing the investment decision
- Pre-agreed success and stop conditions
03
Turning the operating problem into a research question
We classify the roadmap into known implementation, engineering adaptation, research questions and commercial assumptions, then test the decision-critical technical uncertainty first.
The question is then translated into hypotheses, variables, comparisons, thresholds and a progression of work capable of returning a clear no. That is what turns activity into decision-led research.
04
How we work with your team
We can stop after assessment and pathway design, or stay involved to conduct the research, coordinate technical specialists and govern the evidence as the work progresses. The research record sits alongside delivery and preserves why each test or design change happened.
- A defined decision, technical uncertainty and prior-knowledge boundary
- Research questions, hypotheses, variables and measurable thresholds
- A staged experiment plan with decision gates and stop conditions
- Contemporaneous evidence connecting methods, observations and changes
- Findings that support implementation, further research, redesign or a stop decision
05
If the answer is no
Sometimes the capability already exists and the right next step is competent implementation. Sometimes the available evidence cannot support the proposed decision. Sometimes the remaining uncertainty is not worth the cost of resolving. We would rather make that visible early than extend a project designed only to confirm its original promise.
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
Where this goes next
- R&D Pathway Assessment — the first, low-commitment read on whether there is genuine uncertainty here.
- R&D Pathway Design — if there is, what exactly gets tested, and how.
- Case studies — anonymised projects, written around the uncertainty and the record the work produced.
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.