| Component | ||||
| 1 | 2 | 3 | 4 | |
| We see the implementation of projects as learning opportunities and institutionalize mechanisms to manage knowledge relating to, and arising from projects | 0.851 | |||
| We explicitly build time in project schedules for critical reflections on project outcome (not just at the end of project), and also conduct end-of-phase reviews as the project progresses | 0.802 | |||
| Orientate team members towards learning | 0.895 | |||
| Create reward systems that encourage knowledge sharing among team members | 0.836 | |||
| Evaluate learning outcomes of team members | 0.868 | |||
| Nurture a project culture open to experimentation and new insights | 0.587 | |||
| Institutionalize mechanisms for team members to freely reveal their expertise and views concerning solutions to problems rather than firmly instructing them to follow predefined procedures | 0.690 | |||
| Articulate practical knowledge pertinent from past phase to new phase of the project (externalization). | 0.786 | |||
| Articulate cause and effect linkages of past success/failure | 0.693 | |||
| Have past project audits discussed and used in current project/s | 0.789 | |||
| During project execution, you discuss the set of problems encountered during the project | 0.712 | |||
| Ensuring psychological safety |
|
| 0.746 |
|
| Foster meetings with team members from previous and next phases of the projects | 0.768 | |||
| Embed a mentor in each project team to provide support for team members | 0.803 | |||
| Create routines to internalize tacit knowledge stemming from individual and team reflectivity | 0.726 | |||
| On-the-job training | 0.632 | |||
| Job rotation |
|
|
| 0.624 |