Scale of analysis
0
phones represented in the dashboard
Selected work
Different problems.
Same instinct: find out what’s really happening.
01 / KIPP Public Schools Northern California
Who actually needs a work phone?
KIPP was spending roughly $40K each month on staff mobile service without a clear understanding of how different roles actually used their devices. I combined behavioral data, staff research, and device information to turn a cost question into a role-based provisioning strategy.
Pattern investigated
0
zero-cellular-use accounts investigated
Business context
$40K/ month
approx. monthly mobile spend discussed in discovery
The strongest discovery was that usage totals alone could mislead. Many zero-cellular-use lines were still supporting real work over Wi-Fi, while a 242 GB outlier turned out to support laptop setup reliability—not careless usage.
Carrier / JAMF dataExcel + Power QueryManual reconciliationLooker StudioInterviewsRole-based synthesis
Research → strategy
02 / USDA Economic Research Service
What if the status meeting didn’t need to be an hour?
I redesigned project-status reporting into an accessible, self-serve project-health experience that made overdue work, milestones, and project health easier to understand before the meeting ever started.
60 → 15minutes in the approved weekly status-meeting format
30+project managers and division leaders in the presentation audience
WCAGaccessibility guidance informed the dashboard design
Drag to compare the dashboard glow-up
Original dashboard → redesigned project health
Before · Original dashboard
A functional starting point, but the hierarchy was sparse and project status was harder to scan quickly.
After · Redesigned overview
Stronger hierarchy, clearer status cues, and a more structured path into project health details.
My approach
The tools change.
The instinct doesn’t.
I like work that sits between people, systems, and imperfect information. My process is designed to make the messy parts useful.
Ask why.
Find the pattern.
Make it understandable.
Measure what changed.
How I work
Not a fixed design-process diagram. Three modes I move between depending on what the problem actually needs.
Start with the people.
Interviews, stakeholder discovery, user stories, workflow mapping, accessibility, and the context around the screen.
Find what the pieces say together.
Behavioral data, qualitative themes, technical constraints, operational patterns, and business requirements.
Turn evidence into something useful.
Interfaces, prototypes, dashboards, information architecture, recommendations, and clear stories that move decisions forward.
A little about me
I like problems that don’t arrive neatly packaged.
The projects I enjoy most sit somewhere between people, technology, and operations. I like figuring out what users actually need, finding patterns in imperfect information, and turning those findings into experiences people can understand and use.
UX ResearchProduct DesignFigmaPower BILooker StudioAccessibilitySystems ThinkingData