Procore Technologies, Inc. · NYSE:PCOR
Procore Technologies — Conference Presentation (September 2015)
28 slides from Procore Technologies's conference presentation, Sep 30, 2015
Slide 1: Implementation For Success: An Inside Look at Getting Procore Up and Running
Implementation For Success: An Inside Look at Getting Procore Up and Running 9.30.15 | Pete Zafros, Director of Technology, EYA
Slide 2: Presenters
Presenters Pete Zafros Mark Lyons Director of Technology Senior Director of EYA Business Development Procore
Slide 3: EYA
EYA EYA has made its name and reputation developing innovative urban neighborhoods. Since 1992, we’ve built more than 4,000 homes in more than 30 neighborhoods across the Washington AREAS OF EXPERTISE Metropolitan area, tackling some of the region’s most challenging • Urban infill townhomes sites al
Slide 4: Level Setting
Level Setting Aren’t off-the-shelf software products ready for use? • Technology – YES • Process – NO • People – NO When do I hit the maintenance phase? • Never. Continual improvement is necessary to stay ahead of competitors. Will software help my organization? • Do not buy software if you want to
Slide 5: Adoption
Adoption What motivates your employees? Proven Value Delivery Early Late Majority Majority Potential Value Early Adopters Training Enable Laggards Innovators Technology Adoption Curve
Slide 6: Agile / Lean Methods
Agile / Lean Methods Drive adoption with: • Iterative roll outs • Systemized employee feedback • Focus on reality • Build complexity in iterations • Solution design by small, (Gall’s Law) motivated users • Responsive over plan-driven Make the greatest business impact by: • Focusing on business value
Slide 7: Approach
Approach Our specific technique - Agile Sprints: • Executives prioritize and clarify objectives • Users define the best possible solution over a two week period • Everyone provides feedback PRODUCT BACKLOG SPRINT REVIEW DELIVERY RFIs, Submittals, Meetings, etc. SPRINT SELECTION DESIGN RFIs or Submit
Slide 8: Sprint Selection
Sprint Selection Purpose - Select a topic • Discuss long term value and short term needs • Timebox of 15-30 minutes • This is a ‘Now or Later’ decision, not a ‘Yes or No’ Outcomes • Topic is selected • Sprint Leader is selected Who’s involved? • Executives / Users
Slide 9: Sprint Design
Sprint Design Purpose – Design a solution • Executives provide business goals (~1 hour) • Sprint leader, users, and Procore develop a solution • Timebox hours to minimize burden on participants • Encourage change and appreciate mistakes Outcomes • Potential solution of people, process, and Procore W
Slide 10: Sprint Review
Sprint Review Purpose - Assess solution readiness • Demonstrate the solution • Immediately collect feedback • Accept or reject pieces of the solution: > Accepted for further use > Rejected - Incorporate into another sprint > Rejected - Drop from the backlog of options • Focus on progress not perfect
Slide 11: Assessment
Assessment Assess solution performance with early adopters through: • Discussion • Project reviews • Audits The solutions will likely need: • Adjustments or additions • Further training / communication Making adjustments and improving communication will create proven value and engage the early major
Slide 12: Drawing Sets: When and where are drawings loaded to Procore?
Drawing Sets Procore Sprint When and where are drawings loaded to Procore?
Slide 13: Goal
Goal Improve productivity by making drawings easier to: • Locate • Sort, search and filter • Use from the field on mobile devices • Maintain and distribute current versions Decreases risk by: • Minimizing the use of incorrect drawings • Providing mark up, linking, and communication tracking capabili
Slide 14: Process
Process The following policies apply for drawing sets that further complete design (i.e. Bid Set, Issued for Construction, Permit Set): • DOA / DOE authenticates the accuracy and reliability of drawings. • Any drawings used outside of the design team are delivered through the Drawings Tab. • Drawing
Slide 15: Uploading Drawings
Uploading Drawings ● All data fields are required with descriptions below. Attach the file from your computer. Select ‘Create New Set’ or select an existing set when a set comes in pieces. Name the set in a way that others will The Issue / Revision date listed on understand. the drawings. The projec
Slide 16: Drawing Use
Drawing Use ● All departments should use the current set to conduct business. The current set should be used to execute on drawings. Individual sets are used to review changes.
Slide 17: Drawing Management: Revisions
Drawing Management Revisions
Slide 18: Goals
Goals Improve productivity and reduce the risks associated with drawing revisions by: • Reducing the use of incorrect drawings • Improving the ability to locate the correct drawings • Enable use of markups and other Procore Drawings features for the benefit of the entire project team Context - This
Slide 19: Potential Revision
Potential Revision Definition: A drawing is being reviewed and may potentially change. Options: 1. An associated RFI or markup is linked to the drawing by construction or architecture staff. It took 10 minutes and 6seconds to add a markup to 15 drawings with no previous practice.
Slide 20: Revised / Approved
Revised / Approved Definition: The drawing can be used to execute. Steps: 1. Load new drawings. 2. Review each markup to make sure the change was addressed and remove the markup from the drawing. It took 1 minute and 20 seconds to remove the markup on 15 drawings with no previous practice.
Slide 21: Delivery
Delivery Roll out in iterations: • Continuously improve quality • Reduce risk by focusing on easier topics / content first • Reduce the impact of errors / unknowns • Prevent the creation of bad habits • Provide training in real situations • Minimize resource requirements • Improvements are immediate
Slide 22: Training
Training Agile / Lean reduces the need for training: • Users creating solutions is the ultimate training • User-focused solutions are more intuitive • Iterative delivery enables training over time • Intense training is focused on the individuals who need it Training Options: • Sprint reviews • Group
Slide 23: Procore Updates
Procore Updates • New Procore capabilities may initiate sprints. • Enhancements are incorporated through discussions and audits. • Sprints provide Procore with product development ideas.
Slide 24: Challenges, Pt. 1
Challenges, Pt. 1 A lack of understanding of agile / lean methods: • Show quick and consistent progress • Provide supplemental material • Agile Manifesto • Agile for the CFO, Pt. 1 • Agile for the CFO, Pt. 2 • Intro to Lean Change Management • Lean Enterprise
Slide 25: Challenges, Pt. 2
Challenges, Pt. 2 Individual compliance: • Develop a cohesive message about the role of Procore • Incorporate Procore into performance evaluations • Review progress at project meetings Implemented incorrectly: • Maintain rhythm • Narrow your focus • Focus on progress not perfection
Slide 26: Procore Straight Talk
Procore Straight Talk Lessons Learned • Focus on drawings early to enable a logic-based system. • Leave Documents / Emails tabs until the end (or never) to minimize old habits entering the new system. • Do not throw bad user data into the Directory. • Audits can punish your best users and encourage
Slide 27: Questions?
Questions? HE NEIGHBORHOODS OF E YA life within walking distance® PROCORE Cea THE as s ea
Slide 28: Thank you!
Thank you! Contact Us 866.477.6267 sales@procore.com
Procore Technologies — Conference Presentation (September 2015) on 6ix