Back to all writing
Building systems for health NGOs
Most operations don't break loudly: recovering a journal system with no handover
Most operations don't break loudly.
They fail quietly — in fragmented systems, broken dependencies, and workflows no one fully owns.
Last week, I was dropped into a journal system that was running — but not operationally stable or fully controllable.
No documentation. No clean handover. Multiple layers already degraded.
The environment spanned CMS infrastructure, database layer, email authentication, and frontend templating.
Here's what that involved behind the scenes:
- Diagnosed an Open Journal Systems (OJS) instance from zero context — no documentation, no handover
- Bypassed a broken admin interface by working directly in phpMyAdmin at SQL level
- Set up functional email infrastructure (DKIM/MX/SMTP via Google Workspace)
- Rebuilt broken submission workflows by tracing database logic directly
- Connected the registration flow to Google Sheets via Apps Script for structured data capture
From the outside, none of this is visible. What people see is:
- A working system
- Clean communication
- No escalation required
That's the job.