Great Gathering Follow-Through

Barrier Buster Tracker: Themes → Sessions → Action

Ten Tiger Teams each own a barrier surfaced at the Great Gathering. This tracker maps the common root themes found across every session to the sessions where they showed up, and shows what work is underway to close each gap. Note: the Tiger Team meeting cadence was formally discontinued Jul 21 (low attendance / redundancy) — this tracker remains the historical record of what each team surfaced, and now also tracks related work happening independently across the company. Click a theme to filter, or click any row to see details and log a new update.

Cross-cutting flag (Jul 1): Lack of documentation — specs, SOPs, training material — is the single most common pain point across every Tiger Team. Update (Jul 21): leadership discussed the technical writer/trainer hire — landed on a rotation-based model (team-by-team, possibly a targeted contract role) rather than one dedicated hire, but paused for now since product specs aren't defined enough yet to staff against. See "Recently surfaced work" below for details.
Saved — shared with everyone

Showing all 10 sessions. Select a theme to see where it appears.

The 7 common root themes

Select a name or description to edit it.

No single source of truth

Information scattered across Slack, Notion, Confluence, and tribal knowledge with no centralized, searchable home.

Ownership / role clarity gap

"Who do I go to for this?" comes up repeatedly, especially on the R&D/engineering side.

Documentation debt

Missing specs, SOPs, and training material is the root cause behind most other barriers — escalated directly to leadership.

Product readiness / MVP vs. MLP ambiguity

Sales doesn't reliably know what's ready to sell; Product/Eng is actively closing the gap.

Desire for AI-assisted workflows

Multiple teams independently proposed Claude/Granola/Gemini to auto-capture and surface notes and docs.

Standardizing Jira/Confluence as the backbone

Templates that force structured data entry came up in at least three teams as a lightweight fix.

Low bandwidth / inconsistent attendance

Some kickoffs struggled with attendance, suggesting a few teams may need re-energizing or consolidation.