So I was a guest at a meetup last week. One of the participants used an AI notes and summary tool.
The thing that struck me when looking at the summary afterwards is that what got talked about most was actually the least important part of the conversation, but the tool had no way of knowing that.
The thing that struck me when looking at the summary afterwards is that what got talked about most was actually the least important part of the conversation, but the tool had no way of knowing that.
Comments
The flow of learning is the point. There's nothing you can glean from a summary except a quick "oh that's smart!" and promptly forget.
Then people tell me, "We only use it for the first sort," as if not reviewing your own research is a good thing.
But the discomfort is a necessary signal toward finding your way to insight & clarity.
I think many practitioners (&/or bosses) assume the discomfort is bad, so avoiding it must be good.
I find *so* many teams that fail to make an impact with users typically end their synthesis with insightful gems like "want: easy to use" and "hates meetings."
what do you think of condens? a friend & colleague got us on that and we're still playing around with it to get insight from sales/CS calls.
And most of my work these days is helping teams create a practice based on fundamentals. Then they can adopt whatever.