1. Resources/Support
1.1. Lack of resources/Availability
1.1.1. Project selection - align with QBR
1.2. Lack/Change of commitment
1.3. Improve team composition
1.3.1. >1 PME / 1 project
1.4. Collaboration issues
1.4.1. Communication issues
1.4.2. Interface with teams
2. Governance
2.1. Dependencies with other teams (e.g. Legal, IT)
2.2. Lack of decisions (e.g. uncertainty)
2.2.1. Unclear roles & responsibilities (RACI)
2.2.2. Additional analyses requested
2.3. Different Project rhythm (e.g. frequency of SteerCo)
2.3.1. DMAIC project split up in diff stages
2.3.2. Clear milestones
2.3.3. Definition of "Ready"
2.4. Resistance to change
3. Methodology
3.1. Lack of view reusable components (e.g. electronic signature)
3.2. Different Project type (DMAIC/DMA/Quick scan/...)
3.2.1. Increase Kaizen Events
3.2.2. Dedicated implementation team (RM)
3.2.3. Value stream map / data analysis only
3.3. Lack of standardization (ppt, tools,..)
4. Project scope
4.1. Changes over time
4.1.1. Align with QBR
4.1.1.1. Discuss topic in SteerCo
4.2. Size/Complexity
4.2.1. Prioritization matrix PME (e.g. 0-picture), projects limited in time / 3-months)
4.3. Clarity
4.3.1. Definition of "Ready"
4.4. Unclear business case
4.4.1. Definition of "Ready"
4.4.1.1. Business case as a project
5. Data
5.1. Lack of reliable data
5.1.1. Data lake (lack of legacy application data)
5.1.1.1. Definition of "Ready"
5.2. Documentation of data
5.2.1. Increase data analytics skills
5.3. Accuracy of data
5.4. Waiting time to extract data
5.4.1. call upon data-analysts (1:2:1 analytics)
5.5. Transform data (e.g. clean up)
5.5.1. support Tribe (CJEs)
6. Focus
6.1. Prio changes
6.1.1. Align with QBR
6.1.1.1. Solid business case
6.2. Too many priorities equal no priority
6.2.1. Head of TO
6.3. Work-life balance
6.3.1. xPME/1 project
6.3.1.1. Review number of retrospective initiatives