The research and development process is the sequence of steps a team follows to move from a technical problem to a resolved outcome. While every project is different, there are common stages that most R&D efforts pass through. This page offers a general framework for the R&D process. It is not a universal mandatory process — different projects, industries, and teams may follow different sequences — but it describes the stages that are commonly present. It is educational and is not individualized advice. For a broader introduction, see our page on what research and development is.
There Is No Single Universal R&D Process
It is important to state at the outset that there is no single, universal R&D process that every business must follow. Different industries, different project types, and different teams approach R&D differently. Some follow a formal stage-gate process; others use a more iterative, agile approach. The framework below is a general description of the stages that are commonly present, not a prescription. A business should adapt its process to its actual work, not force its work into a generic template.
Stage 1: Identify the Problem or Opportunity
The R&D process typically begins with identifying a technical problem or opportunity — something that does not work as well as it could, a capability that is missing, or a new possibility that could be explored. This stage is about recognizing that there is a technical question worth pursuing, not about solving it. For more on recognizing R&D activity, see our page on research and development examples.
Stage 2: Define Objectives
Once a problem or opportunity is identified, the next stage is to define the objectives — what the work is intended to achieve. A clear objective statement describes the business component being developed or improved and the specific improvement being pursued (for example, a new function, improved performance, greater reliability, or improved quality). Defining the objective at the start helps anchor the work to something concrete. For more on the business-component concept, see our page on qualified research.
Stage 3: Identify Uncertainty
With the objective defined, the next stage is to identify the technical uncertainty — what is not known at the outset. Is it uncertain whether the desired capability can be achieved? Is it uncertain how to achieve it? Is it uncertain what the appropriate design is? Identifying the uncertainty in technical terms, at the start of the project, is important because it defines the question the R&D process is intended to answer. For more on this concept, see our page on documenting technical uncertainty.
Stage 4: Develop Alternatives
With the uncertainty identified, the next stage is to develop alternatives — different designs, methods, materials, configurations, or approaches that could resolve the uncertainty. Developing alternatives is important because an evaluative process generally requires considering more than one possible path. For more on the evaluative-process concept, see our page on process of experimentation.
Stage 5: Prototype and Test
With alternatives developed, the next stage is to prototype and test — to evaluate the alternatives against the objective. This may involve building prototypes, conducting tests, running simulations, modeling performance, or other evaluative methods. The testing should be designed to distinguish among the alternatives and to assess whether they resolve the uncertainty. For more on experiment-level documentation, see our page on R&D experiment logs.
Stage 6: Evaluate Results
After testing, the next stage is to evaluate the results — what did the tests show? Which alternatives worked, which did not, and why? The evaluation should assess the results against the objective and the uncertainty, and should inform the next steps. For more on documenting results and iterations, see our page on documenting trial and error in R&D.
Stage 7: Iterate
R&D is rarely a single-pass process. Based on the evaluation, the team may iterate — revising the alternatives, conducting additional tests, or exploring new approaches. Iteration is a natural part of R&D, and the results of one round of testing often inform the next. For more on the iterative process, see our page on research and development project management.
Stage 8: Document
Throughout the process, the work should be documented — the objective, the uncertainty, the alternatives, the tests, the results, the iterations, the people, and the costs. Documentation created during the process tends to be more useful than documentation reconstructed later, because the technical context is present when the record is made. For more on documentation practices, see our page on how to document R&D projects.
Stage 9: Implement or Discontinue
At some point, the project reaches a conclusion — either the objective is achieved and the result is implemented, or the objective is not achieved and the project is discontinued. Both outcomes are legitimate R&D results; the process does not require success. Recording the outcome completes the project record. For more on project completion, see our page on how to organize R&D projects.
Stage 10: Preserve Learning
Whether the project succeeded or failed, the learning from the process should be preserved — what was discovered, what worked, what did not, and why. Preserving learning helps the business benefit from the R&D effort, whether or not the specific project achieved its objective. For more on evidence preservation, see our page on R&D evidence tracking.
How the Process Relates to the Qualified-Research Analysis
The R&D process described above is a general business process. The qualified-research analysis under Section 41 looks at whether the activities that occurred during the process satisfy the four-part test — permitted purpose, technological in nature, elimination of uncertainty, and process of experimentation — applied to a business component. The process stages above (identifying uncertainty, developing alternatives, testing, evaluating) map loosely to the four-part test, but the analysis is more specific and depends on the applicable rules. For more, see our pages on qualified research and the four-part test.
Key Takeaway
The research and development process is the sequence of steps a team follows to move from a technical problem to a resolved outcome. There is no single universal mandatory process, but common stages include identifying the problem, defining objectives, identifying uncertainty, developing alternatives, prototyping and testing, evaluating results, iterating, documenting, implementing or discontinuing, and preserving learning. The process maps loosely to the qualified-research analysis but is not the same as it. For a project-management companion, see our page on research and development project management.