© Lean Construction Institute
Beyond The RFI: From CYA to CBADavid Craddock . Christian Pikel . Jenna Santamaria . Mark SpiesOctober 4, 2016
© Lean Construction Institute
Introduction / Problem Statement
2
• What’s wrong with RFIs anyway?• Rose colored glasses effect• New behavior paradigm -
Personal Accountability vs CYA• Set behavior, match tools
© Lean Construction Institute
Our Missteps and Learnings
3
• No Punch Lists / No RFIs – Great now what?
• ‘What happened on the call?’• ‘It’s in the Box’• Efficient, Ineffective communication• Attachments, attachments, attachments• Why we meeting minutes• Tool adoption - Ease of Use• Security & Control vs Access &
Transparency• Beware the cave dwellers &
overload
© Lean Construction Institute
Desired Behaviors for Success
4
• Owners Role/Champion• Team learning environment• Holistic approach – efficient for
team• Buy in and follow through• Match tools to Process, not
Process to tools• NO ‘set it and forget it’ mentality –
must PDCA• Go beyond one project
Kno
wle
dge
Mgm
t
PrinciplesBehaviors
ToolsReal World
Virtual
© Lean Construction Institute
Changing Behavior at Team Initiation
5
• Create environment where conversations can happen (Trust)
• Fast start is critical• Initiate Design Conversations early, before
design team is “attached” to a design
© Lean Construction Institute
Designer / Constructor Collaboration
6
• Owner’s pay for buildings, not drawings• Ask - what do craftsmen need to build?• Must have purposeful constructability conversations • Capture decisions on the drawings
© Lean Construction Institute
As the Team Grows
7
• Early involvement of last planners• Transition into construction is critical
point in project• High functioning team enables smooth
assimilation of trade contractors• Core team engagement all the way
through the end is very important• Project team is responsible for
facilitating communication with last planners and craftsmen
• Designer flexible since it never goes exact to drawing
• Update details to actual installed for next project
© Lean Construction Institute
Tools & Process
8
• Tools & Technology can’t solve it for us, but they can support how we want to behave and communicate
• Why?• Opportunities to automate and make
more visible• Put information at the fingertips of those
who need it
• How?• Cloud file space shared by the team• Virtual big rooms (persistent
webex/Go-to, etc)• Collaborative task management
tools: Asana• Enterprise Social• Organization level communities of
practice• Enterprise wide dashboards
© Lean Construction Institute
File sharing: Get files out of email
9
• Lots of choices in on-line cloud storage: Box, Google Drive, One Drive, etc
• File structure and file naming must be re-thought – it’s not about what is good for one organization
• Each team needs a champion –someone to help those who ‘don’t get it’ or need additional support
• Look for frustrations and challenges: “It’s in the box” and do something about it
© Lean Construction Institute
Beyond Spreadsheets: Work Register to Asana
10
© Lean Construction Institute
Virtual Big Rooms
11
• Resources that can help them team collaborate when not face to face
• Don’t replace face time with technology
• Interconnected systems can support each other –e.g. WebEx that can share content via Box, etc.
• Effective for information exchange and discussions
• Ineffective for team building and team health.
© Lean Construction Institute
To understand each other…
12
• We have to understand ourselves• Tools & coaching for team concepts• Break down barriers• Perceptions color our world view &
approach
CoreClarity
© Lean Construction Institute
Conclusion and lessons yet to learn
13
• Prevent regression, safety of the known.
• “What’s in it for me” matters • Always continue PDCA• Technology supports, but don’t
allow it to cause lazy behavior –‘It’s in the box”, “the computer told me” are not acceptable
• Think beyond the project –Knowledge Liberation Movement!
© Lean Construction Institute
Before we close…
14
© Lean Construction Institute
During Start-up / End User Turnover
15
• Design Intent/How is it supposed to work• User manuals that explain the why not just
how
Top Related