Lessons Learned (LL) in Vehicle Programs Quick guidelines

See BMS instruction: Lessons Learned (LL) sessions in Vehicle Programs

Method LL Sessions

Gathering relevant data for actions and to coming programs

Post-its. Good things, bad things

Answer the questions below/ area;
- What went well within your area of responsibility?
- What would you have done differently within your area of responsibility?
- What went well within the other areas and regarding cooperation with the rest of the project?
- What could have been improved within the other areas and regarding cooperation with rest of the project.

Rules
• Specific and explainable
• Avoid 'soft' unmeasurables e.g. 'good teamwork', 'management commitment' etc
• Bring data/evidence/examples on bad things
• Avoid defensive attitudes
Cluster like items
Weight or prioritise clusters
Select 5 or 6 to work through

Analyse the items

• Emphasis on problem statement, root cause analysis and countermeasure proposal and responsibilty. Lear
• For process related issues to be adresses to Process Council within our organisation for further judgement
• For technical problems to be adressed to the Unit LL Fora for LL Intake (PRA Prevent Recurrence Action).
• For positive experiences that people outside our organisation could learn from, to be adressed to the Unit L

Implement relevant actions from previous programs

• Review information.
• Decide if actions that are needed according to received information.
• Appoint a responsible person and a final action date

Documentation and storage

Store the file in Sharepoint Program LL

 t of the project?
ration with rest of the project.

oposal and responsibilty. Learnings to be documented in Controling documents e.g. Design guidelines, BMS
nisation for further judgement and process adjustments.
Prevent Recurrence Action).
, to be adressed to the Unit LL Fora for LL Intake (BEST Best Practice Replication)
 407039043.xls

Program:
Phase:
Department: MP&L
Lessons Learned (LL) Session: Own experiences LL Session: Review meeting
("to be repeated/avoided next time") ("steal with pride")
+/- Issues/Process Root cause/s Recommendations/Actions Solved Documentation Content changed or Escalated Adressed Adressed Responsible Ready Date Review meeting: Responsible Ready Date
within (Controlling added in to Line or to Process to LL Fora for action/ Action needed for action
own org? documents changed documentation Program Council BEST/PRA escalation (What´s in it for my task)
(Y/N) for LL) Mgm. (Y/N) (Y/N)
(Y/N)

- Part Readiness for (New Part) Part late delivery during supplier constraint - cable harness Stock Count 8 weeks before COL, if Y
not enough then directly order.
- Part Readiness (Common Part) Part no stock at warehouse Stock Count 8 weeks before COL, if Y
not enough then directly order.
-

Volvo Car Corporation Confidential 01/18/2019 Page 3

 407039043.xls

+/- Issues/Process Root cause/s Recommendations/Actions Solved Documentation Content changed or Escalated Adressed Adressed Responsible Ready Date Review meeting: Responsible Ready Date
within (Controlling added in to Line or to Process to LL Fora for action/ Action needed for action
own org? documents changed documentation Program Council BEST/PRA escalation (What´s in it for my task)
(Y/N) for LL) Mgm. (Y/N) (Y/N)
(Y/N)

+
-

Volvo Car Corporation Confidential 01/18/2019 Page 4