Frameworks
Luck doesn't repeat. Method does. Everything on this page exists because I needed it, built it, ran it, and kept it — four working methods, each one battle-tested on real production systems.
ALIGN — Discovery that produces a decision, not a pile of answers. Most discovery processes are intake forms: they collect answers and hand a consultant raw material. ALIGN is a gated, dual-track discovery operating system I authored. A short executive track sits over a deeper working track, every module ends in a captured decision — one primary objective, one primary customer, one accountable owner — and readiness is scored before build work is allowed to begin. The output is a blueprint that tells every downstream system, human or AI, exactly what to build.
THE A–F CHANGE MODEL — Marketing moves fast now; that's exactly why it needs brakes. Every change is classified from Class A (read-only audit) through Class F (infrastructure), and higher classes trigger heavier controls: logging, review, before-and-after screenshots, rollback plans, sign-off. Two rules make it work. The screenshot rule: layout, homepage, and navigation changes are never approved from a report — screenshots or it didn't happen. The sacred-page rule: pages that carry the business get the strictest treatment even for small edits.
RECOVERY-FIRST OPERATIONS — Production is never the source of truth. The website can break, the CMS can fail, and an agent — human or AI — can make a confident mistake at scale. Recovery-first means none of those events are existential: current exports, documentation a stranger could rebuild from, and a maintained recovery package per project. No change without a rollback path. No handoff without a written report.
THE 30-SECOND RULE — If your team can't find it, edit it, and understand it in 30 seconds, redesign it. Every system I ship gets that acceptance test, because complexity that requires its author is a liability wearing a clever disguise. This site is held to the same rule — if any page fails it, tell me.