Scale of analysis
1,357phones represented in the dashboard, with 1,343 active lines shown in the usage data.
I combined behavioral data, staff research, and operational analysis to understand how different roles used work-issued phones—and turned the findings into a role-based provisioning strategy.
KIPP was spending about $40K every month on mobile service—but did not have a clear picture of who needed cellular service or why.
The question surfaced during exit conversations: we spend a lot on staff phones, but we don't actually know who needs them or how they're being used.
The initial goal sounded simple: identify potential over-provisioning and support cost efficiency. But the real UX challenge was separating apparent low usage from legitimate role needs.
The project charter framed success around mapping role-based usage, documenting user journeys, and creating recommendations that aligned operational needs with financial resiliency.
phones represented in the dashboard, with 1,343 active lines shown in the usage data.
users showed zero cellular usage—an important signal that required context before action.
approximate monthly mobile spend discussed during discovery.
That meant managing discovery meetings, communicating across groups, developing research questions, analyzing messy usage data, reconciling records, building the dashboard, synthesizing user stories, forming recommendations, and presenting the findings.
Research explored communication tools, office/school Wi-Fi reliance, mobility, and when cellular service was genuinely necessary.
Phones supported parent communication, staff coordination, student safety, emergency alerts, and school-specific applications.
Travel between campuses and remote work made reliable cellular connectivity more important for specific roles.
I combined quantitative device behavior with qualitative staff context so that unusual numbers could be investigated instead of automatically treated as waste.
The dashboard let me inspect total phones, active lines, minutes, messages, data consumption, high-usage accounts, low/zero cellular usage, and changes over time.
Built from manually reconciled carrier, employee, and device data to make patterns and anomalies visible.
On its own, that could look like hundreds of unnecessary devices or lines.
Low cellular usage did not automatically mean low device value. Connectivity context mattered.
The number was dramatically higher than typical RSO usage, which averaged below 1 GB per person across the six-month view.
The employee used cellular connectivity during laptop setups so device provisioning would not fail because of an unreliable connection.
“A lot of these phones probably aren't necessary.”
Phone requirements vary dramatically by role, environment, and workflow.
Phones were closely tied to parent communication, staff coordination, safety, emergency alerts, and school operations. School staff also represented the highest-data-use group in the presentation findings.
Most work happened on school or office Wi-Fi using internet-based communication tools, creating a credible case for Wi-Fi-only devices for some roles.
Cellular connectivity mattered when traveling between campuses or working away from reliable office Wi-Fi, making a blanket reduction strategy risky.
The research supported a role-based phone provisioning strategy rather than a one-size-fits-all decision.
School-based and SPED staff: continue full mobile service where reliable communication and mobility are operationally necessary.
Some RSO roles: consider Wi-Fi-only devices where work is primarily completed on school or office Wi-Fi.
Leadership approved the recommendation and began using the work to change how KIPP thought about mobile provisioning and technology spending.
The most important lesson was not that some phones were over-provisioned. It was that usage metrics needed context. By pairing behavioral data with staff research, I could distinguish low cellular use from low value—and recommend a strategy that balanced operational needs with financial goals.