Please comply with the Lean Construction Institute’s Usage Policies and Attribution Guidelines at http://www.leanconstruction.org/usage.pdf when using this file. Thank you.
Welcome message from author
This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
Transcript
Please comply with the Lean Construction Institute’s Usage Policies and Attribution Guidelines at http://www.leanconstruction.org/usage.pdf
when using this file. Thank you.
Coordinating Action
Kristin Hill
InsideOut Consulting
Last Planner® System
Traditional Delivery Condition
Risk
Missed schedules, budget overruns, poor quality
Lack of team-wide focus on client needs
Team work is unreliable
Communication is not clear
Trust is challenged
Difficult conversations are avoided
Lack of prioritization & whole-system thinking
Alliances are jeopardized or broken
Target Delivery Condition
Minimize Risk Greater value realized by clients (& company)
More effective buildings
Less rework/waste
Less execution/construction problems
More agility for program dynamics
Improved ability to deliver within budgets & schedules
Trust is built
More fun!!!!!
Shift Perspective
Shift Language
Shift Behavior
Lean Fundamental
Understand value from customer’s perspective & take
only those actions that deliver that value (minimize
waste)
“What does the customer want from this process?”
Customer “pulls” the work
Collaborative Planning
“Plans are nothing; Planning is everything.”
-Dwight D. Eisenhower
“Planning is the act of conversation that
leads to well-coordinated action”
Foundation by which the team collectively organizes the actions required to meet their goals
Our Focus
Breakdowns
Focus on expected outcomes
Planning is done in a “pull” manner
Work is made to “flow”
Planning & execution are connected
through conversation
People doing work- plan the work
Based in making reliable
commitments
Manage constraints and variance
Plan-Do-Check-Act
(PDCA) cycle built-in
Planning - Production System
Elements of the Pull Plan Designing the Network of Promises
Master Project Milestones
Phase Milestones
Weekly Plan Promises
(Network of promises)
A project is a very big promise
delivered by people in an ever
changing network of promises
Requests
Elements of a complete request:
Customer
Performer
Time frame
Competency
Mutually understood Conditions of Satisfaction
Responses to Request
Possible responses to a request:
Accept
Decline
Counter-offer (‘yes if’ or negotiate to ‘yes’)
Commit to commit later
Action Workflow
Customer
Requests
Provider
Promises
Provider
Declares Done
Customer
Accepts Done
Negotiate/clarify
Perform Work
Conditions
of
Satisfaction
Assure CoS
Elements of Sticky
Color code sticky
by discipline
Swim lane from milestone
& promise
Make sure your request has
a promise
Try to “take time out” of the
overall schedule!!!!!
Name
MY PROMISE
•What I will Deliver
•Be specific
•Small batch
MY REQUEST (S)
•What I need from others
•Be specific
•Person /date
Delivery
Date
2
1
3
Document the Plan
Deliver the Plan
Daily Check-in Huddle •High energy, stand up
•Make commitments
•Raise constraints
•Track commitments done
Collaboration
Economics of Trust From “The Speed of Trust”
Trust = Speed Cost
Trust = Speed Cost
YouTube - Stephen Covey - Leading at the Speed of Trust
http://www.youtube.com/watch?v=igyxxYShXYo
Related Documents
