Products Are Evaluated Twice Now - Follow Up Story
Product context to help buyers understand your product
What happened after writing a recent Product Management IRL article? These insights are for paid subscribers to Product Management IRL.
This week’s backstory is about who uses your product context:
What Prompted This Article?
I’ve been struggling with the idea of AI finding product documents before people find the product documents. What makes AI discover my product? How long after releasing a change does it take AI to find it?
AI hasn’t been around long enough for us to study AI discovery of products.
In the meantime, what should I do with my product to be discovered by AI and potential customers?
This led me to think about a customer’s journey from first being aware of the product to buying the product. How do I investigate a product that I might buy?
I usually start by asking questions of AI, and if the product still looks promising, then I’ll invest time in learning more about it. In other words, I evaluate the product twice:
For an interesting product, there is limited information available unless you buy the product or talk to a salesperson.
The second part of the article covers architecting product context for reuse and potential buyer use cases. I still have a lot to consider about developing product context that is easy to maintain and useful.
