How do you document your product to ensure internal teams have what they need — and how do they actually access it (especially in the age of AI)?
Hi all! We're currently re-evaluating how we document product information to better support internal stakeholders (Sales, CS, Marketing, Enablement, etc.). I’m curious: - What does your “source of truth” look like? - How do you structure it (by feature, persona, use case, release, etc.)? - How do you ensure it’s actually usable and up to date? - Ownership between PM + PMM? - How do internal teams access information day-to-day? - Are you leveraging AI (e.g., internal GPT trained on docs) to help surface answers? - What’s working — and what’s broken? Context: I’m trying to balance comprehensive documentation with real-world usability, especially as AI search becomes more common internally. Would love to see examples, templates, or systems that have worked well for you.
Atlassian Head of Product Marketing, Platform Experiences & Agents • Tue
Yeah these are all great questions, here's how my team approaches it at Atlassian: 1. What does our "source of truth" look like? We maintain an approved BOM (bill of materials) and Content Library in Confluence for each product area that link out to all the approved resources. BOMs include: Message house, personas, use cases, competitive positioning and battlecards, product tour landing pages, demos, pitch decks, FAQs, customer proof, approved stats, analyst reports Content Library: Thought le ...Read More