Rapid Learning Cycles

Are development programmes stalling because decisions are made too early or too late? With Rapid Learning Cycles, your development team first closes the knowledge gaps and makes Key Decisions at the right time. Three sessions, on your own project.

Your point of contactRené AernoudtsDirecteur / eigenaar 06 50 20 64 38

Develop faster by learning first and deciding later

A development project starts with confidence. During the concept phase, the team selects an engine, a supplier and a target market because the schedule requires it. Months later, during testing, one of those choices proves to be wrong and the design has to go back to the drawing board. At that very point, a change costs the most time and money.

Delays in product development can often be traced back to a few decisions made early in the project, based on assumptions and incomplete information.

Rapid Learning Cycles reverses that order. Your team brings learning forward and postpones the most important decisions until the last responsible moment. This allows the team to make those decisions based on what it has learnt in the meantime.

Do you recognise these challenges?

  • Does the launch date for new products keep being pushed back?
  • Does your team have to reverse design choices late in the project, when this costs a great deal of time and money?
  • Are important choices fixed early because the schedule requires it, even when the team does not yet know enough?
  • Does your project management mainly monitor the schedule and budget, while leaving little room to test assumptions?
  • Is knowledge from previous projects held by just a few people, causing each new project to start from scratch?
  • Have you adopted Agile methods from the software world, even though sprints and backlogs are poorly suited to developing physical products?

Sound familiar? Then Rapid Learning Cycles is a logical next step.

What are Rapid Learning Cycles?

Rapid Learning Cycles (RLC) is a product development framework that helps development teams learn faster and make better-informed decisions. Katherine Radeka, founder of the Rapid Learning Cycles Institute, developed it through her work with development teams and her research into Lean product development. The framework applies Agile principles to the development of physical products and new technology.

Many development projects contain just one major learning cycle. The team makes its decisions during the definition and concept phases and only discovers during testing which choices do not work out. This puts the launch under pressure and creates quality problems.

Rapid Learning Cycles divides that one long cycle into short learning cycles based on Plan-Do-Check-Act. The team learns what it needs to know as early as possible and makes decisions as late as responsibly possible. This reduces the risk of making the wrong decision at the point when correcting it is most expensive.

Many project teams say they work according to PDCA. In practice, Plan then means 'I make a schedule' and Check means 'I monitor results and the budget'. In the original approach, you formulate a hypothesis, test it in an experiment with a genuine possibility that it is wrong, and standardise what works. Rapid Learning Cycles brings that way of thinking back into project management.

The building blocks of Rapid Learning Cycles

Core Hypothesis (Core Hypothesis)

The reason your organisation believes in the product, expressed in one sentence: which new technology the product uses, what value this delivers to the customer and how the company earns money from it. For example: "A cordless electric mower helps professional landscapers cut grass with less noise, while we earn money from mower sales and battery leasing subscriptions."

Key Decisions

Decisions with a major impact on the business case, for which the solution is not yet known. The team has to make them to complete the product or process design, but cannot yet do so with confidence. They relate to what is new to you, new to the world or difficult to achieve. For example: "Which electric motor will we use?"

Knowledge Gaps

What a team member needs to know to make a Key Decision. For example: "Which electric motors are available on the market and how well do they meet our requirements?" Team members close these knowledge gaps in short learning cycles and record what they have learnt.

Last Responsible Moment (Last Responsible Moment)

For each Key Decision, you determine the latest point at which you can decide without harming the project's progress. Until then, the team keeps its options open and gathers knowledge. If you miss that point, you will pay for it later through delays.

Learning Cycles Plan

A visual plan that distributes the Key Decisions and Knowledge Gaps across consecutive learning cycles and integration events. After each learning cycle, the team updates the plan: completed knowledge gaps are removed and new ones are added.

What does it deliver?

Over three sessions, you set up Rapid Learning Cycles with your own project team for a current or new development project. Every assignment concerns your own product, your own decisions and your own schedule. After the third session, the team has a plan that is scheduled directly in the calendar.

After the three sessions, your team will have:

  • a Core Hypothesis that everyone supports;
  • an overview of the Key Decisions, how they relate to each other and the Last Responsible Moment for each decision;
  • Knowledge Gaps with an owner;
  • a Learning Cycles Plan scheduled in the calendars;
  • a meeting structure with ground rules and templates for Knowledge Gap Reports and Key Decision Reports.

The framework is based on an insight from Katherine Radeka's work: long delays and late design changes can usually be traced back to a Key Decision that was made with too much risk. Teams that better substantiate their Key Decisions have to go back to the drawing board less often and therefore complete their project faster.

How to tell whether it is working

