Standard Operating Process - Design
How do you create one standardized operating process for 7 fundamentally different field roles, across 50 centers with no prior consistency, without oversimplifying the complexity each role actually manages on the ground?
PROBLEM STATEMENT
project summary
Prior to this project, no formal SOP existed for field operations — each of the 50 centers operated on its own informal process, resulting in inconsistent execution, conflicting definitions of key milestones, and no standardized way to track or report progress across regions. I authored the complete SOP from the ground up — covering all 7 field personas (Outreach Coordinator, Foundation Course Facilitator, Digital Empowerment Trainer, Spoken English Trainer, Skilling Youth Coordinator, Placement Youth Coordinator, and Center Head) — spanning the full youth journey from outreach through placement, and rebuilt it into a simplified final version after an initial round of field-level testing.
The challenge
No existing standard meant every center had developed its own way of working, making it difficult to compare performance or make consistent decisions across regions.
Each of the 7 personas had a substantially different scope of work, making a single consistent format difficult to design without flattening role-specific complexity.
Field Group Discussions (FGDs) surfaced conflicting input from different role-holders, requiring reconciliation into one coherent process.
Core program milestones — such as "FC Completion" or "Placed" — were being interpreted differently across teams, with no shared definition or evidence standard.
The SOP needed to be simple enough for non-technical field staff to use day-to-day, without losing the operational depth leadership needed for oversight.
strategy utilized
Pilot-then-scale approach — tested the SOP at 2 centers first, using real field feedback to refine before committing to a 50-center rollout.
FGD/UAT-led co-design, gathering direct input from actual role-holders across all 7 personas rather than designing top-down, so the final SOP reflected real operational constraints, not assumptions.
Definition standardization, establishing single, agreed-upon criteria for key milestones (e.g., FC Completion, Placement categories) that all centers and personas would use identically going forward.
Cross-referencing with the We Connect 2.0 platform, ensuring the SOP's process steps and definitions aligned with what was already being tracked and reported digitally — so the two systems reinforced rather than contradicted each other.
Iterative simplification — rebuilding the SOP into a leaner "simplified" version post-UAT, prioritizing usability for field staff over documentation completeness.
Key decisions
Finalized standard definitions for previously ambiguous milestones (e.g., what qualifies as "FC Completion" or "Placed"), resolving inconsistent interpretations that had existed across teams.
Built the SOP around each role-holder's actual KRA, rather than a generic template, ensuring the process matched what each persona was actually accountable for.
Integrated We Connect 2.0's existing data structure into the SOP, rather than designing the process in isolation — ensuring field process and digital reporting stayed aligned.
Chose to simplify rather than add detail after the first UAT round, prioritizing a version field staff would actually use daily over a more comprehensive but less practical document.
results
100% coverage — rolled out across all 50 centers and 6 states in FY 25–26, following a successful 2-center pilot.
Role clarity improved across all 7 personas, contributing to program targets being met within given timeframes.
Reduced hand-holding dependency — centers require substantially less day-to-day guidance to execute correctly.
Standardized reporting achieved across all centers for the first time, replacing center-specific variation.
Improved leadership decision-making — clearer, consistent dashboards now enable faster, trend-based analysis across regions and individual centers.
Quarterly review cycle established (from 26–27), embedding continuous improvement into the process rather than treating the SOP as a one-time document.
Lesson learned
A standard process only works if it's built with the people who'll use it, not handed to them. The FGD/UAT round wasn't a formality — it's what turned a technically correct V1 into a version field staff actually adopted, and it confirmed that simplification, not additional detail, is often the real fix when a process isn't landing.
outcome
The SOP is now the single operating standard for field operations across the organization, replacing 50 centers' worth of inconsistent, informal practice with one common process — and, paired with We Connect 2.0, has created a foundation for consistent reporting and regional trend analysis that didn't exist before. The quarterly review mechanism ensures the process continues to evolve rather than becoming outdated.