WeConnect 2.0
How do you standardize real-time operations and data capture for 500 field staff across 50 centers and 6 states — without the tool itself becoming another barrier to adoption?
PROBLEM STATEMENT
project summary
We Connect 2.0 is a custom-built application designed to replace fragmented, Excel-based field reporting with a single, standardized digital system. As Project Manager, I owned the project from content and information design through to execution — defining what each of 7 user personas needed to see and enter, while directing external design and development vendors, aligning leadership, and driving adoption among 500 end users across 6 states and 50 centers.
The challenge
Operations were run on inconsistent, center-specific spreadsheets with no shared standard, making oversight and data integrity difficult to maintain at scale.
The end-user base was entirely non-technical field staff, with no prior experience using a structured digital tool.
One persona (Center Head) carried disproportionately complex information needs — managing 6 other personas plus annual qualitative and quantitative target-setting.
A compressed timeline meant the team had to weigh full bug resolution against the cost of delaying a much-needed operational shift.
strategy utilized
Phased, persona-by-persona rollout using agile-style sprints, allowing each of 7 personas to be independently designed, tested, and released rather than launching as one large system.
Milestone-linked vendor payments, releasing funds only upon completion of each persona's design and development — keeping vendor delivery accountable to actual progress, not time elapsed.
User-led UAT, testing each persona exclusively with the field staff who would use it day-to-day (e.g., Outreach Coordinators testing the Outreach Coordinator persona), on the premise that their operational fluency made them the most credible evaluators of usability.
SLA-backed issue resolution, with a 2-working-day response and 2-working-day resolution target to manage post-launch bugs transparently.
Key decisions
Rejected the first design draft — a static, spreadsheet-style layout — and redirected the vendor to build an interactive interface, recognizing that replicating Excel would defeat the project's purpose.
Re-planned the Center Head persona mid-execution after identifying that its scope was significantly more complex than initially scoped, adjusting design and development to match.
Launched ahead of full bug resolution under timeline pressure, choosing to prioritize field momentum over a delayed, fully-polished release — supported by a structured live-support system to manage the trade-off.
results
50 of 50 centers (100%) transitioned from Excel-based tracking to real-time digital reporting.
5 of 7 personas (71%) live and in active daily use by field teams.
500 end users onboarded onto a standardized operating system across 6 states.
2-working-day average issue response and resolution SLA maintained post-launch.
Lesson learned
Launching before full technical readiness is a legitimate strategic choice — but only when backed by a fast, transparent support system. The real safeguard for adoption wasn't a perfect product at launch; it was a reliable, responsive process for resolving problems as real users encountered them.
outcome
We Connect 2.0 is now the operational backbone for field reporting across 6 states, with the remaining 2 personas and the deferred Youth profile positioned for phased rollout once current adoption stabilizes — extending the same standardization strategy across the organization's full operational base.