Sales Engineer, PM - Monetization, PM - Enterprise, Customer Success Manager, Designer, Facilitator (me), Engineering Manager
Collective brainstorming, problem definition, prioritization, Hills, impact + effort matrix
2 weeks (prep, conduct, and synthesize)
As Calendly continues to support larger and larger organizations, we've run into serious pain points with our top customers around security, compliance, and disparate accounts throughout the company.
As an IT Manager, I'm tasked with ensuring that employees have access to what they need in compliant, safe ways. It has come to my attention that there are several different teams using Calendly under different tiers of subscriptions (free and paid) so I need to make sure there is a path forward to make Calendly compliant for my entire company.
We collected lists of customers through our Customer Success Managers who have been requesting specific features like domain capture, an activity log for records, and secure log in processes.
As we focused our sights, as a company, on "unlocking enterprise" I rallied together subject matter experts to facilitate a constructive conversation through structured, intentional activities to align on a path to support our largest customers (100-1500 seats).
I worked directly with my Principal Product Manager to plan who needed to be in the workshop and who key decision makers are:
Using Miro, I analyzed the best exercises and activities to help us reach clarity to produce action items and work streams. These exercises included creating Hills, lightning decision jam exercises, prioritization, and journey mapping.
What is "organization consolidation"? It's an internal term we use to describe a company who had multipl departments using different Calendly accounts. For example Sales and Marketing have their own Calendly Pro accounts. If these departments combined into 1 account, they would qualify for an enterprise tier. We aligned on the following:
"Organization consolidation allows a company to know about all the Calendly accounts created with their domain with a path to bringing all those users into one compliant and secure Calendly account."
In order, the following activites helped to define out outcomes and action items for clarity across teams.
Alignment on several streams of work resulted from our prioritization exercise:
Ideas that were deprioritized, mostly for complexity and feasibility reasons:
This informed multiple different agile scrum team's priorities over the next 2 - 3 quarters.
Domain control, group level branding and integrations (primarily Salesforce)
Each of these features have a dedicated designer and team in which alpha, beta, and GA release plans were established.
