Years of fast, yet unstructured decisions had left Calendly's user management with an inconsistent system, with no Groups, no Managed Events, and a team model that assumed everyone belonged to exactly one team, and it was costing the business real enterprise accounts.
As Principal Design Lead, I ran a Product Inception with our Staff PM and Tech Lead that turned into a 5-stream program to rebuild permissions and user management from the ground up, giving organizations the delegation, branding control, and privacy flexibility they actually needed. The result: new enterprise accounts the sales team couldn't previously pursue.
Calendly was growing fast, and every team shipped their own piece of the product without a shared vision for permissions and user management. Over years, that added up to decisions that made sense in isolation but couldn't scale to where our customer base was going. What we actually needed was a cleaner, more flexible system for permissions, user management, and object access.
I planned a multi-session workshop series in a project inception framework that brought stakeholders and customers together to break down the problem collectively. I strategically selected activities to keep everyone aligned, informed, and actively participating as we mapped every area of the product and our clients.
In order to understand the customer needs of large accounts, we needed to work closely with customer success teams and account managers. We had to capture high-level need patterns from an Admin purview, documenting different themes of issues across privacy, security, sharing, and management.
In order to understand the customer needs of large accounts, we needed to work closely with customer success teams and account managers. We had to capture high-level need patterns from an Admin purview, documenting different themes of issues across privacy, security, collaborative scheduling, sharing, and direct, hands-on management.
A new flexible system which would allow for small, medium, large and multi-layer corporate structures to function based on the organization's unique policy landscape.
Objects are abstracted away from the user, users are owners of objects which live in a container. People can have membership to that container.
This workspace based approach was found to be used by other SaaS platforms such as Google Drive, Asana, Airtable and others.
Moving away from a model of users as the main container for event objects toward a more flexible workspaces model allowed for separation and greater access control to organization administrators.
A central hub for managing all permissions, users, roles, teams, groups and more.
No way to delegate management to department or group leads, everything routed through a single admin
Groups feature, with delegated group admins who can manage their own members, pull department-level reporting, and set up complex routing.
Brand and policy updates required an admin to manually log into individual accounts and change settings one by one
Managed Events, letting admins centrally control branding, visibility, and settings to allow flexible customization.
Users could only belong to one team, so a cross-functional initiative or campaign couldn't get its own team without breaking someone's primary org structure
Teams as a nested layer within Groups, letting a person belong to multiple teams at once.
All-or-nothing visibility, which became a non-starter for companies with strict client data privacy policies.
Configurable visibility, so organizations with strict privacy needs and organizations that wanted full transparency could both be supported by the same underlying system.
This work unblocked the business in three concrete ways.
Sales could finally pursue strict-privacy enterprise clients, like financial institutions, that the old permissions model couldn't support at all.
The product could finally accommodate large, multi-layered organizations, global companies with regional structures like Pinterest, and companies managing multiple owned subsidiaries like Adobe, instead of forcing them into a one-size-fits-all model that didn't reflect how they were actually organized.
Multiple product teams got a shared foundation to build on, replacing years of teams solving permissions problems in isolation with one aligned approach everyone could build against.
60 customers synthesized into 5 clear archetypes, not anecdotal guesses
Staff PM and Tech Lead involved throughout, not brought in at handoff
Enough shared structure to keep 5 independent streams coherent, without slowing any of them down
Flexible enough to accommodate structures we hadn't seen yet