Research & Development Support

Entering a new context is not one decision; it is a chain of them. The best-known link is the go/no-go to launch — the question Market & Expansion Research exists to answer. But the earlier links, the ones an R&D team is still turning over, decide as much of the outcome. What problem is really worth solving here? Who is the innovation for, in specifics? Does the current prototype meet the real environment, or only a lab bench version of it? Which of the next design choices actually changes the answer for a user?

Research & Development Support is the service for that earlier stretch. It pairs the Lab's field method with the R&D team's design cycle, so that the evidence arrives while there is still time to act on it, not after the design has frozen.

Companion methods: Market & Expansion Research for the launch decision, Field Research for the primary-contact method, and Impact Measurement once the product is live.

When this is the right service

Signals it fits

You are between TRL 3 and TRL 7 — the prototype works in the lab, and the next question is whether it works in the setting it is meant for.
You need a defensible read of your Societal Readiness Level (SRL 4-6), captured with the stakeholders the innovation affects, not asserted from inside the consortium.
An EU work programme (Horizon Europe RIA or IA, an EIC Pathfinder or Transition grant, an EIT KIC innovation activity, LIFE, ESF+ social innovation, New European Bauhaus) commits you to real-world testing with users and communities, and the funder will want to see the evidence, not the plan.
Your corporate R&D team has a working product in one geography and is redesigning it for another, and the internal signal (visits, workshops, partner conversations) has become too favourable to trust.
The next design cycle is expensive, and you would rather change it now than discover in a pilot what a two-week interview round would have shown.

What the study answers

Every R&D engagement is scoped to a specific design decision, but four questions recur.

Question 01 · Whom is this really for

The user in the pitch deck is rarely the user in the field. R&D teams routinely inherit personas from the home market, from the funding call, or from the consortium's early stakeholder list. We rebuild the target user from primary contact: who will actually adopt this, whose life does it change, and who is being spoken for without being heard.

Question 02 · Does the prototype fit the real environment

A device that works on grid power in the lab meets a village with three hours of grid a day. A digital service designed for smartphone users meets a population that shares a handset across a family. R&D-stage field research surfaces the environmental assumptions the prototype quietly makes, before the next build cycle bakes them in.

Question 03 · Where the SRL actually sits

Societal Readiness Levels name the axis TRL cannot see. Claiming SRL 5 (validated in the relevant context in co-operation with stakeholders) requires evidence from the stakeholders, gathered by someone with no stake in the answer. We turn an asserted SRL into a substantiated one, and we do it in a form a reviewer or evaluator can read.

Question 04 · What to change before the next build

The output of R&D research is decisions, not a report. Ranked recommendations: what to keep, what to redesign, what to drop, and which parts of the design space are still open. Fed back into the team's own sprint or work-package cadence, in time for the next iteration.

Two axes, read together

Two-axis TRL-SRL matrix showing four quadrants: Waiting (low TRL, high SRL - wanted, not yet built); Ready (high TRL, high SRL - works, and society is ready); Early (low TRL, low SRL - neither ready); Dangerous (high TRL, low SRL - works, but rejected or mistrusted). — R&D commonly moves fastest on the TRL axis and stalls on the SRL axis, drifting into the "dangerous" quadrant where the technology works but society will not adopt it. Field-based R&D research is what keeps the two axes moving together.

R&D that reads only technical readiness lands in the most expensive failure mode in the field: a device or service that works, that nobody adopts. See TRL and SRL: The Two Axes of Readiness for the underlying framework and both nine-level scales.

How the study runs

The same five-stage method as every Lab engagement, adapted to an R&D cycle rather than a launch cycle.

