Week 9 at New Job, and here's what I'm thinking about:
Content determines how agents understand and refer to your products. But not all content is equivalent, or even under your control.
With a docs background, I've focused a lot in 2026 about how documentation shapes agent understanding of your product surfaces. (Including both web docs and Agent Skills.) But documentation isn't the only source of content about your products.
On first-party surfaces, you may have any of:
- Case studies, testimonials, etc.
- Product, industry, and vertical pages that describe how your product solves for specific needs
- Blog posts or other technical marketing content
- Documentation
But these surfaces are often written by different teams, who have different goals, which can affect agent understanding in various ways:
- Many of these pages are written through a different lens that may shape how agents see your product surfaces
- When content conflicts across these surfaces, agents may pick one representation of your product which may not be the canonical one, or may conflate information
- When there is a large volume of content that represents your product in a particular way, agents may "assume" that's the only, or at least primary, representation of your product, making other use cases less prominent or difficult for agents to discover
- These different surfaces often have different maintenance expectations, may contain version-specific information that doesn't disclose a version, or may be AI-generated and contain factual errors
If you're only paying attention to one surface - for example, docs - you're missing all of these other agent-facing representations of your product. And if that content represents your product differently, you have no way of knowing which representation of your product an agent will repeat to a human user or rely on during implementation.