Rapid Learning Cycles promises less redesign. You can measure this, and we recommend doing so before the first session, so that you have something to compare against later.

Four indicators work best in practice:

  • How often a decision was made again. In a completed project, count how many times a design choice was reversed or reconsidered. That number should fall.
  • The number of design changes after design release. This is usually the most expensive type of change and is often already recorded in your change process.
  • The lead time from concept to release, particularly how much of it was waiting time.
  • How many Knowledge Gaps had been closed when a Key Decision was made. This is the only one of the four that you can see changing during the project.

You can obtain the first three from your current projects without measuring anything new.

Who is Rapid Learning Cycles for?

The programme is intended for organisations that develop physical products or new technology and want to gain control over the risks in their development projects. You take part with the core team of one project, so that the different disciplines work together on the same decisions.

For example:

  • R&D managers and product development managers
  • Project leaders and programme managers
  • Engineering managers and engineering team leaders
  • Product managers and innovation managers
  • Technical directors

The framework can be used for different types of projects: further development of an existing product, a new product using new technology or intended for a new market, a concept study or a portfolio of smaller projects such as preliminary research.

Why Rapid Learning Cycles with LMI?

Lean Management Instituut has been helping organisations with Lean since 2004 and is part of the Lean Global Network, an international network of Lean institutes. We bring a Lean perspective to PDCA: planning and monitoring, complemented by experimenting and learning.

You start small, with one project team and three sessions. After the third session, the first Learning Cycles Plan is running in your own calendars, and you build from there.

Frequently asked questions

View all FAQs
What is the difference between Rapid Learning Cycles and Agile or Scrum?

Agile originated in software development, where a change costs relatively little and a team delivers working software in short sprints. With physical products, a late change costs much more time and money. Rapid Learning Cycles also works in short cycles and focuses on knowledge and decisions: what does the team need to learn to make a well-informed Key Decision, and by when must that decision be made?

What is the difference between Rapid Learning Cycles and Lean Product Development (LPPD)?

LPPD is the broader approach for an organisation’s entire development system. Rapid Learning Cycles is a practical framework that enables a project team to learn faster within a single project and make decisions at the right time. The two complement each other.

Which projects is Rapid Learning Cycles suitable for?

For projects with a high degree of uncertainty, where a late change would be costly. Examples include a new product featuring new technology or intended for a new market, a concept study, the further development of an existing product or a portfolio of smaller projects.

What is a knowledge gap and how do you identify it?

A knowledge gap is what someone needs to know to make a key decision. You identify these gaps by asking what knowledge is missing for each decision. They are mainly related to what is new to you, new to the world or technically difficult. An example of this connection: the decision “which electric motor should we choose” requires the knowledge “which motors are available and how well do they meet our requirements”.

What is an integration moment?

The point at which the team brings together the knowledge gained and makes the decisions at hand. Between two integration moments, the learning cycles take place in which team members close their knowledge gaps. The Learning Cycles Plan distributes the decisions and knowledge gaps across these moments and is updated after each cycle.

How long does a learning cycle take?

The length depends on the knowledge that needs to be gathered, rather than a fixed sprint duration. A cycle in which a supplier has to produce a prototype takes longer than a cycle involving a calculation and a bench test. In the third session, the team schedules those cycles, taking into account the actual lead times and testing capacity available.

Does this also work for hardware with long lead times?

That is exactly what it was designed for. Katherine Radeka developed the framework to make Agile principles applicable to physical products and new technology, where a two-week iteration is rarely suitable. The last responsible moment for each decision is precisely the tool that makes long lead times manageable: you keep your options open until the point when further delay would affect the schedule.

What if the answer from an experiment is unfavourable?

Then you have the least expensive result of the entire process. An unfavourable outcome in week six requires an adjustment to the plan; the same outcome during integration requires a redesign. That is why the core hypothesis is captured in a single sentence: you can then see whether the unfavourable answer affects the entire proposition or only the chosen route.

How does this relate to a stage-gate or phase-gate model?

A gate checks whether a phase is complete. Rapid Learning Cycles organises the work between those gates around the question of what knowledge is needed and when. The two do not conflict: many organisations retain their gates and structure the phases between them differently, resulting in fewer unresolved questions at the gate.

Does Rapid Learning Cycles become an excuse to postpone decisions?

That is the question executives ask most often, and the answer lies in the method itself. Every Key Decision is assigned two things in advance: an owner and a date. That date is the last responsible moment, and it is included in the Learning Cycles Plan and everyone’s diary. The decision is made on that day, based on the knowledge available at the time.

In most project plans, the decision date is implicit. Here, it is set before the work begins, and it is clear who will make the decision. This generally brings more discipline to decision-making than a plan based on tasks and completion percentages.