Community Operations Platform - Iglesia Tiempo de Cambio
Operational systems used daily by 100+ active users for registration, reporting, branch visibility, and recurring live events.
December 1, 2019 · 6 min
At a glance
- Outcome
- Reliable daily operations for 100+ active users
- Ownership
- Built and maintained registration, reporting, maps, and event-support flows.
- Timeline
- Jun 2016 - Dec 2019
- Stack
- JavaScript · Google Maps APIs · SQL · Role-based dashboards
Impact metrics
- 100+ active users
- Live-event operational support
- Platform remains active in production
Why this matters
This case shows I can simplify messy organization workflows and build software that non-technical teams can keep using.
Context
Inside a large community organization, I built and maintained systems used daily by 100+ active users across recurring operations and live events.
Problem
Core workflows were fragmented across manual steps and disconnected tools. Teams needed better role boundaries, stronger reporting visibility, and dependable daily execution.
Constraints
- Recurring live events required stable behavior under pressure.
- Different roles needed different access and reporting views.
- Changes had to remain practical for non-technical daily users.
Approach
I implemented and supported membership registration, reporting, geospatial branch coverage (Google Maps + geofencing), role-based websites, and event-support workflows with iterative delivery.
Results
- Reliable daily usage by 100+ active users.
- Improved leadership visibility through clearer reporting flows.
- More dependable operational support during recurring live events.
Learnings
- Operational clarity increases when role permissions and reporting ownership are explicit.
- Scope control is critical when release windows are tied to fixed event schedules.
- Next improvements would focus on self-serve reporting and alerting for high-traffic windows.