What signal do you check first after shipping an AI feature?
Monday question: how do you know an AI feature is actually working? A lot of us have shipped something AI-powered this year: a copilot, a summarizer, an agent that drafts or triages. Launch day is the easy part. The harder part is the first week or two, when you have to decide whether it's earning its place in the product. So I'm curious: what's the one signal you check first after shipping an AI feature? A few examples of what people look at:
Repeat usage (do people come back to it on day 2 and day 7?)
Edit or override rate (how often users change or reject the output)
Support tickets or complaints that mention it
Cost per use versus what the feature is worth to the customer
If you've had a feature that looked great in demos but flopped in real usage, what was the signal that told you? Reply in the thread, short answers welcome.