Project e-Tip of the Week: Tightly Couple Learning with Action
by Hal on April 22, 2004
in PM practice, tips
If you're new here, you may want to subscribe to my RSS feed. Thanks for visiting!
It's been awhile since I've published a Project e-Tip. The coming five e-Tips will be follow the themes that I see are shaping the work we do. This first one tightly couple learning with action serves as the basis of working in a lean fashion. Take time to explore what it can mean for you, your team, and your customer.h

The Project Reformer's e-Tip of the Week
|
|
024: Tightly Couple Learning with Action
|
|
We learned from Toyota not to produce in large batches. Doing so creates wastes in storage, in tracking, in rework, in movement, and in space. Toyota's goal is single-piece flow at the signal of the customer. But why is it so important to do just one at a time. The answer is we want to learn from each action we take. Toyota sees it as the opportunity to test and re-test their hypothesis of how to do work effectively. Here's five ways you can begin adopting the principle tightly couple learning with action on your projects:
- Meet at the end of each day for just 5 minutes with the last planners on your project to give them the opportunity to report on the work they finished for the day as they had promised to do. Identify at that time any reasons for not finishing promised work. Replan as necessary.
- Do detailed planning for short horizons (6 weeks). Review the outcome, then do more detailed planning.
- Conduct a plus-delta review at the end of each planning meeting. Start the next meeting by referring back to the last review. Select one item from that list for focus during the meeting.
- Have a conversation with the whole team on something that needs improvement. Take action based on an 80% complete solution. Try it out. Review the results. Then create an 80% solution for the balance of the issue.
- Attack the delays on your project. Explore with your team what keeps them from more closely coupling one person's work with another's work. Do an experiment. Learn. Re-do the experiment.
Put these to work on your project immediately. Start by discussing this Project e-Tip with your team. You might want to create a contest with them to see who can generate the most ways for coupling learning with action.
The Project Leaders' Studio™ |
©2004 Hal Macomber | weblog.halmacomber.com | e-Tip Archive | PDF | Submit Tip
|
I'd like to hear your experience working with this. Please leave a comment or send me an email.
LPSThe Last Planner System® is a lean approach to planning and delivering projects. It is based on a hierarchy of planning: should, can, will, and did. LPS is not a computer system. It is a set of protocols corresponding with the four above items: pull planning, look-ahead planning, task planning, and daily coordination.
The Last Planner System is a registered trademark of the Lean Construction Institute.
Last Planner SystemThe Last Planner System® is a lean approach to planning and delivering projects. It is based on a hierarchy of planning: should, can, will, and did. LPS is not a computer system. It is a set of protocols corresponding with the four above items: pull planning, look-ahead planning, task planning, and daily coordination.
The Last Planner System is a registered trademark of the Lean Construction Institute.
{ 1 comment… read it below or add one }
Let’s discuss it!