Clearer docs, sharper systems.
Knowledgebase Ninjas examines the craft behind useful software documentation through conversations with people working in documentation. Episodes focus on clarity, content structure, user research, analytics, AI, and the practical judgment needed to turn messy product knowledge into dependable guidance.
PRESS PLAY
Knowledgebase Ninjas is a compact, practitioner-led interview show about the discipline behind effective SaaS documentation. It treats documentation as infrastructure for understanding. Across the featured episodes, the conversations keep returning to one central idea: clear content depends on knowing the user, the product, and the system that will deliver the information. The show is practical from the start. Guests talk about making enterprise documentation more down to earth, replacing stiff formality with approachable structure and audience awareness. They also look closely at measurement. Page traffic, search queries, bounce rates, surveys, user feedback, and support conversations all appear as signals, but the show is careful about what those signals can and cannot prove. Numbers need context. AI has become one of the show's most active threads. Episodes discuss AI-ready content, token-oriented writing, metadata, granularity, knowledge graphs, chatbots, and the need to keep human review in the loop. The tone is curious but cautious. Automation is presented as useful, not magical. Several guests stress that technical writing is not only writing; it includes research, testing, interviewing, coordinating with developers, joining meetings, and finding the small piece of truth that survives review. That gives the show a useful honesty. It does not romanticize the work. It shows the profession as a mix of communication, product knowledge, structure, and patience. The interviews also cover how documentation changes for different audiences, from novice users who need definitions and FAQs to developers who expect precision and code samples. Review cycles matter too, especially when content can grow stale in fast-moving technical environments. Knowledgebase Ninjas is strongest when it stays close to the operational details: how writers gather information, simplify complex concepts, measure usefulness, prepare content for AI, and keep documentation maintainable. It is a focused listen for people who already know that good docs are never accidental.
Made for: Knowledgebase Ninjas is for technical writers, documentation teams, SaaS product teams, and support-minded operators who want practical thinking about knowledge bases. It also suits developers and product teams who need documentation to work for both users and AI systems.
What sets it apart: The show stands out by treating documentation as a measurable, structured practice rather than a writing afterthought. Its conversations connect human usability, analytics, content structure, and AI readiness in concrete workplace terms.
Gowri Ramkumar of Document360 finds and interviews the brightest minds in the SaaS documentation space.
A highly 'engaging' help page might be confusing its readers; Gowri Ramkumar gets you asking why.
Press play if you want
Short reviews from the PlayNext desk, based on the episodes we processed.
A grounded case for pairing documentation analytics with user feedback before drawing conclusions.
Documentation measurement becomes more useful when the dashboard stops acting like the full story. In this Knowledge Base Ninjas episode, Sadhana Suresh, a Staff Systems Manager and Software Technical Writer at INS, explains how Google Analytics and GitBook can surface search…
Technical writing lands as coordination, testing, and communication before it becomes prose.
Technical writing comes through here as a practical discipline before it becomes prose. Strahinja Milosevic, Senior Technical Writer at Bitwavo, frames documentation as mapping a user's journey, understanding the goal behind it, and choosing the tools that make instructions…
AI accuracy starts with structured content, clear business goals, and human review that keeps cleanup from creating new errors.
Knowledge Base Ninjas treats AI chatbot accuracy as a content-structure challenge, not just a technical fix. Rahel Ann Bailey, Senior Content Consultant at Content Seriously, explains why unstructured material can still function inside a content delivery platform while leaving…
A practical case for user-focused documentation built on proximity, preparation, and sustained listening.
Strong documentation begins before a writer faces the page. This episode makes that case through a grounded practice of staying close to the work: joining meetings, listening in daily scrums, trying the application, and talking with the people around a project.
Documentation, AI agents and the future of tech writing.
Specialists walking through software's tradeoffs, one system at a time.
Founders and engineers on AI coding agents like Claude Code, and supply chain security.
A discussion on making technical documentation more accessible and human, with insights on the impact of AI on the field.
Sadhana Suresh, Staff Systems Manager and Software Technical Writer at INS, explains how documentation teams can measure whether users complete product tasks without relying on customer support.
Strahinja Milošević, Senior Technical Writer at Bitvavo, describes a 10-plus-year path from English studies and translation into technical writing.
Oana Turnea discusses the importance of keeping documentation simple, scalable, and audience-focused, while leveraging AI and human expertise.
Rahel Ann Bailey, Senior Content Consultant at Content Seriously, tells Gowri Ramkumar of Document360 that AI adoption is often pushed top-down by the C-suite before teams know the use case.
Sakshi Shah compares AI-ready documentation to labeled clothes, recipes, and numbered steps that reduce guesswork.
Lynne Thompson describes technical writing through examples from AT&T, Western Electric, and Verizon, including documentation for a data-scientist application.
Netra Pawar calls “false confidence” the biggest risk when AI evaluates documentation built from imperfect source content.
Jenna Ingersoll says technical writing management extends beyond clear prose to developing writers and setting documentation strategy.
Jason Christie, Shopify’s senior technical writer lead, says AI can expand writers’ capacity but cannot reliably produce accurate, production-ready documentation.
Dennis Dawson discusses how visuals in technical documentation help break up text and improve comprehension.
Syed Haroon Shah discusses best practices for writing user manuals, emphasizing procedures and visuals, and shares his journey from petroleum geoscience to technical writing.
Technical writer Rene Santana discusses how GenAI helps brainstorm ideas and understand product requirements, even if the generated content isn't used directly.
Iga Koprowska discusses how Akamai uses user feedback mechanisms like upvoting, comments, and suggested edits to improve documentation.
David Ingram discusses best practices and challenges in migrating documentation, emphasizing the use of analytics to improve content.