Game in the Brain

the most basic PDCA workflow is:
1) list of Actions
2) update to what happened to those actions. Report on Metrics or what is observable/tangible – how much actually it cost in time, effort and money.
3) if actions incorrect – crossout (For change history) and write in the action that needed to happen instead (repeat if many wrong moves and keep change history).

4) Moving Forward – Learn from all previous PDCA lists and create templates to better predict the Lists of Actions in a Given course of action.

All complicated BOW and SOW and task lists originate from this basic system. From Construction to Programming. But its important to have that mental muscle to LIST it all down and cross them out/or update what really happened.

It gets more complicated just because of Owners, Change Management, Communication Management, Resources Calculations, Component tracking, Version Tracking, etc…

Its weird that I have to think about this and most of my books are Overwhelming in scope when they make BOWs. Scrumm and Agile was the most approachable, in essence it boils down to David Allen’s GTD’s and Atul’s Checklists.

Also the patience and kindness of letting people learn these basic conditioned habits.

Its such a basic skill I NEED to teach it to my son. But at 7 he’s not receptive to writing things down yet.