5d • General discussion
Glen here, learning to document a change before making it
I'm learning practical AI with a contractor background, and Jerry's rollback note interests me. I'd like to get better at describing a small change clearly enough that someone else could understand what happened.
For a practice workflow, I can see the value of writing the intended result and the way back before changing anything. That feels familiar from planning a job: know what you're touching before you start.
What do you keep in the shortest useful change note for a GHL workflow? I'd appreciate a plain example of the few details you need when you return to it later.
1
2 comments
Glen here, learning to document a change before making it
Suggested communities
Powered by