Company wide insights at the org/account level

[ackernaut]

In our design sprint we learned that it may be helpful to have distinct use cases for insights (in order to gauge team health and trends, in order to work together better) and account management (managing seats, membership, integrations, SSO/SMAL, etc.).

Open questions

• What are useful insights at the company level? At the team level (see Team management and insights available to admins #5671 )? Can we define crisp user job stories based on feedback from customers?
• Where can we start? Can we start by building out components of the enterprise usage report (like retro trends, most active users, graphs on usage and adoption, etc.), scoped to a single account, and sticking it in a new IA (see Admin IA and navigation designed #5669)?
• I think we show this at the account level. Is there a safe way to aggregate this across multiple accounts for a top-level domain? Do we build that in a separate section or continue to use the manual report? (see Domain stats tease and CTA #5666)

Possible user job stories

As a leader in the company over many teams, I want to see how my teams are holding meetings (frequency, what types, etc.) so I can gauge healthy team cadence (see this Loom at ~22:13)
As a leader in the company I want to see trends across meeting (e.g. retro topics) so that I can better analyze my company’s culture along other data points (like what we may be hearing in AMAs, town halls, 1:1s, etc.)
As an admin I want to see what features (all 3 meeting types?) are being used by teams so that I can know where they are getting value and look into why they are using certain features (how is it helping the team)
As an admin I want to see who the most active users are so that I can track adoption and know who to talk to about the value they’re deriving

• Administrative IA feedback, concerns, and open questions #5661 (comment)
• Administrative IA feedback, concerns, and open questions #5661 (comment)

Ideas

• We take the retro topics section from the enterprise usage report and stick it under an Insights nav item for a single account/organization. We show other usage graphs. They can drill down by team and maybe navigate to a team view (see Team management and insights available to admins #5671