Playbooks
Three guides that follow one job from start to finish: understanding a workflow, changing it, and keeping it working after release.
They come out of my work with Salesforce, order-management software, and rebase delivery infrastructure, so the examples skew that way (shipping screens, invoices, migrations) and you’ll have to translate. Read them in order, or start with the stage you’re in.
Understand the workflow
-
Map a rented platform before you change it
Compare Salesforce configuration with operator walkthroughs, resolve the gaps, and define a tested path for repair or migration. Includes an evidence-note template and migration rehearsal guidance.
Change it
-
Change one workflow and prove it works where it runs
Define a checkable outcome, implement the full workflow, and verify it on the intended release. Covers task scope, shared ownership, recovery, and when to add a runtime agent.
Support it after release
-
Keep it working after release, with humans and agents
Carry an operator report through diagnosis, assignment, review, release, and verification. Includes a work-order template and guidance for recovering stalled work and learning from corrections.
Working through one of these right now?
Tell me which stage you're in and what the current system makes you do by hand.
Tell me the tool, the workaround, and who does it. I usually reply within two working days.