Research & Development

Turn research questions into clear next steps

Research and development work is most useful when the problem, evidence requirements, and intended decision are clear. GOCS can help structure that work—from early feasibility questions and technology assessment to evaluation planning and implementation handover, subject to an agreed scope.

Explore the working approach

Start with the decision to be made, not a predetermined solution.

The purpose

Make the next R&D decision more concrete

An engagement should reduce uncertainty in a defined area. The right level of research may be a feasibility review, an evaluation plan, a prototype, or a documented recommendation—not necessarily a full product build.

01

Clarify the problem

Define the research question, the operating context, the constraints, and the decision the work must support.

02

Compare viable options

Review alternatives against explicit criteria, available evidence, dependencies, and practical trade-offs.

03

Define a useful next test

Identify what should be evaluated next, what evidence would matter, and which resources are required.

Potential domains

Areas to explore and assess

The starting point is the business or technical question. The appropriate domain, methods, and specialist input are determined during scoping.

AI and data systems

Use-case evaluation, model or system requirements, data readiness, benchmark design, and validation planning.

  • Problem and data suitability
  • Evaluation criteria
  • Integration considerations

Energy and sustainability

Early assessment of technical approaches, operating constraints, performance measures, and feasibility questions.

  • Option comparison
  • Operating assumptions
  • Measurement plans

Life sciences and biotechnology

Research framing and evaluation planning where appropriate specialist expertise and controlled facilities are available.

  • Research question definition
  • Evidence and risk review
  • Facility dependencies

Materials and manufacturing

Assessment of material or process options, relevant performance criteria, prototyping needs, and scale-up constraints.

  • Requirements and tolerances
  • Test planning
  • Production transition needs

These are potential areas for assessment and scoping, not a claim of dedicated in-house laboratories, particular equipment, or completed projects in each domain.

Working approach

A four-stage R&D workflow

The sequence can be adjusted to the problem. Each stage should produce enough clarity to decide whether the work should continue, change direction, or stop.

  1. 01

    Frame

    Define the question

    Agree the objective, constraints, assumptions, stakeholders, and decision to be informed.

    Possible output: research brief
  2. 02

    Assess

    Review evidence and options

    Examine available information, alternatives, dependencies, feasibility questions, and material risks.

    Possible output: options assessment
  3. 03

    Evaluate

    Plan a proportionate test

    Set evaluation criteria and determine whether analysis, simulation, a prototype, or physical testing is appropriate.

    Possible output: evaluation plan
  4. 04

    Transfer

    Document the next step

    Record findings, limitations, unresolved questions, and practical requirements for implementation or further research.

    Possible output: findings and handover

Scope and work products

Agree on the outputs before the work begins

The deliverables should match the decision at hand. Depending on the engagement, work products may include one or more of the following.

  • Research question and requirements brief
  • Feasibility or technology options assessment
  • Evaluation criteria and test plan
  • Prototype scope or validation plan
  • Findings, assumptions, and recommendations
  • Implementation or knowledge-transfer notes

Deliverables are agreed for each engagement. Listing a work product here does not mean it is included in every engagement or that laboratory testing is automatically available.

Common questions

Before defining an R&D engagement

Does every engagement include a prototype?

No. A prototype is one possible way to evaluate an idea, but it is not always the most useful or proportionate next step. The scope should follow the question, available evidence, risks, and agreed evaluation criteria.

Can the work include specialist laboratory or physical testing?

That depends on the project and access to suitable facilities, equipment, and qualified specialists. Any required facilities, safety controls, responsibilities, and costs should be identified and agreed before testing is included in scope.

What should we provide to start a discussion?

Bring the problem you are trying to solve, the decision you need to make, any known constraints, existing research or data, and the outcome you would consider useful. It is acceptable to begin with an open question if the uncertainty itself is clearly described.

Next step

Start with the question you need to answer.

Share the objective, constraints, and what a useful decision would look like. Scope and dependencies can then be discussed before any work is defined.

Discuss an R&D requirement