We help you get your best ideas to market faster.
Knowledge Briefs and other resources for running a program that uses the Rapid Learning Cycles framework.
We make thousands of decisions in product development. While not all of those decisions require the same level of effort, and some should be made quickly, Key Decisions demand the best of the team's decision making skills.
The Rapid Learning Cycles framework provides much. . .
If we don't use Gantt charts to manage our project plans in the Rapid Learning Cycles framework then how do we keep our teams coordinated and on track?
The Rapid Learning Cycles framework uses the simplest of tools to manage complexity...
I still see too many program managers who attempt to use Gantt charts and other traditional project management tools for early product development programs.
These tools were originally developed for large construction projects, where the technology, the sequence, activity duration and dependencies are all well-understood. . .
Rapid Learning Cycles are intended to run fast and light, with only the project management the team needs, so that the team can stay focused on learning and the program manager has time to facilitate, mentor, coach and manage stakeholder relationships.
Since we don't use traditional project management tools for building the plan, the metrics used to manage other kinds of projects don't make sense, either. . . .
The Rapid Learning Cycles Framework uses the simplest tools that get the job done. Visual Planning Boards document a team's Learning Cycle and Activity plans. Short stand-up meetings take the place of lengthy, unproductive program team meetings. Single page A3 reports break long documents down into bite sized pieces of extensible knowledge.
Two simple tools help teams visualize the flow of knowledge...
The reason why Rapid Learning Cycles get products to market faster is that the RLC Framework pulls learning forward and pushes decisions later. When teams learn early and decide late, they give themselves the flexibility to respond to new information, and they avoid late design loopbacks.
Requirements are decisions - but the traditional product development process treats all of these decisions the same way...