Documentation Strategy
-
How to Choose a CCMS Based on Your Documentation Needs
Read more >: How to Choose a CCMS Based on Your Documentation NeedsThere is no universally “best” CCMS. Different documentation platforms are designed around different assumptions about structure, governance, collaboration, publishing, maintenance, and scale. A system that works well for support-oriented knowledge sharing may become painful for complex product documentation over time, while a heavily structured platform may create unnecessary overhead for smaller or simpler documentation environments.…
-
How AI Is Changing SaaS — and Why Documentation Has to Change With It
Read more >: How AI Is Changing SaaS — and Why Documentation Has to Change With ItThere is a growing narrative that AI will replace SaaS. The argument usually goes something like this: if software can perform work autonomously, then we no longer need software tools. Instead of Software-as-a-Service, we’ll move toward "Service-as-Software" systems that simply deliver outcomes. This framing seems compelling, but it misunderstands what SaaS actually is.
-
Mapping the Knowledge System
Read more >: Mapping the Knowledge SystemThe diagram I’ve been building toward (the foundation of a new series launching on The Doc Landscape called The Living Knowledge System) maps the system that product knowledge actually moves through in a software company. Not all knowledge in a company. Not HR onboarding or sales enablement or anything else. Specifically the knowledge that’s born…
-
How Technical Writers Can Think Like Documentation Engineers
Read more >: How Technical Writers Can Think Like Documentation EngineersIf documentation is now part of a living knowledge system, then the role responsible for it has to evolve as well. The shift happening in documentation work isn’t just about new tools or faster workflows. It reflects a deeper change in how documentation is understood.
-
Documentation Has Entered a New Era
Read more >: Documentation Has Entered a New EraFor a long time, documentation followed software. Products were designed, built, and shipped. Then documentation came afterward. Today, software is designed and built while documentation is created in parallel, and both ship together. Documentation is no longer cleanup work. It’s part of delivery.