On August 21, I gave a product demo presentation in the U.S. It turned out to be a great opportunity, because it helped me connect with an audience that could be genuinely interested in zylo-docs.
Digital Jungle SF is a very active local community in San Francisco. I reached out in advance to Alison, the organizer, and asked if they were looking for free speakers. She said yes, so I joined the event. I prepared a 15-minute talk and took about 5 minutes of Q&A.
The most striking moment came when someone asked, “Do you have a product roadmap for technical writers?” At that time, our service was positioned mainly as helping server engineers use AI to write documentation. Engineers often asked, “Why use this if we already have Swagger?” But technical writers were far more curious about how AI could actually fill in the gaps, and they showed much deeper interest.
After this experience, I met Mel—introduced by Bill—once I returned to Korea. Mel is a veteran technical writer with over 40 years of experience. We had more in-depth conversations, and we both agreed that most organizations don’t actually have technical writers. Documentation usually gets created only after a product already exists. Companies hire technical writers only when organizing their docs becomes a pressing need, and in some cases—especially for physical products—they outsource manuals to specialized agencies.
Back in Korea, I also interviewed 12 technical writers from around the world. That’s when I realized just how diverse and complex their work is. They talked about the challenge of maintaining glossaries, keeping documents aligned with QA feedback, and constantly going back and forth with engineers. Some said they occasionally write marketing-style articles to support product launches. Others explained that they work only on internal documentation, while some focus on highly polished external docs for customers. I also learned that the influence of documentation inside a company depends heavily on leadership. When a CTO prioritizes it, technical writers gain leverage, but when they don’t, documentation is often undervalued despite its importance.
Another thing I discovered is that technical writers always keep their audience in mind. Their top priority is creating content that helps users learn a product quickly and clearly. Many would love to add interactive elements to accelerate understanding, but resource constraints make it difficult to try. Even AWS and Google Cloud documentation is still largely text-based for the same reason.
This is exactly the challenge we want to solve. At Zylo-Docs, we’re working to make this process easier by using AI to support SDK guide documentation—helping technical writers enrich their docs without overwhelming their resources. If your company is interested in this vision, we’d love to hear from you.