Pilot admins need a usable adoption signal before inactive seats become a deployment verdict.
Champions need proof that Mail is taking hold, while IT admins need a view that respects existing identity and access boundaries.
Who you’d be doing this for
“My VP asked who’s actually using it, and I had to pull names from three places.”
Laura Greco · IT Administrator
Runs identity, provisioning, and rollout reporting for a client-facing enterprise team in a Mail pilot.
What is at stake
Only 38% of pilot admins can quickly distinguish unconnected users from inactive ones. You have to weigh a clearer Mail-specific view against the boundaries of shared identity and access systems.
Why it isn’t already fixed
Every obvious fix costs something else. That’s the part you’d have to decide.
- pilot speed vs. access boundaries
- simple admin triage vs. complete reporting
- Mail-specific proof vs. shared platform consistency
- seat provisioning vs. meaningful adoption
Why Superhuman
Mail’s enterprise onboarding depends on admins showing whether a newly provisioned team is actually changing its email habits.
Written with these in mind
Not your kind of problem? 30 more at Superhuman, or browse every organization.
This is the setup. The work is inside.
Running it puts you in the room: the full situation and its constraints, stakeholders who push back in their own words, and the decisions that are yours to make. What you produce becomes a Day One Plan — work you can show someone instead of describing.