Engineering Playbooks
How we solve recurring production problems.
How we solve recurring production problems.
A reading shelf. Articles ship when they earn their place.
Engineering Playbooks are practical walkthroughs of the engineering work we keep doing. The decision-audit method we run before migrations. The stabilisation checklist on Implementation engagements. The forensic-audit method for System Rescue. The Git CI/CD pipeline pattern we built on Deploy Monkey. These are the playbooks our own engineers reach for — written so other teams can adapt them.
Each playbook will be specific, sequenced, and testable. Code samples and configuration where useful. Honest about which steps are negotiable and which aren't.
Cutover day sequenced from freeze to go/no-go: the final data sync, the validation gates, the decision point, and the fallback if the new system does not pass.
Read the articleThe playbook we run on a failed implementation before any structural change: a two-to-four-week forensic audit. What it examines, what it produces, and why fixing first is the mistake.
Read the articleThe deploy runbook for an Odoo system: pre-deploy checks, backup, module update, smoke test, and a rollback plan written before you need it.
Read the articleThe procedure we run before any Odoo major-version upgrade: inventory the custom modules, grep for breaking patterns, walk the dependency tree, score each finding by risk.
Read the articleThe runbook for when an Odoo system is down or badly degraded: triage order, what to check first, how to choose between fixing forward and rolling back.
Read the articleThe clone-and-anonymize procedure for a faithful staging environment: database copy, filestore, scrubbing sensitive data, and the config differences that keep it safe.
Read the articleMoving data from a legacy system into Odoo: profile the source, build the mapping, run dry imports, validate against known totals, and plan the cutover load.
Read the articleWhat we do in the first five days of taking over an Odoo system someone else built: what to read, in what order, and which assumptions to verify before touching anything.
Read the articleEngineering Playbooks are the written form of the discipline layers documented on each Engagement Model page. Where the Engagement Model pages describe what's included in an engagement, the Playbooks describe how the included work actually gets done — step by step.
Adjacent surfaces: How We Work — Discipline Layers; System Rescue (forensic audit as a playbook); Modernization & Migration (decision audit as a playbook).
Real questions from your operating reality become real articles. Send them.