Infrastructure Delivery at Helity
Process design and delivery coordination for a remote European infrastructure team.
Technical Project Manager · Elyrix / Helity.org
Client infrastructure is confidential — this case study shows the process artifacts I designed, not the systems they govern.
0
tickets coordinated
0
delivery epics completed
0+
knowledge-base documents
0+
SOPs authored
The problem
A remote infrastructure team was delivering real work — servers, networking, security — but delivery had no gates. Completion meant "the engineer said it's done." There was no review step, no evidence standard, and no documentation system to hold what the team learned.
The 4-Eye Review process
The delivery workflow I proposed, got approved, and implemented — every ticket passes a second pair of eyes and an evidence check before Done.
I designed the workflow end-to-end and then built it: new Jira workflow statuses, a Kanban board replacing the old setup, six system components applied retroactively across 80+ tickets, and saved review filters. I deliberately excluded myself as a reviewer — the coordinator who designed the gate shouldn't also be the gatekeeper.
The documentation system
Diátaxis structure
50+ documents organized by purpose — tutorials, how-to guides, reference, explanation — instead of one flat wiki.
20+ SOPs
Repeatable procedures with owners, so operational knowledge survives personnel changes.
Rollout gate map & RACI
Who validates what, at which stage, with what evidence.
Technical scoping without taking the keyboard
For a high-availability networking epic, I researched the failover approach (CARP/virtual-IP), verified provider-side constraints, and handed the engineers a strawman they could react to — coordination that accelerates implementation without owning it.
Validation works the same way: I check completion evidence — certificate issuance, connectivity, recovery-path testing — against acceptance criteria from the coordination side. Engineers keep hands-on ownership.