---
title: "Coffee Chat recording: Ask Me Anything about Managing API documentation projects"
date: 2024-01-08
description: "You can view the recording here: The topic was pretty open-ended. Here are a few of the..."
canonical_url: https://idratherbewriting.com/blog/ama-managing-api-documentation-projects
---

> For AI agents: a documentation index is available at https://idratherbewriting.com/llms.txt. Markdown versions of all pages are available by appending .md to any page URL.

# Coffee Chat recording: Ask Me Anything about Managing API documentation projects

> I recently participated in a Coffee and Content chat titled 'Ask Me Anything: Managing API Documentation Projects', with Patrick Bosek and Scott Abel, sponsored by Heretto. This was an 'Ask me anything' style chat, though the audience could only participate through chat on Brighttalk's platform. The coffee chat took place on Thursday, Jan 11, 2024.

You can [view the recording here](https://www.brighttalk.com/webcast/9273/593123):

[![Ask Me Anything: Managing API Documenation Projects](https://s3.us-west-1.wasabisys.com/idbwmedia.com/images/ama-managing-api-doc-projects.jpg)](https://www.brighttalk.com/webcast/9273/593123)

The topic was pretty open-ended. Here are a few of the topics that came up:

- The tech writer is pulled in too late into the release cycle.
- Bug reports lack detail to be actionable.
- Engineers are confused about the tech writer role.
- Tech writers prioritize projects based on whoever is shouting the loudest for docs.
- Engineers are slow to review docs, dragging out timelines.
- Attention focuses only on documenting the latest features, not maintaining existing content.
- The tech writer discovers confusing API behavior too late to influence the product design.
- No time to test pre-release products—setup too hard.
- Dividing tasks among multiple writers for the same project is too difficult.
- Complex release cycles and processes are opaque.

For more information, see all the links in my [Processes and methodology section](https://idratherbewriting.com/learnapidoc/docapis_managing_doc_processes.html) in my API course:

- [Following agile scrum with documentation projects](https://idratherbewriting.com/learnapidoc/pubapis_agile_scrum_for_docs.html)
- [Managing large documentation projects](https://idratherbewriting.com/learnapidoc/docapis_managing_doc_projects.html)
- [Managing small documentation requests](https://idratherbewriting.com/learnapidoc/docapis_managing_small_doc_requests.html)
- [Managing SDK releases](https://idratherbewriting.com/learnapidoc/docapis_managing_sdk_releases.html)
- [Documentation kickoff meetings and product demos](https://idratherbewriting.com/learnapidoc/docapis_kickoff_meeting_agenda.html)
- [Processes for reviewing documentation](https://idratherbewriting.com/learnapidoc/docapis_review_processes.html)
- [Maintaining existing documentation](https://idratherbewriting.com/learnapidoc/docapis_doc_maintenance_processes.html)
- [Collecting feedback post-release](https://idratherbewriting.com/learnapidoc/docapis_collecting_feedback_post_release.html)
- [Managing content from external contributors](https://idratherbewriting.com/learnapidoc/docapis_processes_for_external_contributors.html)
- [Changing internal doc culture](https://idratherbewriting.com/learnapidoc/docapis_changing_internal_doc_culture.html)
- [Sending doc status reports – a tool for visibility and relationship building](https://idratherbewriting.com/learnapidoc/docapis_status_reports.html)
- [Broadcasting your meeting notes to influence a wider audience](https://idratherbewriting.com/learnapidoc/docapis_meeting_notes.html)
- [Ensuring documentation coverage with each software release](https://idratherbewriting.com/learnapidoc/docapis_release_process.html)
- [DX content strategy with developer portals](https://idratherbewriting.com/learnapidoc/docapis_dx_content_strategy.html)