If you are designing an app for setting meetings, how will you set and prioritize metrics for it?

• Is the setting meetings app for personal user or for enterprise purpose? à enterprise purpose
• Is it being designed for any specific platform such as Android or iOS? à Both
• Is it being designer for any specific region or globally? à Global
• Is it a web application or native app? à Web application
• Are there any salient features of this application such transcribing capability, multi-lingual support for transcribing as well as for the actual meeting, AI assisted creation of meeting notes? à Not in the Phase 1 of the application

I will structure my answer by discussing the overall goal of such an application. Then move on to the user actions and next brainstorm the prioritize the metrics for such an application.

Goal:

In the market, there are already multiple enterprise/personal use products available for setting meetings such as Microsoft Calendar, Google Calendar, Calendly etc. which have quite a lot of dominance in the market. To design and launch an app for setting meetings, the major business goal should be to capture market share (so will not focus on monetization aspect). Therefore, in turn the product goal is to acquire users, provide them with good engagement capabilities and gradually consider retention of those users as well so as not to lose them to dominant players. Since it is an enterprise application, there might be 14-days to 30days free trial and different pricing tiers for different organization sizes (small, medium, and large).

 User actions:

• Sign up for the application
• Log into the application
• Search for available slots of meeting participants
• Setup a meeting (one-on-one or group)
• Accept/Reject meeting
• Attend the meeting
• Recording of the meeting
• Sharing of the meeting notes

 Metrics:

Acquisition:

1. No. of organizations signing up for free trial (split by org type) – P0
2. No. of organizations signing up for licensed product (split by org type or price tier) – P1

 Activation:

1. No. of organizations moving to licensed product from free trial (split by org type or price tier) in a month – P0
2. No. of employees/org signing up into the application (split by org type for free and licensed) – P1
3. No. of employees/org setting up at least 1 meeting (split by org type for free and licensed) – P1

 Engagement:

1. No. of employees/org logging into the application daily/weekly/monthly (split by org type for free and licensed) – P2
2. No. of employees/org setting up meetings daily/weekly/monthly (split by org type for free and licensed) – P1
3. No. of employees/org attending the meetings daily/weekly/monthly (split by org type for free and licensed) – P2
4. No. of meetings set/org daily/weekly/monthly (split by org type for free and licensed; split by number of meeting invitees – 1, 10-20, 20-50, 50-100 and > 100; split by meeting duration of 30 mins, 1 hour, 2hour and > 2 hours; split by number of different timezones involved) – P1
5. No. of meetings cancelled/org daily/weekly/monthly (split by org type for free and licensed; split by number of meeting invitees – 1, 10-20, 20-50, 50-100 and > 100; split by meeting duration of 30 mins, 1 hour, 2hour and > 2 hours; split by number of different timezones involved) – P2
6. No. of meetings recorded/org daily/weekly/monthly (split by org type for free and licensed; split by meeting duration of 30 mins, 1 hour, 2hour and > 2 hours) à longer duration meetings take up more storage space and if the application can come up with some features to reduce the longer duration meetings – P2
7. No. of meetings setup/user/org daily/weekly/monthly (split by org type for free and licensed; split by number of meeting invitees – 1, 10-20, 20-50, 50-100 and >100; split by meeting duration of 30 mins, 1 hour, 2hour and > 2 hours; split by within/outside of work schedule) – P1
8. No. of meetings attended/user/org daily/weekly/monthly (split by org type for free and licensed; split by meeting duration of 30 mins, 1 hour, 2hour and > 2 hours; split by within/outside of work hours) – P2
9. No. of meetings rejected/user/org daily/weekly/monthly (split by org type for free and licensed; split by meeting duration of 30 mins, 1 hour, 2hour and > 2 hours; split by within/outside of work hours) – P2
10. Avg time taken to setup meetings (split by org type for free and licensed; split by number of meeting invitees – 1, 10-20, 20-50, 50-100 and > 100; split by meeting duration of 30 mins, 1 hour, 2hour and > 2 hours; split by number of different timezones involved) à number of invitees to be involved, meeting duration and the different timezones involved will affect the time taken to set up the meetings as appropriate slots need to be searched for maximum participation – P2

 Retention:

1. No. of organizations renewing their licenses in a year (split by org type or price tier) – P2
2. No. of organizations not renewing their licenses in a year (split by org type or price tier) – P2
3. No. of organizations upgrading their licenses (split by org type or price tier) – P2
4. No. of organizations downgrading their licenses (split by org type or price tier) – P2

 Keeping in mind the business and product goals, the 2 most important metrics –

No. of organizations moving to licensed product from free trial (split by org type or price tier) in a month

No. of meetings set up/user/org daily/weekly/monthly (split by org type for free and licensed; split by number of meeting invitees – 1, 10-20, 20-50, 50-100 and > 100; split by meeting duration of 30 mins, 1 hour, 2hour and > 2 hours; split by number of different timezones involved)

Indicated the above as P0 and prioritized the other metrics as P1 and P2 depending on the initial challenge of gaining and engaging the users and next looking at retention of the users.