MISA
Portfolio Drive

Vice President for eServices Candidate

Navarro, Philippe Zachariah G.

Goals

1. A more MISA-open eServices, not only to empower the officers within, but to technologically transform the community through workshops and newsletters regarding Emerging Industry Tech trends beyond the MIS education. 2. Improve cross-committee coordination and client by 50% through building a semester-long calendar with HR, Comms, OET, OSG, Events and Marketing so that no project ever stalls waiting on assets, billing, internal product deployment/requests, or client confirmation. 3. Scale revenue from ₱45K to ₱80K by expanding to 5-6 client projects with full officer deployment and ownership per project while maintaining the quality of our internal products. 4. Maintain the CoLab bar by formulating a Manual for Crafting Tech Module, Activities, and Coordination for an everlasting efficient and effective (and fun) CoLab experience for kids.

Platforms

CoLab Legacy: Sustainable Social Transformation

Context: CoLab is currently 10x better than before, but the knowledge of how to run it effectively lives in people's heads, not in documentation. If key officers leave, the quality drops.

Action: Formulate a Manual for Crafting Tech Modules covering lesson structure, activity design, age-appropriate pacing, coordination protocols, logistics benchmarks, and best practices for making CoLab fun and memorable, then pass it down as a living document updated each cycle.

Result: CoLab quality maintained regardless of officer turnover, new officers onboard faster with a clear playbook, and MISA's social impact becomes sustainable and repeatable.

Own it, Ship it: Revenue & Delivery Scale

Context: eServs shipped ₱45K in external revenue and proved the PM/Dev/UI-UX/SysDocs method works, but training timelines slipped which limited how many officers were deployment-ready, and internal products risked being neglected while chasing new work.

Action: Front-load 3rd-level training to finish as soon as 2nd Wave results drop so officers are client-ready earlier, standardize training methods so quality stays consistent with faster timelines, expand to 5-6 external client projects with full officer deployment and end-to-end ownership per project, dedicate separate maintenance owners for internal products, price based on actual value delivered, and start all client projects at the beginning of each semester so delivery wraps 5 weeks before finals.

Result: ₱80K in revenue (78% increase), 5-6 shipped projects, every officer deployed with a portfolio piece, internal products maintained, all deliveries completed 5 weeks before semester ends.

Open Source: Knowledge Sharing Beyond eServices

Context: Members look up to eServs as MISA's technical standard, but access is limited since you either get in or you don't. There's no formal channel to learn from eServs or stay updated on industry tech trends beyond the MIS curriculum.

Action: Run 1-2 hands-on technical workshops per semester on emerging industry tech (Data Engineering, APIs, Automation, AI tools), structured as builds not lectures so participants leave with something they made, and launch a recurring newsletter on emerging tech trends relevant to MIS students.

Result: 40-60 members trained per semester, eServices positioned as MISA's knowledge hub, and stronger community engagement beyond just officers.

Locked In: Proactive External Coordination

Context: Cross-committee coordination was reactive as projects stalled waiting on Comms, OET, OSG, Events, and HR. Dependencies weren't mapped early, causing projects to start during midterms or get rushed last-minute.

Action: Build a semester-long coordination calendar with all committees before any project kicks off, set fixed SLAs per committee (e.g., Comms assets 2 weeks before launch, OET deployment windows, Marketing client leads by Week X), establish regular touchpoints rather than only reaching out when eServs needs something, and own the timeline by accounting for real working weeks including midterms, holidays, and ramp-up periods.

Result: 50% improvement in cross-committee coordination, 2-3 clients in pipeline before each cycle, zero projects stalled from missing dependencies.