Scope. A short design conversation with the R&D team locates the specific decision the next iteration hinges on, the SRL threshold the funder expects, and the evidence that would actually move the design.
Design. A mixed-method instrument built for the design stage: rapid in-depth interviews with the intended user population, a short structured protocol for stakeholders on the deployment side (installers, regulators, aggregators), and a lightweight observational protocol for prototype-in-context sessions. Grounded in the interview guide and the impact-tracking template where a baseline is being set for later evaluation.
Collect. Local field researchers who speak the language and know the setting run the sessions directly. Prototype sessions are recorded, consented, and analysed against a pre-agreed observation frame, not left as anecdote.
Analyse & benchmark. Findings mapped explicitly to the design choices they inform, and read against comparable R&D reference points where they exist. SRL evidence is filed against the level the project is claiming, in a form an external reviewer can trace.
Deliver. A design-decision briefing (what to change, what to keep, what to drop, in the team's own sprint or work-package language), the evidence trail behind each recommendation, and the instrument in a repeatable form so the next iteration has a baseline to measure against.

Turnaround is measured in weeks, not seasons, so the evidence arrives inside the design cycle rather than after it.

For European R&D consortia

Flag of the European Union - twelve gold stars in a circle on a blue field.

For projects funded by the European Union Independent user- and stakeholder-facing research for Research and Innovation Actions, Innovation Actions, EIC Pathfinder and Transition grants, and EIT KIC innovation activities. Set up with the design cycle, closed with an SRL claim that will survive review. See the European Impact Tracking service →

Europe funds R&D at a scale unmatched anywhere in the world. Horizon Europe alone runs Research and Innovation Actions (RIA) that carry a technology from TRL 4 to TRL 6, and Innovation Actions (IA) that carry it from TRL 6 to TRL 8 with a real-world demonstration. The European Innovation Council funds the same journey through EIC Pathfinder at the frontier end and EIC Transition and EIC Accelerator as the technology matures. The EIT KICs, the LIFE programme, Digital Europe, the European Social Fund Plus, and the New European Bauhaus all commit their projects to demonstrable social readiness alongside technical progress.

Every one of these instruments asks R&D teams to demonstrate real-world validation with users, communities, and other stakeholders, not just laboratory maturity. The proposals promise it. The mid-term reviews and evaluators look for it. Where this often breaks down is not intent but capacity: consortia are built for technical work packages, and structured user- and stakeholder-facing research is either bolted on late or self-assessed from inside the team.

The Lab is that independent capacity, brought in from the start:

Set up at the start. A theory of change that names both the technical and the societal claim, an SRL rubric agreed with the coordinator, a baseline captured before the first prototype is deployed, and a clean line between what the team is building and what an independent partner is measuring.
Run through the design cycles. Structured user and stakeholder work aligned to work-package milestones, with findings fed back to WP leads in time for the next iteration. Midline reads that let the consortium redesign before a demonstrator freezes.
Close with evidence. An endline read against the SRL levels the project is claiming and the OECD-DAC evaluation criteria where they apply, with a full evidence trail. Dissemination and exploitation work handed to Reporting to Funders so the finding actually reaches the audience that can use it.

Related programmes and companion services: European Impact Tracking for the full baseline-to-endline architecture, ESF+ Social Innovation for the specifically social-innovation strand, and Monitoring, Evaluation & Dissemination for the full three-part loop.

Where the design assumption meets the field

Every R&D failure mode we see at this stage has the same underlying shape: a plausible assumption the design team was working from, and a field reality the design team had not yet met. The value of independent field work is closing that gap while the design is still open.

What the design assumes

The user is the persona in the deck.

What the field shows

The persona was inherited from the home market and nobody has spoken to a target user in the target setting. The person the design should have been built for often does not fit the archetype at all.

What the design assumes

The prototype meets a lab-grade version of its environment.

What the field shows

Power flickers, connectivity drops, devices are shared, dust and heat and repair-shop culture behave in ways the design cycle never rehearsed. Prototype-in-context sessions surface these on the first day.

What the design assumes

The SRL claim is the level the proposal committed to.

What the field shows

The evidence behind the claimed level is often thin: workshops with a friendly stakeholder group, self-report from the project team, testimonials picked for the report. An evidence file per level, gathered by an independent partner, is what makes the number defensible.

What the design assumes

Formative research can be caught up later.

What the field shows

A missed month of user research at the start typically costs a year of iteration later, and freezes design choices that field evidence would have overturned. The first field round belongs inside the design phase, not after it.

What the design assumes

Stakeholder workshops equal co-design.

What the field shows

Two workshops with self-selected participants are not co-creation. Real co-design is recurring, reciprocal, structured, and honest about who was in the room and who was not.

Where this shows up in the Lab's work

For the dedicated illustrative case built around this service — a European hardware venture's R&D-stage field test of a cold-chain vaccine fridge in rural East African clinics, before design freeze — see Before the Freeze: An R&D-Stage Field Test of a Cold-Chain Prototype.

R&D-stage field evidence has also run through most of the Lab's live engagements. the mobility case is the clearest example on the technical side: an electric motorcycle iterated for Nairobi conditions, where the rider's daily economics decided which design choices were viable. MiMaji is the equivalent on the service-design side: a water-transparency tool co-designed with residents whose access to that information had never been mapped. Pyropower turned direct kiln-operator interviews into the design brief for the next iteration of the technology.

The public thinking behind this service line sits in two insights: Who Absorbs the Gap on why market-entry decisions in e-mobility ultimately turn on a reliability question the R&D team must design for, and The Incumbent's Second Life on what actually transfers when an incumbent moves capability into a new regime.

Who this is for

Corporate R&D EU consortia EIC-backed ventures Academic R&D partners Programme innovators

See Who We Serve for how the fit works in each case.

Companion methods: Market & Expansion Research once the design is stable and the question moves from "should we build this?" to "will it scale here?"; Field Research for the primary-contact method behind both; Impact Measurement once the product is live. For the readiness framework the SRL claim rests on, see TRL and SRL: The Two Axes of Readiness. For how a study runs end to end, see How It Works. To start a conversation, see Contact.