Bulletins

Events to Drive Knowledge: How the RLC Framework Supports Real Time Knowledge Capture

posted Jul 5, 1:03 am (526 days ago), permalink

For the past two weeks, the news in the United States has been dominated by the Republican and Democratic National Conventions. What does a political convention have in common with Learning Cycle and Integration Events?

It's a pull event for real-time knowledge capture, providing a treasure trove of material that the media and candidates can use and re-use in this campaign and in future elections.

The structure of Learning Cycle and Integration Events generates pull for real-time knowledge capture in product development teams.

This week's Knowledge Brief describes the three ways that Rapid Learning Cycles drive real-time knowledge capture, even from teams who typically capture knowledge at the end of a program - or not at all.

Key Takeaways:

  • The Rapid Learning Cycles framework drives real-time knowledge capture by providing a place for it in the process, giving clear guidance for how to capture knowledge, and pull events to create urgency so that it gets done.
  • A Knowledge Gap isn’t closed and a Key Decision isn’t finalized until the report is finished.
  • Teams need rigorous enforcement of this rule at first, when they are trying to change from a mindset of deferring knowledge capture until after the program is finished.

Events to Drive Knowledge Capture: How the Rapid Learning Cycles Framework Supports Real Time Knowledge Capture 

Real-Time-Knowledge-Capture-Letter.pdf

Real-Time-Knowledge-Capture-Tabloid.pdf

 

This Knowledge Brief may be freely distributed without modifications in its original PDF form, including all authorship, copyright and contact information. Other uses require our explicit permission.

 

Design-Experiment-Capture: Close Your Knowledge Gaps Scientifically and Permanently

posted Jul 5, 12:58 am (526 days ago), permalink

Design-Experiment-Capture

Even the best of us will devolve into Build-Test-Fix cycles when there is no structure to the learning phases of our projects. It's our default way of working when we're trying to bring something new into existence. We give the idea a try, and then we start refining it until it works.

But it's not a very efficient way to learn, because we're doggedly pursuing one path instead of looking for alternatives.  Eric Ries attempted to improve on Build-Test-Fix with Build-Measure-Learn, which at least frames each build as a learning experiment, and it's not a bad alternative for software / IT products that can be build from the beginning.

But if we're working in the physical world, then we may have a lot to learn before we can build anything.  And building a full physical prototype may not be the most effective way to learn.  In that environment, we need to be a lot more careful about the experiments that we run.

This week's Knowledge Brief describes the three steps we need to close Knowledge Gaps:  Design an experiment, run the Experiment and then Capture the things you learned.

Key Takeaways

  • Build-Test-Fix mode is our default mode for product development - it’s the most intuitive process even though it does not lead to good results and takes a long time.
  • Design-Experiment-Capture summarizes the process for closing a Knowledge Gap scientifically and permanently.
  • LAMDA and other problem-solving methods based on the Scientific Method can enrich this process to build better experimental designs.

 

Design-Experiment-Capture: Close Your Knowledge Gaps Scientifically and Permanently

Design-Experiment-Capture-Letter.pdf

Design-Experiment-Capture-Tabloid.pdf

 

 

This Knowledge Brief may be freely distributed without modifications in its original PDF form, including all authorship, copyright and contact information. Other uses require our explicit permission.

 

RLC Events Don't Move: Three Ways the Rapid Learning Cycles Framework Reinforces Project Timelines

posted Jul 5, 12:46 am (526 days ago), permalink

Rapid Learning Cycle Events Don't Move

I met with a program team this week that experienced a delay when the group was assigned to help out another project team. That led to some fruitful discussions about how to handle such a delay. In a traditional product development program, the date just slips, and it may not be visible to everyone that this has happened until weeks or months down the road.

In a Rapid Learning Cycles program, we don't assume that a program delay like this will change the schedule. The Learning Cycle and Integration Events still take place on schedule.

The team and stakeholders may decide to delay the program - but they do that by adding additional Learning Cycles - not by extending the cadence of Rapid Learning Cycles or delaying Events. In fact, a team in trouble is the kind of team that benefits the most from holding the Events on time.

This week's Knowledge Brief describes how the Rapid Learning Cycles Framework reinforces project timelines so that product teams stay on track to deliver on time.

 

Key Takeaways

  • In a traditional product development program, project updates and gate reviews get delayed until the team is ready for them.
  • In the Rapid Learning Cycles framework, Learning Cycle and Integration Events are fixed in time, and teams hold these events whether or not they feel “ready” to have them.
  • Teams that are having problems are the ones that most need these events to be on time.

 

Rapid Learning Cycle Events Don't Move: Three Ways the Rapid Learning Cycles Framework Reinforces Project Timelines

Events-Dont-Move-Letter.pdf

Events-Dont-Move-Tabloid.pdf

 

This Knowledge Brief may be freely distributed without modifications in its original PDF form, including all authorship, copyright and contact information. Other uses require our explicit permission.

 

1 2 [3]