BA-First: Why I Diagnose Process Before Automating
Most automation projects fail because teams skip the diagnostic step. Here is the BA-first approach I use with every client.
A working library of consulting field notes, vendor evaluations, and short takes - written first for the desk it sits on, kept public so other operators can use it. No demos, no decks, no “transformations.”
Audit patterns, post-mortems, and methodology pieces. Written after a project closes, not while it’s being sold.
Most automation projects fail because teams skip the diagnostic step. Here is the BA-first approach I use with every client.
Tool releases, vendor announcements, and quick reads that didn’t earn a full article. Read in under three minutes.
Built for retrieval, not reading. Comparisons, scorecards, and checklists I open during client calls - if they help you too, take them.
Side-by-side scorecards on the workflow automation stack: Zapier, n8n, Make, and others.
Side-by-side scorecards on the workflow automation stack: Zapier, n8n, Make, and others.
Reusable shapes for SMB operations: lead-to-cash, intake-to-onboarding, weekly-close.