Advanced Support Consultant Spotlight: Building Systems That Survive Staff Turnover

A lot of my recent work has focused on cleaning up old data and processes and creating new futureproofed ones. The best systems aren’t just effective today—they’re understandable and maintainable six months from now by new staff members.

What this looks like in practice:

Plain-language naming conventions

Saved searches and automations named for what they do, not how they were built, reduce confusion and onboarding time.

Fewer workflows, clearer purpose
Consolidating overlapping automations makes it easier to troubleshoot and adjust when priorities shift.

Documented ‘why,’ not just ‘how’
A short note explaining why a workflow exists helps future users decide whether to reuse, pause, or retire it.

Standardized campaign checklists inside EveryAction
Rather than external docs, we embed consistency directly into configuration—forms, receipts, and follow-ups behave predictably every time.

Any other ideas for helping teams design systems that work today—and still make sense tomorrow?