Back to library
AtlassianAtlassian

Community Audit + 30-60-90 Day Strategy Presentation

Growth & Marketing

What it tests

Structured thinking about community health, ability to diagnose problems from observable signals, and quality of prioritization in a resource-constrained environment

Format

  1. 1Candidate receives access to a real or simulated community — public Slack, Discourse forum, GitHub Discussions, or a curated dataset of community metrics — with 72 hours to complete the audit
  2. 2Candidate submits a written audit covering: current health signals (engagement rates, response times, content quality, lurker-to-contributor ratio), top 3 problems, and a 30-60-90 day plan to address them with specific OKRs
  3. 315-minute presentation to a panel (Community Lead, Head of Product, one community member if possible)
  4. 415-minute Q&A where interviewers stress-test prioritization choices: 'Why this over that?', 'What's the first thing you cut if headcount is half of what you planned?'

What to look for

  • Does the audit surface non-obvious problems — or just report what's visibly broken?
  • Is the 30-60-90 plan sequenced logically: listening/discovery first, then pilots, then scaled programs — or do they jump straight to big launches?
  • Do their OKRs measure community outcomes (member activation, repeat contributions, peer-to-peer answers) or just output metrics (posts per week, events hosted)?
  • In Q&A, when forced to cut half the plan, do they have a clear prioritization framework or do they panic?

Adaptation guide

For early-stage companies without an existing community, give candidates a competitor's public community to audit instead. For senior roles, require the plan to include a business case — how does community ROI connect to pipeline, retention, or product feedback loops?

Full description

Format:

  1. Candidate receives access to a real or simulated community platform with 72 hours to complete the audit
  2. Written deliverable: health signal analysis, top 3 prioritized problems, and a 30-60-90 day plan with specific OKRs
  3. 15-minute presentation to a panel including Community Lead, Head of Product, and ideally a community member
  4. 15-minute Q&A stress-testing prioritization: "Why this over that?" and "What gets cut if you have half the headcount?"

Time: 72 hours (take-home) + 30 minutes (presentation + Q&A)

What to look for:

  • Does the audit surface non-obvious problems or just repeat what's visibly broken?
  • Is the plan sequenced correctly: discover → pilot → scale?
  • Do OKRs measure community outcomes or just output volume?
  • Under pressure to cut scope, do they have a principled framework or do they stall?

Adaptation: Use a competitor's public community for companies without an existing one. For senior hires, require a business case connecting community ROI to pipeline, retention, or product feedback loops.